xp client does not run login script on 2003 server

We have a problem with our Windows XP Pro clients not
running login scripts on a 2003 AD Domain Controller.
The XP client **SEEMS** to login to the AD domain
controller just fine. i.e. a bad username or password
results in a failed login.
However the machine does not run the login script assigned
to the user account.
In addition once logged in they are unable to access any
resources on the AD server itself or any server in the
domain. Any attempt to view resources shared on the server
results in a request for a username and password. No
username and password works at this prompt.
If we take the exact machine and connect it to a Windows
2000 Server based network it logins in fine and runs it's
assigned login script with no problems.

Our AD 2003 server runs perfectly well with our Windows 98
clients which are able to login, run their login scripts
and access resources just fine. This problem is restricted
to only WinXP clients.

Any ideas would be appreciated. I have searched for the
problem and been unable to find anything close to it. Feel
free to email me with your comments.

"Charles" <(E-Mail Removed)> wrote in message
news:1ac7901c44f02$4ce6f5b0$(E-Mail Removed)...
> In addition once logged in they are unable to access any
> resources on the AD server itself or any server in the
> domain. Any attempt to view resources shared on the server
> results in a request for a username and password. No
> username and password works at this prompt.
> If we take the exact machine and connect it to a Windows
> 2000 Server based network it logins in fine and runs it's
> assigned login script with no problems.

What Windows2000 Domain? A machine cannot be a member of two Domains at the
same time. It will only login to and run login scripts from a Domain it is
actually a member of.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

I suspect the domain login is failing, and the machine is coming up using
cached credentials. Check the event log on the client to see if this is in
fact the case.

If W98 clients log in OK, it is probably the DNS setting on the client
that is the problem. Make sure the client's DNS setting points to the local
DNS server which has the AD records. W2k/XP clients will use DNS to find the
login server. W98 clients use its Netbios name.

"Charles" <(E-Mail Removed)> wrote in message
news:1ac7901c44f02$4ce6f5b0$(E-Mail Removed)...
> We have a problem with our Windows XP Pro clients not
> running login scripts on a 2003 AD Domain Controller.
> The XP client **SEEMS** to login to the AD domain
> controller just fine. i.e. a bad username or password
> results in a failed login.
> However the machine does not run the login script assigned
> to the user account.
> In addition once logged in they are unable to access any
> resources on the AD server itself or any server in the
> domain. Any attempt to view resources shared on the server
> results in a request for a username and password. No
> username and password works at this prompt.
> If we take the exact machine and connect it to a Windows
> 2000 Server based network it logins in fine and runs it's
> assigned login script with no problems.
>
> Our AD 2003 server runs perfectly well with our Windows 98
> clients which are able to login, run their login scripts
> and access resources just fine. This problem is restricted
> to only WinXP clients.
>
> Any ideas would be appreciated. I have searched for the
> problem and been unable to find anything close to it. Feel
> free to email me with your comments.

Yes Phillip, If we remove the machine from the windows
2003 server domain and join it to a Windows 2000 server
domain it then runs login scripts on the windows 2000
server domain perfectly.

Please note these domains are on physically separate
networks. Both use DHCP and in both circumstances the XP
client receives a valid ip address from the AD Domain
controller. All the XP network diagnostics work fine with
no problems found.


>-----Original Message-----
>
>"Charles" <(E-Mail Removed)> wrote in message
>news:1ac7901c44f02$4ce6f5b0$(E-Mail Removed)...
>> In addition once logged in they are unable to access any
>> resources on the AD server itself or any server in the
>> domain. Any attempt to view resources shared on the
server
>> results in a request for a username and password. No
>> username and password works at this prompt.
>> If we take the exact machine and connect it to a Windows
>> 2000 Server based network it logins in fine and runs
it's
>> assigned login script with no problems.
>
>What Windows2000 Domain? A machine cannot be a member of
two Domains at the
>same time. It will only login to and run login scripts
from a Domain it is
>actually a member of.
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>
>.
>

Bill,
No events are logged in the XP clients event log. The
client is not using cached credentials since I can logon
with any of over 1500 accounts and no errors in user name
and/or password and/or Domain Name will permit a logon.
The XP client receives it's ip address via DHCP from the
AD DC.
NSLOOKUP from the XP client does not report any problems
and is using the AD DC as the primary DNS server, backup
DNS is from another AD DC.
Thank you both (Phillip and Bill) for your responses so
far, heres hoping an idea pops up that helps me resolve
this issue.


>-----Original Message-----
> I suspect the domain login is failing, and the machine
is coming up using
>cached credentials. Check the event log on the client to
see if this is in
>fact the case.
>
> If W98 clients log in OK, it is probably the DNS
setting on the client
>that is the problem. Make sure the client's DNS setting
points to the local
>DNS server which has the AD records. W2k/XP clients will
use DNS to find the
>login server. W98 clients use its Netbios name.
>
>"Charles" <(E-Mail Removed)> wrote in message
>news:1ac7901c44f02$4ce6f5b0$(E-Mail Removed)...
>> We have a problem with our Windows XP Pro clients not
>> running login scripts on a 2003 AD Domain Controller.
>> The XP client **SEEMS** to login to the AD domain
>> controller just fine. i.e. a bad username or password
>> results in a failed login.
>> However the machine does not run the login script
assigned
>> to the user account.
>> In addition once logged in they are unable to access any
>> resources on the AD server itself or any server in the
>> domain. Any attempt to view resources shared on the
server
>> results in a request for a username and password. No
>> username and password works at this prompt.
>> If we take the exact machine and connect it to a Windows
>> 2000 Server based network it logins in fine and runs
it's
>> assigned login script with no problems.
>>
>> Our AD 2003 server runs perfectly well with our Windows
98
>> clients which are able to login, run their login scripts
>> and access resources just fine. This problem is
restricted
>> to only WinXP clients.
>>
>> Any ideas would be appreciated. I have searched for the
>> problem and been unable to find anything close to it.
Feel
>> free to email me with your comments.
>
>
>.
>

Try changing it to a workgroup, reboot and the with it connected to the 2003
server, connect to that domain.