Log in

View Full Version : Unable to log in after Character select


booya
12-28-2008, 03:33 PM
<p>whille recently playing today i was abruptly disconnected from the game.   atempting to logback in i could get to the char select screen, but atempting to log a char in(any char, issue affect all my chars)  always resulted in being looped back to character select after a few mins of loading screens.   prior to today i have never had issues, and no recent changes in software hardware or router/cable modem.  according to the tracert info it apears the server is dead or just not responding.  this is curently affecting Crushbone</p><p>connection info and tracert :</p><p>Windows IP Configuration   Host Name . . . . . . . . . . . . : Q-Vist3000   Primary Dns Suffix  . . . . . . . :    Node Type . . . . . . . . . . . . : Hybrid   IP Routing Enabled. . . . . . . . : No   WINS Proxy Enabled. . . . . . . . : No   DNS Suffix Search List. . . . . . : hsd1.or.comcast.net.Ethernet adapter Local Area Connection:   Connection-specific DNS Suffix  . : hsd1.or.comcast.net.   Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.0)   Physical Address. . . . . . . . . : 00-1D-7D-A5-22-B1   DHCP Enabled. . . . . . . . . . . : Yes   Autoconfiguration Enabled . . . . : Yes   Link-local IPv6 Address . . . . . : fe80::40a:3d24:3c2d:e58d%8(Preferred)    IPv4 Address. . . . . . . . . . . : 192.168.123.100(Preferred)    Subnet Mask . . . . . . . . . . . : 255.255.255.0   Lease Obtained. . . . . . . . . . : Sunday, December 28, 2008 10:03:33 AM   Lease Expires . . . . . . . . . . : Sunday, February 08, 2009 2:03:32 AM   Default Gateway . . . . . . . . . : 192.168.123.254   DHCP Server . . . . . . . . . . . : 192.168.123.254   DNS Servers . . . . . . . . . . . : 192.168.123.254   NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter Local Area Connection* 7:   Connection-specific DNS Suffix  . :    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface   Physical Address. . . . . . . . . : 02-00-54-55-4E-01   DHCP Enabled. . . . . . . . . . . : No   Autoconfiguration Enabled . . . . : Yes   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:c3:3942:3f57:849b(Preferred)    Link-local IPv6 Address . . . . . : fe80::c3:3942:3f57:849b%9(Preferred)    Default Gateway . . . . . . . . . : ::   NetBIOS over Tcpip. . . . . . . . : DisabledTunnel adapter Local Area Connection* 9:   Media State . . . . . . . . . . . : Media disconnected   Connection-specific DNS Suffix  . : hsd1.or.comcast.net.   Description . . . . . . . . . . . : isatap.hsd1.or.comcast.net.   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   Autoconfiguration Enabled . . . . : YesTracing route to ableq2-03-01.everquest2.com [199.108.202.97]over a maximum of 30 hops:  1     9 ms     7 ms     9 ms  73.90.148.1   2     8 ms     7 ms     7 ms  ge-5-21-ur04.beaverton.or.bverton.comcast.net [68.87.216.233]   3    11 ms    11 ms    11 ms  68.85.243.181   4    12 ms    16 ms    13 ms  te-0-4-0-4-cr01.seattle.wa.ibone.comcast.net [68.86.90.233]   5   143 ms   223 ms    52 ms  te-3-2.car1.Seattle1.Level3.net [4.79.104.105]   6    20 ms    17 ms    17 ms  ae-31-55.ebr1.Seattle1.Level3.net [4.68.105.158]   7    12 ms    13 ms    17 ms  ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]   8    47 ms    40 ms    49 ms  ae-2.ebr2.Denver1.Level3.net [4.69.132.54]   9    64 ms    67 ms    64 ms  ae-3.ebr1.Chicago2.Level3.net [4.69.132.62]  10    65 ms    80 ms    65 ms  ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]  11    92 ms    91 ms    93 ms  ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]  12     *        *        *     Request timed out. 13     *        *        *     Request timed out. 14     *        *        *     Request timed out. 15     *        *        *     Request timed out. 16     *        *        *     Request timed out. 17     *        *        *     Request timed out. 18     *        *        *     Request timed out. 19     *        *        *     Request timed out. 20     *        *        *     Request timed out. 21     *        *        *     Request timed out. 22     *        *        *     Request timed out. 23     *        *        *     Request timed out. 24     *        *        *     Request timed out. 25     *        *        *     Request timed out. 26     *        *        *     Request timed out. 27     *        *        *     Request timed out. 28     *        *        *     Request timed out. 29     *        *        *     Request timed out. 30     *        *        *     Request timed out.</p>

Wingrider01
12-28-2008, 05:55 PM
<p>Not the server that is dead, according to your posted tracert your data signal stops at hop 9 in washington, looks like Level 3 has problems again as normal, one of their border routers puked again</p>

TSR-DanielH
12-29-2008, 09:58 PM
<p><cite>Wingrider01 wrote:</cite></p><blockquote><p>Not the server that is dead, according to your posted tracert your data signal stops at hop 9 in washington, looks like Level 3 has problems again as normal, one of their border routers puked again</p></blockquote><p>/agreed</p><p>Thats definitely a routing issue.  You might want to contact your ISP but be prepared to hear them say that it's a known issue and they're working to correct it.</p>