Does there have to be a WINS server at each site?

[YokyDoky]

This agency has 50-plus remote sites around the state. All workstations log in to one domain - PDC is in central office. Some remote sites have a server which is file/DHCP server. Workstations at sites w/o server obviously have fixed IP addresses. In current config, all workstations and remote servers point to one WINS server in central office. There is not now, nor has there ever been NetBIOS name resolution across the WAN. Why? Does there have to be a WINS server at each remote site? NT4 servers only, mix of NT4, W95 and W2K workstations. Y. Doky - "Manager" of Systems

"Works well under constant supervision or when trapped like a rat in a pipe."

 

[lifto]

No, you only need one Wins server but you can run into problems if you have "slow" links.

The workstation needs to know where the WINS server is and be able to get to it. On a statically addressed workstation, there is a "WINS" tab under the advanced option. The IP address of the WINS server needs to be in there. If the workstation is getting its IP address from a DHCP server, the IP address of the WINS server can be supplied by the DHCP server.

The last thing is, why not use just 1 DHCP server for the entire network. You really don't need more than 1 or 2 (as a backup for your primary DHCP server) unless you are on a very low band width WAN.

 

[YokyDoky]

Okay, thanks, but this is how it is configured now and it doesn't work. Some of the remote sites have DHCP servers for the reason you cited and other reasons besides - some valid, some not. If your assertion is correct, our NetBIOS name resolution problem must lie beyond our configuration. The state owns and maintains everything on the other side of our routers, so who knows what they've got there. Y. Doky - "Manager" of Systems

"Works well under constant supervision or when trapped like a rat in a pipe."