asked on

replaced motherboard now can't RDP

replaced a server motherboard with embedded NICs. Now I can't RDP. I deleted the old registry entries. all I get is a "cannot connect" reponse. this is whether I rdp to dns name or IP. I can ping the IP though just fine. I've done an ipconfig /flushdns as well. do I need to clear an arp table or something?

windows server 2008 r2 sp1

Software_onbekend

Check on the server if RDP is enabled.
Check if the windows firewall is allowing RDP sessions.
Check also if the account is member is the local administrators group or ad you r account to the Remote desktop users group.

MrVault

ASKER

rdp is enabled for all types (old and new)

firewall is turned off

i'm logged in as local admin.

Software_onbekend

Have you already checked if the services needed for RDP are started ?

MrVault

ASKER

yes. remote desktop services (no longer terminal services) are started and running just like all the other servers. is there another service that's required?

Software_onbekend

I have the following Services started on my Win 2008 R2.
-Remote Desktop Configuration
-Remote Desktop Services
-Remote Desktop Services UserMode Port Redirector
-Remote Procedure Call (RPC)

MrVault

ASKER

I have those too. No dice.

MrVault

ASKER

I don't get it but it has to have something to do with old NICs. it's like the connection is tied to an old, gone nic in the registry somewhere

Software_onbekend

Can you find any errors in the log files related to this problem...?
Do you see any loggon attemps in the security log ?

MrVault

ASKER

unfortunately no. there are no eventlog entries when I try to rdp in. on my machine it says:

ASKER CERTIFIED SOLUTION

Software_onbekend

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

MrVault

ASKER

i checked and according to one article, the settings are all missing, but that may because server 2008 puts it in the rdp-listener subkey instead of rdp-tcp. my rdp-tcp key is completely blank. see article below

http://www.techrepublic.com/blog/datacenter/changing-the-rdp-listening-port-on-windows-server/1939

I also followed tihs article below and it failed. however firewall is off.

http://support.microsoft.com/kb/187628

Software_onbekend

On my Win 2008 R2 is the key stil there.
Screenshot.doc

MrVault

ASKER

did you try deleting and recreating the rdp-listener in admin tools? all those keys are there under rdp-listener, not under rdp-tcp

Software_onbekend

I did a standard installation of Win 2008 R2 Standard.
And only enabled RDP using the gui of win 2008..

If you look at the bottom of the screen shot you will see the complete path of the register..

MrVault

ASKER

Thanks. I wonder if there's a way to restore those settings?

MrVault

ASKER

so i popped in the registry entry from another identical server, then I could get into remote desktop session host configuration. i re-created RDP-Tcp with same settings. I noticed that this server now had 2 - 1 for RDP 7.1 and one for 6. Just for heck of it, I went back to remote tab on computer properties and it had gone back to "not allowed". I put it back in mixed client mode and voila, it worked. so some combination of a corrupted registry, with that setting getting undone and having to recreate the connection in RDSHC was the combination. I'm not writing a how-to for someone else, but chances are it's in there somewhere. I could not find anything online which explains how to reinstall this. only if you had installed rdp ts role could you reinstall the role. thanks for the help!

Software_onbekend

Fine to hear that I have pointed you into the right direction...
And I don't know if it is possible to reinstall RDP...
Perhaps the installation of the TS roule could perhaps also fix the problem as you mentioned..
But that is also a long shot without garanties.