Is it the router or what . . .

[rcsinc]

I have two separate small businesses that I run out of my home.

I have Optimum’s cable coming into the house with boost with all available ports open (or at least that’s what they say) and a Scientific Atlantic modem.

I have a Cisco Linksys WRT610N router.

I have two servers behind the router.

The servers are hardwired to the router.

I need to access these servers remotely by more than one person at a time. 4 on the first server, 3 on the second server.

Server One is one company running Windows Server 2008 OS with an application that is accessed via RD (5-client license). This works fine.

The second server, Server Two, will run a separate application once I can get connection to it from the outside world. Right now it is running Windows 7 Profesional OS.

It seems that I cannot get access to BOTH servers with port forwarding. I am not sure if the router does not let it, as in not capable (although I don’t know why), or do I not have it configured correctly. I have configured similar networks using SonicWall appliances. That's why I ask if it is a limitation of the WRT Router.

I need the first server to run RD the way it is right now. So, the second server can either use Remote Desktop as well (if possible) or via HTTP using some particular port (preferred), or something else – if you have any ideas.

Any ideas?

Thanks,

BTW – I do have a block of IP address that I pay for from an ISP in PA. I am not using all of them. If that will help anything.

Thank you.

- Robert

[Tripredacus]

Some questions from me, probably not an answer but maybe it triggers something...

1. Do both servers have private IP addresses? For example, I am thinking that your Cable Modem gets a Public IP, then the router gets an IP from the modem.

2. Are you using either the router or modem in Bridge mode? I do not know if the modem supports this or if Optimum has locked this feature.

I am thinking that you cannot RDP into both machines at once because they use the same port. Did you try changing the port used for RDP on the second machine?

[rcsinc]

Tri, (or is that Trip ),

Yes, both servers have private IP addresses; Server1 = 192.168.2.100, Server2 = 192.168.2.101.

The Router IP address = 192.168.2.1. The modem gets its address from the cable company = 12.123.12.1234. I know that can change but rarely does unless the power's out for several hours. Anyway...

I have port forwarding on the router to forward any request on the Remote Desktop port (3389) to Server1 so when someone uses Remote Desktop to access 12.123.12.1234 they get a login credentials screen for Server1. If the credentials match, they are pushed into sign-on screen for the application. This works perfectly.

I then set up another port to forward to Server2. For example: http://12.123.12.1234:6789, port 6789 forwards to Server2 @ 192.168.2.101. This does NOT work. I am looking to have similar application execution as on Server1.

I do not know what Bridge Mode is, so... ?

[MrJinje]

The easy method to connect to multiple behind router targets, is to turn one of your servers into a VPN gateway. Then after the VPN is established you can connect directly to each server as if they were on the local lan. (by specifying the internal IP address 192.168.2.101 or 192.168.2.100)

[rcsinc]

The easy method to connect to multiple behind router targets, is to turn one of your servers into a VPN gateway. Then after the VPN is established you can connect directly to each server as if they were on the local lan. (by specifying the internal IP address 192.168.2.101 or 192.168.2.100)

Please elaborate.

1. First though, I do not want to have to install and then support VPN software on the remote clients. Using TCP or Remote Desktop pretty much allows someone to use any computer that is available wherever they may be to access the application.

2. Second, the users of Server1 are not the same users of Server2. I am the only common user.

3. Third, one of the reasons that they are separate machines is that I don’t want the people who access Server1’s apps to even know Server2’s apps exist. They are two completely separate entities.

If it’s still doable and would be blind to the end-user, I’m open to it. With one exception, see #1

AND Thanks to everyone for the replies!!!

[MrJinje]

in that case, then your next easiest choice will be to just use one of your other Public IP's. That way you don't need to fumble with port-forwarding and changing the RDP listening port.

Plus your users will have no clue about the other server.

[CoffeeFiend]

I then set up another port to forward to Server2. For example: http://12.123.12.1234:6789, port 6789 forwards to Server2 @ 192.168.2.101. This does NOT work

Because terminal services on Server2 ain't listening on port 6789. You would have to change the destination port (source stays 6789 or whatever you setup, but destination port would have to be 3389 (on Server2's IP obviously). That's assuming your router supports doing this (I've never tried the WRT610N). Then it should work just fine. If it doesn't, then you'd have to change the port terminal services listens on indeed.