Irregularities In Workgroup Visibility

Let’s say you connect 2 computers, running any of the many versions and editions of Windows, with default configurations, in a network. To find each computer from the other, you open Windows Explorer (don’t confuse this with Internet Explorer, please), and look in My Network Places. In theory, and on a fully working LAN, this will work just fine. In your case, it may not.

In your case, Computer A shows both Computers A and B, as it should, and files on Computer B are accessible. On Computer B, either you don’t see Computer A, or when you try to access Computer A, you get an error. You may, or it may not, see Computer B. This visibility problem may be observed constantly, or it may come and go.

Now before you start, you should be aware that you will enjoy it more, and frequently will be more successful, when you work on a properly designed and setup network. Having reviewed that, I recommend that you tackle the task at hand in this order.

Browser Involvement
This is almost certainly a browser problem. However, in most cases, browser problems are symptoms of more basic network issues.

  • Since Computer B is accessible from Computer A, a physical connectivity issue is unlikely.
  • Besides physical problems, browser problems can have several possible causes. Browser functionality depends upon several relationships:
    • The browser server (ie the browser), and this computer. If this computer can’t access its designated browser server, it may lack browse information, and / or have outdated information.
    • The browser server, and the client server (ie any computer being enumerated by the browser). A server, remember, is any computer being displayed in Network Neighborhood. If the browser server can’t contact a client server, or if the client server uses a different browser, that server may not appear in Network Neighborhood.
    • The browser server, and the master browser (if not the same computer). If a browser server can’t contact the master browser, it won’t get the browse list aggregated by the master browser. Any client computers that use that browser won’t have the browse list aggregated by the master browser.
    • The master browser for this domain / workgroup, and master browsers for other domains / workgroups. Any master browsers that can’t contact other master browsers won’t be able to exchange browse lists with them, and their clients won’t have the browse lists for the other domains / workgroups.
  • Problems with any of the above relationships – now, or in the past – can cause various problems with Network Neighborhood.

Basic Diagnostics

  1. Look at the complete and exact text in any observed error messages. Some very obscure errors have very simple resolutions.
  2. Check for a personal firewall problem. A misconfigured or malfunctioning personal firewall, on either computer, can block browser access. Do you have antivirus protection? Make sure that your antivirus is not part of a package that contains a personal firewall, and does not contain a component that acts as a firewall.
  3. Look carefully for a hardware firewall, sitting inside your computer. The nVidia nForce is probably the first, but surely not the last, device of this type.
  4. Make sure that NetBIOS Over TCP is consistently set, in TCP/IP Properties for each computer in your network.
  5. Some newer, WiFi routers, have a complete firewall between ALL client computers, connected wired or wireless. Look for an “Isolation Mode” setting, if no computers are visible to each other.
  6. Check for several well known and lesser known registry settings, which will affect visibility of, and access to, your server.
  7. Look again at the content of the error message. Do you see either “error = 5” (aka “access denied”), or “error = 53” (aka “name not found”)? Read the appropriate article, and follow the links.
  8. Run, and examine output from, “browstat status”, “ipconfig /all”, and “net config server” and “net config workstation”, for each computer.
  9. Post output from the above step for expert interpretation and advice. Include relevant background details in your post. When including diagnostic logs, such as “browstat status”, “ipconfig /all”, or background details, format them properly when you post them.

Intermediate Diagnostics

  1. Make any changes in your network per the advice of the helpers in the forums. Retest as advised.
  2. Run, and examine, CDiag output for each computer. If you have more than 3 computers, post diagnostics for at least 3, and try and include some computers which show no symptoms of the problem (if any exist), as a control. The more data here the better.
  3. Post output from the above step for expert interpretation and advice. Again, format CDiag logs properly when you post them.
  4. Check that all necessary network components and services are provided. The necessary protocols and transports must be loaded and activated. The necessary services should be Started and Automatic.
  5. Run, and examine, CPSServ output for each computer. Try and do this on the same computers that you ran CDiag (above) on, to make the diagnostics more effective.
  6. Post output from the above step for expert interpretation and advice. Again, format CPSServ logs properly when you post them.
  7. Check for, and remove, unnecessary protocols and transports, like IPV6, IPX/SPX, and NetBEUI. Check “browstat status” logs for evidence of IPX/SPX or NetBEUI. Check “ipconfig /all” logs for evidence of IPV6. Remove any protocols found. If you solve your immediate problems, you can re in stall any protocols removed, later.
  8. Check for LSP / Winsock / TCP/IP corruption. The mysterious LSP / Winsock layer in the network, on either computer, can malfunction and block server datagrams. If you have more than 2 computers, the computer causing your problems may not be immediately apparent. Use CDiag to identify the computers to work on first.

Advanced Diagnostics

  1. Learn How To Solve Network Problems.
  2. Try my comprehensive troubleshooting guide, Troubleshooting Network Neighborhood Problems. Use CDiag and / or CPSServ logs, to identify the computers to work on first.
  3. Read about Windows XP File Sharing.

NOTE: The comprehensive troubleshooting guides, referenced in Advanced Diagnostics, contain all of the other sections and more, sequenced by network design (ie, physical connectivity issues first, and file sharing permissioning last). The last article talks about problems specific to File Sharing, such as authentication and authorisation, and it is most useful when all other problems (such as are discussed in the previous step) are resolved. This article, as a whole, emphasises the most productive procedures for resolving your symptoms. You are free to try any of the above steps, in any order which pleases you – it is, after all, your network.

These are simply the procedures which currently seem to produce the best results. So become familiar with them, because, if you ask for help and I am involved, I will likely ask you for the diagnostics discussed above. And, if we don’t get immediate results here or elsewhere, I’ll ask you to repeat each step above, one by one, as I examine the results. Read each linked article, and follow the links within each article.

Now I’m a Networking and Security advisor, and I don’t provide advice on security issues casually. Using the Internet, without considering the privacy and security implications, makes trouble for a lot of innocent people. When you’re considering the necessity of providing requested details about your computer network, in an open Internet forum, please read this brief Privacy Statement. Help us to help you.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: