2 Terminal Servers on 2 different ports

[bankajac]

I have a terminal server running on the default port 3389 behind a linksys router. On the router I forward port 3389 to my internal IP of 192.168.0.104. I have another terminal server with IP of 192.168.0.101. On the server I changed the terminal server listening port to 3390 and on the router I forwarded port 3390 to IP 192.168.0.101.

When I connect from inside the network with 192.168.0.101:3390, it does not work. When I use 192.168.0.101:3389 it works. I don't get it. I canged the port in the registry to 3390. What am I doing wrong?

Thanks in advance.

[boogerjones]

Have you restarted the server?

The other option would be to leave both servers listening on port 3389 and then simply forward port 3390 to port 3389 on 192.168.0.101. That's how I connect to my home computers.

[bankajac]

Yes, I just did that and it fixed the problem internally. The problem now is that I cannot connect to the server on port 3390 from outside of the network. Is this a limitation of the linksys router? It should see a request xx.xxx.xxx.xx:3390 and forward to internal IP of 192.168.0.101. It seems like that is not happening. Why not? I have FTP, email and web all forwarded and everything works.

[Guest]

Your testing from externally from another internet connection yes?

[bankajac]

Internally it works, externally it does not. I logged on to my computer at work to test externallly. I will test again when I am actually there but I believe that tha result will be the same.

[profets]

Internally it works, externally it does not. I logged on to my computer at work to test externallly. I will test again when I am actually there but I believe that tha result will be the same.

i assume from outside that you can connect to the first server with 3389 port for RDP? but connecting to the 1.101 with 3390 does not? i've set this up on linksys routers for people before and it should be ok.. maybe need to check settings on the router and update/reboot it.

[bankajac]

i assume from outside that you can connect to the first server with 3389 port for RDP? but connecting to the 1.101 with 3390 does not? i've set this up on linksys routers for people before and it should be ok.. maybe need to check settings on the router and update/reboot it.

Your are 100% correct! I can connect with my external IP:3389 but not with 3390. I believe that the router has the latest firmware and I will reboot it when I get home. I hope that will help but I am not optimistic.

[bankajac]

This is weird. I am able to connect with the old RDP client (5.2 I believe) but not with 6.0. Is there a different way to specify the port number is RDP 6.0 client?

[Guest]

Just IP:Port as before.

[bankajac]

So why does it not work on the new RDP client but works on the old?

[+BudMan MVC]

Are you trying to hit the console? They changed the flag from /console to /admin on the new client.

Also the new client has an option to not connect if auth fails under advanced.

[bankajac]

Are you trying to hit the console? They changed the flag from /console to /admin on the new client.

Also the new client has an option to not connect if auth fails under advanced.

No, not the console. I checked the authentication and it is set to connect and not warm. I'm just scratching my head still.

[+BudMan MVC]

Do you get asked for auth? You dont have anything under the TS gateway settings do you?

Are you using any 3rd party security to lock down your remote desktop connections. The 2x SecureRDP for example

http://www.2x.com/securerdp/download.html

It has a feature where you can lock down the client versions that can connect -- you might need to add the new client version. I have seen this issue before.

[bankajac]

No it does not ask me for authentication nor do I have anything under the TS gateway settings. The strange thing is that it worked fine when the port was 3389. I cange the TS listening port to 3390 and now I can only connect from the old RDP client. The only change was the port.

I am not using any third party software yet.

[+BudMan MVC]

You really should not have any need to change the port it listens on.. As already stated -- on the router just forward 3390 to 3389 on the inside.

example

PC one publicip:3389 ext - router - int 192.168.1.100:3389

PC two publicip:3390 ext - router - int 192.168.1.101:3389

PC three publicip:3390 ext - router - int 192.168.1.102:3389

I have set this up multiple times on many different routers. If your router does not support this would be the only reason you would have change the IP your PC rdp listens on. Any decent router would allow you to listen on a different port on the public side and then forward to different port on the private side.

Here is an example from a very common dlink router.

What specific router are you using? If the native firmware does not support this -- maybe it can run 3rd party like dd-wrt, openwrt or tomato, etc. Which for sure would allow for such a basic feature.

[bankajac]

I am using a WRT54G with the latest firmware. I do not see that option.

[+BudMan MVC]

Yeah that linksys native firmware is lame at best.. I would suggest you put 3rd party on that wrt54G of yours -- what hardware version is it?

As you can see dd-wrt clearly supports changing the port on a forward.

[bankajac]

Yeah that linksys native firmware is lame at best.. I would suggest you put 3rd party on that wrt54G of yours -- what hardware version is it?

As you can see dd-wrt clearly supports changing the port on a forward.

It is version six.

[+BudMan MVC]

version 6 is supported by dd-wrt and openwrt, but not tomato.

I would highly suggest you take a look at dd-wrt vs the lame native stuff. Not only will it allow you do do the different port forwards it has many many many features and enhancements over the native junk.

Here are the instructions for flashing a V6 to dd-wrt

http://www.bitsum.com/openwiking/owbase/ow.asp?WRT54G5_CFE

[bankajac]

Thanks, I will check that out. A while back I was considering Tomato. Is this better?

On my original issue, I decided to go to another workstation that had the old version of RDP client and it was not letting me connect. Now I think that maybe it has something to do with the security on our systems. When I stated before that I could connect from the old client, it was from our terminal server here (the terminal server I am connecting to is at another location). Maybe the workstations are blocking port 3390 and the terminal server is not? I disabled the firewalls on the workstations so it must be some other security program (ISA maybe?). I will try connecting from a friend's computer and that will be my final test.

[+BudMan MVC]

Yeah for it work the firewalls on both the client and server side are going to have to allow for the traffic. Or any other routers in between, etc.

As to dd-wrt being better than tomato -- I think so, but both have their advantages, etc. The problem is tomato does not support the version of hardware you have. So you could not run it if you wanted too.