connect to domain

Posted on 2007-12-07
Last Modified: 2013-12-23
need to put a windows nt 4 workstation in a native w2k domain. haven't found it yet. think to remember thats impossible on native w2k dc. does anyone know a way if its possible?
Question by:soki
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Expert Comment

ID: 20426709
You can add Windows NT4 workstations and servers to the domain, but they cannot be domain controllers.
LVL 85

Accepted Solution

oBdA earned 500 total points
ID: 20428597
That should be no problem, but make sure that NetBIOS over TCP/IP is enabled at least on your DCs, and you should have a WINS server (used at least by the DCs and the NT4 machines) to make sure the NT4 machines and the DCs will find each other and communicate properly.
LVL 37

Expert Comment

ID: 20439159
you need this extension.

Active Directory Extension for Windows NT 4.0

"Microsoft has developed extensions for the Windows® 95, Windows 98, and Windows NT® 4.0 operating systems that allow those client platforms to take advantage of features provided by the Windows 2000 Active Directory service. These client extensions were developed for customers who want to deploy Windows 2000 Server in environments with Windows 95-, Windows 98-, and Windows NT 4-based client workstations."

hope it helps,
Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

LVL 85

Expert Comment

ID: 20440046
The AD extensions aren't necessary to join an NT4 machine to an AD domain.
NTLM v2 has been available in NT4 since SP4, and the other components in the AD client are just add-ons, but not a requirement.

Author Comment

ID: 20440618
hmm. have installed sp6a. with ipconfig /all i can see the compuertname.domain. i also can make network connections with my own user/pw. when i try to change the computer from workgroup to domain it says: it's impossible to connect to domain controller. contact your admin to check the account.

useing a german version so the above message is a translation
LVL 85

Expert Comment

ID: 20440977
Do you have a WINS server in your AD domain?
If not, install one on your DC, make sure NetBIOS over TCP/IP is enabled on all your machines, and let your machines point to the WINS server in the TCP/IP configuration.
With the NT4 member, you need to use the NetBIOS domain name to join (enter "set userdomain" in a command window on the DC if you're unsure about this), not the FQDN.

Author Comment

ID: 20441003
have all needed servers to enter my domain. installed all protocols needed. no effect. changed the hardware - no effect
LVL 85

Expert Comment

ID: 20441096
You're not really answering my questions.
1. Do you have a WINS server installed and running on your DC(s) (is the WINS service showing as running in the Services MMC)?
2. Are all machines in your domain (especially the DCs and the NT4 machine ) pointing to the machine(s) running a WINS server?
3. Are you using the NetBIOS domain name when trying to join the domain?
4. NetBIOS over TCP/IP doesn't require an extra installation; what exactly do you mean with "installed all protocols needed"?
To the basics:
5. Can you ping the DC by name and IP address from the NT4 workstation?
6. Did you install the NIC in NT4 during setup, or did you skip the NIC installation in setup and installed the NIC driver later?

Author Comment

ID: 20441162
yes, running WINS on my DC and is up. all machines pointing to wins server. installed tcpip and netbios protocol. can ping any ip adress in my domain. installed my NIC later, reapplyed SP6a then
LVL 85

Expert Comment

ID: 20442465
This could be the issue:
> installed my NIC later
NT4 never really recovers completely if TCP/IP isn't installed during setup.
Reinstall from scratch, and when it comes to installing the NIC, choose the Microsoft Loopback Adapter if you can't install the regular NIC drivers (because they need SP6 or whatever.) Once you've installed the physical NIC and assigned an IP address, you can remove the Loopback adapter again.

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I'm a big fan of Windows' offline folder caching and have used it on my laptops for over a decade.  One thing I don't like about it, however, is how difficult Microsoft has made it for the cache to be moved out of the Windows folder.  Here's how to …
Learn about cloud computing and its benefits for small business owners.
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor ( Top Charts is a view in which you can set seve…
Add bar graphs to Access queries using Unicode block characters. Graphs appear on every record in the color you want. Give life to numbers. Hopes this gives you ideas on visualizing your data in new ways ~ Create a calculated field in a query: …
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question