Weird TCP/IP Problems

[Guest]

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

 

[John Wunderlich]

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?

None of the above. It works this way by design (i.e. this is the way
it's supposed to work). The problem is that you are confusing
Windows Networking (NetBT = NetBios over TCP/IP) with TCP/IP
addressing.

Names prefixed with "\\" are interpreted to be Windows Networking
devices and are discovered on the network using NetBT protocol
(usually by network broadcasting in a small home network). Microsoft
networking devices are usually located with a combination of
Broadcasting, lookups in WINS servers, and entries in the "lmhosts"
file. As a last resort, it can use DNS servers.

The "ping" routine takes as its argument a TCP/IP address (not a
NetBT address). TCP/IP addresses are resolved using a DNS server or
by entries in your "hosts" file. Local devices on the LAN side of
your router will [generally] not be found via DNS.

Rather than using "ping laptop" to see if a your device is on your
subnet, try using "nbtstat -a laptop".

HTH,
John

 

[Guest]

That seems to find the remote machine just fine. But I used to be able to
remote desktop to other machines in my home by just typing the computer name
into the Terminal Server Client (Remote Desktop Connection in XP). Now it
only works if I specifify an IP address, and it's not easy to assign a static
IP adress to a laptop because it usually needs to be dynamic in public places.

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?

None of the above. It works this way by design (i.e. this is the way
it's supposed to work). The problem is that you are confusing
Windows Networking (NetBT = NetBios over TCP/IP) with TCP/IP
addressing.

Names prefixed with "\\" are interpreted to be Windows Networking
devices and are discovered on the network using NetBT protocol
(usually by network broadcasting in a small home network). Microsoft
networking devices are usually located with a combination of
Broadcasting, lookups in WINS servers, and entries in the "lmhosts"
file. As a last resort, it can use DNS servers.

The "ping" routine takes as its argument a TCP/IP address (not a
NetBT address). TCP/IP addresses are resolved using a DNS server or
by entries in your "hosts" file. Local devices on the LAN side of
your router will [generally] not be found via DNS.

Rather than using "ping laptop" to see if a your device is on your
subnet, try using "nbtstat -a laptop".

HTH,
John

 

[Peter R. Fletcher]

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.

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

 

[Guest]

Wow. Just wow.

Why does changing the DNS Server my router uses to lookup domain names screw
up my computer from resolving computer names on a simple home network?

I'm no network guy, but I think that maybe that shouldn't happen.

- skeene

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.

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

 

[Peter R. Fletcher]

I now have a fix for the problem from the OpenDNS folks - my first
message to them must have got lost, since they replied to a second
within 12 hours - this is much more typical of their usual level of
support, BTW.

Basically, you need to create an account for yourself on the OpenDNS
site, register your IP address (they call it registering your
network), and turn off "typo correction" for it. I imagine that they
will be working on providing a less wholesale solution to what must
(IMHO) be a bug in the typo correction code. If you have a dynamic
address, there is a little bit more to it - email me at
"pfletch<at>fletchers<hyphen>uk.com" (editing spam traps
appropriately) if you have problems with the rather sketchy
instructions on the OpenDNS site.

Wow. Just wow.

Why does changing the DNS Server my router uses to lookup domain names screw
up my computer from resolving computer names on a simple home network?

I'm no network guy, but I think that maybe that shouldn't happen.

- skeene

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.

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

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

 

[Guest]

I am on a dynamic IP from my DSL provider. My router (Linksys) supports
updating a DynDNS host name for me, whch I've used for years to make it
easier to host files on a simple FTP server I set up and to Remote-Desktop to
my home without knowing what my IP is, so I'm familiar with most of that.

Now I'm trying to install "inadyn", which is the updating client that
opendns recommends, onto my Windows 2000 Server (yes it's actually a server,
but being used as a workstation) as a service, but I've gotten a little lost.

Is this something you're familar with? I think I know the command line
syntax to execute the utility and have it perform a single update, but I'd
rather it runs as a service so it can recover after something like a power
failure or run while no one's logged in.


- skeene
(I think this is getting outside the realm of this newsgroup).

I now have a fix for the problem from the OpenDNS folks - my first
message to them must have got lost, since they replied to a second
within 12 hours - this is much more typical of their usual level of
support, BTW.

Basically, you need to create an account for yourself on the OpenDNS
site, register your IP address (they call it registering your
network), and turn off "typo correction" for it. I imagine that they
will be working on providing a less wholesale solution to what must
(IMHO) be a bug in the typo correction code. If you have a dynamic
address, there is a little bit more to it - email me at
"pfletch<at>fletchers<hyphen>uk.com" (editing spam traps
appropriately) if you have problems with the rather sketchy
instructions on the OpenDNS site.

Wow. Just wow.

Why does changing the DNS Server my router uses to lookup domain names screw
up my computer from resolving computer names on a simple home network?

I'm no network guy, but I think that maybe that shouldn't happen.

- skeene

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

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

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

 

[Peter R. Fletcher]

I do now have inadyn installed as a service. The difficulties you have
obviously encountered will have arisen at least partly from the
instructions in the readme file assuming that you have downloaded and
unpacked the full distribution from inadyn's home site, rather than
the minimal package from the OpenDNS site. The latter only suffices if
you just want to run the program from the command line. Proceed as
follows:

1) Go to http://inadyn.ina-tech.net/readme.html and download the
version 1.96 executables for Windows. Unzip the contents of the
package into a directory on your hard disk. Note that the version of
inadyn.exe in this package _won't_ work with OpenDNS (it doesn't
support a secure connection), so you should delete it - it's some of
the installation files that you need.

2) As instructed in the readme file, download the Windows files
intsrv.exe and srvany.exe into the Win32 subdirectory in your new
inadyn directory - both files are available at the
http://www.electrasoft.com/srvany/srvany.htm location.

3) The inadyn people provide template .reg files for dyndns and
freedns. Neither they nor the OpenDNS folks provide one for OpenDNS,
but I have written one. Cut the lines at the end of this message,
paste into a file called (e.g.) OpenDNS.reg, remove any extra <CR>s
added by the news client, and edit it to insert your OpenDNS user name
and password and the full path to the (V1.97) inadyn.exe file which
you got from the OpenDNS site..

4) Double-click on your new .reg file and confirm that you want to
modify the Registry.

5) Double-click on the install_inadyn_service.bat file to run it.

The inadyn service should now be installed and configured. If you use
the appropriate Server 2000 applet to view your services, you can
check that it is set to run automatically and start it (which will
only be necessary this time). Once it is running, check the log fille
(which corresponds to standard output on the command line version) to
ensure that there were no errors.

Good Luck!

{reg file template]
REGEDIT4
; This is a template file without personal information
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inadyn\Parameters]
; Edit the next line to show the full path to the inadyn.exe V1.97
; executable file. Note that any backslashes "\" in the path must be
; _doubled_ "\\"
"Application"="D:\\inadyn\\inadyn.exe"
; Edit the next line to replace "username" and "password" with your
; OpenDNS user name and password. The "--alias" string is arbitrary,
; and is really only relevant to more complex setups.
; N.B. what follows should be on a _single_ line
"AppParameters"="--background --dyndns_server_name updates.opendns.com
--dyndns_server_url /account/ddns.php? --secure -u username -p
password --update_period 60000 --alias test.opendns.net --log_file
inadyn_srv.log"
[/reg file template]

I am on a dynamic IP from my DSL provider. My router (Linksys) supports
updating a DynDNS host name for me, whch I've used for years to make it
easier to host files on a simple FTP server I set up and to Remote-Desktop to
my home without knowing what my IP is, so I'm familiar with most of that.

Now I'm trying to install "inadyn", which is the updating client that
opendns recommends, onto my Windows 2000 Server (yes it's actually a server,
but being used as a workstation) as a service, but I've gotten a little lost.

Is this something you're familar with? I think I know the command line
syntax to execute the utility and have it perform a single update, but I'd
rather it runs as a service so it can recover after something like a power
failure or run while no one's logged in.


- skeene
(I think this is getting outside the realm of this newsgroup).

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