Cannot see XP system from other PCs on network.

Hello all,

I have a problem seeing a Win XP Pro PC from other PCs on the network.

Here is my setup:

Time Warner (Roadrunner cable) connected to:

LinkSys 4-port router, connected to:

P4 running Win XP Pro acting as a server (running IIS 5.0), P3 running Win
98, and a 486SX2 running Windows For Workgroups 3.11.
The Sever runs just fine.

In Network Neighborhood, From the P4, I can see the P3 & 486. From the P3,
I can see the P3 and the 486. From the 486, I can see the 486 and the P3.

All of the disks have been shared correctly.

I have even disabled the Windows Firewall on the P4. I still can't see the
P4.

Any suggestions, hints, etc as to where to look?

Thanks in advance.

Ted

Can you ping the P4 by IP? If not, check another other firewall software. If yes, can you ping the computer name? If not, enable NetBIOS over TCP/IP. check this link for more details,

Access issues
"computername is not accessible. No permission to access the resources" Case Study ·
Troubleshooting "No accessible" ... is not accessible ...
www.chicagotech.net/accesserrors.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Ted Brewer" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Hello all,

I have a problem seeing a Win XP Pro PC from other PCs on the network.

Here is my setup:

Time Warner (Roadrunner cable) connected to:

LinkSys 4-port router, connected to:

P4 running Win XP Pro acting as a server (running IIS 5.0), P3 running Win
98, and a 486SX2 running Windows For Workgroups 3.11.
The Sever runs just fine.

In Network Neighborhood, From the P4, I can see the P3 & 486. From the P3,
I can see the P3 and the 486. From the 486, I can see the 486 and the P3.

All of the disks have been shared correctly.

I have even disabled the Windows Firewall on the P4. I still can't see the
P4.

Any suggestions, hints, etc as to where to look?

Thanks in advance.

Ted

Thanks for replying Bob.

I can ping all of the PCs using the IP address.

I can ping the 486 & the P3 using the name, but the ping for the P4 returns
the wrong IP address (I feel).

For instance:

The 486 is ted3 and 192.168.1.101.

The P3 is ted2 and 192.168.1.104

The P4 is ted1 and 192.168.1.103

The ping for ted1 returns the IP address 192.168.1.100 instead of
192.168.1.103 (like I think it should).

As you can tell, I am at a loss as to what to do next.

Ted




> Can you ping the P4 by IP? If not, check another other firewall
> software. If yes, can you ping the computer name? If not, enable
> NetBIOS over TCP/IP. check this link for more details,
>
> Access issues
> "computername is not accessible. No permission to access the
> resources" Case Study ·
> Troubleshooting "No accessible" ... is not accessible ...
> www.chicagotech.net/accesserrors.htm
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Ted Brewer" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> Hello all,
>
> I have a problem seeing a Win XP Pro PC from other PCs on the
> network.
>
> Here is my setup:
>
> Time Warner (Roadrunner cable) connected to:
>
> LinkSys 4-port router, connected to:
>
> P4 running Win XP Pro acting as a server (running IIS 5.0), P3
> running Win
> 98, and a 486SX2 running Windows For Workgroups 3.11.
> The Sever runs just fine.
>
> In Network Neighborhood, From the P4, I can see the P3 & 486. From
> the P3,
> I can see the P3 and the 486. From the 486, I can see the 486 and
> the P3.
>
> All of the disks have been shared correctly.
>
> I have even disabled the Windows Firewall on the P4. I still can't
> see the
> P4.
>
> Any suggestions, hints, etc as to where to look?
>
> Thanks in advance.
>
> Ted

Good morning Ted.
When you ping ted1 and tou get the wrong ip address, you are pinging the
computer name ?
It seems a problem with names resolution.
I suggest two tests :
a) create (if you don't have it already) a share on ted1 and try, from ted3
and ted2 to open \\ted1\sharename
b) Maybe you have an host with 192.168.1.100 on your net that is not ted1 ?
If you are sure that ted1 is 192.168.1.103 and you get response from
192.168.1.100, try to shut ted1 and see if pinging 192.168.1.100 still works.

Let me know
--
Fabrizio Volpe
MCSE 2003/2000/NT
MCT

Thanks for the info, Fabrizio.

How do I shut ted1?

Ted




>> Good morning Ted.
>> When you ping ted1 and tou get the wrong ip address, you are pinging
>> the computer name ?
>> It seems a problem with names resolution.
>> I suggest two tests :
>> a) create (if you don't have it already) a share on ted1 and try,
>> from ted3 and ted2 to open \\ted1\sharename
>> b) Maybe you have an host with 192.168.1.100 on your net that is not
>> ted1 ? If you are sure that ted1 is 192.168.1.103 and you get
>> response from 192.168.1.100, try to shut ted1 and see if pinging
>> 192.168.1.100 still works.
>>
>> Let me know
>> --
>> Fabrizio Volpe
>> MCSE 2003/2000/NT
>> MCT

Hello Ted.
I thought ted1 was an host on your network.
It's a remote computer ?
Anyway, I would try to "isolate" the connection to ted1 and see if the
"wrong" ip still responds.

--
Fabrizio Volpe
MCSE 2003/2000/NT
MCT

Hi Fabrizio.

I guess I was in error about the wrong IP addr.

ted1 (win xp pro) is 192.168.1.100, also acts as a server for my website.

ted2 (win 98) is 192.168.1.104.

ted3 (wfw 3.11) is 192.168.1.101.

I can ping all names & address from all pcs. This works.

I had to add netbios to ted1, and all pcs show up in the network
neighborhood workgroup now.

ted2 & ted3 only show each other in network neighborhood.

I can map drive to all pcs from ted1.

I cannot map drive to ted1 from ted2 or ted3.

I tried to disable the firewall on ted1, but it made no difference.

I am slowly but surely running out of ideas. I'm sure it is a simple
setting that I'm missing, but danged if I can figure it out.

Thanks for any help.



>> Hello Ted.
>> I thought ted1 was an host on your network.
>> It's a remote computer ?
>> Anyway, I would try to "isolate" the connection to ted1 and see if
>> the "wrong" ip still responds.
>>
>> --
>> Fabrizio Volpe
>> MCSE 2003/2000/NT
>> MCT

If ted1 hosts your website, it will have a public IP. Make sure that
Netbios over TCP/IP is disabled on that interface, and enabled on the
192.168.1.100 interface.

Ted Brewer wrote:
> Hi Fabrizio.
>
> I guess I was in error about the wrong IP addr.
>
> ted1 (win xp pro) is 192.168.1.100, also acts as a server for my
> website.
>
> ted2 (win 98) is 192.168.1.104.
>
> ted3 (wfw 3.11) is 192.168.1.101.
>
> I can ping all names & address from all pcs. This works.
>
> I had to add netbios to ted1, and all pcs show up in the network
> neighborhood workgroup now.
>
> ted2 & ted3 only show each other in network neighborhood.
>
> I can map drive to all pcs from ted1.
>
> I cannot map drive to ted1 from ted2 or ted3.
>
> I tried to disable the firewall on ted1, but it made no difference.
>
> I am slowly but surely running out of ideas. I'm sure it is a simple
> setting that I'm missing, but danged if I can figure it out.
>
> Thanks for any help.
>
>
>
>>> Hello Ted.
>>> I thought ted1 was an host on your network.
>>> It's a remote computer ?
>>> Anyway, I would try to "isolate" the connection to ted1 and see if
>>> the "wrong" ip still responds.
>>>
>>> --
>>> Fabrizio Volpe
>>> MCSE 2003/2000/NT
>>> MCT

Thanks for the reply, Bill.

My brain, at this stage of the game, is pure mush.

How do I go about making the changes that you suggest?

Ted




>> If ted1 hosts your website, it will have a public IP. Make sure
>> that Netbios over TCP/IP is disabled on that interface, and enabled
>> on the 192.168.1.100 interface.
>>
>> Ted Brewer wrote:
>>> Hi Fabrizio.
>>>
>>> I guess I was in error about the wrong IP addr.
>>>
>>> ted1 (win xp pro) is 192.168.1.100, also acts as a server for my
>>> website.
>>>
>>> ted2 (win 98) is 192.168.1.104.
>>>
>>> ted3 (wfw 3.11) is 192.168.1.101.
>>>
>>> I can ping all names & address from all pcs. This works.
>>>
>>> I had to add netbios to ted1, and all pcs show up in the network
>>> neighborhood workgroup now.
>>>
>>> ted2 & ted3 only show each other in network neighborhood.
>>>
>>> I can map drive to all pcs from ted1.
>>>
>>> I cannot map drive to ted1 from ted2 or ted3.
>>>
>>> I tried to disable the firewall on ted1, but it made no difference.
>>>
>>> I am slowly but surely running out of ideas. I'm sure it is a
>>> simple setting that I'm missing, but danged if I can figure it out.
>>>
>>> Thanks for any help.
>>>
>>>
>>>
>>>>> Hello Ted.
>>>>> I thought ted1 was an host on your network.
>>>>> It's a remote computer ?
>>>>> Anyway, I would try to "isolate" the connection to ted1 and see if
>>>>> the "wrong" ip still responds.
>>>>>
>>>>> --
>>>>> Fabrizio Volpe
>>>>> MCSE 2003/2000/NT
>>>>> MCT

You do it from the TCP/IP properties for each NIC. Try the advanced
TCP/IP settings, WINS tab.

If it is enabled on more than one interface in a machine, it can cause
problems with browsing the machine (because there is more than one IP for
the machine name).

Ted Brewer wrote:
> Thanks for the reply, Bill.
>
> My brain, at this stage of the game, is pure mush.
>
> How do I go about making the changes that you suggest?
>
> Ted
>
>
>
>
>>> If ted1 hosts your website, it will have a public IP. Make sure
>>> that Netbios over TCP/IP is disabled on that interface, and enabled
>>> on the 192.168.1.100 interface.
>>>
>>> Ted Brewer wrote:
>>>> Hi Fabrizio.
>>>>
>>>> I guess I was in error about the wrong IP addr.
>>>>
>>>> ted1 (win xp pro) is 192.168.1.100, also acts as a server for my
>>>> website.
>>>>
>>>> ted2 (win 98) is 192.168.1.104.
>>>>
>>>> ted3 (wfw 3.11) is 192.168.1.101.
>>>>
>>>> I can ping all names & address from all pcs. This works.
>>>>
>>>> I had to add netbios to ted1, and all pcs show up in the network
>>>> neighborhood workgroup now.
>>>>
>>>> ted2 & ted3 only show each other in network neighborhood.
>>>>
>>>> I can map drive to all pcs from ted1.
>>>>
>>>> I cannot map drive to ted1 from ted2 or ted3.
>>>>
>>>> I tried to disable the firewall on ted1, but it made no difference.
>>>>
>>>> I am slowly but surely running out of ideas. I'm sure it is a
>>>> simple setting that I'm missing, but danged if I can figure it out.
>>>>
>>>> Thanks for any help.
>>>>
>>>>
>>>>
>>>>>> Hello Ted.
>>>>>> I thought ted1 was an host on your network.
>>>>>> It's a remote computer ?
>>>>>> Anyway, I would try to "isolate" the connection to ted1 and see
>>>>>> if the "wrong" ip still responds.
>>>>>>
>>>>>> --
>>>>>> Fabrizio Volpe
>>>>>> MCSE 2003/2000/NT
>>>>>> MCT




Ted Brewer wrote:
> Thanks for the reply, Bill.
>
> My brain, at this stage of the game, is pure mush.
>
> How do I go about making the changes that you suggest?
>
> Ted
>
>
>
>
>>> If ted1 hosts your website, it will have a public IP. Make sure
>>> that Netbios over TCP/IP is disabled on that interface, and enabled
>>> on the 192.168.1.100 interface.
>>>
>>> Ted Brewer wrote:
>>>> Hi Fabrizio.
>>>>
>>>> I guess I was in error about the wrong IP addr.
>>>>
>>>> ted1 (win xp pro) is 192.168.1.100, also acts as a server for my
>>>> website.
>>>>
>>>> ted2 (win 98) is 192.168.1.104.
>>>>
>>>> ted3 (wfw 3.11) is 192.168.1.101.
>>>>
>>>> I can ping all names & address from all pcs. This works.
>>>>
>>>> I had to add netbios to ted1, and all pcs show up in the network
>>>> neighborhood workgroup now.
>>>>
>>>> ted2 & ted3 only show each other in network neighborhood.
>>>>
>>>> I can map drive to all pcs from ted1.
>>>>
>>>> I cannot map drive to ted1 from ted2 or ted3.
>>>>
>>>> I tried to disable the firewall on ted1, but it made no difference.
>>>>
>>>> I am slowly but surely running out of ideas. I'm sure it is a
>>>> simple setting that I'm missing, but danged if I can figure it out.
>>>>
>>>> Thanks for any help.
>>>>
>>>>
>>>>
>>>>>> Hello Ted.
>>>>>> I thought ted1 was an host on your network.
>>>>>> It's a remote computer ?
>>>>>> Anyway, I would try to "isolate" the connection to ted1 and see
>>>>>> if the "wrong" ip still responds.
>>>>>>
>>>>>> --
>>>>>> Fabrizio Volpe
>>>>>> MCSE 2003/2000/NT
>>>>>> MCT