Re: Weird TCP/IP Problems

My crystal ball tells me that you are using OpenDNS as a DNS server
(actually, 208.67.219.40 is one of their server addresses). I am
seeing exactly analogous bizarre behaviour, having recently changed to
using OpenDNS, and have not had a reply to my query to them about it.
It is screwing me up because one of the systems on my local network
can no longer find my mail server (on another local system), because
its address is now being returned as 208...... Please post back here
if you find a solution elsewhere.


On Sat, 11 Nov 2006 17:58:01 -0800, Shawn Keene
<ShawnKeene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I have four computers on my netork, all on the same workgroup, who get their
IP information over DHCP from a Linksys Wireless G router. Two computers are
wired, two are wireless. Simple enough?

I can only ping other computers by using IP addresses (ping 192.168.1.10).
If I type [ ping laptop ], I get this response:

---------------------------------
Pinging laptop.domain_not_set.invalid [208.67.219.40] with 32 bytes of data:
Reply from 208.67.219.40: bytes=32 time=96ms TTL=47
Reply from 208.67.219.40: bytes=32 time=97ms TTL=47
Reply from 208.67.219.40: bytes=32 time=97ms TTL=47
Reply from 208.67.219.40: bytes=32 time=96ms TTL=47
---------------------------------

That is not my laptop's IP address. And I have no idea where 207.67.219.40
is, but it's not in my house that I know of. And what does
"domain_not_set.invalid" mean? And what's with the latency of almost 100ms
if it's in my house?

I don't get what's causing this.

BUT -- I can open up Run and type "\\laptop" and I get a folder listing of
shares that are on my laptop. Why can Windows resolve \\laptop but not ping
laptop?

Is this a problem with my router or computers (all four of them?!) or just a
setting?


- Skeene

Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher
.

Relevant Pages