If you're having ping problems

[Rik]

Please carry out the following diagnostic procedures (assuming Windows XP):

1 ) Boot to safe mode with network support

2 ) Hit Start > Run > Type CMD and press <enter>

3 ) Type netstat -b and press <enter>

4 ) Type ping www.idnet.net and press <enter>

5 ) Type tracert www.idnet.net and press <enter>

6 ) Right-click the title bar of the window, select Edit > Select all and press <enter>

7 ) Paste those results into an email to support@idnet.net, adding information about date and time,
    and identifying your router make and model, together with either your IP address or your ADSL phone number.

8 ) Run a BT speed test and paste the results into the email.

By all means add further pings/tracerts to other servers.

[mynnydd]

Are you sure this works in windows 7?
It wasn't for me.

[Rik]

I can't be sure, Mynnydd, but someone who uses it will no doubt confirm.

[Glenn]

Windows 7, possibly Vista too

1 ) Boot to safe mode

2 ) Start > All Programs > Accessories > right click on Command Prompt select run as administrator

3 ) Type netstat -b and press <enter>

4 ) Type ping www.idnet.net and press <enter>

5 ) Type tracert www.idnet.net and press <enter>

6 ) Right-click the title bar of the window, select Edit > Select all and press <enter>

7 ) Paste those results into an email to support@idnet.net, adding information about date and time,
     and identifying your router make and model, together with either your IP address or your ADSL phone number.

8 ) Run a BT speed test and paste the results into the email.

[Rik]

Thanks, Glenn.

[Ted]

what function is -b its invalid in Linux.

here's the choice. I'm thinking -r ?
       

        -r, --route                display routing table
        -I, --interface=[<Iface>] display interface table for <Iface>
        -i, --interfaces           display interface table
        -g, --groups               display multicast group memberships
        -s, --statistics           display networking statistics (like SNMP)
        -M, --masquerade           display masqueraded connections

        -v, --verbose              be verbose
        -n, --numeric              don't resolve names
        --numeric-hosts            don't resolve host names
        --numeric-ports            don't resolve port names
        --numeric-users            don't resolve user names
        -N, --symbolic             resolve hardware names
        -e, --extend               display other/more information
        -p, --programs             display PID/Program name for sockets
        -c, --continuous           continuous listing

        -l, --listening            display listening server sockets
        -a, --all, --listening     display all sockets (default: connected)
        -o, --timers               display timers
        -F, --fib                  display Forwarding Information Base (default)
        -C, --cache                display routing cache instead of FIB
        -T, --notrim               stop trimming long addresses
        -Z, --context              display SELinux security context for sockets

[Glenn]

C:\Windows\system32>netstat ?

Displays protocol statistics and current TCP/IP network connections.

NETSTAT [-a] [-b] [-e] [-f] [-n] [-o] [-p proto] [-r] [-s] [-t] [interval]

  -a            Displays all connections and listening ports.
  -b            Displays the executable involved in creating each connection or
                listening port. In some cases well-known executables host
                multiple independent components, and in these cases the
                sequence of components involved in creating the connection
                or listening port is displayed. In this case the executable
                name is in [] at the bottom, on top is the component it called,
                and so forth until TCP/IP was reached. Note that this option
                can be time-consuming and will fail unless you have sufficient
                permissions.
  -e            Displays Ethernet statistics. This may be combined with the -s
                option.
  -f            Displays Fully Qualified Domain Names (FQDN) for foreign
                addresses.
  -n            Displays addresses and port numbers in numerical form.
  -o            Displays the owning process ID associated with each connection.
  -p proto      Shows connections for the protocol specified by proto; proto
                may be any of: TCP, UDP, TCPv6, or UDPv6.  If used with the -s
                option to display per-protocol statistics, proto may be any of:
                IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, or UDPv6.
  -r            Displays the routing table.
  -s            Displays per-protocol statistics.  By default, statistics are
                shown for IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, and UDPv6;
                the -p option may be used to specify a subset of the default.
  -t            Displays the current connection offload state.
  interval      Redisplays selected statistics, pausing interval seconds
                between each display.  Press CTRL+C to stop redisplaying
                statistics.  If omitted, netstat will print the current
                configuration information once.

[Rik]

What Glenn said, Ted, I was just busy cutting and pasting.

[Azy]

on a mac

go to finder/Applications/Utility/Network Utility

select ping tab, type www.idnet.net and enter

copy and paste

then select tracert tab, type www.idnet.net and enter

copy and paste

not sure this is helpful  

[Simon]

It may well be, thanks Azy. 

[kinmel]

Anyone using a 2700HGV router with V6 firmware can do the ping and tracert from the router itself and know that your pc setup is not affecting the results.

this link takes you straight to the I.P. Utilities page

[Simon]

Doesn't apply to me, but thanks, Alan. 

[mynnydd]

Under windows 7.
There is no need to boot.
1. With windows running go to accessories.
2. click on the command prompt program.
3. type ping www.idnet.com (do not forget the space between ping and www.)
4. you will see the following.

[Simon]

I believe that's just a normal Windows command prompt screen.  I'm not sure of the reason for the advice to reboot into safe mode, but I assumed it was so that no other network activity could impact on the ping results. 

[mynnydd]

I believe that's just a normal Windows command prompt screen.  I'm not sure of the reason for the advice to reboot into safe mode, but I assumed it was so that no other network activity could impact on the ping results. 

Oh, to eliminate the possibility of computer issues?

[Simon]

That too. 

[DarkStar]

I have been trying to follow this procedure in Safe Mode on XP Home SP. Can get into safe mode OK, enter netstat -b but when I enter the ping www.idnet.net I just get the message: "Ping request could not find host. Please check name and try again"
Have tried with and without OpenDNS - every way I can but get the same message every time.
Any ideas why or about what to do next?
If I do a cmd prompt not in safe mode and enter netstat -b it works, I just get two of my security apps listed and then can do the ping, no problem 

[Rik]

Very odd, Ian. I've been having a problem with DNS failing intermittently, I wonder if it's related. Is your DNS obtained through the router automatically, or do you set it in Windows?

[DarkStar]

I set it in Windows, control panel > network connections, the router (netgear DG834) was set up by IDNet for me when I got it and I have not messed about with it.
What puzzles me is why I cannot get it to work in Safe Mode but no problem out of Safe Mode. I'll give support a ring on Monday if no one comes up with an answer - I'm a bit short of time at the moment.

[Rik]

Switch the primary and secondary around, Ian, iow, make the 40 server your primary and the 36 your secondary, see if that helps.

[DarkStar]

I have always had mine set up to find DNS automatically (see screeny) but have just had a look at my papers I got from IDNet when I joined and now see them on there. Does it make much difference in any way how you have it set up. I have never had DNS problems so have never bothered to look into it very much.

[attachment deleted by admin]

[Rik]

Just click on the Use the following DNS servers, Ian, then enter 212.69.40.3 as the preferred and 212.69.36.3 as the alternate. If that works, do the same on any other machines you have. Doing it in Windows won't drop your connection.

[DarkStar]

Just tried that, no difference.
Have one more trick to try, if it does not work I'll have to ring support on Monday.

[Rik]

It was a long shot, Ian, but I thought it might just relate to the issue I was seeing.

[Simon]

Do you have to be in safe mode with networking to do this?

[Rik]

You do.

[Simon]

Just checking. 

[Rik]

 

[DarkStar]

Do you have to be in safe mode with networking to do this?

When I go into Safe Mode I have three Safe Mode options to choose from:
Safe Mode
Safe Mode with Networking
Safe Mode with Command Prompt

I have trying all this in plain flavor Safe Mode, should I have doing it in Safe Mode with Networking ?

[Rik]

You should, Ian.

[Rik]

Sticky now corrected. 

[DarkStar]

Bingo 
Would you believe that my pings are now down to 35 - 45, they have been between 100 - 200 all day.
Will get the evidence together later and let support have it.

[Rik]

Great. Sorry about missing the vital bit from the sticky, Ian.

[DarkStar]

No problem Rik, now I've sorted that out pings have settled down - sods law I suppose. Never had pings like this since I started keeping an eye on them, been like it all day 

[attachment deleted by admin]

[Rik]

Things are gradually getting resolved.

[Matt M]

been having loads on ping issues on GW5 though seems to have died down now

[Sebby]

See how it goes and let IDNet know if you run into problems again.