RDC port changing

I'm trying to change the listening port for RDC on an XP pro machine.
Everything works fine through a linksys router (with ports 3389-3390
forwarded) when the registry is set to use port 3389, but when i change it to
3390 according to http://support.microsoft.com/kb/306759 and then restart RDC
stops working

I also have been trying to set up that computer for VPN incoming connections
http://www.onecomputerguy.com/netwo..._vpn_server.htm and that doesnt
seem to work from the inside or outside.

Hokie wrote:
> I'm trying to change the listening port for RDC on an XP pro
> machine. Everything works fine through a linksys router (with ports
> 3389-3390 forwarded) when the registry is set to use port 3389, but
> when i change it to 3390 according to
> http://support.microsoft.com/kb/306759 and then restart RDC stops
> working
>
> I also have been trying to set up that computer for VPN incoming
> connections
> http://www.onecomputerguy.com/netwo..._vpn_server.htm and that
> doesnt seem to work from the inside or outside.

I'm confused by your wording, I guess.
You are trying to change the listening port.. I get that.
I guess you have TCP 3389 forwarded on your router and opened on your
Windows Firewall (through the appropriate and usually already created
checkbox in the exceptions list for the Windows Firewall) and all works.

Then you change the listening port via the registry change. You change the
opening through your Windows Firewall (exception for TCP 3390) and forward
3390 through to said internal private IP and when you try to connect to:

public_IP_address:3390

(subbing in appropriate IP address, noting the 3390 at the end.)

It does what?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Hi thanks for the advice, I forgot to open the new port on Windows Firewall.
Everything works now, thanks again

"Shenan Stanley" wrote:

> Hokie wrote:
> > I'm trying to change the listening port for RDC on an XP pro
> > machine. Everything works fine through a linksys router (with ports
> > 3389-3390 forwarded) when the registry is set to use port 3389, but
> > when i change it to 3390 according to
> > http://support.microsoft.com/kb/306759 and then restart RDC stops
> > working
> >
> > I also have been trying to set up that computer for VPN incoming
> > connections
> > http://www.onecomputerguy.com/netwo..._vpn_server.htm and that
> > doesnt seem to work from the inside or outside.
>
> I'm confused by your wording, I guess.
> You are trying to change the listening port.. I get that.
> I guess you have TCP 3389 forwarded on your router and opened on your
> Windows Firewall (through the appropriate and usually already created
> checkbox in the exceptions list for the Windows Firewall) and all works.
>
> Then you change the listening port via the registry change. You change the
> opening through your Windows Firewall (exception for TCP 3390) and forward
> 3390 through to said internal private IP and when you try to connect to:
>
> public_IP_address:3390
>
> (subbing in appropriate IP address, noting the 3390 at the end.)
>
> It does what?
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>