Can't connect to the login servers. [Archive]

Bli

08-08-2009, 06:06 AM

Hello,I simply can't connect to the login servers. I have installed the trial version of eq2 from this page <a href="http://everquest2.station.sony.com/de/freeTrial.vm" target="_blank" rel="nofollow">http://everquest2.station.sony.com/de/freeTrial.vm</a>Yesterday evening I started my connect tries, but I failed each time. This morning the same thing. I can't believe that the login servers are down more than 10 hours. I attached a traceroute to the three gameservers.Information to my Network:<ul><li>connected through VPN (that I can't bypass) to the Internet</li><li>no firewall running</li></ul>I don't have any connection issues in vanguard.-----------Attachment:Windows-IP-Konfiguration Hostname . . . . . . . . . . . . : blizxp Prim„res DNS-Suffix . . . . . . . : Knotentyp . . . . . . . . . . . . : Hybrid IP-Routing aktiviert . . . . . . : Nein WINS-Proxy aktiviert . . . . . . : Nein DNS-Suffixsuchliste . . . . . . . : ds.fh-kl.deEthernet-Adapter LAN-Verbindung* 17: Verbindungsspezifisches DNS-Suffix: ds.fh-kl.de Beschreibung. . . . . . . . . . . : Shrew Soft Virtual Adapter Physikalische Adresse . . . . . . : AA-AA-AA-AA-AA-00 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja Verbindungslokale IPv6-Adresse . : fe80::ed08:8429:5f87:f3bc%25(Bevorzugt) IPv4-Adresse . . . . . . . . . . : 10.26.64.20(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.0.0 Standardgateway . . . . . . . . . : 0.0.0.0 DNS-Server . . . . . . . . . . . : 10.0.3.201 10.0.3.204 NetBIOS ber TCP/IP . . . . . . . : DeaktiviertEthernet-Adapter LAN-Verbindung 3: Verbindungsspezifisches DNS-Suffix: ds.fh-kl.de Beschreibung. . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet Physikalische Adresse . . . . . . : 00-22-15-23-C9-41 DHCP aktiviert. . . . . . . . . . : Ja Autokonfiguration aktiviert . . . : Ja IPv4-Adresse . . . . . . . . . . : 172.17.4.16(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.255.0 Lease erhalten. . . . . . . . . . : Samstag, 8. August 2009 10:39:29 Lease l„uft ab. . . . . . . . . . : Sonntag, 9. August 2009 10:39:29 Standardgateway . . . . . . . . . : 172.17.4.254 DHCP-Server . . . . . . . . . . . : 10.0.3.201 DNS-Server . . . . . . . . . . . : 10.0.3.201 10.0.3.204 Prim„rer WINS-Server. . . . . . . : 172.17.4.58 NetBIOS ber TCP/IP . . . . . . . : DeaktiviertTunneladapter LAN-Verbindung*: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physikalische Adresse . . . . . . : 02-00-54-55-4E-01 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : JaTunneladapter LAN-Verbindung* 13: Medienstatus. . . . . . . . . . . : Medium getrennt Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : isatap.ds.fh-kl.de Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : JaRoutenverfolgung zu sdkeq2-01-01.everquest2.com [199.108.12.33] ber maximal 30 Abschnitte: 1 24 ms 1 ms <1 ms 172.17.0.1 2 14 ms 1 ms 1 ms 10.26.254.253 3 14 ms 1 ms 1 ms elrond.rz-zw.fh-kl.de [143.93.17.254] 4 14 ms 1 ms 1 ms irouter.rz-zw.fh-kl.de [143.93.16.2] 5 15 ms 1 ms 1 ms s-fh-kl-zweibruecken-1.rlp-net.net [217.198.243.33] 6 35 ms 4 ms 4 ms s-hbf-hom-1.rlp-net.net [217.198.240.201] 7 18 ms 6 ms 6 ms g-hbf-kl-1.rlp-net.net [217.198.240.197] 8 18 ms 4 ms 5 ms g-uni-ma-1.rlp-net.net [217.198.240.42] 9 18 ms 5 ms 4 ms g-decix-2.rlp-net.net [217.198.240.50] 10 17 ms 4 ms 4 ms xe-10-0-0-444.fra-006-score-1-re0.interoute.net [212.23.33.161] 11 24 ms 12 ms 11 ms ae1-0.ams-koo-score-2-re0.interoute.net [84.233.190.49] 12 43 ms 11 ms 11 ms ae0-0.ams-koo-score-1-re0.interoute.net [84.233.190.1] 13 25 ms 12 ms 12 ms 212.72.48.161 14 30 ms 12 ms 23 ms ae-33-51.ebr1.amsterdam1.level3.net [4.69.139.129] 15 36 ms 15 ms 19 ms ae-2-2.ebr2.dusseldorf1.level3.net [4.69.133.90] 16 29 ms 15 ms 17 ms ae-1-100.ebr1.dusseldorf1.level3.net [4.69.141.149] 17 32 ms 18 ms 18 ms ae-2-2.ebr2.frankfurt1.level3.net [4.69.132.138] 18 150 ms 118 ms 118 ms ae-43-43.ebr2.washington1.level3.net [4.69.137.58] 19 112 ms 109 ms 107 ms ae-72-72.csw2.washington1.level3.net [4.69.134.150] 20 115 ms 107 ms 108 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.133] 21 140 ms 115 ms 123 ms ae-2.ebr3.atlanta2.level3.net [4.69.132.85] 22 159 ms 150 ms 141 ms ae-7.ebr3.dallas1.level3.net [4.69.134.21] 23 175 ms 161 ms 161 ms ge-7-0-0-89.bbr1.Dallas1.Level3.net [4.68.19.129] 24 232 ms 213 ms 285 ms as-2-0.mp1.SanDiego1.Level3.net [64.159.1.137] 25 193 ms 193 ms 180 ms so-10-0.hsa1.SanDiego1.Level3.net [4.68.113.38] 26 195 ms 186 ms 180 ms vl861.sdtermswitch-1.sonyonline.net [63.215.251.130] 27 185 ms 180 ms 181 ms vl831.sdkollsw-1.sonyonline.net [64.37.144.82] 28 193 ms 181 ms 181 ms sdkeq2-01-01.everquest2.com [199.108.12.33] Ablaufverfolgung beendet.Routenverfolgung zu ableq2-01-01.everquest2.com [199.108.202.33] ber maximal 30 Abschnitte: 1 8 ms 1 ms <1 ms 172.17.0.1 2 14 ms 1 ms 1 ms 10.26.254.253 3 14 ms 1 ms 1 ms elrond.rz-zw.fh-kl.de [143.93.17.254] 4 14 ms 1 ms 1 ms irouter.rz-zw.fh-kl.de [143.93.16.2] 5 30 ms 1 ms 1 ms s-fh-kl-zweibruecken-1.rlp-net.net [217.198.243.33] 6 16 ms 3 ms 3 ms s-hbf-hom-1.rlp-net.net [217.198.240.201] 7 21 ms 6 ms 5 ms g-hbf-kl-1.rlp-net.net [217.198.240.197] 8 17 ms 5 ms 5 ms g-uni-ma-1.rlp-net.net [217.198.240.46] 9 17 ms 5 ms 6 ms g-decix-2.rlp-net.net [217.198.240.54] 10 19 ms 6 ms 5 ms tge5-3.fr3.frf.llnw.net [80.81.192.221] 11 34 ms 11 ms 11 ms tge10-1.fr3.ams.llnw.net [69.28.172.9] 12 109 ms 93 ms 94 ms tge5-1.fr4.lga.llnw.net [69.28.171.86] 13 112 ms 108 ms 99 ms tge2-3.fr4.iad.llnw.net [69.28.171.153] 14 112 ms 98 ms 98 ms sony.ge4-12.fr4.iad.llnw.net [69.28.156.214] 15 130 ms 100 ms 100 ms vl47.ashaens-2.sonyonline.net [64.37.144.181] 16 112 ms 100 ms 102 ms ableq2-01-01.everquest2.com [199.108.202.33] Ablaufverfolgung beendet.Routenverfolgung zu amseq2-01-01.everquest2.com [195.33.135.161] ber maximal 30 Abschnitte: 1 17 ms 1 ms <1 ms 172.17.0.1 2 14 ms 1 ms 1 ms 10.26.254.253 3 15 ms 1 ms 1 ms elrond.rz-zw.fh-kl.de [143.93.17.254] 4 14 ms 1 ms 1 ms irouter.rz-zw.fh-kl.de [143.93.16.2] 5 32 ms 1 ms 1 ms s-fh-kl-zweibruecken-1.rlp-net.net [217.198.243.33] 6 15 ms 2 ms 2 ms s-hbf-hom-1.rlp-net.net [217.198.240.201] 7 22 ms 7 ms 5 ms g-hbf-kl-1.rlp-net.net [217.198.240.197] 8 16 ms 5 ms 3 ms g-uni-ma-1.rlp-net.net [217.198.240.42] 9 18 ms 4 ms 4 ms g-decix-2.rlp-net.net [217.198.240.50] 10 18 ms 5 ms 4 ms xe-10-0-0-444.fra-006-score-1-re0.interoute.net [212.23.33.161] 11 25 ms 5 ms 5 ms dcix1nap.de.ip.att.net [80.81.192.199] 12 25 ms 12 ms 11 ms 32.119.116.2 13 27 ms 12 ms 12 ms vl50.amsixmsfc-1.sonyonline.net [195.33.129.76] 14 26 ms 12 ms 11 ms amseq2-01-01.everquest2.com [195.33.135.161] Ablaufverfolgung beendet.

TSR-DanielH

08-10-2009, 05:13 PM

Greetings,Are you getting a specific error message when you are unable to connect? Were you able to connect with the game before or is this your first time trying to access the game?Assuming you are using a firewall, please open the exception list for it and delete any entries that contain the words Everquest2, EQ2, or launchpad. Then launch the game again by right clicking on the program shortcut and selecting 'run as an administrator'. Make sure to select 'allow' when it asks you to allow or deny. If the problem is being caused by a firewall then that should correct it.Please keep in mind that the game was not designed to use a VPN and that could be causing errors by itself. The most common error that a VPN will cause is the 41780 message. Let me know if that's what you are receiving.

Bli

08-10-2009, 09:35 PM

I have never been able to connect to EQ2. It's my first time trying this game.I run the game right from the executable Everquest2.exe in the game directory as administrator. I enter my account data. Now the client tries to connect to the login servers "Connect to Server: 1..." When this message times out I get the following error message (translated) : "unable to connect to login server... servers seem to be busy... please try again later"Yesterday I have installed a Firewall for testing purposes. Right after I launch the game an UDP connection is being made. I allow this connection but always the same problem. I can't get no connection.This error also occur when I run the game from the station launcher.Let me know if I can send you additional information. I try to describe the problem as exactly as possible.Thanks for support!

Wingrider01

08-11-2009, 07:30 AM

suspect it is the vpn, was under the impression that the game could not run under a VPN connection.

Bli

08-11-2009, 08:12 AM

But every other game runs smoothly <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /> Don't think that EQ2 is the only game that uses the UDP protocol <img src="/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" alt="SMILEY" />I will ask our local network support if any required port is blocked.

TSR-DanielH

08-12-2009, 04:23 PM

<cite>Blizi wrote:</cite><blockquote>But every other game runs smoothly <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /> Don't think that EQ2 is the only game that uses the UDP protocol <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" />I will ask our local network support if any required port is blocked.</blockquote>You mention local network support but where are you trying to connect from? Is this a university or military base where the game connection might be blocked?

Bli

08-17-2009, 01:36 PM

Jeah I'm trying to connect via the university network. And they might be block the game connection so the next step would be asking <img src="/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" alt="SMILEY" />Maybe they can give me feedback on this issue.

TSR-DanielH

08-17-2009, 04:20 PM

<cite>Blizi wrote:</cite><blockquote>Jeah I'm trying to connect via the university network. And they might be block the game connection so the next step would be asking <img src="/eq2/images/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" />Maybe they can give me feedback on this issue.</blockquote>The most common issue on a university network would be blocked ports on the campus router. You'll probably need to contact the network admin to get those ports opened. If you present that person with the following information then they should be able to allow it through(assuming they want to):EverQuest II LaunchPad and Patch Servers A TCP connection is initiated from the LaunchPad client port > 1023 to patch.station.sony.com port 7000. A UDP connection is initiated from the LaunchPad client port > 1023 to sdlaunchpad1.station.sony.com and sdlaunchpad2.station.sony.com port range 3016-3021 and 9700-9703.EverQuest II Patch:A TCP connection is initiated from the EverQuest II client port > 1023 to patch.everquest2.com, abepatch.everquest2.com, laepatch.everquest2.com, or amspatch.everquest2.com at port 7010. Some of the above patchers resolve to multiple IP addresses, so if you have a strict outbound firewalling policy, be sure to check for all IP addresses using a DNS lookup tool.EverQuest II Game Client:UDP connections are initiated from the EverQuest II client port >1023 to servers on UDP ports 9100, and UDP ports in the range 32800-33000. Additionally, ICMP messages type 0 (echo reply), 3 (unreachable), 8 (echo request) and 11 (expired) should be permitted bi-directionally between the client PC and the EverQuest II servers.EverQuest II Servers Subnets:There are multiple IP addresses for the Patch and LaunchPad clusters, and they may change as the network demands, so check often using a DNS lookup tool if you provide a specific firewall rule for these services. The EverQuest II server IP addresses are currently in these subnets: 64.37.158.*, 199.108.11.*, 199.108.12.*, 199.108.13.*, 199.108.202.*, 199.108.203.*, 195.33.135.*