9 replies
by popper
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
by sgood
by popper
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
by popper
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending