L2server can't connect to Auth server

[dreba]

Hi everybody,

 

I try to start L2off interlude server ant the game server can't connect to Auth if in l2server.ini "AuthD = wan ip". If it's local ip (127.0.0.1) then everything is OK. First I thought it was firewall, but the same thing happens if it's off. 7777 and 2106 ports are opened in my router. Any suggestions ?

 

[minideed]

Do you have you WAN IP and Local IP set in the "l2db.dbo.server" in MSSQL correctly?

[mcbigmac]

  On 10/17/2011 at 7:24 PM, dreba said:

Hi everybody,

 

I try to start L2off interlude server ant the game server can't connect to Auth if in l2server.ini "AuthD = wan ip". If it's local ip (127.0.0.1) then everything is OK. First I thought it was firewall, but the same thing happens if it's off. 7777 and 2106 ports are opened in my router. Any suggestions ?

 

 

Your dbo.server has LAN IP set.

 

Set it your WAN ip.

 

 

If you want to connect locally on the same OS with a client, you need to do... something

Which i've forgotten at this moment.

 

doh.

[dreba]

  On 10/17/2011 at 9:40 PM, minideed said:

Do you have you WAN IP and Local IP set in the "l2db.dbo.server" in MSSQL correctly?

 

Here's the screenshot of my dbo.server

 

 

  Quote

Your dbo.server has LAN IP set.

 

Set it your WAN ip.

 

 

If you want to connect locally on the same OS with a client, you need to do... something

Which i've forgotten at this moment.

 

doh.

 

My wan ip is 195.12.182.133 and local is 192.168.2.40 I agree it looks similar

[minideed]

Would need to see your l2server.ini configuration.

 

It should not matter if you want to connect locally using your WAN IP or Local IP, but perhaps your local IP is being blocked. In the AuthD directory check the Black_IPs.txt file and see if there is a wildcard setting to block IP's.

[dreba]

  On 10/18/2011 at 12:17 PM, minideed said:

Would need to see your l2server.ini configuration.

 

It should not matter if you want to connect locally using your WAN IP or Local IP, but perhaps your local IP is being blocked. In the AuthD directory check the Black_IPs.txt file and see if there is a wildcard setting to block IP's.

 

My l2server.ini:

 

 

[CacheD]

address="127.0.0.1"

port=2006

 

[AuthD]

address="195.12.182.133"

port=2104

 

[LogD]

address="127.0.0.1"

port=3999

 

[World]

WorldId=1

UserLimit=1000

LetBuilder=1

 

[PetitionD]

address="127.0.0.1"

port=2107

WorldName="LineageIV"

;world name have to exact 9 characters.

DisableStart=5

DisableEnd=13

 

[Report]

Interval=600 ;minute

 

[setting]

UserPathFind=true

WorldCollision=false

ExceptionMailing = false

MailServer=false

ExceptionMinidump = false

IOBufferCount=30000

;check age (0:don't, 1:korean, default is 0)

AgeCheckType=0

AcceptEscapeCommand = true

country=4

; Korea=0, USA=1, Japan=2, Taiwan=3, China=4, Thailand=5

BOTLog = false

BOTBlock = false

gameguard=false

gameguard_checkonly=false

canrolldice=0

reconnectAuth=1

 

[fontCHECK]

fontcheck=0

; enable=1, disable=0

filename=smallfont.gly

 

[bBS]

WriteLevel=10

WorldNames="Lineage02"

 

[L2COMM]

Address="127.0.0.1"

Port=2010

Autoconnect=0

Usesvr=0

 

[bOT]

block=0

 

[NPCPOS]

extra_mob=off

 

 

I can't find the "Black_IPs.txt" file

[mcbigmac]

Misunderstood, it's not a user problem it's your daemons.

my bad.

 

IP represents the external ip, the socket will be transferred to when switching from AUTH to GS.

And the one socket will communicate with, from that poitn on.

This is in 99% of the cases the GS WAN IP(Unless your on some proxy routing scheme customly).

 

You need to change the inner ip to the LAN ip, if your L2Server/GS is connecting via LAN and not localhost.

 

If they're on the same Instance of a Windows Server, local should always work.

If you have several boxes on a LAN network, LAN ip must be configured as inner ip.

 

 

EDIT:

 

They're on the same box.

Why are you so... stupid... to not just set AUTHD in configs to 127.0.0.1/localhost?

 

You don't have a local network to worry about.

[dreba]

  On 10/18/2011 at 12:37 PM, mcbigmac said:

Misunderstood, it's not a user problem it's your daemons.

my bad.

 

IP represents the external ip, the socket will be transferred to when switching from AUTH to GS.

And the one socket will communicate with, from that poitn on.

This is in 99% of the cases the GS WAN IP(Unless your on some proxy routing scheme customly).

 

You need to change the inner ip to the LAN ip, if your L2Server/GS is connecting via LAN and not localhost.

 

If they're on the same Instance of a Windows Server, local should always work.

If you have several boxes on a LAN network, LAN ip must be configured as inner ip.

 

 

EDIT:

 

They're on the same box.

Why are you so... stupid... to not just set AUTHD in configs to 127.0.0.1/localhost?

 

You don't have a local network to worry about.

 

Thank you for your post, now it's everything clear to me betveen auth and server. I'm not using "localhost" because second computer for auth is still not ready