WINS Config

ALWAYS put Wins on your site .....You really don`t want to waste Wan Time....Wins is a heavy network user for over 100 clients and for the sake of $2000 it`s not worth the bother..it`s never a good idea to put any name resolution on a remote site unless you have only a small amount of user`s less than 50.....(i personally would NOT even recommend that!!)

Dennis.

I would create a WINS Server on your local LAN and then make this a replication partner with your Corp WINS server. And also configure the CORP to be the Secondary wins box

I would use DHCP to provide the client with the WINS Servers addresses, this means you won't have to visit every machine to change the node type See Q142042 & Q160177
044 WINS/NBNS Servers - add the address of WINS server(s)
046 WINS/NBT Node - configure as 0x8 (H-Node)

You can setup your PCs to register with their WINS (IP PROP.. MANUAL and enter the IP) but DONT!

They would have to register over the WAN and its not worth the performance hit your going to take.

If you have a NT server, set it up and it does everything on its own. There is nothing to it. You can manually put in the IP of your server if you dont use DHCP, but if you do, just tell your IP stack to get the address from DHCP.

HTH

Trent

I agree with answer #2 - local WINS machine at each site, with the corporate machine as secondary. Set them up as replication partners with the Corp machine, and set the timing to replicate after hours (it will generate a fair bit of network traffic).

When at all possible you want to do your name resolution locally. Apparently someone must be having problems connecting somewhere.

Turn on a wins service on your local network. You might want to also consider a LMHOSTS file.

1) how fast is your link to CORP? that is paramont.
2) how many BDC's in CORP and do you have the credentials (Doamin authority to create another one? Microsoft will not support ANY site no mater how big - with more than 25 WINS servers. WINS databases are too easy to corrupt.
Do you currently have a BDC on site? If not you're already going to CORP for all your authentications anyway - have them configure you for DHCP & point the clients to the correct servers (and tell them to do their jobs...). If your site's got static IP's then to heck with it configure the client's like they say - they don't seem to be worried about bandwidth.

First, any MS WAN engineer would say "as little of WINS servers as possible" This is because manging replication between multiple WINS servers gets more difficult with each addition. However the true answer lies with in the link speed you have to the corporate WINS server. If you have greater that 128k you DON'T need one locally. A WINS request is only about 40 bytes in size and once an address is in local cache, it will stay there until the pc is rebooted. If you don't build one than Yes you do need to point you servers to the corporate WINS as they are clients too. Managing WINS pretty much sucks, so don't do it if you dont need to

I am not quite sure where some people get the idea that WINS creates traffic as the computer talks to it when it turns on turns off and the default renewal interval is 4 days so that is not a lot of traffic. Also if you use DHCP the WINS registration is automatic. I don't know about your network but in my company you don't just go around settig up any kind of servers without there OK. I belive if they felt having a WINS server at your location made sense then they would have said so.

The long and short go ahead and point to theirs the cost is ZERO IF you start having bandwidth problems etc...Then you could revisit the question of doI need my own.

It would be a waste not to try it without first and see what happens withou WINS your machines have been doing network broadcasts that probably eat more bandwidth than the WINS ever will!