New Netgear Dg1000 router - Unstable EQ2 connection [Archive]

View Full Version : New Netgear Dg1000 router - Unstable EQ2 connection

Kalthaza

09-21-2011, 11:02 AM

Hi, just started using the above mentioned router, wired connection to PC, and I am losing connection to the game.I have tried portforwarding all ports, but what is happening is I can log into the game no problem, but once loaded, it takes an age for even the welcome window to appear. I can move around, but cannot interact with anything. And if I'm in a guild hall, the welcome window won't appear at all, and after a few minutes, will just quit back to the char select screen.I'm assuming there is a time out issue with a server not being reachable. Any suggestions?Edit: Oh yes, I can see chat with no problem, but I cannot send anything.Edit 2: If I try to zone when I can finally interact with items, I am kicked back to char select.

TSR-JoshuaM

09-21-2011, 11:07 AM

Is it a router/modem combo? We've had many reported issues with these class of devices. I'll do some testing on my end as well with that router which I happen to have. I'll get any ongoing issues reported up but I may not be able to resolve this for you immediately.

Kalthaza

09-21-2011, 11:23 AM

Yeah ADSL+Router. What causes enormous pain with this router is the seemingly impossible-to-turn-off firewall (at least, on my firmware anyway - which is incidentally locked down by my UK ISP so I can't change it...)I'm convinced the firewall is blocking the game, even after trying using DMZ, so if you can somehow figure out what I can do, I will buy you a pint :p

Kalthaza

09-21-2011, 11:26 AM

I think this may shed some light....pathping to ab server....Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Home-PC [192.168.0.10] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1 0/ 100 = 0% | 2 34ms 0/ 100 = 0% 0/ 100 = 0% 217.47.186.58 0/ 100 = 0% | 3 --- 100/ 100 =100% 100/ 100 =100% 217.47.186.161 0/ 100 = 0% | 4 --- 100/ 100 =100% 100/ 100 =100% 213.1.67.74 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% 213.1.79.14 0/ 100 = 0% | 6 48ms 0/ 100 = 0% 0/ 100 = 0% 87.237.20.244 0/ 100 = 0% | 7 47ms 1/ 100 = 1% 1/ 100 = 1% bundle-ether1.lontr1.London.opentransit.net [193.251.255.101] 0/ 100 = 0% | 8 46ms 1/ 100 = 1% 1/ 100 = 1% level3-1.GW.opentransit.net [193.251.248.46] 0/ 100 = 0% | 9 48ms 0/ 100 = 0% 0/ 100 = 0% ae-52-52.csw2.London1.Level3.net [4.69.139.120] 0/ 100 = 0% | 10 46ms 0/ 100 = 0% 0/ 100 = 0% ae-57-222.ebr2.London1.Level3.net [4.69.153.133] 0/ 100 = 0% | 11 114ms 0/ 100 = 0% 0/ 100 = 0% ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70] 0/ 100 = 0% | 12 120ms 0/ 100 = 0% 0/ 100 = 0% ae-10-10.ebr2.Washington12.Level3.net [4.69.148.50] 0/ 100 = 0% | 13 123ms 0/ 100 = 0% 0/ 100 = 0% ae-1-100.ebr1.Washington12.Level3.net [4.69.143.213] 0/ 100 = 0% | 14 137ms 1/ 100 = 1% 1/ 100 = 1% ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105] 0/ 100 = 0% | 15 134ms 1/ 100 = 1% 1/ 100 = 1% ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241] 0/ 100 = 0% | 16 154ms 0/ 100 = 0% 0/ 100 = 0% ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21] 0/ 100 = 0% | 17 154ms 0/ 100 = 0% 0/ 100 = 0% ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145] 0/ 100 = 0% | 18 152ms 0/ 100 = 0% 0/ 100 = 0% ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138] 0/ 100 = 0% | 19 195ms 0/ 100 = 0% 0/ 100 = 0% ae-4-4.car2.SanDiego1.Level3.net [4.69.133.213] 0/ 100 = 0% | 20 180ms 0/ 100 = 0% 0/ 100 = 0% ge-1-1.hsa1.SanDiego1.Level3.net [4.69.134.86] 0/ 100 = 0% | 21 184ms 1/ 100 = 1% 1/ 100 = 1% vl861.sdtermswitch-1.sonyonline.net [63.215.251.130] 0/ 100 = 0% | 22 --- 100/ 100 =100% 100/ 100 =100% vl831.sdkollsw-1.sonyonline.net [64.37.144.82] 0/ 100 = 0% | 23 181ms 0/ 100 = 0% 0/ 100 = 0% sdkeq2-04-01.everquest2.com [199.108.12.129]

TSR-JoshuaM

09-21-2011, 11:31 AM

100% packet loss is more commonly an indicator that the router identified does not respond to pings. Problematic connections will usually float under 100%. We would have to do additional testing but I do think the issue lies in the router itself. Is there an alternative available?

Kalthaza

09-21-2011, 11:36 AM

Thankfully, my old one works just fine - I was just hoping there was something I could do with this new one as it was supplied with my new ISP.

TSR-JoshuaM

09-21-2011, 11:41 AM

<cite>Kalthaza@Antonia Bayle wrote:</cite><blockquote>Thankfully, my old one works just fine - I was just hoping there was something I could do with this new one as it was supplied with my new ISP.</blockquote>It's a functionality issue that we have very little ability to affect on our end. I won't be able to resolve this for your in a timely manner, if at all.

Kalthaza

09-21-2011, 11:46 AM

No problem... I'll just go back to the old router. First connection problem since beta <img src="/smilies/69934afc394145350659cd7add244ca9.gif" border="0" alt="SMILEY" />

TSR-JoshuaM

09-21-2011, 11:54 AM

Not bad at all! <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />