Server 2003 & XP pro network problem

[bestax1]

Any ideas on this one...(please, im pulling my hair out over this)

We recently replaced our old (NT4 Server) domain controller with a Server
2003 domain controller (and a new domain name) and successfully migrated all
the machines on the same subnet as the new controller to the new domain.

However, when we tried to migrate machines on a different subnet to use the
new domain controller, XP Pro machines are unable to locate the new domain
controller (but NT4 and W2000 are OK).

So what we have is this:

Subnet A
========
Server 2003 Domain Controller (oecu.ox.ac.uk)
NT4 Server (GEOGRAPHY)
Workstations running NT4, W2000, XP Pro all on oecu.ox.ac.uk

Subnet B
========
Workstations running NT4 and W2000 can join OECU domain

Workstations running XP Pro cannot join domain (get the following error when
attempting to join the domain "The following error occurred attempting to
join the domain "oecu.ox.ac.uk" The RPC server is unavailable". This
includes machines which were running NT4 on the new domain and were
subsequently upgraded to XP Pro (i.e. upgrade rather than re-install).

All the machines have lmhosts 0x1B entries for both old and new domain
controllers.

I have hunted for hours on Google and support.microsoft.com without any
successful resolution.


cheers in advance for any help

[Skinny Boy]

Dunno if this will help, but your problem caught my attention maybe this is whats going on, or XP's firewall , after looking at some stuff. Let us know, as there are many people here that may be able to help with more info ...
Good luck...

http://www.microsoft.com/technet/tre...eat/domain.asp

or this...

TechNet Home > IT Solutions > Networking & RAS > Support > Troubleshooting

or here ..

TechNet Home > IT Community >

[onyx]

This is just a guess, but you may as well check it out.

XP has a setting in the local security policy (accessed via the Group Policy snap-in of the MMC) called "Domain Member: Require strong (Windows 2000 or later) session key." Basically, if this setting is enabled, it forces all your domain members to use Kerberos, which would work fine if you had only Win2k and WinXP domain members. But since you stated you have NT4 also, you can't require a strong session key or your NT4 boxes won't be able to talk to any other domain members.

I THINK WinXP may have this policy setting enabled by default, which could be what is causing your problem (in that the WinXP client cannot establish a session with the domain controller).

Check whether the policy setting is enabled, and if so, try disabling it before joining the WinXP computer to the domain.

[bestax1]

Thats a good idea. ive finished for the weekend now but ill try on monday.

ill let you know how i get on.

cheers