| Author |
Having Router Issues Look No Further! |
Slippi Toad
1st Rear Admiral
Joined: May 07, 2009
Posts: 12
|  Posted: 2009-06-06 21:14
just signed into sagitt ... spawed under a mandible... couldn't select it.., tried to jump away.. d/c ---->> ALT F4 ALT F4 ALT F4 ALT F4 .. hope i didn't die again 
_________________
|
Eledore Massis [R33]
Grand Admiral
Templar Knights
Joined: May 26, 2002
Posts: 2694
From: tsohlacoLocalhost
| Posted: 2009-06-07 13:47
Quote:
|
On 2009-06-06 20:17, JaMeRiRa wrote:
C:tracert titan.palestar.com
.... ^see previous page^
.....
BTW i downloaded a prog which checks if your ports are open (from portforward.com) and all ports in the range are closed or not reachable.. mm |
|
Most likely because your router/modem has its firewall and or NAT active. (if you say you have strict NAT than thats probaly the reason)
the program from portforward checks if the ports between there server and the program your running are accessible.
But most likely there server will be the one poking your ports, the router/modem will just ignore the port call since it has no rules for it and from the internal network no computer has made a request on that port.
Hench the program telling there not reachable.
Ok thats the technical stuff..
Data allowance (aka Bandwidth cap) the worst thing i find of when picking a provider, but ok i agree, there is a financial factor to it..
Still if you got ADSL2 speeds thats more than enough, don't bother going cable if the offer less Cap.
Still that made me wonder, with your ADSL provide what do they do when you reach that cap? warn you or limit your speed..
anyhow, hope you didn't lost that mandi.
_________________
DS Discordion
|
jedi42
Grand Admiral
Evil Empires Inc.
Joined: February 25, 2002
Posts: 478
From: jedi42
| Posted: 2009-06-10 02:40
Agree with the above, but:
10 * 38 ms 38 ms i-14-1-0.sydp-core01.bi.reach.com
11 187 ms 186 ms * i-10-2-0.wil-core03.bx.reach.com
12 186 ms 186 ms 187 ms i-2-2.tlot03.bi.reach.com
~30% packet drop to x.x.x.reach.com is not really acceptable.
I suggest pinging the the core01 and core 3 bi/bx reach.com addresses repeatedly and posting the results.
If you have considerable packet loss and wildly varying pings, I doubt it has to do with a port issue (afa connectivity to DS is concerned).
From reach.com:
"APCN2 (Asia Pacific Network 2)
APCN2 provides seamless interconnection to Australia and Europe via SMW3 and AJC and across the Pacific Ocean to USA via the China-US and Japan-US cables that were commissioned in 2001."
If he's having packet loss in this link, it's due to poor routing by his ISP.
Pinging the relevant latter-hop routers in the traceroute would determine if it was a packet-loss issue or otherwise. Then he could contact his ISP with the results to get their input.
We need a bigger sample size (several more traceroutes) and some pings to individual late-hop reach.com routers to determine the problem spot in the route to the USA.
Thoughts?
[ This Message was edited by: dj42 {C?} on 2009-06-10 02:52 ]
_________________
jedi42, darkjedi42, [drunk], hoid o' toitles, evil, rum, cl2k drainer, gdi, {C?}, hive teets, fusion mating, perfect cloud formation, death star, point jump, tractor scout, torp det, def cluster, cloaked elf
|
Eledore Massis [R33]
Grand Admiral
Templar Knights
Joined: May 26, 2002
Posts: 2694
From: tsohlacoLocalhost
| Posted: 2009-06-10 14:05
Quote:
|
On 2009-06-10 02:40, dj42 {C?} wrote:
Thoughts? |
|
Sounds valid but only for the lost packets.
The latency increase is about what you can expect for a transatlantic hop.
Ok this is from europe over a business class connection but.
1 <1 ms <1 ms <1 ms NZER.braindeath.nl [192.168.23.250]
2 1 ms <1 ms <1 ms 10.166.23.1
3 16 ms 16 ms 17 ms lo1.dr6.d12.xs4all.net [194.109.5.213]
4 12 ms 11 ms 11 ms 0.ge-3-0-0.xr3.3d12.xs4all.net [194.109.7.141]
5 13 ms 13 ms 11 ms 0.so-7-0-0.xr1.tc2.xs4all.net [194.109.5.14]
6 13 ms 12 ms 12 ms ams-ix.ams01.mzima.net [195.69.144.73]
7 23 ms 19 ms 17 ms eos4-0.cr01.lhr01.uk.mzima.net [216.193.255.101]
8 102 ms 94 ms 103 ms eos2-2.cr01.lga02.us.mzima.net [216.193.255.177]
9 94 ms 105 ms 93 ms xe1-0.cr01.lga01.us.mzima.net [216.193.255.213]
10 102 ms 108 ms 107 ms te1-1.cr01.iad01.us.mzima.net [69.174.120.62]
11 113 ms 125 ms 112 ms te1-3.cr01.atl01.us.mzima.net [69.174.120.53]
12 136 ms 144 ms 143 ms te0-1.cr01.dfw01.us.mzima.net [69.174.120.49]
13 159 ms 162 ms 161 ms te1-1.cr01.phx01.us.mzima.net [69.174.120.37]
14 176 ms 164 ms 177 ms te1-1.cr01.lax02.us.mzima.net [69.174.120.33]
15 169 ms 169 ms 187 ms ge0-calpop.cust.lax02.mzima.net [72.37.172.90]
16 169 ms 168 ms 168 ms 216.240.152.146
As you see about 80 increase when crossing the atlantic.
But ya it could be interesting to compare.
Still keep in mind that ISP's don't necessarily can control how there transatlantic are routed.
(Atleast thats how its here, its controlled by the nations internet exchainges).
_________________
DS Discordion
|
Slippi Toad
1st Rear Admiral
Joined: May 07, 2009
Posts: 12
| Posted: 2009-06-11 10:53
ur gonna have to give me instructions 
results without instructions
C:>ping 216.240.152.146
Pinging 216.240.152.146 with 32 bytes of data:
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=186ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=188ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 186ms, Maximum = 188ms, Average = 187ms
C:>ping 216.240.152.146
Pinging 216.240.152.146 with 32 bytes of data:
Reply from 216.240.152.146: bytes=32 time=188ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 188ms, Average = 187ms
C:>ping 216.240.152.146
Pinging 216.240.152.146 with 32 bytes of data:
Request timed out.
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 187ms, Average = 187ms
C:>ping 216.240.152.146
Pinging 216.240.152.146 with 32 bytes of data:
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=188ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 188ms, Average = 187ms
C:>ping 216.240.152.146
Pinging 216.240.152.146 with 32 bytes of data:
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Request timed out.
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 187ms, Average = 187ms
C:>ping 216.240.152.146
Pinging 216.240.152.146 with 32 bytes of data:
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 187ms, Average = 187ms
C:>ping 216.240.152.146
Pinging 216.240.152.146 with 32 bytes of data:
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Request timed out.
Ping statistics for 216.240.152.146:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 187ms, Average = 187ms
C:>ping 216.240.152.146
Pinging 216.240.152.146 with 32 bytes of data:
Reply from 216.240.152.146: bytes=32 time=188ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 188ms, Average = 187ms
C:>ping 216.240.152.146
Pinging 216.240.152.146 with 32 bytes of data:
Reply from 216.240.152.146: bytes=32 time=188ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Reply from 216.240.152.146: bytes=32 time=187ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 188ms, Average = 187ms
C:>
[ This Message was edited by: JaMeRiRa on 2009-06-12 07:53 ]
_________________
|
Eledore Massis [R33]
Grand Admiral
Templar Knights
Joined: May 26, 2002
Posts: 2694
From: tsohlacoLocalhost
| Posted: 2009-06-12 17:42
Not that that shocking there, since ever average is 187ms.
Only thing that could be shocking is that it keeps 187 ms average on every try.
Basically it doesn't look like its a connection issue at both your and the darkspace end.
Might be something completely different.
just for the sake of asking.
When trying to play pull up the stats screen "Alt + P" and when your experiencing a freeze or other stange thing, Look at the second row.
you will notice Latency: Tick: and UDP: .try to remember Latency and UDP since these are your connection speeds to the server.
(They should be below 200, mine is usually at ~80/90ms)
Second there is the fifth row, FPS: when this drops below 10 than we found your problem in a totaly different area, when this happens plz tell us.
In addition some extra ping commands.
ping titan.palestar.com -l 3200 -n 25 (will ping 25 times with a packet size of 3200 bites.)
Ping titan.palestar.com -f -n 30 (will ping 25 times, ping will be send immediately when receiving a reply.)
_________________
DS Discordion
|
Slippi Toad
1st Rear Admiral
Joined: May 07, 2009
Posts: 12
| Posted: 2009-06-12 22:09
OKAY
During game.. when connection is failing here are the ALT P results
Latency is 38500 ??! (this value WAS around 200 during good game play.
UDP never changes from 85-95
I don't seem to be recieveing much data,. do lots of shooting and no shield or armor or hull damage.. I do not get shot back,. but allies will shoot,. enemies do not.
Frame rate is adequate,. 110 - 125 during action and about 40 when motionless.
My computer has 256mb graphics,. 1 gb ram. 2.4ghz amd athlon and no lower than 600+kb connection to the internet.
results for Reply from 216.240.152.146: bytes=3200 time=231ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 228ms, Maximum = 231ms, Average = 229ms
C:>ping titan.palestar.com -l 3200 -n 25
Pinging titan.palestar.com [216.240.152.146] with 3200 bytes of data:
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=229ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=232ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Reply from 216.240.152.146: bytes=3200 time=230ms TTL=116
Ping statistics for 216.240.152.146:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 229ms, Maximum = 232ms, Average = 229ms
_________________
|
|
English
Deutsch
Nederlands
)
