Ping and tracert problem

thehourman · February 2011

So I having this issue with ping and tracert stuff. I am getting a weird output from both commands.
It keep routed to the IP address 192.168.1.3.
I check the host file but I don't see the address 192.168.1.3 there.
ping:

C:\Users\Quis>ping wwww.techexams.net -t

Pinging wwww.techexams.net [63.251.179.13] with 32 bytes of data:
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255
Reply from 192.168.1.3: bytes=32 time=4ms TTL=255

Ping statistics for 63.251.179.13:
    Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 4ms, Average = 4ms
Control-C
^C

Tracert:

C:\Users\Quis>tracert -d www.techexams.net

Tracing route to www.techexams.net [174.133.7.131]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     4 ms     4 ms     6 ms  192.168.1.3

Trace complete.

Does anyone know how to fix this?

drainey · February 2011

Try doing an ipconfig /flushdns (from the command prompt) to clear the dns cache on your workstation.

Check your internal DNS (server/router/etc. whatever is serving as the DNS for your internal LAN). Clear the cache/Scavange old records on your internal DNS server.

thehourman · February 2011

I have done the ipconfig /flushdns, but that didn't work.

I am using FIOS router, and I checked that the DNS server and nothing there.

The 192.168.1.3 is my netgear switch.

Ping and tracert problem

Comments