Can't see XP PC on network

F

fj

Have three PC's on Linksys LAN. Two of the pc's can be 'seen' in Microsoft
Windows Network from all three pc's. But, one of the pc's doesn't show in
Microsoft Windows Network - even from itself.

If I stop/start Computer Browser on the pc that isn't visible, the pc will
show up in Microsoft Windows Network on all three pc's.

The 'problem' pc is pingable from the other two pc's even when it is not
visible in Microsoft Windows Network.

Any idea of how to get the problem PC to always show?

Thanks
 
B

Brian A.

Do you have a third party software firewall? If so, check it's log file to
see if the machine is being blocked, and if it is add it's IP to the Trusted
Zone. As a matter of fact, you should add all IP's to the Trusted Zone.

If you're using XP's firewall, make sure file and print sharing is enabled in
the exceptions.
Start > Settings > Control Panel > Windows Firewall applet > Exceptions tab.

Is the machine set to obtain IP automatically? If yes:
Start > Run, type in: cmd and press Enter.
At the prompt type: ipconfig /all and press Enter. Not the space before /.
Take note of the IP address, subnet mask and gateway. Do they appear correct?
Check the other machines and make sure all of the IP's do not have a match with
another machine. I've seen DHCP dole out matching IP's to seperate machines and
the first one with it connected while the second failed.

Recheck your settings for the machine in Network properties.

Right click My Network Places on the Desktop.
Click Properties.
Right click Local Area Connection.
Click Properties.

Under "This connection uses....."
Click "Client for MS Networks".
Click Properties.
Select "Windows Locator" from the dropdown box.
Click Ok.

Scroll to and select Internet Protocol (TCP/IP).
Click Properties.

Under the General tab make sure "Obtain an IP address automatically" is
selected.
Click the Advanced button.

Under the DNS tab:
Selected "Append Primary and Parent DNS suffixes.
Register this connections address in DNS"

Under the WINS tab > NetBIOS:
Selected Default.
Ok out of MNP.
Reboot if required.

Test connectivity:
Open a command prompt, click Start > Run, type in: cmd and press Enter.
At the prompt type each command below and press Enter after each.
**Note: Command noted by =, Space noted by ^. Do not type the = or ^.

=ping ^ 192.168.1.1 *Routers IP, change as necessary.
If it times out then there is no communication between the router and machine.
If not then the machine communicates with the router.

=ping ^ google.com
If it times out then there is no connection to the net.
If not then net connection is established and all is well.

ping 127.0.0.1
If it fails it may be a TCP/IP stack problem.

Ping each computer from the other using the UNC:
=ping ^ computername
If it fails either way there's an IP or Name resolution problem.

If pinging times out on any address, to see if the machines IP is correct along
with other settings.
= ipconfig ^ /all
If anything isn't correct, at the prompt type and press Enter after each command
(98 may be different):

=ipconfig ^ /release
=ipconfig ^ /flushdns
=ipconfig ^ /renew
=ipconfig ^ /registerdns
=exit
If that fails reopen the command prompt, run release and flushdns only and exit.

Shut down the machine.
Pull the power from the router.
Pull the power from the modem.
Wait approx 30 secs.
Apply power to the modem and wait for it to finish synchronizing with the cable.
Apply power to the router and wait for it to finish synchronizing with the
modem.
Power up the machine.
The machine should now be assigned a new IP from the router.
Run ipconfig or attempt net connection to test

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
R

Roberto

fj said:
Have three PC's on Linksys LAN. Two of the pc's can be 'seen' in
Microsoft Windows Network from all three pc's. But, one of the pc's
doesn't show in Microsoft Windows Network - even from itself.

Then this machine isn't setup correctly for networking, or either the NIC or
cable to the Linksys is defective.

Do the basic stuff listed below

1. replace/ test the CAT5 cable
2. ensure the NIC is installed correctly [drivers]
3. rerun Network Wiz, ensuring the machine is added to the same
workgroup as the other two machines
4. check TCP/IP settings are the same on all machines
5. disable any firewalls
6. check there is no duplicate machine names
7. Don't use an empty [nul] logon password [if this is the case]

rgds
Roberto
 
F

fj

Brian A. said:
Do you have a third party software firewall? If so, check it's log file
to see if the machine is being blocked, and if it is add it's IP to the
Trusted Zone. As a matter of fact, you should add all IP's to the Trusted
Zone.
Zone Alarm is installed on all three pcs with the same settings => but the
problem is only with one PC. In any case, there are no entries in the log
viewer showing blocked communications with any of the other pc's on the
network.
If you're using XP's firewall, make sure file and print sharing is
enabled in the exceptions.
Start > Settings > Control Panel > Windows Firewall applet > Exceptions
tab.

Is the machine set to obtain IP automatically? If yes:
Start > Run, type in: cmd and press Enter.
At the prompt type: ipconfig /all and press Enter. Not the space
before /.
Take note of the IP address, subnet mask and gateway. Do they appear
correct? Check the other machines and make sure all of the IP's do not
have a match with another machine. I've seen DHCP dole out matching IP's
to seperate machines and the first one with it connected while the second
failed.

All three pc's have unique IP addresses - 192.168.1.100, .101 and .102
Recheck your settings for the machine in Network properties.

Right click My Network Places on the Desktop.
Click Properties.
Right click Local Area Connection.
Click Properties.

Under "This connection uses....."
Click "Client for MS Networks".
Click Properties.
Select "Windows Locator" from the dropdown box.
Click Ok.


Scroll to and select Internet Protocol (TCP/IP).
Click Properties.

Under the General tab make sure "Obtain an IP address automatically" is
selected.
Click the Advanced button.

Under the DNS tab:
Selected "Append Primary and Parent DNS suffixes.
Register this connections address in DNS"

Under the WINS tab > NetBIOS:
Selected Default.
Ok out of MNP.
Reboot if required.

All checked out exactly as described.
Test connectivity:
Open a command prompt, click Start > Run, type in: cmd and press Enter.
At the prompt type each command below and press Enter after each.
**Note: Command noted by =, Space noted by ^. Do not type the = or ^.

=ping ^ 192.168.1.1 *Routers IP, change as necessary.
If it times out then there is no communication between the router and
machine.
If not then the machine communicates with the router.

all pc's can be pinged [using ip address from each other]
=ping ^ google.com
If it times out then there is no connection to the net.
If not then net connection is established and all is well.

ping 127.0.0.1
If it fails it may be a TCP/IP stack problem.

Ping each computer from the other using the UNC:
=ping ^ computername
If it fails either way there's an IP or Name resolution problem.

If pinging times out on any address, to see if the machines IP is correct
along with other settings.
= ipconfig ^ /all
If anything isn't correct, at the prompt type and press Enter after each
command (98 may be different):

=ipconfig ^ /release
=ipconfig ^ /flushdns
=ipconfig ^ /renew
=ipconfig ^ /registerdns
=exit
If that fails reopen the command prompt, run release and flushdns only and
exit.

Shut down the machine.
Pull the power from the router.
Pull the power from the modem.
Wait approx 30 secs.
Apply power to the modem and wait for it to finish synchronizing with the
cable.
Apply power to the router and wait for it to finish synchronizing with the
modem.
Power up the machine.
The machine should now be assigned a new IP from the router.
Run ipconfig or attempt net connection to test

The problem seems to come and go. After the problem pc disappears from the
network [but is still pingable from the other pc's], it will reappear on all
three pc's if Computer Browser is restarted on the problem PC. Then, after
many hours, the problem pc will disappear from Windows Network, but still be
pingable. I have notice that, on the problem PC there are errors from
Computer Browser stating that the browser failed too many times to retreive
the backup list. And, that the browser is being stopped. However, when
checking Computer Browser after the error shows up, the service says it's
running. But, as mentioned above, if Computer Browser is restarted, the
problem pc shows up.

Thanks
 
F

fj

Roberto said:
Then this machine isn't setup correctly for networking, or either the NIC
or cable to the Linksys is defective.

Sorry, should have mentioned that the pc does show up for a while, then
disappears. Only reappears after restarting Computer Browser on the problem
pc.

All three pc's have been on the LAN for several years and have always been
visible on all pc's. Only recently - say in the last week, has the problem
started.
That would roughly coincide with the latest patches from MS, but all three
pc's are running xp and all were updated with the most recent updates.
Do the basic stuff listed below

1. replace/ test the CAT5 cable I'll try this - can't hurt.
2. ensure the NIC is installed correctly [drivers]
They look good - using nvidia's ethernet drivers.
3. rerun Network Wiz, ensuring the machine is added to the same
workgroup as the other two machines
yep - all on MSHOME1. [original, hunh?]
4. check TCP/IP settings are the same on all machines - yep.
5. disable any firewalls
hmm - all three run exactly the same version of ZA [actually Checkpoint
Integrity Flex]. Seems unlikely, but, since they are all behind the router,
i'll give this a shot.
6. check there is no duplicate machine names check
7. Don't use an empty [nul] logon password [if this is the case] check.

Thanks
rgds
Roberto


If I stop/start Computer Browser on the pc that isn't visible, the pc
will show up in Microsoft Windows Network on all three pc's.

The 'problem' pc is pingable from the other two pc's even when it is not
visible in Microsoft Windows Network.

Any idea of how to get the problem PC to always show?

Thanks
 
B

Brian A.

See if this helps:
Troubleshooting browser Event ID 8021 and 8032 on master browsers
http://support.microsoft.com/kb/q135404/

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
Brian A. said:
Do you have a third party software firewall? If so, check it's log file
to see if the machine is being blocked, and if it is add it's IP to the
Trusted Zone. As a matter of fact, you should add all IP's to the Trusted
Zone.
Zone Alarm is installed on all three pcs with the same settings => but the
problem is only with one PC. In any case, there are no entries in the log
viewer showing blocked communications with any of the other pc's on the
network.
If you're using XP's firewall, make sure file and print sharing is
enabled in the exceptions.
Start > Settings > Control Panel > Windows Firewall applet > Exceptions
tab.

Is the machine set to obtain IP automatically? If yes:
Start > Run, type in: cmd and press Enter.
At the prompt type: ipconfig /all and press Enter. Not the space
before /.
Take note of the IP address, subnet mask and gateway. Do they appear
correct? Check the other machines and make sure all of the IP's do not
have a match with another machine. I've seen DHCP dole out matching IP's
to seperate machines and the first one with it connected while the second
failed.

All three pc's have unique IP addresses - 192.168.1.100, .101 and .102
Recheck your settings for the machine in Network properties.

Right click My Network Places on the Desktop.
Click Properties.
Right click Local Area Connection.
Click Properties.

Under "This connection uses....."
Click "Client for MS Networks".
Click Properties.
Select "Windows Locator" from the dropdown box.
Click Ok.


Scroll to and select Internet Protocol (TCP/IP).
Click Properties.

Under the General tab make sure "Obtain an IP address automatically" is
selected.
Click the Advanced button.

Under the DNS tab:
Selected "Append Primary and Parent DNS suffixes.
Register this connections address in DNS"

Under the WINS tab > NetBIOS:
Selected Default.
Ok out of MNP.
Reboot if required.

All checked out exactly as described.
Test connectivity:
Open a command prompt, click Start > Run, type in: cmd and press Enter.
At the prompt type each command below and press Enter after each.
**Note: Command noted by =, Space noted by ^. Do not type the = or ^.

=ping ^ 192.168.1.1 *Routers IP, change as necessary.
If it times out then there is no communication between the router and
machine.
If not then the machine communicates with the router.

all pc's can be pinged [using ip address from each other]
=ping ^ google.com
If it times out then there is no connection to the net.
If not then net connection is established and all is well.

ping 127.0.0.1
If it fails it may be a TCP/IP stack problem.

Ping each computer from the other using the UNC:
=ping ^ computername
If it fails either way there's an IP or Name resolution problem.

If pinging times out on any address, to see if the machines IP is correct
along with other settings.
= ipconfig ^ /all
If anything isn't correct, at the prompt type and press Enter after each
command (98 may be different):

=ipconfig ^ /release
=ipconfig ^ /flushdns
=ipconfig ^ /renew
=ipconfig ^ /registerdns
=exit
If that fails reopen the command prompt, run release and flushdns only and
exit.

Shut down the machine.
Pull the power from the router.
Pull the power from the modem.
Wait approx 30 secs.
Apply power to the modem and wait for it to finish synchronizing with the
cable.
Apply power to the router and wait for it to finish synchronizing with the
modem.
Power up the machine.
The machine should now be assigned a new IP from the router.
Run ipconfig or attempt net connection to test

The problem seems to come and go. After the problem pc disappears from the
network [but is still pingable from the other pc's], it will reappear on all
three pc's if Computer Browser is restarted on the problem PC. Then, after
many hours, the problem pc will disappear from Windows Network, but still be
pingable. I have notice that, on the problem PC there are errors from
Computer Browser stating that the browser failed too many times to retreive
the backup list. And, that the browser is being stopped. However, when
checking Computer Browser after the error shows up, the service says it's
running. But, as mentioned above, if Computer Browser is restarted, the
problem pc shows up.

Thanks
--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
F

fj

Brian A. said:
See if this helps:
Troubleshooting browser Event ID 8021 and 8032 on master browsers
http://support.microsoft.com/kb/q135404/

Thanks.

Just to confirm, do I have it right that I don't need Computer Browser?
I.e., the Workstation service detects and maintains list of computers on the
network?

Thanks
--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
Brian A. said:
Do you have a third party software firewall? If so, check it's log
file
to see if the machine is being blocked, and if it is add it's IP to the
Trusted Zone. As a matter of fact, you should add all IP's to the
Trusted
Zone.
Zone Alarm is installed on all three pcs with the same settings => but
the
problem is only with one PC. In any case, there are no entries in the
log
viewer showing blocked communications with any of the other pc's on the
network.
If you're using XP's firewall, make sure file and print sharing is
enabled in the exceptions.
Start > Settings > Control Panel > Windows Firewall applet > Exceptions
tab.

Is the machine set to obtain IP automatically? If yes:
Start > Run, type in: cmd and press Enter.
At the prompt type: ipconfig /all and press Enter. Not the space
before /.
Take note of the IP address, subnet mask and gateway. Do they appear
correct? Check the other machines and make sure all of the IP's do not
have a match with another machine. I've seen DHCP dole out matching
IP's
to seperate machines and the first one with it connected while the
second
failed.

All three pc's have unique IP addresses - 192.168.1.100, .101 and .102
Recheck your settings for the machine in Network properties.

Right click My Network Places on the Desktop.
Click Properties.
Right click Local Area Connection.
Click Properties.

Under "This connection uses....."
Click "Client for MS Networks".
Click Properties.
Select "Windows Locator" from the dropdown box.
Click Ok.


Scroll to and select Internet Protocol (TCP/IP).
Click Properties.

Under the General tab make sure "Obtain an IP address automatically" is
selected.
Click the Advanced button.

Under the DNS tab:
Selected "Append Primary and Parent DNS suffixes.
Register this connections address in DNS"

Under the WINS tab > NetBIOS:
Selected Default.
Ok out of MNP.
Reboot if required.

All checked out exactly as described.
Test connectivity:
Open a command prompt, click Start > Run, type in: cmd and press
Enter.
At the prompt type each command below and press Enter after each.
**Note: Command noted by =, Space noted by ^. Do not type the = or ^.

=ping ^ 192.168.1.1 *Routers IP, change as necessary.
If it times out then there is no communication between the router and
machine.
If not then the machine communicates with the router.

all pc's can be pinged [using ip address from each other]
=ping ^ google.com
If it times out then there is no connection to the net.
If not then net connection is established and all is well.

ping 127.0.0.1
If it fails it may be a TCP/IP stack problem.

Ping each computer from the other using the UNC:
=ping ^ computername
If it fails either way there's an IP or Name resolution problem.

If pinging times out on any address, to see if the machines IP is
correct
along with other settings.
= ipconfig ^ /all
If anything isn't correct, at the prompt type and press Enter after each
command (98 may be different):

=ipconfig ^ /release
=ipconfig ^ /flushdns
=ipconfig ^ /renew
=ipconfig ^ /registerdns
=exit
If that fails reopen the command prompt, run release and flushdns only
and
exit.

Shut down the machine.
Pull the power from the router.
Pull the power from the modem.
Wait approx 30 secs.
Apply power to the modem and wait for it to finish synchronizing with
the
cable.
Apply power to the router and wait for it to finish synchronizing with
the
modem.
Power up the machine.
The machine should now be assigned a new IP from the router.
Run ipconfig or attempt net connection to test

The problem seems to come and go. After the problem pc disappears from
the
network [but is still pingable from the other pc's], it will reappear on
all
three pc's if Computer Browser is restarted on the problem PC. Then,
after
many hours, the problem pc will disappear from Windows Network, but still
be
pingable. I have notice that, on the problem PC there are errors from
Computer Browser stating that the browser failed too many times to
retreive
the backup list. And, that the browser is being stopped. However, when
checking Computer Browser after the error shows up, the service says it's
running. But, as mentioned above, if Computer Browser is restarted, the
problem pc shows up.

Thanks
--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

fj wrote:
Have three PC's on Linksys LAN. Two of the pc's can be 'seen' in
Microsoft
Windows Network from all three pc's. But, one of the pc's doesn't show
in
Microsoft Windows Network - even from itself.

If I stop/start Computer Browser on the pc that isn't visible, the pc
will
show up in Microsoft Windows Network on all three pc's.

The 'problem' pc is pingable from the other two pc's even when it is
not
visible in Microsoft Windows Network.

Any idea of how to get the problem PC to always show?

Thanks
 
B

Brian A.

fj said:
Thanks.

Just to confirm, do I have it right that I don't need Computer Browser?
I.e., the Workstation service detects and maintains list of computers on the
network?

Thanks

IIRC since Win2K the Browser wasn't necessary. I don't have it enabled on any
machine here that I'm aware of, unless a 98SE does which I rarely go into much
anymore as they're mainly used for storage/backup images.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top