Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Just upgraded domain from 2K to 2K3 and Metaframe server issue

Status
Not open for further replies.

manikm

Technical User
Mar 29, 2001
147
GB
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.




 
Manikim,

You can get away with removing and readding to the domain although you might want to have a look at the Event Logs and see if it just the Computer Account password which needs resetting.

There are plenty of MS Articles on how to do this depening on the individual siutation.

Hope that helps, post a reply if you get no joy.

Mike.
 
Hi there,

I tried this, but still having the problem.

One thing to mention, is that when i wrote:

"it doesnt see the shares from the Metaframe server and it wont process logon scripts either"

I MEANT to say

"it doesnt see the shares from the Win2K3 DC's - therefore it wont process logon scripts either"

Weird thing is why is one Metaframe server ok, but the other not?

 
Might be a stupid question but have you checked that the DNS Server settings are correct on the failing server and is the working server set the same?

I take it you can ping (by addr) these servers and it not a strange subnet issue or anything?
 
Make sure the computer is listed in AD, I'm gonna assume probobaly under "Migrated Computers"

Computer/Network Technician
CCNA
 
Have you checked that the time is in sync with the rest of the domain becuase if it is too far out of sync it will not allow logons in some cases.
 
Is this MF server a DC? We expirienst (bad english) problems that from a msclient dos we cannot access shares, maybe simmilar problem..
 
the answer to this I found in google groups under a SAMBA thread of all topics.

the resolution was to move the machine into a workgroup (called WORK), rebooted, and then tried rejoining the domain.

when i tried to rejoin the domain it gave me a access denied msg, SO i moved it into a workgroup name that we havent used before (called TEST)

Rebooted, and then i could join the domain again, and then the shares etc were fine.

Most bizzarre.

Thanks for all your comments.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top