Re: >>Two XPs can't see each other<<
From: Bob Willard (BobwBSGS_at_TrashThis.comcast.net)
Date: 02/20/04
- Next message: BobC: "Re: Does Internet Connection Sharing really work"
- Previous message: Marc Reynolds [MSFT]: "Re: what are WINS servers, and how do I find out if I need them, and how to identify them?"
- In reply to: Wayne B.: "Re: >>Two XPs can't see each other<<"
- Next in thread: Wayne B.: "Re: >>Two XPs can't see each other<<"
- Reply: Wayne B.: "Re: >>Two XPs can't see each other<<"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 20 Feb 2004 10:57:41 -0500
Wayne B. wrote:
> Well Bob, I'm a little lost then. My LAN setup is
> isolated to only these 3 PCs via a five port switch and
> CAT5 cables. So how did my Pro machine get in touch with
> a DNS server to come up with 192.168. for MY network?
> Before you just enlightened me with your reply, I had
> always thought that 192.168. was another grouping made
> possible by APIPA. Since the Pro machine gets the
> internet via dialup modem, did it happen that way
> somehow?? any thoughts? Wayne B.
>
>
>>-----Original Message-----
>>Wayne B. wrote:
>>
>>>Hey Chuck, I was thinking along those same lines. I
>
> have
>
>>>already changed the NIC and swapped the cables. The
>>>cables and cards are in working order. I have manually
>>>configured the IP thru the properties of the NIC that
>
> I
>
>>>have connected to the existing LAN, --> Internet
>
> Protocol
>
>>>(TCP/IP) | Properties It now shows (after reboot)
>>>that's it's on the same subnet from within
>>>
>>>
>>>>ipconfig /all<, but still no luck. The workgroup is
>>>
>>>named identical to the existing network.
>>>What is it that I'm missing.
>>>
>>>ALSO, just thought that I would mention this too.
>
> When I
>
>>>try pinging my XP Pro and Win2k by name from the XP
>
> Home,
>
>>>it times out BUT, it also gives the correct IP
>
> addresses
>
>>>of the machines next to the names of the machines.
>>>Meaning, when I type in Ping
>
> <computername>
>
>>>the next line is, Pinging <computername>
>>>[192.168.x.x] with 32 bytes of data:
>>>
>>>Now I don't know Exactly how this works, but, I would
>>>figure that if it can't ping the name OR the IP, then
>>>that means that it can't see the computer. So how is
>
> it
>
>>>giving the actual IP of the name that I type in???
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>On Wed, 18 Feb 2004 23:52:56 -0800, "Wayne B."
>>>><*false_email_address_deleted*> wrote:
>>>>
>>>>
>>>>
>>>>>Hi Chuck. When I have my XP Pro to ping itself by
>>>
>>>IP
>>>
>>>
>>>>>and name, it responds with it's own IP accordingly
>
> for
>
>>>>>both times. (192.168.X.X) I also have a 2k
>
> connected
>
>>>>>within my LAN, I get the same proper results with
>
> this
>
>>>>>machine as well.(192.168.X.X) They can also ping
>
> each
>
>>>>>other with no problem as well.
>>>>> Now, When I have the XP Home to ping itself
>>>
>>>by
>>>
>>>
>>>>>name AND IP, it replies with it's own IP for both.
>>>>>(169.254.X.X) but requests are timed out when it
>
> tries
>
>>>to
>>>
>>>
>>>>>ping out to either the Pro or 2k. And the same goes
>>>
>>>for
>>>
>>>
>>>>>the Pro and 2k trying to ping the Home. (timed out)
>>>>
>>>>Wayne,
>>>>
>>>>169.254.X.X is an APIPA address.
>>>><http://compnetworking.about.com/cs/protocolsdhcp/g/bld
>
> ef
>
>>>_apipa.htm>.
>>>
>>>
>>>>The XP Home is NOT connecting to the network. Since
>
> it
>
>>>will ping
>>>
>>>
>>>>itself by name, it sounds like the network is loaded
>>>
>>>(it's resolving
>>>
>>>
>>>>its own name successfully). Use another port in the
>>>
>>>switch. Use
>>>
>>>
>>>>another network cable. Finally, check or replace the
>>>
>>>network card.
>>>
>>>
>>>>>PS - That is not an accurate Email. Thanx
>>>>
>>>>Please read:
>>>>http://www.mailmsg.com/SPAM_munging.htm
>>>>http://members.aol.com/emailfaq/mungfaq.html#how-not-
>
> mung
>
>>>>Cheers,
>>>>Chuck
>>>>Paranoia comes from experience - and is not
>
> necessarily
>
>>>a bad thing.
>>>
>>>
>>>>.
>>>>
>>
>>The translation from name to number is done by a Domain
>
> Name Server,
>
>>not by either the source or target PC on your LAN. So
>
> getting the
>
>>right IPA for the target PC does not mean that your
>
> source PC can
>
>>talk to the target PC.
>>
>>Check ICF on your XP HE PC -- if it is enabled, disable
>
> it forever.
>
>>ICF is not intended for use on a LAN.
>>--
>>Cheers, Bob
>>
>>.
>>
Here's what typically happens (simplified quite a bit):
First event: you (or somebody acting for you, such as the vendor who
installed XP) gave your PC a name. Second event: an IPA was given
to your PC, either by you assigning a static IPA, or by your PC's
asking and being given an IPA by a DHCP server, or by your PC's giving
itself an APIPA after a failed attempt to get an IPA from a DHCP
server. Third event: your PC registers itself with a DNS server by
announcing its name and IPA. Note that the DNS server and the DHCP
server are software entities which may or may not reside on the same
hunk of hardware. Also note that events 1-3 happen for each PC.
Fourth event: when you command your source PC to communicate with
a target PC (by, say, PING PC123) on your LAN, your source PC sends
a request to the DNS server to translate the target PC's name (PC123)
into the IPA for that PC; if translation succeeds, then the source PC
uses the IPA of the target PC as the target for packets sent over the
network (your LAN, in the case of interest).
I assume that your XP PRO PC is a gateway to the internet for your
other PCs, and that your LAN is controlled by ICS (with the XP PRO PC as
the ICS host and the other PCs as ICS clients). If that's true, then
that ICS host is the DHCP server and the (real or virtual) DNS server.
ICS is hard-wired to use 192.168.x.y for its LAN. Also, your XP PRO PC
has a separate IPA to use on its WAN-side, which it gets by a similar
process (usually DHCP) from your dial-up ISP.
Caveat: The details of address assignment and address translation
vary a lot, depending on the protocol(s) used. If you want to really
understand how it works, a good starting point is Cisco's handbook:
http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/index.htm
-- Cheers, Bob
- Next message: BobC: "Re: Does Internet Connection Sharing really work"
- Previous message: Marc Reynolds [MSFT]: "Re: what are WINS servers, and how do I find out if I need them, and how to identify them?"
- In reply to: Wayne B.: "Re: >>Two XPs can't see each other<<"
- Next in thread: Wayne B.: "Re: >>Two XPs can't see each other<<"
- Reply: Wayne B.: "Re: >>Two XPs can't see each other<<"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
