Anybody else who cant login? - Retail Forum Archives

Woodsman Oct 4, 2006, 12:23 AM #1

Hmmm, server status says all servers are up. Account still active.

Yet I cannot log on. No message, no nothing.
Anybody else got the same problem?

traxz Oct 4, 2006, 12:51 AM #2

Got the same problem :/ and I dont use any firewalls etc, anyone know how to fix it?

EvilBunny Oct 4, 2006, 2:00 AM #3

same here.. seems like its a router issue.. where u from, coz some ppl can login and other cant..

im from austria / vienna
get the netinfotool_allOS_USEU.exe from the PlayNC.com site and send them your textfile afterwards
i have a timeout on the loginserver :(

Woodsman Oct 4, 2006, 2:02 AM #4

Nope, flushed dns and all but still no go. I know that not a thing changed on my computer and yesterday I had no problem whatsoever to enter it.

Next logical place to look for an error are the servers of NCSoft, hence my question here. If that aint it, then it could be my provider.

I am from Europe btw.

Woodsman Oct 4, 2006, 2:43 AM #5

Well after a reset and a few hours since I noticed this problem. Still no luck.

:(

traxz Oct 4, 2006, 2:44 AM #6

I think that the problem lies on their servers because yesterday I could play just fine. I also live in europe (Sweden and there's no problem when I conect to WoW)

AquaSpark Oct 4, 2006, 2:47 AM #7

I can't either :(

I live in Japan. 2 hours ago I could log in. Then after trying to relog in 30 minutes later I couldn't... :confused:

traxz Oct 4, 2006, 2:50 AM #8

I might add that i got this from using the netinfotool

Beginning: Updaters & Login Port Tests.

Check: l2update.lineage2.com (216.107.250.194) --> successful
Check: l2update.lineage2.com (216.107.250.198) --> successful
Check: l2update.lineage2.com (216.107.250.196) --> successful
Check: l2update.lineage2.com (216.107.250.195) --> successful
Check: l2update.lineage2.com (216.107.250.197) --> successful
Check: l2update.lineage2.com (216.107.250.199) --> successful
Check: Login Server Check (l2authd.lineage2.com) --> problem connecting to "l2authd.lineage2.com", port 2106: Unknown error

MalineII Oct 4, 2006, 3:32 AM #9

Do a tracert (hit start and type command or cmd, then type tracert at the prompt) to lineage2.com or l2authd.lineage2.com. You'll get a list - and it will at some point likely break off and start consisting of stars. That's where the problem is. ;)

Many German players have had problems with their provider(s) not routing over to NCSoft right recently. If you can read German, you can read more about it on Schmuse's site's forums.

AquaSpark Oct 4, 2006, 3:39 AM #10

Check: Login Server Check (l2authd.lineage2.com) --> problem connecting to "l2authd.lineage2.com", port 2106: Unknown error

I get the same error. Anyone have any idea how to fix this? Why would it happen suddenly to all of us???

MalineII Oct 4, 2006, 3:46 AM #11

I log in fine - I'd assume it's somewhere en route, not at their end.

AquaSpark Oct 4, 2006, 3:46 AM #12

Woot its works now - if NcSoft fixed something ty :)

Woodsman Oct 4, 2006, 3:47 AM #13

Well my tracert stops at a certain place indeed. How can I find out where that is when I use that IP number?

MalineII Oct 4, 2006, 3:48 AM #14

Check the domain and google it and/or call your ISP about it if they have good service.

Woodsman Oct 4, 2006, 4:00 AM #15

Well, my provider connects to another system and it is somewhere on that line where it gets stuck (step 8). According to Arin this is an organisation called RIPE.

So I guess it is not my provider either.

TarnVeda Oct 4, 2006, 7:06 AM #16

I stopped being able to log in last night, and cannot again this morning.:confused: Connection to update server works fine, but logon goes nowhere. I am in Canada, so this is obviously not a regional issue.

Mistryl Oct 4, 2006, 9:28 AM #17

The servers are not currently experiencing any issues that I'm aware of. Please contact Technical Support (http://support.lineage2.com) to find the cause of the problem if you're still unable to log in.

Thank you!

Woodsman Oct 4, 2006, 12:12 PM #18

Well it seems to work now. However the tracert command still gets stuck at the same place everytime I try.

SithMaster Oct 4, 2006, 1:03 PM #19

Well it seems to work now. However the tracert command still gets stuck at the same place everytime I try.

Requires valid ping returns...which are not always enabled by servers or networks.

TarnVeda Oct 4, 2006, 7:51 PM #20

It appears that here on the West Coast, the problem resides somewhere in the routers in or after Seattle:

############### Beginning: Updaters & Login Port Tests.

Check: l2update.lineage2.com (216.107.250.194) --> successful
Check: l2update.lineage2.com (216.107.250.198) --> successful
Check: l2update.lineage2.com (216.107.250.196) --> successful
Check: l2update.lineage2.com (216.107.250.195) --> successful
Check: l2update.lineage2.com (216.107.250.197) --> successful
Check: l2update.lineage2.com (216.107.250.199) --> successful
Check: Login Server Check (l2authd.lineage2.com) --> successful

############### Ended: Port Tests

Tracing route to l2authd.lineage2.com [216.107.242.195]
over a maximum of 30 hops:

0 workstation.domain.com [xxx.xxx.xxx.xxx]
1 xxx.xxx.xxx.xxx
2 xxx.xxx.xxx.xxx
3 rd1so-ge3-0-0-9.cg.shawcable.net [64.59.142.162]
4 rc1so-ge6-0.cg.shawcable.net [66.163.71.129]
5 rc1wh-pos12-0.vc.shawcable.net [66.163.76.10]
6 rc1wt-pos1-0-0.wa.shawcable.net [66.163.76.2]
7 ge3-0.cr02.sea01.pccwbtn.net [198.32.180.13]
8 * * *

elvenaura Oct 4, 2006, 8:59 PM #21

there were mass bot bannings yesterday...so who knows eh

TarnVeda Oct 4, 2006, 10:24 PM #22

I'm glad they're doing something about the bots, slim though it is. I am not a bot, but perhaps they also want to kick bot killers? After all, I doubt we rake in as much cash as the bot and farmers do.

XenoGear Oct 5, 2006, 12:44 AM #23

there were mass bot bannings yesterday...so who knows eh

Nice thread hijack.