Lost SBS 2003 Remote Desktop connectivity.

[mrgulic]

I rebooted my SBS 2003 server yesterday and for some reason I am refused remote connection to it now. There have been no updates applied or changes to the configeration. RDP is enabled and allows access to users through GPOE.

The custom port number (8089) is still correct and netstat shows that it is LISTENING. I do not see anything out of the ordinary in the event logs and all services that are set to automatic start are running.

I am completly stumped. I hope that someone here has some helpful advise.

Thanks in advance.

 

[Dashsa]

have you checked all the services started correctly?

 

[mrgulic]

thanks for the reply Dashsa.

the terminal service (and its dependancies) are started and the event log does not show any errors. i can remote from the sever to clients but the clients can not remote to the sever.

any other ideas?

 

[Xanthias]

TheAccessHack,

I am having the same issue. Have you fixed this issue yet?
If yes, could you please lemme know how did you fix it?
If No, Try this solution below.

I was reading some forums and they suggested us to do the following
Right click 'My Computer' -> Properties -> Remote tab -> untick "Enable remote desktop on this computer" -> Apply -> OK.
And go back to Remote tab again and tick "Enable remote desktop on this computer" -> Apply -> OK.

I don't have physical access to the server now as such I can't try this.
May be, you can try this solution and let me know, if this works?


Thanks

 

[mrgulic]

Thanks for the reply Xanthias. No, I have not fixed it yet. For now I am using VNC to connect remotely.

I will try your suggestion and tell you how it goes. Be patient as remote access in this enviorment is controlled through group policy so i'll have to push out the change and wait for it to take effect.

 

[mrgulic]

Xanthias,

I would have been surprised if that had worked, but alas it did not.

Let me know if you run across any other ideas and I will do the same if I find a solution that works for me.

 

[Xanthias]

TheAccessHack,

It didn't work for me either.
I also came across some other solutions. Please check the link below.

http://groups.google.com/group/micr...RDP-Tcp+key++missing&rnum=10#91e863d3c4681b69

Apparently, we have to make sure that 'RDP-Tcp' folder and its contents exist on the registry. If this doesn't exists, I am not sure how to create/import this folder.

Also, do you have Nvdia video card? It seems that some of the users had this issue because of the video card driver.
They need to uninstall the driver and re install old version of the driver.

Anyway, keep me posted.

Thanks

 

[mrgulic]

I set my port number back to 3389 and it worked. I don't understand it. There shouldnt be anything blocking that port. But the good news is that it is accessable. I never would have thought to try something so simple.

thanks

 

[Xanthias]

I am glad that it is fixed.

 

[ShackDaddy]

My guess is that the port you picked was actually in a port range for some other service, perhaps your AV product, and RDP was unable to bind to it. I know that 3387 and 3388 are usually unused, so I tend to pick those when I want an alternate port.

Dave Shackelford
ThirdTier.net