I have encountered the following problem with a Vista x64 machine. Connecting to the machine via Remote Desktop just stopped working (probably after a windows update) – was working one day, not the next. On investigation found:

  • Services manager reports Terminal Services service as Automatic and Started
  • netstat –a –n shows port 3389 not open -Event log shows the error “Terminal Service start failed. The relevant status code was No such interface supported”

Best suggest fix I can find is to add the Network Services account to the administrator group:

net localgroup "Administrators" "NT Authority\Network Service" /add

This works, but can’t be very secure and I’d like to find a proper explanation and fix.

  • So, just to be clear, you're saying you're having a problem connecting TO the Vista machine with RDP? Or are you saying you're having a problem connecting to other machines FROM the Vista machine via RDP? – squillman May 18 '09 at 2:08
  • From what you describe it sounds like the machine comes up way before the network – CPU_BUSY May 18 '09 at 3:21
  • @squillman Connecting to the Vista machine with RDP. (i'll clarify the question). – RedBlueThing May 18 '09 at 3:31
  • @UndertheFold Not sure what you mean ? I can connect from the machine to the network, just can't connect to the machine via RDP (hopefully my edit clarified that ambiguity). – RedBlueThing May 18 '09 at 3:34
  • Re: adding Nework Services to local Adminstrators group. I have real concerns over escalating the priviledges of a built in account like Network Service - that account has the restrictions it does for a good reason. Jack B Nimble's tip about KB313222 sounds like better practice. – nray May 18 '09 at 7:22

In my research for this question it looks like everything has to do with the Network Service Account suddenly not having enough permissions to access the network or becoming corrupt in someway.

Maybe you can try This link which will reset your VISTA security settings.

You can also try restoring an old registry copy if you have one, you would need to boot into the recovery console to replace the files in c:\windows\system32\config

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.