Windows XP Professional In Windows 2000 Domain Based network.

[Adam]

I had a workstation running Windows 2000 Professional that I used to
monitor and run some admin work from with no problems.

My workstation was replaced by Windows XP professional.

All service packs are installed and up to date.
The computer joined the domain with no problems.
I am a member of the administrators group.

I cannot access most of the computers on the network without being
prompted again for my password over and over, and some of them do not
even allow me to access them.

Nothing like that happens if I go to any Windows 2000 computer on the
network and log in using the same exact profile.

Anyone has any suggestions or can give a clue where to look at or what
am I missing?


I have deleted my profile and reconstructed it again from the Windows XP
computer.


Thank you for any suggestions.

 

[Pegasus]

I had a workstation running Windows 2000 Professional that I used to
monitor and run some admin work from with no problems.

My workstation was replaced by Windows XP professional.

All service packs are installed and up to date.
The computer joined the domain with no problems.
I am a member of the administrators group.

I cannot access most of the computers on the network without being
prompted again for my password over and over, and some of them do not
even allow me to access them.

Nothing like that happens if I go to any Windows 2000 computer on the
network and log in using the same exact profile.

Anyone has any suggestions or can give a clue where to look at or what
am I missing?

I have deleted my profile and reconstructed it again from the Windows XP
computer.

Thank you for any suggestions.

When logging on to the WinXP machine, make sure to get validated
by the domain controller, not by the WinXP machine itself.

 

[Adam]

When logging on to the WinXP machine, make sure to get validated
by the domain controller, not by the WinXP machine itself.

What do you mean?
I log in using my roaming profile which is on the domain controller.

 

[Adam]

A fresh installation of Windows XP Professional (few workstations) have
been added to our Windows 2000 domain based network.

All servers and workstations have all the up to date patches and
updates.

I checked local admin group and the domain admin group is a member of
that on the workstations as expected.

DNS Servers are properly defined in both Windows 2000 and XP
workstations,


No errors can be seen in any event log.
No custom or third party security packages are installed.


Windows 2000 server hosts also DNS.

Windows 2000 clients have no such problems.

The problem:
Windows XP clients, when used by members of the domain administrator
group, cannot access folders that are assigned to domain administrators,
access denied.

Cannot read security event log or clear even logs for Application and
System.
Access denied.

Any network or IP address discovery package running from the Windows XP
get access denied.

No such thing happens on Windows 2000 workstations.

I even tried fresh user profile to separate the profile on Windows XP
from Windows 200 profiles.
No luck.

Any suggestions?

I cannot see anything in the event logs.

Any pointers would be appreciated.

Thank you from a confused user.

 

[Steven L Umbach]

You mentioned that dns is correctly configured, just be sure that the XP computers do
NOT have any ISP dns servers listed as a preferred dns server even down the list as
shown by ipconfig /all on those computers. Also run netdiag on a couple of XP
computers looking for any failed tests/errors/warnings that relate to dns, dc
discovery, kerberos, or trust relationship/secure channel. If any templates have been
applied to those computers or the domain controllers, there could be a problem with
security option incompatibilities. Smb signing, as configured via security options
for digitally sign communications, can cause problems if required in a W2K domain
with XP Pro computers. Using a packet sniffer like the free Ethereal on the XP Pro
computers to capture a packet exchange sequence while trying to perform an operation
that is denied could be very helpful. --- Steve

 

[Benn Wolff]

Just to make sure this is not the problem,
make two accounts, same name, same password, on both server & workstation.
see if these accounts get the same errors doing what you where doing befor.