7000->7068 (x64) = lost Rem Desktop

[JeeperDon]

I had a machine I could RD into fine, then I did an Upgrade with 7068. The upgrade worked in every sense, all apps, users, settings, etc. The only thing wrong is not I can't RD into it. I have RD enabled and 'all computers' set as before. I get the "'1./2./3. not powered on or RD not setup" message. Another machine on the network that did the same (7000->7068), but was not a RD machine. We turned on RD on that machine as a test and it worked fine. I turned RD off on the broken machine, rebooted, then turned it back on, no help. Any ideas? The machine is on the network because it has things shared that I can see and access.

 

[JeeperDon]

I'm not sure what got screwed up, but it took renaming the computer to correct the problem. I tried it again and it did the same thing. RD on 7000 was working, update to 7068, RD breaks, rename computer and RD on 7068 works again.

 

[FreakyFerret]

Weird. I have 2 computers. The one I use was 7000 x64. The Remote is 7000 x86. I updated the one I use to 7068 x64, and now I can't get Aero effects. I did before though. Going to update the remote to 7068 x32 tomorrow. I'll let you know

 

[Studulike]

Seems to be a problem I an many are having. Just about to see if build 7077 is any better.
You can overcome this problem by re-joining the network or changing computer name that in effect re-joins the network and rebooting. For some reason when you reboot again all network setting will stop working again(printer sharing etc.), so you will have to do it all again.
Its a real pain in the arse.

 

[JeeperDon]

For some reason when you reboot again all network setting will stop working again(printer sharing etc.), so you will have to do it all again. Its a real pain in the arse.

I don't get that. I only lost RD and nothing else, then that came back after a rename. Subsequent boots of any of the 7068 computers and print servers have no problems with access.

 

[johngalt]

Report it via the reporting tool - this may be a simple registry import from the old machine (based on old SIDs) that is causing the issue....