Windows XP cannot login Windows 2000 domain

[Chris]

I have a Windows 2000 domain setup with a Windows XP Pro
machine logging on a secure workgroup. Windows XP has
access to the Windows 2000 domain through the workgroup, I
have setup a user account(administrator account) on the
Windows 2000 server and the Windows XP machine with the
same Username and Password to enable proper access.
However, I tried to change the user account password on
the Windows 2000 server and the Windows XP machine using
the same password on both and I was no longer able to log
on to the domain from the Windows XP machine. I tried
setting up new accounts with administrator account rights
on the Windows 2000 server and Windows XP machine without
any success in logging onto the domain. However, if I use
the "original" account I setup on the server and on the
Windows XP machine I am able to log on the domain from the
Windows XP machine. Shouldn't I be able to just change
passwords on Active Directory for user accounts? I have
other networks setup with similar operating systems. This
however is the first I have encountered with a WinXP
machine giving me problems with something as simple as
changing passwords....could it be that it's logging in
through a secure workgroup???? I would really appreciate
any suggestions...
Thank you,
Chris

 

[none]

what do you mean by a secure workgroup?
Have you joined the xp system to th w2k domain?
The two users you create are two different users with the
same name.
Full user account names are domain\username or
systename\username.

 

[Chris]

What I mean by a secure workgroup is that the WinXP
machine is able to log into the Win2000 Server domain
through the workgroup name.
Ex. Windows 2000 Server (Domain Name): Central
Windows XP Pro (Workgroup Name): Central
I was able to log in when I made the same administrator
account on the WinXP as on the Win2000 Server. However,
when I change the password or make a new account...I am
not able to log on the domain from the workgroup. Very
frustrating? Any ideas?
Chris

 

[Chris]

I had difficulty joining the domain, therefore I decided
to logon through a workgroup. Should it not work? I have
this setup at other sites and it works.

 

[John LeMay]

I had difficulty joining the domain, therefore I decided
to logon through a workgroup. Should it not work? I have
this setup at other sites and it works.

I'm going out on a limb here and say no, this won't work. I doubt you are
actually logging into the domain. Do you have domain login scripts that
run when you login so you can verify you are logged into the domain?

I think you need to revisit the issue that prevented you from joining the
domain in the first place. Off the top of my head, did you setup the XP
client to use the DC as it's DNS server? Can you tell us what error you
get when you try to join the domain?

--
John LeMay
kc2kth
Senior Technical Manager
NJMC | http://www.njmc.com | Phone 732-557-4848
Specializing in Microsoft and Unix based solutions

 

[Cary Shultz]

-----Original Message-----
I had difficulty joining the domain, therefore I decided
to logon through a workgroup. Should it not work? I have
this setup at other sites and it works.



.

Chris,

I can not tell you how to do things, so I will not. I
just question why you have a Domain Controller if you are
going to be using WORKGROUPS. You could just as easily
spare yourself ( and your client ) the time and expense.
Anyway, I am sure that there is a good reason that you
have not mentioned.

Is DHCP handing out IP Addresses? It does not matter if
the "DHCP Server" is the WIN2000 Server, a Router or the
Firewall. It can hand out additional information - such
as WINS Server information( Options 044 and 046 in Windows
NT and WIN2000 and WIN2003 DHCP ) , DNS Server information
( Option 006 and 015 ), etc. Is the DHCP Server handing
out the L O C A L DNS Server information? Meaning, the IP
Address of your local WIN2000 DNS Server and not the IP
Address of your ISP's DNS Servers? WIN2000 and WINXP are
extremely dependent upon DNS to find Domain Controllers.
I guess that it does not even need to be Microsoft WIN2000
or WIN2003 DNS. I guess that it could be BIND 8.2.2 or
above. The all important factor would be the support of
SRV records....

Anyway, verify the DNS information that your XP client is
receiving. Do an ipconfig /all to do this....

HTH,

Cary