No Domain Server at logon

Well, ya know, there's a lot to know!

List reads:

Got same client software on (Client for MS Networks et al) each machine
Got file and print sharing enabled
Got domain master disabled on all except PDC
Got TCP/IP on all machines (Don't run any other protocols - unless you really need)
Got look for DHCP to get IP address on all macines
DHCP allocation OK on PDC
Hubs? Are the ME's on one hub - check crossover
Backwards compatibility - we've got 9x, NT and 2k all on net and all PARTICIPATING IN DOMAIN SECURITY - which is what really counts when adding a box to a domain
Got accounts for all users set up - no access restrictions, time restrictions etc - of course you should have these in Groups, just labouring the point
Cables - you wire 'em? if all cabled, swap some cables from OK machines to ME's
DNS disabled?
There,s a lot more you could check......

Quote:

---

Originally posted by b4uc1i81:
You can join the ME boxes to the domain. You can also create computer accounts for the machines also, using the computer names.

One thing to check, when logging on with a user name and password, are you using roaming profiles? Are these Administrator accounts?

Try using an account that's qualified to have computers join the domain.
;)

---

PLONK.

Only an NT box will join the domain. Period.

"Machine Accounts
Unlike Windows 9x, Windows 2000 computers that are to participate in a Microsoft network domain require a machine account on that domain." ..per Technet

Machine accounts relate to security and managability. In order to fully administer a 9x machine you need remote registry services installed. In addition, 9x or ME boxes do NOT support the same level of security of NT and will NEVER join a domain. You may see their computer name show up in server manager but they are NOT part of the domain.

I have been following this post because I having the same problem with a Win98 box seeing a win2000 domain.

If a win98 machine can't be part of a domain then why is the win9x client on the win2000 disk?

Is everyone on the network going to have to move to win2000 or are they going to have to stay a workgroup without a domain?

FYI: There is a great tool that comes on the CD in the support/tools folder called NetDiag. It can be used to troubleshoot the whole TCP/IP stack all at once...

Quote:

---

Originally posted by Weazel:
Ok, so is it necessary to install the dsclient software ??? I'm kinda confused on that point. Whats the purpose of the dsclient software?

---

The Distributed File System (DFS) was the beta predecessor to the active directory for Windows NT 4 domains. As far as I know it was never actually released for general use because Win 2k Server was release a short time later. However, at that point it had already spread to many companies. It was originally designed to allow Win 9x/ME machines to access shared resources in the active directory.

If your ME clients no not need to access any shared folders or printers on that domain, they do not need DFS to authenticate on the domain. If they need to access the shared folders and printers, then I am afraid DFS is necessary.

One solution would be to convert to domain to a Win 2k domain and assign rights and privileges to those shared resources through the active directory. Another option would be to upgrade those ME clients to NT or 2000 professional (depending on your 2000 license agreement).

O.K. here's a thought Windows 2000 machines use DNS to resolve host names to IP addresses by default and query the Active Directory. The other O/S's rely much heavier on Netbios resolution, in other words WINS, especially when you can't get the DS client installed. I didn't see any mention of what you are using for name resolution so if you haven't already make sure you install WINS. I have it running on every Active Directory install that still has pre-2000 client machines, Wins doesn't seem to want to go away.