![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Any chance your running something like NAV worm protection or OneCare Live
that may block incoming Remote Desktop connections? Have you tested over your local LAN from another PC on the same LAN. In that case it is NOT a valid test to use the public IP of your router. Use the private LAN IP instead. -- Al Jarvi (MS-MVP Windows Networking) This posting is provided "AS IS" with no warranties, and confers no rights... The MS-MVP Program - http://mvp.support.microsoft.com "FunkyRX" wrote: Hi, I am having trouble configuring remote desktop for vista Ultimate. I have followed the microsoft setup guide for vista remote desktop. As part of this process, I also changed the remote desktop port to 3393 and configured the firewall rules. When I attempt to connect from an XP pc I get the message "The client could not connect to the remote computer. I do include the port number when connecting. netstat -a shows the remote desktop port 3393 listening telnet local 3393 connects to telnet (both from vista host and remote xp pc) telnet host 3393 connects to telnet (both from vista host and remote xp pc) canyouseeme.org shows the port is open and the service can be seen 'terminalservices' service is started I don't know what else to check to sort this issue out. Does anyone have a suggestion? FYI, I set the port back to 3389 to get the same issue. Thanks in advance, Jarrad |