DC and separate WINS

Is it advisable to have multihomed Win2k Adv Svr DC? If not, how do I go
about removing it safely.
I have an application that is running on NT and the users (5) need to
connect to DC. I have a separate DNS/DHCP/WINS server (B). All these 5
workstations as well as other workstations obtain information from server B.
And workstation are joined to domain. But everytime when users login, they
get "Domain controller not found". Upon checking WINS info on server B, I
see Domain name is listed as workgroup name against IP of that user
workstation and also domain name as dc & master browser is in released
state. I did setup WINS on DC so that it can replicate with server B. No
avail.

How to solve this problem?

Thanks
Kris

Yes, having a multihomed DC is a bad idea. It causes all sorts of
problems. It is probably what is causing your master browser problem,
because the domain master browser (which is the DC) has two IP addresses
linked to its name.

Checking WINS will not solve your "Domain Controller not found" problems.
Windows 2000 does not use Netbios names to find a DC (although NT did).
Clients find the logon server through DNS. The multihomed DC can cause this
sort of thing as well, because again there are two IP addresses associated
with the server's name.

You need to disable Netbios over TCP/IP on the "extra" interface in the
DC. Check that there are no left-over entries in WINS afterwards. You also
need to prevent the DC from registering the extra IP address in DNS.

"Krishna" <(E-Mail Removed)> wrote in message
news:%23J$(E-Mail Removed)...
> Is it advisable to have multihomed Win2k Adv Svr DC? If not, how do I go
> about removing it safely.
> I have an application that is running on NT and the users (5) need to
> connect to DC. I have a separate DNS/DHCP/WINS server (B). All these 5
> workstations as well as other workstations obtain information from server
> B.
> And workstation are joined to domain. But everytime when users login, they
> get "Domain controller not found". Upon checking WINS info on server B, I
> see Domain name is listed as workgroup name against IP of that user
> workstation and also domain name as dc & master browser is in released
> state. I did setup WINS on DC so that it can replicate with server B. No
> avail.
>
> How to solve this problem?
>
> Thanks
> Kris
>
>

Thanks Bill. I will work towards removing another IP address.
Do you think after doing that my NT workstation will be able to find DC even
though WINS, DNS and DHCP info is linked to another server?

Sorry for the delayed response.

It should be OK as long as WINS is working properly. NT uses the special
Netbios name <domainname 1C> to find a DC and it should be able to get that
from WINS if it is set up as a WINS client. A query to WINS should return
the IP of the logon DC.

"Krishna" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks Bill. I will work towards removing another IP address.
> Do you think after doing that my NT workstation will be able to find DC
> even though WINS, DNS and DHCP info is linked to another server?
>
> Sorry for the delayed response.
>

But Bill, in WINS server, DC is in released state. How will NT workstation
will be able to pull?