Massive Posted February 11, 2012 Share Posted February 11, 2012 So I went to play on your 24/7 Office Deathmatch server and look! It made me cry.. I was losing packets everywhere. Warping to previous spots I was in. So i took some actions to try to resolve.. -Hard reset Router and Modem -Reset to Factory Router and Modem -Reinstalled Wireless drivers for laptop -contacted Mediacom --- They advised that the problem lies outside of their network and that that signals and MTU are all at great levels. So, basically, sorry sir, nothing we can do. Just wanted to share. This sucks. Tracert Panel: C:\Users\Jerry Lilly>tracert 67.228.245.2 Tracing route to 67.228.245.2-static.reverse.softlayer.com [67.228.245.2] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.1.1 2 8 ms 8 ms 7 ms 10.24.21.1 3 9 ms 8 ms 9 ms 172.30.0.105 4 10 ms 8 ms 13 ms 172.30.1.149 5 8 ms 12 ms 9 ms 12.249.52.13 6 18 ms 18 ms 19 ms cr81.desia.ip.att.net [12.122.153.50] 7 22 ms 22 ms 19 ms cr2.cgcil.ip.att.net [12.122.153.41] 8 19 ms 17 ms 18 ms cgcil03jt.ip.att.net [12.122.84.93] 9 40 ms 43 ms 40 ms chp-brdr-03.inet.qwest.net [63.146.26.217] 10 * * * Request timed out. 11 84 ms 40 ms 41 ms xe-1-0-0.bbr01.eq01.chi01.networklayer.com [65.1 13.255.94] 12 33 ms 60 ms 32 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192. 18.136] 13 32 ms 32 ms 33 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.1 8.253] 14 33 ms 33 ms * po2.fcr04.sr05.dal01.networklayer.com [66.228.11 8.218] 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. Trace complete. C:\Users\Jerry Lilly> Quote Link to comment Share on other sites More sharing options...
Scott Posted February 11, 2012 Share Posted February 11, 2012 bort or enigma can fix this Quote Link to comment Share on other sites More sharing options...
enigma# Posted February 14, 2012 Share Posted February 14, 2012 hmm sounds like the backbone might be a bit loosy goosy D= Are you able to connect to D2Dm and play fine there? Quote Link to comment Share on other sites More sharing options...
Darkwing Duck Posted February 14, 2012 Share Posted February 14, 2012 Enigma, thats actually been a problem for a long time, although the last time I brought it up to someone I was told its simply because our server boxes aren't top of the line. Quote Link to comment Share on other sites More sharing options...
enigma# Posted February 14, 2012 Share Posted February 14, 2012 Seems like even trying to ping the server, it's not active HLSW seems to work fine for it. When you play, enable net_graph 3 and get a video of it. I don't think demos work though. I'm curious to see what kind of packet loss/choke you get. Quote Link to comment Share on other sites More sharing options...
Massive Posted February 15, 2012 Author Share Posted February 15, 2012 Yeah, it is ridiculous. Choke is way high and packet loss is almost 65%. I don't think it would be CPU related but it seems more like router issues maybe? Although if you are guys have single core xeons and low memory channels with 50287283 servers, I could see that being a problem, even at idle. Quote Link to comment Share on other sites More sharing options...
enigma# Posted February 23, 2012 Share Posted February 23, 2012 Yeah, it is ridiculous. Choke is way high and packet loss is almost 65%. I don't think it would be CPU related but it seems more like router issues maybe? Although if you are guys have single core xeons and low memory channels with 50287283 servers, I could see that being a problem, even at idle. nope, however, I don't think memory or CPU usage would cause choke, it'd probably cause poor registration or slow game play (network loss at most). if you're having massive choke and loss, it's most likely either 1. A very crappy connection from your ISP to the SoftLayer backbone chances are your ISP is not going take the blame for this one and SoftLayer either. Can't really do anything until one of them does something. MTU means shit when it comes to these connections (most have at least 68 bytes/second, ethernet does 1500 Bps so, most ISPs will do less than 1500 Bps anyways). If signal levels are good, it perhaps may suggest the backbone connects poorly with your ISP. 2. Something on the backbone causing your connection to drop Have you tried optimising your Windows TCP/IP settings, esp if you're using XP? -------- Tracert is a useful tool to see where the connection fails, if you're able to make a connection try to use pathping instead. It's a wonderful diagnostic tool to see how the nodes react to your connection (attempts). Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.