ase question

Judas · **ase question -** 10-09-2002, 09:28 PM

Im not sure what ive done to ase but now most of the servers i have listed in my favorites, aa, doa, kaos, are all pinging at 100+. aa is at 155, and it used to show up around 40. Another server i used to play on sometimes is now at a whoopping 5378 ... no joke. Chicken boos server stays at around 130+ in gamespy, but when i play i get a normal ping 50+ ... I i have homelan set as pinger and scanner. Anyone ? ed:

r3mix · 10-10-2002, 12:09 AM

set whatever it gives you as thescanner.
set your own machine as the pinger.

what someone elses ping is for a server is not useful info.

Judas · 10-10-2002, 05:01 AM

bump

Rudedog ?

rudedog · 10-10-2002, 05:28 AM

Same thing. I believe they the rout they check ( ping ) is bad. This is why your getting the wrong info in your ASE.

I will drop over to the ASE message board and see what's up. They are really good at picking up on these things early. Kind of weird a company being pro active LOL>

I will report back ASAP

r3mix · 10-10-2002, 05:30 AM

uh..... still same deal.... unless you are pinging these servers yourself theres no difference between it showing 50 and showing 800. if its not your ping it doesnt mean anything.

Captain_McCusker · 10-10-2002, 05:33 AM

How do you set your own comp as the pinger?

rudedog · 10-10-2002, 05:36 AM

Check out this thread:
http://www.udpsoft.com/forum/topic.cgi? ... &topic=908

Basically they tell you to retest your network connection within ASE. I did that and my pings are still high. I checked them against my own pings from a dos prompt and am getting the same thing.

It seems when I do a tracert I get a bad router between myself and the provider, a Tier3 router.

I will send another email to XGS seeing if anyone else is having the same problems.

BTW does anyone know where Kaos IP 65.174.230.77 is being hosted? they are pinging in at around 55.

I know UUNET was having problems buy my friend said that was over in Europe and did propagate back to some of the main providers here but has been since fixed.

Judas · 10-10-2002, 05:37 AM

i wasnt trying to undermind you remix ed: ... just wanted to see what rude would say ... thanks to all of you for the responses. I tried setting my comp as pinger, still the same deal. Also tried to reinstall it.

Judas · 10-10-2002, 05:41 AM

sorry boo forgot .. to set your comp as the pinger look under view / options / then look two sections down to pinger and remove the check from that box ... i think eek:

rudedog · 10-10-2002, 05:45 AM

Ok, just did a tracrt from my box to the game server.
[code:a43a6]1 5 ms 17 ms 5 ms 10.2.120.1
2 5 ms 217 ms 35 ms 68.9.8.85
3 23 ms 7 ms 8 ms 68.9.8.201
4 406 ms 68 ms 401 ms provdsrc02-gew0304.rd.ri.cox.net [68.9.14.17]
5 431 ms 59 ms 347 ms provbbrc02-pos0101.rd.ri.cox.net [68.1.0.48]
6 308 ms 53 ms 19 ms provbbrc01-pos0100.rd.ri.cox.net [68.1.0.42]
7 72 ms 45 ms 34 ms mtc1bbrc02-pos0103.rd.om.cox.net [68.1.0.47]
8 54 ms 51 ms 48 ms mtc3bbrc02-pos0102.rd.ok.cox.net [68.1.0.110]
9 46 ms 45 ms 45 ms mtc3bbrc01-pos0100.rd.ok.cox.net [68.1.0.102]
10 57 ms 416 ms 61 ms dllsbbrc02-pos0103.rd.dl.cox.net [68.1.0.107]
11 110 ms 55 ms 52 ms dllsbbrc01-pos0100.rd.dl.cox.net [68.1.0.142]
12 102 ms 53 ms 53 ms DLLSTX9LCE1.wcg.net [206.223.118.83]
13 73 ms 54 ms 61 ms dllstx1wcx2-oc48.wcg.net [64.200.110.81]
14 103 ms 87 ms 386 ms 64.200.232.126
15 87 ms 87 ms 86 ms hrndva1wcx2-oc48.wcg.net [64.200.95.77]
16 126 ms 93 ms 86 ms nycmny2wcx2-oc48.wcg.net [64.200.240.45]
17 87 ms 86 ms 86 ms nycmny2wcx3-pos9-0.wcg.net [64.200.87.226]
18 86 ms 118 ms 87 ms nycmnyhlce1-oc48.wcg.net [64.200.87.110]
19 87 ms 86 ms 86 ms nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150
]
20 148 ms 86 ms 86 ms so-3-0-0.core1.iad1.globali.net [64.186.143.169]

21 90 ms 88 ms 201 ms gig1-2.cust1.iad1.globali.net [64.186.143.138]
22 196 ms 87 ms 86 ms 64.186.142.138
23 125 ms 86 ms 374 ms 216.52.118.2
24 87 ms 87 ms 127 ms 66.151.108.123[/code:a43a6]

well for Cox cable users it looks like they have some bad routers. So I know my problem is with my ISP. I will be phoning them shortly. See if I have to terminal into their routers and play. last time they had an unsecured one LOL.

Check tracert judas and post the contents. you will need to click on the little dos window and select edit to copy from the window.

Judas · 10-10-2002, 05:54 AM

do i need to use any switches ?

tracert 66.151.108.123

cause all im getting are a bunch of stars with request timed out ed: ed:

Also tried with ws_ping propack same deal ....

pest · 10-10-2002, 06:00 AM

Quote:

Originally Posted by Judas

do i need to use any switches ?

tracert 66.151.108.123

cause all im getting are a bunch of stars with request timed out ed: ed:

Also tried with ws_ping propack same deal ....

What do the stars mean. My ISP has been having local problems lately and cant handle the evening bandwidth load. I try to run tracert and I get timed out servers, and when I do get results I really dont know how to interpet them.

rudedog · 10-10-2002, 06:01 AM

The stars are BAD. That means your losing packets to those "hops" or routers.

If you look at my tracert you will see all the very high ping routers in the cox network. That tells me my problem lies within my ISP and I can complain. If it was outside of the cox network then, I personally could not do anything about it

rudedog · 10-10-2002, 06:08 AM

when you send data ( bunch of packets ) to another computer across the Internet.
It hops from one router to another until it reaches it's final destination.
A router is suppose to look for the fastest route to your destination and send packets that way. a routable network can automatically reroute any given packets because of congestion or broken link. This is why the ARPA net was formed in the mid to late 60's you now know it as the Internet.

Tracert sends 3 packets and waits for a reply from each "hop" (router)
if for some reason it does not make it to the next router or does not receive a reply then it has to send it again. thus the asterisks.
Breakdown:
My 4th hop
[code:aa743]4 406 ms 68 ms 401 ms provdsrc02-gew0304.rd.ri.cox.net [68.9.14.17] [/code:aa743]

the number 4 represents the 4th hop
the 406ms, 68ms and 401ms repsents the 3 tries.
the provdsrc02-gew0304.rd.ri.cox.net is the name or address of the router
This one is by far having some problems

This is the quick overview hope it helps, I'm late for work, I will post more info tonight.

Bazooka_Joe · 10-10-2002, 09:15 AM

A little late into this thread, but I pinged both Chickenboo's svr & AA.COM from home; both below 100. Then I checked through Gamespy, still under 100.