General discussion

Locked

Win 2K Svr login domain name question

By Ed2967 ·
I'm a student of Win 2K & 2K3 server, and this my be a rediculous question.
After a recent move from an Win NT4 server to a Win 2K server(AD), My Win NT & Win 98 PCs wouldn't correctly login to the same domain name(Domain.com)format(without a failure to find domain error, but they were visible, but file transfer was iffy). The Win 2K & XP Pro PCs logged in perfectly. I have noticed that Win 2K server is really slow & sluggish. Browsing the network from the server could take a minute to display computers. To get the NT4 & Win98 PCs logged in, I finally found that I had to use the Domain alone (no .Com). I tried a Win 2K WS on Domain only & it seems faster too.

My question is, should all workstations in the domain login using Domain or Domain.com?
Thanks
Ed

This conversation is currently closed to new comments.

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

All Comments

Collapse -

by azizhakim In reply to Win 2K Svr login domain n ...

As you know winnt4 and earlier os use netbios and wins for name resolution.if you have these clients you will need wins for name mapping.Your win2000 and Xp Clients are good because those clients use dns for name resolution and name registration.as far as your question goes,legacy clients log on using Netbios domain\username to log on as and with 2k and xp domain.(Com)\username to log on.Goes back to my answer earlier about name resolution.Hope this helps

Collapse -

by Ed2967 In reply to

I have a follow up on this old post. It seems that my original question was because of one XP Pro pc, that had originally been a client on our Win NT 4 server, domain name "domain". When it is connected and active on our newer server under Win2K Server(domain name "domain.com)it still chooses to be listed under "domain" while all the newer clients are listed under "domain.com". Both domains can be seen when browsing 'Microsoft Windows Network' from any client, with the old WinXP Pro pc shown alone in the "domain". Efforts to introduce it to the new domain have failed. Its on the shelf for now.
Thanks.

Collapse -

by Ed2967 In reply to Win 2K Svr login domain n ...

Ok, I have a follow up question then, it may be silly & obvious, but I'm still searching text books and tech support groups for an answer/ explanation/example. In my Win 2k server, when browsing the network, in Microsoft Windows Network, is listed Domain and Domain.Com. The server is listed under Domain, while my workstations(logged in using Domain.Com)
are displayed under Domain.Com Since I have changed to the Domain login for the NT4 Pro and Win 98 PCs, they also display under the Domain. Which is correct? A Win2K Pro PC I have changed to Domain(from Domain.com) seems faster on the network. Ther server browses Domain & lists all computers instantly with no delay, while it may take 45 seconds to populate my Domain.com browse. It looks like I need to loose th .Com.
Thanks

Collapse -

by CG IT In reply to Win 2K Svr login domain n ...

humm after reading your question and comments, what I'm seeing is 2 domains listed in DNS. <Domain> AND <domain>.com. You shouldn't have 2 unless you have subdomains under the root. If you have a root domain AND subdomains, each needs a zone and the authoritative NS for each one [can all be on one DC]. Also as the first answer stated, NT & W9X needs NETBIOS and WINS to work on a W2K based and above network. [also, if you've got NT servers in there your W2K AD DC needs to be operating in Mixed Mode.

Open up DNS and tell us what you got in there e.g. from the general tab, Zone of Authority tab.

Also are you running DHCP services? if so, hows that configured? [e.g. DHCP options listings for name servers, routers, etc].

might be a simple matter of clients getting the wrong info out of DHCP and are looking for the wrong DC to authenticate with.

Collapse -

by CG IT In reply to

man that last sentence is wrong. sheesh.

Collapse -

by CG IT In reply to

and wow did I really screw up my suggestion. Where's the coffee!!!

If you browse my network places and see "2" domains [the DC on one and clients on another] what that indicates is clients are NOT logging on to the domain [same as having a domain and workgroup show up under my network places]. so for the sake on not confusing myself I'll change the references. W2K AD domain = domain. anything else that shows up NOT under domain is workgroup.

so, if NT and W9X clients don't show up under Domain in my network places then they aren't part of the domain and have defaulted to workgroup. That would explain the long log in times or no log in [provided you have NETBIOS and WINS running in the W2K AD domain and it's in mixed mode so NT and W9X computers can actually contact the W2K AD domain.

Rejoin the NT and W9X computers to your domain. should solve the problem

Collapse -

by Ed2967 In reply to

I have a follow up on this old post. It seems that my original question was because of one XP Pro pc, that had originally been a client on our Win NT 4 server, domain name "domain". When it is connected and active on our newer server under Win2K Server(domain name "domain.com)it still chooses to be listed under "domain" while all the newer clients are listed under "domain.com". Both domains can be seen when browsing 'Microsoft Windows Network' from any client, with the old WinXP Pro pc shown alone in the "domain". Efforts to introduce it to the new domain have failed. Its on the shelf for now.
Thanks.

Collapse -

by Ed2967 In reply to Win 2K Svr login domain n ...

This question was closed by the author

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

Related Discussions

Related Forums