|
it
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Remote Desktop not workingWhen I try to connect to a Server 2003 box from another, it fails giving me
this error. The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try your connection again later. If the problem continues to occur, contact your administrator. I can connect to any other machine in my domain without error. Remote Desktop is enabled, I have access in the RD persmissions. I can pint the server fine, by IP, Hostname and by FQDN. I have tried connecting to it using each method, but no luck. The server is on the same subnet as me, so I am not sure what the issue could be. I do not want to use TSWEB. thanks spepi ****FOLLOW UP*****
Port 3389 is not listening, but it is in the registry following this link. http://support.microsoft.com/?kbid=306759 Show quoteHide quote "spepi" wrote: > When I try to connect to a Server 2003 box from another, it fails giving me > this error. > The client could not connect to the remote computer. Remote connections might > not be enabled or the computer might be too busy to accept new connections. > It is also possible that network problems are preventing your connection. > Please try your connection again later. If the problem continues to occur, > contact your administrator. > > I can connect to any other machine in my domain without error. > Remote Desktop is enabled, I have access in the RD persmissions. > I can pint the server fine, by IP, Hostname and by FQDN. I have tried > connecting to it using each method, but no luck. The server is on the same > subnet as me, so I am not sure what the issue could be. I do not want to use > TSWEB. > > thanks > spepi Try unticking RDP from System | Remote and reticking (this simply changes a
registry key) but it has been known to cause problems, also check ip filtering/firewalls to ensure that tcp/3389 is not blocked. If you try a telnet <machinesip> 3389 from the local box does it connect? Cheers, Simmo Show quoteHide quote "spepi" wrote: > ****FOLLOW UP***** > Port 3389 is not listening, but it is in the registry following this link. > > http://support.microsoft.com/?kbid=306759 > > "spepi" wrote: > > > When I try to connect to a Server 2003 box from another, it fails giving me > > this error. > > The client could not connect to the remote computer. Remote connections might > > not be enabled or the computer might be too busy to accept new connections. > > It is also possible that network problems are preventing your connection. > > Please try your connection again later. If the problem continues to occur, > > contact your administrator. > > > > I can connect to any other machine in my domain without error. > > Remote Desktop is enabled, I have access in the RD persmissions. > > I can pint the server fine, by IP, Hostname and by FQDN. I have tried > > connecting to it using each method, but no luck. The server is on the same > > subnet as me, so I am not sure what the issue could be. I do not want to use > > TSWEB. > > > > thanks > > spepi  
Other interesting topics
Reboot Speed
Problem with using sysprep for cloning Windows 2003 Server Switching from workgroups to domain windows firewall Please Help Qhost.apd virus throughout network Q: copy with permission Windows Server 2003 - System Information not displayed correctly WPA Security and Cert Services Connecting to Event Viewer from 2003 server Restore point |
|||||||||||||||||||||||
