Cannot remote desktop to server 2003 after installing Cisco VPN client

Friday, November 06, 2009 5:44 PMMarty Borg

0
Sign In to Vote
Have removed Cisco client,
reinstalled remote desktop client (WindowsServer2003-KB925876-v2-x86-ENU.exe)

stopped Firewall service

removed and reinstalled network cards from device manager

run netsh winsock reset

done a repair install of the operating system.

Server will not answer "telnet server 3389" or remote desktop connections from any workstation.

Remote desktop client does not report error but mRemote reports "RDP Disconnected! Error code: 516 Error description: WinSock Socket connect Failed"

Can connect to server using computer management, and can remote desktop OUT.

Open to any ideas.
- Reply
- Quote

Answers

Thursday, November 12, 2009 4:01 PMMarty Borg

0
Sign In to Vote
Fixed It!

"Not listening" was my clue.

>> clipped from Daniel Petri's excellent site (www.petri.co.il) <<

To change the default port for all new connections created on the Terminal Server:
1. Run Regedit and go to this key:
HKEY_LOCAL_MACHINE'SYSTEM'CurrentControlSet' Control'Terminal Server'WinStations'RDP-Tcp
1. Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value.
>> thanks Dan <<

Somehow my RDP port had been changed to 80.

That explains why SharePoint broke at the same time.

Changed it back to 3389 and all is well.
- Marked As Answer byMarty Borg Thursday, November 12, 2009 4:01 PM
- Reply
- Quote

All Replies

Friday, November 06, 2009 7:34 PMKristin L. GriffinMVP, Moderator

0
Sign In to Vote
I think I have run across this in the past when my subnet mask was wrong.
PLease check your subnet mask, and other Ip settings to make sure they are correct.

I would also check DNS and make sure things match up with what you have for Ip config on the NIC on the server.
Hope this helps,

Kristin L. Griffin

Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!)
- Reply
- Quote
Friday, November 06, 2009 8:10 PMRobert Maijen

0
Sign In to Vote
Hello

I believe that Cisco VPN also adds something to your network adapter that might not be removed properly. Check you NIC settings. In the mean time you can check Kristin's option.

Regards Robert
- Reply
- Quote
Friday, November 06, 2009 9:12 PMMarty Borg

0
Sign In to Vote
I configure everything but domain controllers using DHCP to minimize those kinds of problems.
Just in case; I manually assigned it a new address, and rebooted it but no change.

It won't answer rdp, and drops telnet (to 3389) requests.

Netdiag looks good (as near as I can tell)

Any other suggestions?
- Reply
- Quote
Tuesday, November 10, 2009 7:09 PMMarty Borg

0
Sign In to Vote
I ran the netsh int ip reset command to reset all the tcpip information.
I manually verified that the cisco vpn stuff had been removed.

At this point I am not willing to say that the Cisco VPN is what killed Remote desktop, just that I noticed them both at the same time.

I am willing to try anything, since rebuilding will mean having to rebuild the sharepoint installation as well.
- Reply
- Quote
Tuesday, November 10, 2009 8:01 PMKristin L. GriffinMVP, Moderator

0
Sign In to Vote
is this server a terminal server?

Kristin L. Griffin

Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!)
- Reply
- Quote
Tuesday, November 10, 2009 8:08 PMKristin L. GriffinMVP, Moderator

0
Sign In to Vote
also, as an expepriment, can you turn your firewall back on and make sure it is configured to allow access ot port 3389 in and out. then try to telnet to the server via 3389.
Hope this helps,

Kristin L. Griffin

Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!)
- Reply
- Quote
Thursday, November 12, 2009 3:05 PMMarty Borg

0
Sign In to Vote
No. It is a member server that I use for testing.

(I submitted the question to the TS group, because I could'nt find a remote desktop group.)
- Reply
- Quote
Thursday, November 12, 2009 3:18 PMMarty Borg

0
Sign In to Vote
Same result.

It doesn't appear to be even listening on 3389

Active Connections

  Proto Local Address Foreign Address State

  TCP 0.0.0.0:25 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:80 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:135 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:445 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1041 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1042 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1046 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1059 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1067 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1074 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1078 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1085 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:1114 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:2301 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:2381 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:4651 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:15005 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:15006 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:41333 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:56737 0.0.0.0:0 LISTENING

  TCP 0.0.0.0:56738 0.0.0.0:0 LISTENING

  TCP 10.0.1.8:80 10.0.1.8:1289 ESTABLISHED

  TCP 10.0.1.8:139 0.0.0.0:0 LISTENING

  TCP 10.0.1.8:1037 10.0.1.2:1026 TIME_WAIT

  TCP 10.0.1.8:1043 10.0.1.2:135 TIME_WAIT

  TCP 10.0.1.8:1044 10.0.1.2:1026 TIME_WAIT

  TCP 10.0.1.8:1059 10.0.1.8:1071 ESTABLISHED

  TCP 10.0.1.8:1059 10.0.1.8:1076 ESTABLISHED

  TCP 10.0.1.8:1059 10.0.1.8:1093 ESTABLISHED

  TCP 10.0.1.8:1059 10.0.1.8:1174 ESTABLISHED

  TCP 10.0.1.8:1059 10.0.1.8:1210 ESTABLISHED

  TCP 10.0.1.8:1059 10.0.1.8:1219 ESTABLISHED

  TCP 10.0.1.8:1059 10.0.1.8:1320 ESTABLISHED

  TCP 10.0.1.8:1063 10.0.1.8:8093 TIME_WAIT

  TCP 10.0.1.8:1071 10.0.1.8:1059 ESTABLISHED

  TCP 10.0.1.8:1074 10.0.1.8:1077 ESTABLISHED

  TCP 10.0.1.8:1076 10.0.1.8:1059 ESTABLISHED

  TCP 10.0.1.8:1077 10.0.1.8:1074 ESTABLISHED

  TCP 10.0.1.8:1078 10.0.1.8:1081 ESTABLISHED

  TCP 10.0.1.8:1081 10.0.1.8:1078 ESTABLISHED

  TCP 10.0.1.8:1085 10.0.1.8:1090 ESTABLISHED

  TCP 10.0.1.8:1087 10.0.1.8:1059 TIME_WAIT

  TCP 10.0.1.8:1090 10.0.1.8:1085 ESTABLISHED

  TCP 10.0.1.8:1093 10.0.1.8:1059 ESTABLISHED

  TCP 10.0.1.8:1104 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1105 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1106 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1107 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1108 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1109 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1110 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1111 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1112 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1113 10.0.1.23:1433 ESTABLISHED

  TCP 10.0.1.8:1127 10.0.1.8:15005 ESTABLISHED

  TCP 10.0.1.8:1129 10.0.1.8:15005 ESTABLISHED

  TCP 10.0.1.8:1132 10.0.1.8:15005 ESTABLISHED

  TCP 10.0.1.8:1133 10.0.1.8:15005 ESTABLISHED

  TCP 10.0.1.8:1134 10.0.1.8:15005 ESTABLISHED

  TCP 10.0.1.8:1135 10.0.1.8:15005 ESTABLISHED

  TCP 10.0.1.8:1136 10.0.1.8:15005 ESTABLISHED

  TCP 10.0.1.8:1174 10.0.1.8:1059 ESTABLISHED

  TCP 10.0.1.8:1176 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1177 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1183 10.0.1.2:445 TIME_WAIT

  TCP 10.0.1.8:1188 10.0.1.2:135 TIME_WAIT

  TCP 10.0.1.8:1192 10.0.1.2:389 TIME_WAIT

  TCP 10.0.1.8:1194 10.0.1.33:139 ESTABLISHED

  TCP 10.0.1.8:1198 10.0.1.2:139 TIME_WAIT

  TCP 10.0.1.8:1202 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1203 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1210 10.0.1.8:1059 ESTABLISHED

  TCP 10.0.1.8:1211 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1218 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1219 10.0.1.8:1059 ESTABLISHED

  TCP 10.0.1.8:1220 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1221 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1224 10.0.1.2:135 TIME_WAIT

  TCP 10.0.1.8:1225 10.0.1.2:1026 TIME_WAIT

  TCP 10.0.1.8:1228 10.0.1.2:389 TIME_WAIT

  TCP 10.0.1.8:1230 10.0.1.2:389 TIME_WAIT

  TCP 10.0.1.8:1233 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1234 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1235 10.0.1.8:1059 TIME_WAIT

  TCP 10.0.1.8:1240 10.0.1.8:139 TIME_WAIT

  TCP 10.0.1.8:1244 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1245 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1252 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1259 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1268 10.0.1.30:445 TIME_WAIT

  TCP 10.0.1.8:1271 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1273 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1275 10.0.1.8:8093 ESTABLISHED

  TCP 10.0.1.8:1276 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1277 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1284 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1287 10.0.1.8:41333 ESTABLISHED

  TCP 10.0.1.8:1288 10.0.1.8:4651 ESTABLISHED

  TCP 10.0.1.8:1289 10.0.1.8:80 ESTABLISHED

  TCP 10.0.1.8:1294 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1295 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1296 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1303 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1304 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1312 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1313 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1320 10.0.1.8:1059 ESTABLISHED

  TCP 10.0.1.8:1321 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:1328 10.0.1.8:15005 TIME_WAIT

  TCP 10.0.1.8:4651 10.0.1.8:1288 ESTABLISHED

  TCP 10.0.1.8:8082 0.0.0.0:0 LISTENING

  TCP 10.0.1.8:8093 0.0.0.0:0 LISTENING

  TCP 10.0.1.8:8093 10.0.1.8:1275 ESTABLISHED

  TCP 10.0.1.8:15005 10.0.1.8:1127 ESTABLISHED

  TCP 10.0.1.8:15005 10.0.1.8:1129 ESTABLISHED

  TCP 10.0.1.8:15005 10.0.1.8:1132 ESTABLISHED

  TCP 10.0.1.8:15005 10.0.1.8:1133 ESTABLISHED

  TCP 10.0.1.8:15005 10.0.1.8:1134 ESTABLISHED

  TCP 10.0.1.8:15005 10.0.1.8:1135 ESTABLISHED

  TCP 10.0.1.8:15005 10.0.1.8:1136 ESTABLISHED

  TCP 10.0.1.8:41333 10.0.1.8:1287 ESTABLISHED

  TCP 127.0.0.1:445 127.0.0.1:1331 ESTABLISHED

  TCP 127.0.0.1:1062 0.0.0.0:0 LISTENING

  TCP 127.0.0.1:1239 127.0.0.1:445 TIME_WAIT

  TCP 127.0.0.1:1308 127.0.0.1:445 TIME_WAIT

  TCP 127.0.0.1:1331 127.0.0.1:445 ESTABLISHED

  TCP 127.0.0.1:8005 0.0.0.0:0 LISTENING

  UDP 0.0.0.0:445 *:*

  UDP 0.0.0.0:500 *:*

  UDP 0.0.0.0:1040 *:*

  UDP 0.0.0.0:1060 *:*

  UDP 0.0.0.0:1066 *:*

  UDP 0.0.0.0:1068 *:*

  UDP 0.0.0.0:1082 *:*

  UDP 0.0.0.0:1091 *:*

  UDP 0.0.0.0:1096 *:*

  UDP 0.0.0.0:1121 *:*

  UDP 0.0.0.0:1297 *:*

  UDP 0.0.0.0:1298 *:*

  UDP 0.0.0.0:1299 *:*

  UDP 0.0.0.0:1302 *:*

  UDP 0.0.0.0:1305 *:*

  UDP 0.0.0.0:1309 *:*

  UDP 0.0.0.0:1315 *:*

  UDP 0.0.0.0:1316 *:*

  UDP 0.0.0.0:1317 *:*

  UDP 0.0.0.0:1318 *:*

  UDP 0.0.0.0:1323 *:*

  UDP 0.0.0.0:1324 *:*

  UDP 0.0.0.0:1326 *:*

  UDP 0.0.0.0:1329 *:*

  UDP 0.0.0.0:1334 *:*

  UDP 0.0.0.0:1434 *:*

  UDP 0.0.0.0:3456 *:*

  UDP 0.0.0.0:4500 *:*

  UDP 10.0.1.8:123 *:*

  UDP 10.0.1.8:137 *:*

  UDP 10.0.1.8:138 *:*

  UDP 10.0.1.8:2637 *:*

  UDP 127.0.0.1:123 *:*

  UDP 127.0.0.1:1026 *:*

  UDP 127.0.0.1:1050 *:*

  UDP 127.0.0.1:1226 *:*

  UDP 127.0.0.1:3456 *:*
- Marked As Answer byMarty Borg Thursday, November 12, 2009 3:54 PM
- Unmarked As Answer byMarty Borg Thursday, November 12, 2009 4:25 PM
- Reply
- Quote
Thursday, November 12, 2009 4:01 PMMarty Borg

0
Sign In to Vote
Fixed It!

"Not listening" was my clue.

>> clipped from Daniel Petri's excellent site (www.petri.co.il) <<

To change the default port for all new connections created on the Terminal Server:
1. Run Regedit and go to this key:
HKEY_LOCAL_MACHINE'SYSTEM'CurrentControlSet' Control'Terminal Server'WinStations'RDP-Tcp
1. Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value.
>> thanks Dan <<

Somehow my RDP port had been changed to 80.

That explains why SharePoint broke at the same time.

Changed it back to 3389 and all is well.
- Marked As Answer byMarty Borg Thursday, November 12, 2009 4:01 PM
- Reply
- Quote