- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Remote Desktop remote connection timeout
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2007 05:36 AM
05-21-2007 05:36 AM
Remote Desktop remote connection timeout
netstat show port 3389 listening
can drive map and remote into registry
Did manage to get following error once in the logs
The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
Tried clearing certifications from HKLM\System\CurrentControlSet\Services\TermServices\Parameters - no luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2007 06:57 AM
05-21-2007 06:57 AM
Re: Remote Desktop remote connection timeout
I had timeouts when trying to connect remotely and there was a problem with the IP "Don't fragment" flag. The client had don't fragment set to 1 and the packets needed fragmentation, so the connection was dropped (MTU problems).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2007 06:59 AM
05-21-2007 06:59 AM
Re: Remote Desktop remote connection timeout
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2007 07:09 PM
05-21-2007 07:09 PM
Re: Remote Desktop remote connection timeout
Let us know if you find the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2007 08:15 PM
05-21-2007 08:15 PM
Re: Remote Desktop remote connection timeout
when you say clearing the certificate, do you mean deleting it, because you really need to delete that entry for that to work.
Also after deleting the certificate, the machine needs to boot up.
I've had a lot of problems with that to, and deleting the certificate always helped me.
Besides this, and since you are on the same subnet, the only thing you need more, is allowing file and print sharing on the firewall and activating remote desktop on the system properties.
Hope this helps,
hugo tigre
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2007 01:18 AM
05-22-2007 01:18 AM
Re: Remote Desktop remote connection timeout
I also have ensured that file and print sharing enabled.
Remote Desktop enabled in system properties.
tried disabling it and got error saying it was not enbled - re-enable and get back to the "remote connection timed out" error
sc queryex termservices - running
netstat -a port 3389 listening
MTU is at default 1500. I seem to have no other problems, application clents can connect, can map to c$ and can send remote shutdown and remote regedit, ping times great
Only thing not normal here is the Remote Desktop time out when trying to connect