"Olaf Engelke [MVP]" wrote:

> Hello,
> AJA wrote:
> > I have one DC in my network at it is wearing all the hats.  WINS,
> > DNS, DHCP & NAT -- I have locked down my external NIC (connects to
> > cable) by having NO client No file and print sharing, No DNS
> > registration, No NBT.  My wins server wants to always set itself up
> > on the external NIC and I get a red X by the WINS servers external IP
> > -- I want it to set WINS  up on my internal NIC not external.  Is
> > there anyway to do this while still only having one server on the
> > network.
>
> which operating system you are using?
> WINS on a multihomed machine is not a very good idea.
> Since WINS is binding to the first network interface in the system, the
> sequence of the network adapters is playing a role.
> If you move the internal NIC to the first position on the Adapters and
> Bindings window, this could work.
> (on Windows Server 2003 in Control Panel/Network
> Connections/Advanced/Advanced Settings)
> At least does it here on a Windows 2000 based WINS Server.
> Best greetings from Germany
> Olaf
>
>