|
Home | Site Map | How To | Windows Vista | Case Studies | Articles | Forums | Services | Donations | Careers | About Us | Contact Us| |
|
Troubleshooting Computer Browsing Issues
Can ping and search a remote computer but not browse it Can ping and search a remote computer but not browse itIf you can see or search a remote computer in mixed OS (win98, ME, NT, W2K and XP) network, this is master browser issue. You may try to use browstat.exe from NT resource kit to check the master browser status. Or stop computer browser on w2k/xp. For consultants, refer to case 100903RL.
Can't see any
or only some computers in My Network Places Resolutions: this is likely Computer Browser
issue. Master Browsing issue on Multihomed DC You may experience browsing and/or NetBIOS name resolution problems if you install a DC on multihomed server. This is because each browser service bounds to each interface operates independently and does not merge the browse list for separate networks. The master browser is confused. One computer screw up the networkSymptoms: you have a workgroup network and most computers are win9x, NT and ME. After you add XP computer into the network, you can't browse other computers in workgroup list.Resolutions: This is mostly like master browser issue. The simple solution is stopping Computer Browser service on the XP. To stop Computer Browser service, go to the Computer Management>Services and Applications>Services.The browser was unable to retrieve a list of servers from the browser masterSYMPTOMS: 1) Event Viewer System log shows Event id: 8021 and Description: The browser was unable to retrieve a list of servers from the browser master <PDC> on the network \device\<protocol_netcard>. 2) Event id: 8032 and Description: The browser service has failed to retrieve the backup list too many times on transport of <protocol_netcard>.This symptom occurs because 1) your computer is a multihomed computer or using multiple network cards in the same subnet; 2) your computer is a master browser; 3) Your computer is running the TCP/IP protocol.
Resolutions: find the failed protocol_netcard or use browstat status
(from NT Resource Kit) to find the problem and the card. Then
|
|
|
This web is provided "AS IS" with no warranties.
Copyright © 2002-2007
ChicagoTech.net,
All rights reserved. Unauthorized reproduction forbidden.