Why can't I ping the SNET server ?
#1
Following on to my ongoing problems trying to access SNET from home it now appears the reason I can't access SNET is that it's timing out looking for the server. Can anyone explain why it only happening with SNET and why it's intermittent - if I keep logging on and off it eventually does find the server and everything is ok. I could understand if it was happening with other sites but why just SNET ?
Kevin.
Kevin.
#2
Scooby Regular
Join Date: Sep 2002
Location: Essexville
Posts: 4,391
Likes: 0
Received 0 Likes
on
0 Posts
hi mate
are you using a modem or adsl
try ping www.scoobynet.co.uk -t
see how long the time takes..
this is from my office
C:\>ping www.scoobynet.co.uk -t
Pinging www.scoobynet.co.uk [217.79.111.23] with 32 by
Reply from 217.79.111.23: bytes=32 time=30ms TTL=114
Reply from 217.79.111.23: bytes=32 time=30ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
anything longer than 100ms may time out on request.
BB
are you using a modem or adsl
try ping www.scoobynet.co.uk -t
see how long the time takes..
this is from my office
C:\>ping www.scoobynet.co.uk -t
Pinging www.scoobynet.co.uk [217.79.111.23] with 32 by
Reply from 217.79.111.23: bytes=32 time=30ms TTL=114
Reply from 217.79.111.23: bytes=32 time=30ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
Reply from 217.79.111.23: bytes=32 time=20ms TTL=114
anything longer than 100ms may time out on request.
BB
#3
Scooby Regular
Kevin,
Sorry I missed the replies in your other post.
If it's timing out but everyone else is OK, then it's down to your connection to the ISP or your ISP's routing to SN.
Try this command
tracert www.scoobynet.co.uk
Here's my results:-
U:\>tracert www.scoobynet.co.uk
Tracing route to www.scoobynet.co.uk [217.79.111.23]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms rdf-sco-gw [x.x.x.x]
2 <1 ms <1 ms <1 ms xxxx.xxxx.com [x.x.x.x]
3 13 ms 13 ms 12 ms gyle-ll-12.access.demon.net [194.159.254.21]
4 26 ms 26 ms 26 ms tele-core-1-fxp3.router.demon.net [194.159.254.100]
5 27 ms 26 ms 27 ms tele-core-12-e15.router.demon.net [194.159.176.142]
6 27 ms 26 ms 26 ms tele-core-11-245.router.demon.net [194.159.176.129]
7 78 ms 78 ms 76 ms ams3-border-1-at-1-2-3-102.router.demon.net [194.217.238.254]
8 69 ms 73 ms 75 ms GigabitEthernet3-2.core2.ams1.level3.net [193.148.15.110]
9 75 ms 70 ms 80 ms ae0-15.mp1.Amsterdam1.Level3.net [213.244.165.65]
10 34 ms 34 ms 38 ms so-3-0-0.mp1.London1.Level3.net [212.187.128.58]
11 35 ms 34 ms 33 ms gige10-0.ipcolo2.London1.Level3.net [212.187.131.8]
12 462 ms 407 ms 407 ms f0-1.core1.tchx.lon.uk.griffin.com [195.50.116.2]
13 39 ms 108 ms 134 ms atm1-0.core1.srbp.dby.uk.griffin.com [217.79.96.130]
14 234 ms 43 ms 45 ms 217.79.111.23
Trace complete.
U:\>
I've blanked out my IP address from the results.
Look for long access times.
Stefan
Sorry I missed the replies in your other post.
If it's timing out but everyone else is OK, then it's down to your connection to the ISP or your ISP's routing to SN.
Try this command
tracert www.scoobynet.co.uk
Here's my results:-
U:\>tracert www.scoobynet.co.uk
Tracing route to www.scoobynet.co.uk [217.79.111.23]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms rdf-sco-gw [x.x.x.x]
2 <1 ms <1 ms <1 ms xxxx.xxxx.com [x.x.x.x]
3 13 ms 13 ms 12 ms gyle-ll-12.access.demon.net [194.159.254.21]
4 26 ms 26 ms 26 ms tele-core-1-fxp3.router.demon.net [194.159.254.100]
5 27 ms 26 ms 27 ms tele-core-12-e15.router.demon.net [194.159.176.142]
6 27 ms 26 ms 26 ms tele-core-11-245.router.demon.net [194.159.176.129]
7 78 ms 78 ms 76 ms ams3-border-1-at-1-2-3-102.router.demon.net [194.217.238.254]
8 69 ms 73 ms 75 ms GigabitEthernet3-2.core2.ams1.level3.net [193.148.15.110]
9 75 ms 70 ms 80 ms ae0-15.mp1.Amsterdam1.Level3.net [213.244.165.65]
10 34 ms 34 ms 38 ms so-3-0-0.mp1.London1.Level3.net [212.187.128.58]
11 35 ms 34 ms 33 ms gige10-0.ipcolo2.London1.Level3.net [212.187.131.8]
12 462 ms 407 ms 407 ms f0-1.core1.tchx.lon.uk.griffin.com [195.50.116.2]
13 39 ms 108 ms 134 ms atm1-0.core1.srbp.dby.uk.griffin.com [217.79.96.130]
14 234 ms 43 ms 45 ms 217.79.111.23
Trace complete.
U:\>
I've blanked out my IP address from the results.
Look for long access times.
Stefan
Trending Topics
#9
In Windows
Start > Run > type in Command and hit [Enter]
This will bring up a Command Prompt where you can Ping / TraceRoute and be able to capture the results
Chris.
Start > Run > type in Command and hit [Enter]
This will bring up a Command Prompt where you can Ping / TraceRoute and be able to capture the results
Chris.
#11
Kevin,
You seem to be pinging the old server IP address.
The new server is:
www.scoobynet.co.uk [217.79.111.23]
If you ping www.scoobynet.co.uk from a Command Prompt, what IP address is returned?
You seem to be pinging the old server IP address.
The new server is:
www.scoobynet.co.uk [217.79.111.23]
If you ping www.scoobynet.co.uk from a Command Prompt, what IP address is returned?
#13
Im actually having the same problem with adsl on nildram, ie unable to connect to the scoobynet servers at night, but no probs from work. Nothing has changed my end on either connection, and the DNS is correct because if it wasn't i wouldn't be typing this.
#15
Scooby Regular
Bad IP Address - do you mean the old Scoobynet server address?
If so, then this is resolved through your ISP's DNS servers. If you run winipcfg (Win9x) or IPCONFIG (W2K/XP command prompt), it'll confirm the DNS servers you're using.
Anyway, you'd need to contact your ISP to check that it's their servers that haven't been updated with the new Scoobynet servers IP address.
Stefan
If so, then this is resolved through your ISP's DNS servers. If you run winipcfg (Win9x) or IPCONFIG (W2K/XP command prompt), it'll confirm the DNS servers you're using.
Anyway, you'd need to contact your ISP to check that it's their servers that haven't been updated with the new Scoobynet servers IP address.
Stefan
#17
Scooby Regular
Yeah, just to emphasise what Nigel said. If you have a personal firewall installed it may be configured to prevent icmp pings (incoming, outgoing or both).
Try temporarily disabling any firewall software and try it.
Stefan
[Edited by ozzy - 2/4/2003 10:39:22 PM]
Try temporarily disabling any firewall software and try it.
Stefan
[Edited by ozzy - 2/4/2003 10:39:22 PM]
Thread
Thread Starter
Forum
Replies
Last Post
Reshard1977
ScoobyNet General
84
22 September 2015 05:47 PM
Puff The Magic Wagon!
Non Scooby Related
5
06 November 2000 08:09 PM