NT4 -> W2K3 client can't fallback...

I am doing a in-place-upgrade of a NT4 -> W2K3 domain. Our DNS were already
on W2K server. In the lab I duplicated DNS from the live DNS server, turned a
NT4 BDC into NT4 PDC took offline and did a in-place-upgrade. This all went
fine until I tried to test fallback for client workstations (XP-Pro). In the
new AD Domain,(lab scenario) I can get a sample client workstation to logon
get a revised GP etc etc . I then took the DHCP assigned workstation and
moved it back to the unchanched live NT4 domain where it has it's original
computer account. When I try to logon all I get is "Domain not available". In
the NT4 domain nothing has changed and my lab workstation were originally
from to the NT4 domain. DNS can't be a problem as I am just moving the
workstation back to where it came from with DHCP assigned attibutes.... Any
ideas...? Thanks

"Pieter" wrote:

> I am doing a in-place-upgrade of a NT4 -> W2K3 domain. Our DNS were already
> on W2K server. In the lab I duplicated DNS from the live DNS server, turned a
> NT4 BDC into NT4 PDC took offline and did a in-place-upgrade. This all went
> fine until I tried to test fallback for client workstations (XP-Pro). In the
> new AD Domain,(lab scenario) I can get a sample client workstation to logon
> get a revised GP etc etc . I then took the DHCP assigned workstation and
> moved it back to the unchanched live NT4 domain where it has it's original
> computer account. When I try to logon all I get is "Domain not available". In
> the NT4 domain nothing has changed and my lab workstation were originally
> from to the NT4 domain. DNS can't be a problem as I am just moving the
> workstation back to where it came from with DHCP assigned attibutes.... Any
> ideas...? Thanks