Thanx in advance,
Jeremy Kinsey
I would like to point out a minor problem that seems to being happening
somewhere between Mia.net and Alpha.net:
(tracert done by me)
C:\WINDOWS>tracert www.mixcom.com
Tracing route to www.mixcom.com [198.137.186.91]
over a maximum of 30 hops:
1 * * * Request timed out.
2 143 ms 138 ms 136 ms alpha-mia.alpha.net [206.190.25.101]
3 136 ms 137 ms 133 ms mke-1.alpha.net [156.46.1.1]
4 207 ms 140 ms 135 ms aads.nap.net [198.32.130.39]
5 145 ms 140 ms 138 ms edge0-a0-2.chi1.nap.net [207.112.247.190]
6 168 ms 146 ms 146 ms chi1-t1.mixcom.net [207.227.0.94]
7 150 ms 169 ms 159 ms www.mixcom.com [198.137.186.91]
Trace complete.
(tracert done by a friend to mia.net)
C:\WINDOWS>tracert ftp.mia.net
Tracing route to mia.net [206.190.23.194]
over a maximum of 30 hops:
1 136 ms 134 ms 131 ms pm3-2.mixcom.com [198.137.186.112]
2 134 ms 134 ms 133 ms mixcis1.mixcom.com [198.137.186.88]
3 140 ms * 241 ms edge0-s3-5-t1.chi1.nap.net [207.227.0.93]
4 140 ms 144 ms 156 ms core0.chi1.nap.net [207.112.247.33]
5 165 ms 143 ms 146 ms aads-nap.alpha.net [198.32.130.20]
6 144 ms 142 ms 144 ms mke-39.alpha.net [156.46.1.40]
7 * * * Request timed out.
8 176 ms 168 ms 159 ms mia.net [206.190.23.194]
Trace complete.
You'll notice that all communication to/from mia.net always times out once
somewhere between mia.net and mke-39.alpha.net. I realize this isn't
having
much impact the majority of the time, but while playing Quake 2 online
this
has major impact since this game is extremely sensitive to latency, and
causes major disruptions making it unplayable, even on servers running off
of nap.net, which should be flawless.
Thanks for taking a look into this for me.
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.