RDP Fails Due To Failed X.224 Connection
I have a server running Windows 2003 that I am not able to make a RDP connection to on a local network. It was multi-homed but for troubleshooting this problem I have disabled all but one NIC. When trying to connect to the server by RDP it gives a generic Protocol Error message and says it is disconnecting and to try connecting again. Actually the connection is never really made.
I did a packet capture of the connection to this server as well as the connection to a server with out this problem. The TCP handshake goes fine in both instances. However on the working server a X.224 connection request is made by the client and confirmed by the server before proceeding with the RDP connection. With the problem server the client make the X.224 connection request but the server never returns a confirmation.
I'm not familiar with X.224 and google doesn't turn up much. The server is definitely listening on port 3389 but I have no idea what would cause the X.224 connection to fail on this one server.
BTW, this server is newly installed in our datacenter and RDP hasn't worked on it from the beginning.
I did a packet capture of the connection to this server as well as the connection to a server with out this problem. The TCP handshake goes fine in both instances. However on the working server a X.224 connection request is made by the client and confirmed by the server before proceeding with the RDP connection. With the problem server the client make the X.224 connection request but the server never returns a confirmation.
I'm not familiar with X.224 and google doesn't turn up much. The server is definitely listening on port 3389 but I have no idea what would cause the X.224 connection to fail on this one server.
BTW, this server is newly installed in our datacenter and RDP hasn't worked on it from the beginning.
Keith Alabaster
Have you right-clicked the my computer icon - properties - remote- enable remote -access on the new server?
ASKER
Yes, remote desktop has been enabled and the appropriate users have been added to remote desktop users group. As I said, the server is listening on port 3389. Checked it with both netstat and nmap.
Local firewall on the server - have the rdp exceptions been added?
There were some issues with Broadcom Net extreme cards - do you have these in the server?
What is the server role - has it got any NAT services running? 2003 r2 sp2 also had some issues
http://support.microsoft.com/kb/927695
There were some issues with Broadcom Net extreme cards - do you have these in the server?
What is the server role - has it got any NAT services running? 2003 r2 sp2 also had some issues
http://support.microsoft.com/kb/927695
ASKER
The windows firewall is disabled on the adapter and I don't see anything in the event log indicating a blocked connection. YES this is a Broadcom Netxtreme NIC. It is a Dell Poweredge 2950. I hope that helps identify the problem.
The server is being used for Backup Exec and Trackit which uses a sql db. Nothing doing NAT as far as I know.
The server is being used for Backup Exec and Trackit which uses a sql db. Nothing doing NAT as far as I know.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have the very same problem and have not found a solution as of yet. I am thinking there is a registry setting or such, which is preventing the server from sending its x.224 connection confirmed. In my case, the server is responding to the clients "connection request" with a "RST ACK" rather than "connection confirmed"