<snip> Another faulty configuration is setting a remote IP address (in this
example, Wins2) as Primary while setting the local WINS (Srv1) as Secondary.
In this case, Srv1 will eventually stop refreshing its NetBIOS lease at
Wins2, and will begin registering locally. Depending on your WINS
replication scheme, this may cause connection problems. <snip>
Setting Primary and Secondary WINS Server Options
http://support.microsoft.com/kb/150737/EN-US/
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Hello,
>
> We have sites in the US and in Europe. Our WINS infrastructure
> consists of one WINS server in the US for all US servers and
> workstations and one in Europe for all servers and workstations in
> Europe. What we are finding out is that all workstations and servers
> set themselves up to use the US WINS server as the primary and the
> Europe server as the secondary even if we specifically put the Europe
> server as the primary. This happens if we set DHCP to use it as the
> primary or if we hard code the WINS servers on the Workstation/Server.
> After boot up, I run ipconfig /all and it shows the US server as
> primary and the EU server as secondary. If I do an ipconfig /release
> then /renew, it switches the servers back to the correct settings, EU
> as primary and US as secondary.
> Has anyone else experienced this or know of a way to troubleshoot this?
> We tried installing another WINS server local to the site and it still
> pulls the US server as the primary after reboot. I have trying
> reinstalling WINS and DHCP on the EU servers with the same problems.
> WINS isn't used much in our environment as we are 99% windows 2000/xp
> clients but we don't want EU workstations and server contacting the
> US WINS server if possible.
> This happens on almost every Windows Server 2003 SP1 and Windows XP
> Workstations SP2.
> Any help would be appreciated.
>
> Thanks,
> Kevin
>