The infrastructure that I have is a central and a delegation, joinedVPN and create Site in AD. I Cualdo dcdiag in the central of DC and the DC of the branch have no error. The Netdiag of central smoothly and Netdiag of the branch: ****************************** DC .... Failed Test List Failed to enumerate DCs by using the brwoser [ERROR_NO_BROWSER_SERVERS] ****************************** If I go to My Network Places to browse the Microsoft Windows Network I get the domain but it takes 30 seconds, but if I double click I get the error: ****************************** You do not have access to DOMAIN. It may not have permission to use this network resource. Please contact the administrator of this server to check if you have permission. The list of servers for this workgroup is not available at this time. ****************************** I have a domain based Widows in 2003 in the central DCs x32, DC Windows 2003 R2 x64 in delegation andMembers ServersWindows Server 2003 R2 x32 in the central. Thanks.

Do you have WINS installed? Even though it is legacy so is the browse list so I tend to install it.Is the computer Browser Service started on your master browser?The browse list won't be avaliable if you are connecting via VPN. Not sure of your setup but you did mention a VPN.Cheers,Laralforbes

I agree with Lara. If it is a site to site VPN link, the browser service should work as long as Netbios over TCP/IP is enabled on the server in the remote site and WINS is running. If you are runnng a WINS server in the branch site it needs to replicate with the one at central (ie both sites must see the same WINS data). A far as the browser service is concerned, your setup is simply two segments joined by an IP router. It does not know or care about the VPN link if it is configured as a site to site. What are you using for the VPN routers? If they are hardware routers all should be OK. If they are RRAS servers, make sure that Netbios over TCP/IP is disabled on all interfaces except the LAN connection. The most common problem with browser failures(after Netbios over TCP/IP being disabled altogether)is a multihomed browse master (ie the machines has Netbios over TCP/IP enabled on more than one interface).Bill

Bill Grant said: I agree with Lara. If it is a site to site VPN link, the browser service should work as long as Netbios over TCP/IP is enabled on the server in the remote site and WINS is running. If you are runnng a WINS server in the branch site it needs to replicate with the one at central (ie both sites must see the same WINS data). A far as the browser service is concerned, your setup is simply two segments joined by an IP router. It does not know or care about the VPN link if it is configured as a site to site. What are you using for the VPN routers? If they are hardware routers all should be OK. If they are RRAS servers, make sure that Netbios over TCP/IP is disabled on all interfaces except the LAN connection. The most common problem with browser failures(after Netbios over TCP/IP being disabled altogether)is a multihomed browse master (ie the machines has Netbios over TCP/IP enabled on more than one interface). Bill Thanks Bill. I have had a VPN for years and never got the browse list on my home computer but I will look into what you said about TCP/IP enabled on more than one interface. I run ISA on a multi-homed machine so that is my VPN and I can map via netbios shares so netbios is working. The browse list never shows up in My Network Neighborhood.Cheers,Laralforbes

Ok, solved. I have themaster browser Automatic only the DCS and is running to first. Ialso enable themaster browser in Member Servers and Computers?

Hi Lara, That is even harder. If it is a site to site link and all machines are domain members, browsing works just like any routed network. A dialup-style VPN connection from a non-domain joined PC doesn't work. I remember looking into this some time back, even to the extent of monitoring the traffic. The basic problem is that the client tries to access the Domain Master Browser using the Netbios special name <domainname 1B> . The trouble is that, if it is not a domain-joined machine, ir uses the wrong name for the domain! I couldn't work out a way to force it to use the right one.Bill

Bill Grant said: Hi Lara, That is even harder. If it is a site to site link and all machines are domain members, browsing works just like any routed network. A dialup-style VPN connection from a non-domain joined PC doesn't work. I remember looking into this some time back, even to the extent of monitoring the traffic. The basic problem is that the client tries to access the Domain Master Browser using the Netbios special name <domainname 1B> . The trouble is that, if it is not a domain-joined machine, ir uses the wrong name for the domain! I couldn't work out a way to force it to use the right one. Bill Ahh that is what I remembered from my research too. I don't need browsing as long as mapping works anyway.ThanksLaralforbes

hi.. do u need. 1. go to control panel(click) 2. add/remove (click) 3. windows commpaet wiazard (click) 4. managemnt and Monitor tools (click) 5. did u add now WMI windwos installer provider WMI SNMP Provider Simple Netwrok management protocol best regard semih soykal from turkey