[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 702
  • Last Modified:

Can't see user VLAN from Server VLAN

After setting up VLANs we can no longer see computers on the users VLAN from the server VLAN.  I was told to install WINS and that would fix the issue, and it has.  The problem being is now I am being told that they want to do away with WINS and only use DNS.  

Do I have to do anything specific with DNS to make it talk between VLANs?  It seems WINS fixed this problem, but if they are not going to allow me to run WINS anymore I am not sure how to fix this problem.

Also when I take out the WINS setting I can't go to My Network Places and see all our computers and servers.  I was told that this all can be done with DNS, but I am not sure how it is done.  Any help would be great!
0
eServ
Asked:
eServ
  • 4
  • 2
1 Solution
 
ChiefITCommented:
The issue you are running into is Netbios is not a routeable program. Netbios carries the information for the master browser. The domain master browser is used to populate My network places. Netbios broadcasts from the clients and servers on one site will not see clients and servers on the other VLAN because Netbios will not go through a VPN tunnel, across NAT, to different subnets, or over VLAN.

You can set up a WINS connection between the two sites MASTER BROWSERS. Or you can set up a LMHOST RECORD between the two master browsers.

The default ports for file and print sharing and the master browser are similar. I think the browser service will populate using the SMB ports, and I know it will populate over the old school way to populate the master browser.

((((UNFORTUNATELY)))) the master browser service and its use of netbios broadcasts HASN'T changed a bit since the NT4 server era.

WINS and NETBIOS BROADCASTS ports:
Netbios /WINS    port 137   UDP and TCP
Netbios datagram ports 138 UDP
Netbios datagram port 139 UDP

SMB (server Message Block) File and print sharing ports:
SMB port 445 UDP and TCP
Netbios datagram port 139 UDP

I have helped MANY folks get over this issue. So, just google search ChiefIT + Master + Browser. Or EE search for this.
0
 
ChiefITCommented:
Any additional questions please ask.
0
 
eServAuthor Commented:
Thanks for the help ChiefIT

From what I have looked over to fix this problem I need to setup one Master Browser on each VLAN correct and one Domain Master Browser?  Then I need to use the LMHOST RECORD to link between the VLANs?

If I complete this then I should be able to see all the computers on the network via My Network Places?
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
ChiefITCommented:
Three VLANS:

Main VLAN: One domain master browser and hopefully one backup browser.
Second VLAN: One Master browser
third VLAN: One Master browser.


Enable LMHOST lookup on each nic of these machines.
Now create an LMHOST file that includes all of these machines.

LMHOST is the WINS version of the HOST file that belongs to DNS. So, you are cheating in a way. Instead of WINS you are using the LMHOST to connect your master browsers between sites. You will not have a WINS server, but the LMHOST acts as a WINS hookup between the machines.
0
 
ChiefITCommented:
You could also unblock port 137, 138 and 139 between VLANS. I think that will work for you as well.
0
 
eServAuthor Commented:
Thanks again ChiefIT!
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now