Unable to browse Active Directory without server share

I'm new to Active Directory and I was asked to deploy Win2k Active Directory in my network. This is my network environment:
-use VLAN(5 VLAN) whereas the DC will be place at a server VLAN and all other VLAN can access the server VLAN.
-2003 server is used to deploy the Active Directory(1-pdc & MS ISA (proxy mode), 2-bdc, Wins & DHCP 3- BDC and file server)

The deployment process went smoothly and accepted that workstation from other VLAN but I cannot browse the Active Directory network. If I mount a server share i.e. server1share1 it works! Login, DHCP, DNS and Wins work and all terminals can register with the AD. This confuses me. Does this have to do that the fact that we use VLAN? Or is it because I installed MS ISA and AD in one machine? I've added all of the VLAN subnet on the AD services and subnet.
Browsing in the Network Neighborhood style, involves the use of an old system of broadcasts and master browsers. The Master and Backup browsers are based on subnet. So, if you have workstations on a different VLAN, sometimes browsing in this way can present a problem. If you show your users how to leverage AD searches instead you will find that you can locate any device in the domain/AD.

Additional Expert Help: Be sure to check our Answer FAQ for more expert advice. For faster answers, visit ITKnowledge...


Don't let your Active Directory deployment turn into a fiasco. Be prepared by knowing what to expect ahead of time. This checklist provides a step-by-step approach that will help steer you around the pitfalls, while highlighting the best practices for a successful deployment.

Click to view or download a copy of the AD preparation checklist  
This was first published in January 2005

Dig Deeper



Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.



Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:









  • Virtual desktop security guide

    To secure virtual desktops, consider antivirus, certificates and network vulnerabilities. Just remember, VDI doesn't always ...

  • Guide to low-cost desktop virtualization

    In this guide, learn to virtualize desktops without spending more than you would when deploying PCs, and what VDI vendors are ...

  • VDI pilot project guide

    A VDI pilot project should start with a VDI project plan. Know what pitfalls to avoid and test product options to achieve a ...