General discussion

Locked

Forcing a W2k Workstation to Domain

By lmiller ·
I need to know how to force a Windows 2000 Workstation to Windows NT 4.0 Domain. It is currently in a Workgroup and I want to add it to my Domain.

I get a Network Identification error...

---Begin error---

Network Identification

The following error occured validating the name "DOMAIN".

The specified domain either does not exist or could not be contacted.

---end of error---


I have been able to add other Windows 2000 Servers and Workstations to the same domain. It seems that, since it is already part of the same Workgroup as the Domain name (I have already tried changing the name of the Workgroup to something else, rebooted, and tried to add it to the Domain).

Can you help?

Thanks,
Larry Miller
lmiller@dykema.com

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Forcing a W2k Workstation to Domain

by cviehweg In reply to Forcing a W2k Workstation ...

First verify that the computer you are trying to attach to the domain is on its LAN. Use the ping utility to verify it can see the IP addresses of other computers on the domain (try the PDC or the DHCP computer).

If you verify that the computer can see the domain, regardless of the domain name (similar names for both the workgroup and domain is not smart) and you have configured all the other network parameters (DNS, DHCP, IP addressing, etc.) it will work. If you need guidance, drop me a note.

Collapse -

Forcing a W2k Workstation to Domain

by lmiller In reply to Forcing a W2k Workstation ...

I have verified that computer is attached to network (LAN). I have pinged both PDC and DHCP Servers.

I can see the domain via Network Neighborhood. I, however, cannot see ping the DOMAIN name directly (i.e. ping DOMAINNAME). I have also made sure that my IP settings are working and have been reloaded twice.

Thanks,
Larry

Collapse -

Forcing a W2k Workstation to Domain

by O/Siris In reply to Forcing a W2k Workstation ...

I suspect you're on the right track with the idea that you had a workgroup name identical to the domain name.

Have you tried removing the network adapter, then reinstalling it, to see if that resets everything?

----------
R??, HDSE*

Collapse -

Forcing a W2k Workstation to Domain

by lmiller In reply to Forcing a W2k Workstation ...

Yes, I did do just that.

Thanks for the response.

Larry

Collapse -

Forcing a W2k Workstation to Domain

by Charles_ In reply to Forcing a W2k Workstation ...

I've had this type of problem too. Usually when first installing W2K, it will not join the domain, but after the install I can usually get it to join. When I've had problems after the fact, usually it's in a secure environment (internal firewalls)and the netbios ports aren't open.

I'd also check your WINS server - or, to make sure it isn't a WINS problem - I'd put the Domain controller in your lmhosts file locally - note the domainname MUST be ALLCAPS (the servername doesn't have to be)
Check out http://www.microsoft.com/technet/support/kb.asp?ID=180094 for detailed info on how to setup the lmhosts file.

This usually also solves the problem if it is a filter/firewall/port/addressing type of problem.

Good luck

Collapse -

Forcing a W2k Workstation to Domain

by Charles_ In reply to Forcing a W2k Workstation ...

Oh - the other thing I've noticed problems with is the computer account in server manager getting confused. If the W2K WKS computername is already there, delete it and recreate it - if it's not there - create it.

Collapse -

Forcing a W2k Workstation to Domain

by lmiller In reply to Forcing a W2k Workstation ...
Collapse -

Forcing a W2k Workstation to Domain

by lmiller In reply to Forcing a W2k Workstation ...

This question was closed by the author

Back to Desktop Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums