We have recently upgraded our domain from Windows 2000 to Windows 2003.
We have two Windows 2000 servers with Metaframe XP on, in our farm.
The problem now is that one them doesnt talk to the domain, it doesnt see the shares from the Metaframe server and it wont process logon scripts either.
Eg, if im on the problem server and type \\dcservername and hit return, it normally brings up the shares such as NETLOGON etc.
When i do that now it asks for username and password.
I have run NLMON and it thinks the domain is not synced, BUT the stange thing is, that our other Metaframe server is fine, which has all the the same software\config as the now non working one.
Can i get away with removing it from the domain and re-adding it...
Any ideas what the issue is?
Bear in mind that its only since we've gone to Windows 2003 AD from Windows 2000 AD.
Thanks for your time.
We have two Windows 2000 servers with Metaframe XP on, in our farm.
The problem now is that one them doesnt talk to the domain, it doesnt see the shares from the Metaframe server and it wont process logon scripts either.
Eg, if im on the problem server and type \\dcservername and hit return, it normally brings up the shares such as NETLOGON etc.
When i do that now it asks for username and password.
I have run NLMON and it thinks the domain is not synced, BUT the stange thing is, that our other Metaframe server is fine, which has all the the same software\config as the now non working one.
Can i get away with removing it from the domain and re-adding it...
Any ideas what the issue is?
Bear in mind that its only since we've gone to Windows 2003 AD from Windows 2000 AD.
Thanks for your time.