XP to NT Networking

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have 15+ Win 98 computers networked through a hub to a server running Win
NT. On startup of the Win 98 computers, the Client for Microsoft Networks
log on dialog box appears asking for Username, Password and Domain name
(although Username and Domain are retained from last log in). Now we have
Windows XP machines to add to network. If I attempt to have them join the
domain, the XP computers ask for a computer name and password, but when they
are entered, it says "Access Denied". Any suggestions?
 
We have 15+ Win 98 computers networked through a hub to a server running Win
NT. On startup of the Win 98 computers, the Client for Microsoft Networks
log on dialog box appears asking for Username, Password and Domain name
(although Username and Domain are retained from last log in). Now we have
Windows XP machines to add to network. If I attempt to have them join the
domain, the XP computers ask for a computer name and password, but when they
are entered, it says "Access Denied". Any suggestions?
Click to expand...

Sounds like a DNS problem, at first glance. Are the Windows XP computers setup
properly for domain access, and domain name resolution?
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html
 
Unlikely to be aDNS problem, as NT domains don't use DNS to locate computers
the same way that 2000/XP domains do. It's perfectly possible to run an NT
domain with no local DNS server.

To see if the server is accessible, type

PING SERVERNAME

(replace SERVERNAME with its name) at a command-pronmpt. If this doesn't
work, chances are you have a TCP/IP config problem.

I may be stating the obvious, but do you realise that the usernames
asked-for once the machine is a domain-member are are those on the server,
not local user-accounts? Local logon is still possible (there should be a
drop-down box allowing you to select logon to the local computer or the
domain-controller) but the domain-logon must be with a domain-account.
 
Back
Top