mleidich
asked on
Custom port
I have a ISA 2006 and want to come in on address x.x.x.x:101010 and be fowarded to my PC x.x.x.1, but want to go back out on port 3389.
I do not want to change my PC to listen on port 101010 for RDP. How can this be configured?
If I make the PC RDP port 101010 it works fine from the outside, but I do not want to do that.
I do not want to change my PC to listen on port 101010 for RDP. How can this be configured?
If I make the PC RDP port 101010 it works fine from the outside, but I do not want to do that.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just external
ASKER
I can see this should be working but it isn't. Do you need to reboot the ISA?
It doesn't make it to the PC with the rule and it should.
It doesn't make it to the PC with the rule and it should.
No, ISA does not need rebooting. There is nothing else to do apart from ensuring that your external firewall/router is allowing port xxxx through to the ISA in the first place and secondly, making sure external RDP users make the RDP connection using port xxxx
Thanks
ASKER
Just one last question, I see someone is already setup on the network with this rule. When I publish my rule I get this error
"The Firewall service failed to bind a socket for the server on the ISA Server computer because another process is using the same port. Check if any other process is using the same port, and stop it if necessary"
Can you only have one rule like that?
Only One PC can be seup to come in on a x.x.x.x:xxxx to publish to 3389?
"The Firewall service failed to bind a socket for the server on the ISA Server computer because another process is using the same port. Check if any other process is using the same port, and stop it if necessary"
Can you only have one rule like that?
Only One PC can be seup to come in on a x.x.x.x:xxxx to publish to 3389?
Yes - only one instance per external ISA ip address. If you had two external ISA IP addresses then you could set up the same on the second ip address also and so on.
or
If port xxxx = 4444 currently then you could make a new protocol using tcp port 4445 and publish another instance of RDP using this so you had more than one listening port but on the same IP address.
or
If port xxxx = 4444 currently then you could make a new protocol using tcp port 4445 and publish another instance of RDP using this so you had more than one listening port but on the same IP address.
ASKER