Windows Forum

Ask something
Discussion Locked

Network browsing problem

0 helpful
5 replies

by info

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have client with 25 workstations running windows NT 4.0 and exchange 5.5. Recently they added more workstations. They are limited on routable IP addresses. I installed linksys DSL router to expand internet access. I connected 8 workstations to thelinksys. I have made internet connection work fine. But there is a problem of browsing the internal network. I can not see other workstations and servers which they are connected to the different hub in my network neighborhood. I can access some of them by the way of find computer. I can not access exchange server but I can access NT server. Also there is a network printer which uses one routable IP address and when I am able to connect to it from one of the NT workstations connected to the DSLrouter but when the workstation reboots the printer is not accessable and needs to be reconfigure again. I would appreciate any suggestion on this issue.

5 replies

by vickie

hi there
You've not gone into detail about how your name resolution is happening here, but since you don't specifically mention a WINS server I'm assuming that you were relying on broadcast to resolve your netbios names. Broadcasts are not passed over a router, so as soon as you introduced one, the PCs on one segment wouldn't know about the ones on the other side when they came onto the network. All you need is a way for all PCs to resolve each others' netbios names across the network. If yourPCs are using static addressing, you could put the Ip addressing info of each one into each others' local lmhosts file, but if they're using DHCP (or in fact in most cases) the best way to resolve the names is to set up your exchange server (or another NT server if you have one) to run the WINS service. That way they will dynamically register on boot up onto the network and resolve each others' names. All you need to do is make sure the ones on the non-WINS side have a route to the WINS servers' IP...

hope that helps
Vic

This discussion is closed to new replies.