Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Inbound connection to Remote Desktop 1
- Thread starter gajh
- Start date
-
1
- #2
Hello,
Do you have an available public address? Or is it on a DSL or cable connection were you only have one IP.
The reason I ask is because if you have an available IP, we could use a MIP. If not, you can use a VIP, and is actually preferred for what your trying to accomplish.
Simply use the WEBUI, open your "Untrust" interface, and go into the VIP link. Create a new VIP and use the port needed, along with the internal IP to your machine.
Once the VIP is created, you can create a TCP 3389 service. Then add a policy from Untrust to Trust, permit, 3389 via the VIP. You also might need a route in case you don't have one. Your existing default route would be used and that would prevent the traffic from routing to the internal IP.
Hope this helps.
Rgds,
John
Do you have an available public address? Or is it on a DSL or cable connection were you only have one IP.
The reason I ask is because if you have an available IP, we could use a MIP. If not, you can use a VIP, and is actually preferred for what your trying to accomplish.
Simply use the WEBUI, open your "Untrust" interface, and go into the VIP link. Create a new VIP and use the port needed, along with the internal IP to your machine.
Once the VIP is created, you can create a TCP 3389 service. Then add a policy from Untrust to Trust, permit, 3389 via the VIP. You also might need a route in case you don't have one. Your existing default route would be used and that would prevent the traffic from routing to the internal IP.
Hope this helps.
Rgds,
John
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question