Login server issues/Packet loss [Archive] - EQ2 Forum Archive @ EQ2Wire

Xinl

10-10-2010, 03:57 PM

Hello. All my toons are currently on the Mistmoore server. Since about last Saturday, I have been having issues intermittantly with packet loss and subsequent zoning issues. Once the packetloss/lag begins and I zone I am booted to character select after a lengthy wait at "Logging into zone server". I have run virus scans, re checked firewall settings and even re installed windows 7 yet I still have the same problem...Ususally during raid time, go figure. I know that other people are having the same problem and I hope that someone with tech support will finally shed some light on the situation very soon. Below are my net stats for your perusal. Thank you.Tracing route to ableq2-05-01.everquest2.com [199.108.202.161]over a maximum of 30 hops: 1 3 ms 2 ms 3 ms 192.168.1.1 2 11 ms 10 ms 11 ms 69.138.148.1 3 15 ms 11 ms 11 ms ge-1-6-ur01.south.tn.knox.comcast.net [68.85.38.101] 4 10 ms 11 ms 10 ms te-3-3-ar01.bluelight.tn.knox.comcast.net [68.86.136.22] 5 78 ms 83 ms 99 ms xe-0-1-1-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.85.232.97] 6 38 ms 41 ms 37 ms pos-3-5-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.93.201] 7 37 ms 36 ms 46 ms te-3-3.car1.Atlanta2.Level3.net [4.71.252.1] 8 41 ms 51 ms 52 ms ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30] 9 66 ms 50 ms 73 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86] 10 76 ms 53 ms 53 ms ae-71-71.csw2.Washington1.Level3.net [4.69.134.134] 11 52 ms 55 ms 52 ms ge-9-0.ipcolo2.Washington1.Level3.net [4.68.121.44] 12 52 ms 50 ms 52 ms vl124.asheqnx-2.sonyonline.net [63.215.136.202] 13 65 ms 55 ms 80 ms vl47.ashaens-2.sonyonline.net [64.37.144.181] 14 53 ms 52 ms 54 ms ableq2-05-01.everquest2.com [199.108.202.161]Trace complete.C:UsersEvan>pathping mistmoore.everquest2.comTracing route to ableq2-05-01.everquest2.com [199.108.202.161]over a maximum of 30 hops: 0 PC [Edited Out] 1 192.168.1.1 2 69.138.148.1 3 ge-1-6-ur01.south.tn.knox.comcast.net [68.85.38.101] 4 te-3-3-ar01.bluelight.tn.knox.comcast.net [68.86.136.22] 5 xe-0-1-1-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.85.232.97] 6 pos-3-6-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.93.205] 7 te-3-3.car1.Atlanta2.Level3.net [4.71.252.1] 8 ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30] 9 ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86] 10 ae-71-71.csw2.Washington1.Level3.net [4.69.134.134] 11 ge-9-0.ipcolo2.Washington1.Level3.net [4.68.121.44] 12 vl124.asheqnx-2.sonyonline.net [63.215.136.202] 13 vl47.ashaens-2.sonyonline.net [64.37.144.181] 14 ableq2-05-01.everquest2.com [199.108.202.161] Source to Here This Node/LinkHop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 PC [Edited Out] 0/ 100 = 0% | 1 6ms 1/ 100 = 1% 1/ 100 = 1% 192.168.1.1 0/ 100 = 0% | 2 17ms 0/ 100 = 0% 0/ 100 = 0% 69.138.148.1 0/ 100 = 0% | 3 16ms 2/ 100 = 2% 2/ 100 = 2% ge-1-6-ur01.south.tn.knox.comcast.net [68.85.38.101] 0/ 100 = 0% | 4 17ms 2/ 100 = 2% 2/ 100 = 2% te-3-3-ar01.bluelight.tn.knox.comcast.net [68.86.136.22] 0/ 100 = 0% | 5 46ms 2/ 100 = 2% 2/ 100 = 2% xe-0-1-1-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.85.232.97] 0/ 100 = 0% | 6 42ms 11/ 100 = 11% 11/ 100 = 11% pos-3-6-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.93.205] 0/ 100 = 0% | 7 55ms 0/ 100 = 0% 0/ 100 = 0% te-3-3.car1.Atlanta2.Level3.net [4.71.252.1] 0/ 100 = 0% | 8 49ms 2/ 100 = 2% 2/ 100 = 2% ae-63-51.ebr3.Atlanta2.Level3.net[4.68.103.30] 0/ 100 = 0% | 9 56ms 1/ 100 = 1% 1/ 100 = 1% ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86] 0/ 100 = 0% | 10 62ms 0/ 100 = 0% 0/ 100 = 0% ae-71-71.csw2.Washington1.Level3.net [4.69.134.134] 0/ 100 = 0% | 11 56ms 0/ 100 = 0% 0/ 100 = 0% ge-9-0.ipcolo2.Washington1.Level3.net [4.68.121.44] 0/ 100 = 0% | 12 61ms 0/ 100 = 0% 0/ 100 = 0% vl124.asheqnx-2.sonyonline.net [63.215.136.202] 0/ 100 = 0% | 13 --- 100/ 100 =100% 100/ 100 =100% vl47.ashaens-2.sonyonline.net [64.37.144.181] 0/ 100 = 0% | 14 58ms 0/ 100 = 0% 0/ 100 = 0% ableq2-05-01.everquest2.com [199.108.202.161]Trace complete.

LA Smog

10-10-2010, 09:07 PM

While there are quite a few server issues at Sony's side right now, the packet loss you are showing is starting within your network which is probably just making the problems Sony is having with their equipment magnified for you.I don't know how much you know about networking, so please don't think I am talking down to you since I am making no assumptions for this. The first address shown, 192.168.1.1, is your router/bridge/whatever (E.G. your equipment): Source to Here This Node/LinkHop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 PC [Edited Out] 0/ 100 = 0% | You---> 1 6ms 1/ 100 = 1% 1/ 100 = 1% 192.168.1.1 0/ 100 = 0% | Your ISP assigned equipment --->2 17ms 0/ 100 = 0% 0/ 100 = 0% 69.138.148.1 0/ 100 = 0% | Your ISP's network---> 3 16ms 2/ 100 = 2% 2/ 100 = 2% ge-1-6-ur01.south.tn.knox.comcast.net [68.85.38.101] 0/ 100 = 0% |Ditto---> 4 17ms 2/ 100 = 2% 2/ 100 = 2% te-3-3-ar01.bluelight.tn.knox.comcast.net [68.86.136.22] 0/ 100 = 0% |Ditto---> 5 46ms 2/ 100 = 2% 2/ 100 = 2% xe-0-1-1-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.85.232.97] 0/ 100 = 0% |Ditto (Big loss spike)---> 6 42ms 11/ 100 = 11% 11/ 100 = 11% pos-3-6-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.93.205] 0/ 100 = 0% |Your ISP's backbone provider---> 7 55ms 0/ 100 = 0% 0/ 100 = 0% te-3-3.car1.Atlanta2.Level3.net [4.71.252.1] 0/ 100 = 0% |Your ISP's backbone provider---> 8 49ms 2/ 100 = 2% 2/ 100 = 2% ae-63-51.ebr3.Atlanta2.Level3.net[4.68.103.30] 0/ 100 = 0% |Your ISP's backbone provider---> 9 56ms 1/ 100 = 1% 1/ 100 = 1% ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86] 0/ 100 = 0% |Your ISP's backbone provider---> 10 62ms 0/ 100 = 0% 0/ 100 = 0% ae-71-71.csw2.Washington1.Level3.net [4.69.134.134] 0/ 100 = 0% |Your ISP's backbone provider---> 11 56ms 0/ 100 = 0% 0/ 100 = 0% ge-9-0.ipcolo2.Washington1.Level3.net [4.68.121.44] 0/ 100 = 0% |Sony starts here---> 12 61ms 0/ 100 = 0% 0/ 100 = 0% vl124.asheqnx-2.sonyonline.net [63.215.136.202] 0/ 100 = 0% |Full loss here for a brief time, then cleared on next hop---> 13 --- 100/ 100 =100% 100/ 100 =100% vl47.ashaens-2.sonyonline.net [64.37.144.181] 0/ 100 = 0% |Next hop showing no loss again---> 14 58ms 0/ 100 = 0% 0/ 100 = 0% ableq2-05-01.everquest2.com [199.108.202.161]The problem when you have packet loss on both sides (worse on Sony's side) is that it is multiplicative. They just make each other worse.Hopefully Sony will get their act together soon. It looks like the Extended version may be hammering their network as the accounts climb.