Unable to Connect to Remote Desktop After Port Change

[Guest]

Hello Everyone and thanks for your help in advance. I have several Windows
XP pro machines on a Win 2003 network of which i want to be able to remote
into. For that reason, I changed the default listening port for one of the
machines to 23389 using the registry changes outlined in the Microsoft article

http://support.microsoft.com/kb/306759

I was previously able to connect to this particular machine simply typing
the IP address. Now, when i attempt IPAddress:23389, it will not connect,
nor will it connect using simply the IP address. I have verified that the
box to allow remote connection is checked, so I'm really out of ideas as to
what the problem is. Any help on this topic would be greatly appreciated.
Thanks.

 

[Rory Becker]

Hello Everyone and thanks for your help in advance. I have several

Windows XP pro machines on a Win 2003 network of which i want to be
able to remote into. For that reason, I changed the default listening
port for one of the machines to 23389 using the registry changes
outlined in the Microsoft article

http://support.microsoft.com/kb/306759

I was previously able to connect to this particular machine simply
typing the IP address. Now, when i attempt IPAddress:23389, it will
not connect, nor will it connect using simply the IP address. I have
verified that the box to allow remote connection is checked, so I'm
really out of ideas as to what the problem is. Any help on this topic
would be greatly appreciated. Thanks.

Are you perhaps working through a firewall or other server facility which
ports would need to be opened or forwarded through?

Perhaps 3389 (Default if I remember correctly) was already being forwarded
and you need now to do the same for 23389?

 

[Sooner Al [MVP]]

Hello Everyone and thanks for your help in advance. I have several
Windows
XP pro machines on a Win 2003 network of which i want to be able to remote
into. For that reason, I changed the default listening port for one of
the
machines to 23389 using the registry changes outlined in the Microsoft
article

http://support.microsoft.com/kb/306759

I was previously able to connect to this particular machine simply typing
the IP address. Now, when i attempt IPAddress:23389, it will not connect,
nor will it connect using simply the IP address. I have verified that the
box to allow remote connection is checked, so I'm really out of ideas as
to
what the problem is. Any help on this topic would be greatly appreciated.
Thanks.

In addition to Rory's advice make sure you reboot the PC after making the
registry change for the new listening port.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

 

[Guest]

Thanks for the response. Yes, I have already set up port forwarding for port
23389 and the computer has been rebooted several times. Any other ideas?
This should be pretty straight forward, but not working out that way.

 

[Sooner Al [MVP]]

Thanks for the response. Yes, I have already set up port forwarding for
port
23389 and the computer has been rebooted several times. Any other ideas?
This should be pretty straight forward, but not working out that way.

What happens if you go to the http://www.canyouseeme.org test site while
logged in locally on that particular PC? Does the test pass for Port 23389?

Can you connect to that PC from another PC on the same local LAN using the
local LAN IP and port, ie. 192.168.1.45:23389 for example?

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

 

[Guest]

Found the problem. It was actually in Windows Firewall. When you change the
listening port, Windows Firewall has to be configured to allow the new port
traffic. Thanks again for the assistance.

 

[Sooner Al [MVP]]

Found the problem. It was actually in Windows Firewall. When you change
the
listening port, Windows Firewall has to be configured to allow the new
port
traffic. Thanks again for the assistance.

Excellent... Thanks for the feedback...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375