In uk.telecom.broadband, Wireless Reader wrote:
>>And what about a trace route to the address - what happens?
In uk.telecom.broadband, Nigel M wrote:
>It works.
My reply here was misleading! I meant an *external* traceroute worked.
If I can't ping it, I don't think traceroute would work either. I've
since found that I can ping the server OK if I dial up with another ISP,
same modem, same PC.
Strangely, NTL "support" have asked me to give them my IP address by
using ipconfig. Here is the email I sent them, slightly snipped:
"Well, my IP address as shown by ipconfig is 192.168.0.1 so that doesn't
help much. However, my IP address to the Internet is 217.137.54.3 at the
moment (given by
http://www.whatismyip.com/)
I'm not sure what traceroute is supposed to show, if I can't ping the
host, how would traceroute work?
Traceroute results:
C:\tracert 85.133.16.62
Tracing route to gwrbc2b02.rxtxtech.net [85.133.16.62] over a maximum of
30 hops:
1 * * * Request timed out.
[snip]
10 * * * Request timed out.
11 * ^C
[at this point I cancelled with control C]
However, using the traceroute from
http://www.nildram.net/traceroute.cgi
the results were:
Result for 85.133.16.62:
traceroute to 85.133.16.62 (85.133.16.62), 30 hops max, 40 byte packets
1 lon1-9 (195.149.20.130) 0.321 ms 0.327 ms 0.250 ms
2 GigabitEthernet5-0.linx1.lon1.level3.net (195.66.224.77) 0.320 ms
0.192 ms 0.161 ms
It think this proves my point. Nildram (for example) can reach the host
but I can't, unless I dial up via another ISP."
Assuming that NTL support still say it is my problem, can anyone make a
suggestion (other than move to another ISP - I'm doing that on 28th of
this month, when I *finally* get broadband).
--
Nigel M
"Time may be a great healer,
but he's a lousy beautician"