Discussion Locked

NT (NetBios) throught a router

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I work at a univerisity in PA.. we've segmented our network in two, seperated by a router (student traffic/admin traffic).. however, we need to have some users be able to connect (join) to an NT server. We have multicasting turned off on the routers. What can we do to accomplish this? Thanks.

15 replies

by jamie

You will need to add WINS to the NT servers on both networks or edit your LMHost files.

by Member 35772270

NetBios protocol is not a routable protocol, it is a broadcast protocol. You might want to try puting the sutdents and admin is seporate subnets instead of using a router.

by joshg

Set up WINS on the NT server in each subnet then add that entry to the DHCP server in each subnet this will allow the clients to see then netbios names of the servers. You will have to setup the two WINS servers as Push/Pull partners of each other so that the addresses will get replicated to both subnets.

If you have only a few computers that need access to resources in both subnets the you will probably want to use the LMHOSTS file and maintain the browser list locally.

by ronnonf

NETBIOS is a non-routable protocol that runs from machine to machine asking if that machine is the target. This is intended for small networks. The only way you can get it to cross is via a "bridge."
My advice would be if you are in a Windows NT domain instead of Win2k implement TCP/ip with a WINS server. This should give you some speed and will allow you cross a router. WINS is designed to route Netbios names to ip addresses. You can also implement LMHOSTS files.
The LMHOSTS files are like alocal WINS database. They are stored in the \\system32\drivers\etc directory or \ directory.
The DNS translates ip addresses to FQDN (like www.microsoft.com) this scenario has a future in Win2k.

by craig it mangaer

Definitely your easiest solution is to use LMHOSTS to map the names to the IP addresses. This will work whether they are on the same subnet or not. Only using WINS can be a hit or miss solution but would be necessary if any connections are to a DHCPclient, which I wouldn't recommend anyway.

by gregory w. smith

While TCP/IP would definitely make this easier in most minds, NetBEUI/NetBIOS will work; most current routers will also support bridging. Also, bridging will keep "local" packets localized (not pass them across the bridge), but you would need to enable broadcasts again - a definite performance hit.

by allan

If it's only a few users the LMHost file is the way to go.
If you understand the routers, you could use NAT and map the IP addresses between the subnets.

This discussion is closed to new replies.