Re: Weird TCP/IP Problems
- From: Shawn Keene <ShawnKeene@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 12 Nov 2006 01:23:02 -0800
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.
"John Wunderlich" wrote:
=?Utf-8?B?U2hhd24gS2VlbmU=?= <ShawnKeene@xxxxxxxxxxxxxxxxxxxxxxxxx>.
wrote in news:474A57F4-411C-4E8A-9CBD-92214EE0A868@xxxxxxxxxxxxx:
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
- References:
- Re: Weird TCP/IP Problems
- From: John Wunderlich
- Re: Weird TCP/IP Problems
- Prev by Date: Re: Accessing networked Desktop
- Next by Date: computer freezes when trying to setup wifi router
- Previous by thread: Re: Weird TCP/IP Problems
- Next by thread: Re: Weird TCP/IP Problems
- Index(es):
Relevant Pages
|
