Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I recently migrated a Win2003 Small Business Server from a physical machine to a VM. It seemed to be working great for one day, until it mysteriously stopped authenticating Remote Desktop sessions to workstations and servers. The Administrator domain account can log on, but other accounts cannot.

When we try to Remote Desktop to a workstation a domain account, we get this error:

An authentication error has occurred (Code: 0x80090304).

When we try to Remote Desktop to a Windows 2008 Terminal Server, we get this error:

The credentials that were used to connect to SERVERNAME did not work. Please enter new credentials.

I haven't changed anything since the other day when everything seemed to be working right after the migration. I've entered both of these error messages into Google and tried following whatever troubleshooting steps I could find on the first page of results, but haven't had any success thus far in resolving the problem. I also tried reverting the SBS VM to a snapshot that I took after converting it and reconfiguring the network (setting the static IP as appropriate and deleting the now-unneeded "Internet" network adapter since the server was no longer functioning as a router), and that didn't seem to help, either.

share|improve this question
1  
"I also tried reverting the SBS VM to a snapshot that I took after converting it and reconfiguring the network " - I hope your SBS sever wasn't functioning as a Domain Controller. Was it? If so, was it the only DC in your domain? –  MDMarra Jul 11 '12 at 18:03
    
Yes, it's the only DC, but we're a small company and only a couple users are actually using it. I can't tell from your remark whether you're implying the act of reverting to a snapshot as a troubleshooting step was a bad idea, or whether converting to a VM and/or configuring its network adapters after the conversion was a bad idea. Either way, if you have any suggestions on how to properly convert this machine to a VM so everything works, I'd appreciate them. I still have the original hard drive and a copy, so I can redo the conversion if necessary. –  rob Jul 11 '12 at 18:11
1  
Most conversion tools sysprep the box being moved. This is bad. Don't ever sysprep a DC. Reverting from a snapshot on a DC is also very bad. I think that the problem that you're seeing now is only the tip of the iceberg and you might be seeing a lot more shortly. You really shouldn't even P2V a DC. Just install a new one as a VM, transfer the FSMO roles, and demote the old one after replication has completed. SBS sort of complicates this, but a migration should happen, not a conversion. –  MDMarra Jul 11 '12 at 18:13
    
well at least is only a sbs server and not a dc with thousands of users :) –  tony roth Jul 11 '12 at 18:16
    
I used VMware Converter 5. The original reason for converting it was that it kept freezing up and I suspected a hardware failure (aside from having to replace hard drives a few times, the hardware has been in service for more than 10 years). Do you have any recommendations on how to do this the right way? –  rob Jul 11 '12 at 18:17

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.