Active Directory and network neighborhood


  • I have a questions concerning a problem that seems to have arisen with many of our domain computers.  It seems that if i go to my XP Prof SP3 computer and go into browse my network neighborhood I do not get any computers.  The domain controllers are Win2003. I in fact only get an error message saying,

    " Domain is not accessible.  you might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.  No more connections can be made to this remote comptuer at this time because there are already as many connections as the computer can accept. "

    We thought the problem was associated with a netbios over TCP/IP problem but we made some modifications to the WINS section under the advance properties of the network adapter checking the enable netbios over TCP/IP and it worked for a few minutes then the error returned.  Any idea what the problem could be.  Is it something on our domain controllers or something on our PCs?


    Tuesday, June 23, 2009 9:25 PM


All replies

  • Tony,
    have you determined which computer is functioning as the master browser for the client in question? If not, use the steps described in Disable Browser Service on all computers that are not supposed to function as master browsers. Also ensure that WINS is configured/functioning properly.

    My advice would be to ditch browsing/Network Neighborhood altogether and use AD for publishing resources instead. This can be accomplished using procedures described in and


    Tuesday, June 23, 2009 10:01 PM
  • It seems that some of my master browsers are mutihomed.  If i am to understand correctly after reading some material if a master browser is multihomed we can end up having this issue since computers might be connecting to the nic that is not being used as the master browser therefore no entries are on the list.   It seems that this is the problem i was experiencing.  On the problematic server it was connecting to a multihomed master browser.  I was able to prevent the mulithomed server from being a master browser and made another server the master browser.  the issue went away, just now verifying that the problem does go away completely. 
    Wednesday, June 24, 2009 4:52 PM
  •    Multihomed browse masters have been a problem since the days of NT. It is important to remember that the computer browser service is a legacy application from pre-W2k days and has no relation to Active Directory.

    Thursday, June 25, 2009 6:33 AM