Discussion Locked

Win 98 will not join a Win 2K domain?

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have set up a Win 2K server DC file server and had intended to use the existing Win 98/95 workstations to work within the domain but cannot get them to join. Error indicates no domain is present at login. Win 2K Pro systems join without error and there is no indication of a problem in the event log. Am I missing something? I know this arrangement was possible with Win NT 4.0 and assumed the backwaard compatability with Win 2K. Just to eliminate the obvious I've already checked the hardware and lines, and peer to peer works fine.

9 replies

by tony.colgrove

You might have a name resolution problem. Are you running WINS? Also you can check and make sure you have NETBIOS over IP enabled on your Win2K servers. Win9x only know how to speak via Netbios names. Use WINS and have your Win9x and 2K machinesregister with WINS, and you should be okay. If you dont want to use WINS, you should enable NETBIOS listening on your server. Goto your WINS tab (LAN settings > IP > Advanced) and click Enable NETBIOS over TCP/IP.

by popper

WINS is enabled and working and NETBIOS is enabled. Name resolution doesn't seem to be the issue as Windows 2K Pro logs in without error and is using the same paramaters.

by gbainbridge

Which mode is your 2k server running in, Mixed or Native? It in Native mode, only NT workstations and servers (and of course 2k boxes) can be members of a domain.

If you are in native mode, switched to Mixed. This should solve your problem.

To see which mode you're in, and make the changes, go to the run menu, and enter "domain.msc" (without the quotes)

Hope this helps.

by popper

I'm sorry, although a good answer, the momentary hope didn't pan out. The server is running in mixed mode, and just as a referance once changed to native the operation cannot be reversed.

by sgood

I wish these boards had a comment selection vs a answer only one. Did you specify the 98 machines to logon to the 2000 domain? And when you created the machines in AD did you tell them that the coompter accounts were going to be used by a pre-2000 machine?

by popper

Are you refering to the the set up in client for Microsoft Networks in Win 98 or in the configuration of the users login? Client for MSN in Win 98 shows the Domain name and "log onto an NT network" is checked. In Win 2K the user was created using the defaults.

by tony.colgrove

I couple comments to clear up.
1) Win2K Pro, does NOT use Netbios to talk to a Win2K server. It will flow through DNS, and Kerboros authentication. A completing differnet process then Win9x and NT machines. Just because Win2K Pro has no problems, does not mean its still not a name resolution (NBT) problem.
2) Mixed vs Native only affects Domain controllers. Win9x, MAC's, NT4, Win2K can all work on a Native AD domain. Native means NO NT4 BDC's. Native mode opens up features in Universal groups and group nesting. Some NT4 DC's don't have a clue about.

You can try a LMHOSTS file with the Win2K PDC Emulator specified. (This is the first AD server installed, unless you have moved the FSMO role to another DC) Include the #PRE and #DOM:domain fields for the server.

Are you using DHCP, or statically assigning IP's? If you are using DHCP, do your Win9x machines receive a vaild address from the server (this proves again no hardware or lines problem)

The ADClient for Win9xon the Win2K server CD will not help with this either. The client only adds the features to search the directory and allow change password to any DC instead of the PDC Emulator.

by popper

Absolutly a great answer! Although it didn't give me the answer, it did point me in the right direction. silly as it sounds, I was attepting a login using the entire DNS (something.something). This works from the pro login. From the 98/95 systems I instead used the NETBIOS name and they loged in. Your first comment was the bell ringer! Thanks all

This discussion is closed to new replies.