For details on cookie usage on our site, read our Privacy Policy
NAT Configuration to access Remote Desktop
- LIVEcommunity
- Discussions
- General Topics
- Re: NAT Configuration to access Remote Desktop
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
NAT Configuration to access Remote Desktop
- Mark as New
- Subscribe to RSS Feed
- Permalink
07-22-2019 04:09 AM
Hi,
We need to configure an input rule to authorize an public IP address to access at one of our virtual machine on our subnet.
Concretely, I need to authorize public IP address 195.193.194.195 access directly to our virtual machine with the private IP 192.168.1.1 on the port 3389 (Remote Desktop) only via our public IP address (82.83.84.85).
I configured a NAT rule but it didn't work. May be I doing something wrong ?
Can you help us about this topic ?
Thank you for your help.
- Mark as New
- Subscribe to RSS Feed
- Permalink
07-23-2019 10:45 AM - edited 07-23-2019 10:46 AM
Exposing RDP = BAD BAD BAD!
Use a product designed to do this that can open via a proxy service. Something like teamview or a similar solution that includes some kind of authentication/authorization. This avoids all the NAT goofyness and security implications you are getting yourself into as well.
- Global protect VPN disconnecting multiple times in GlobalProtect Discussions
- No Super User to authorise my Support Portal account in General Topics
- Radius authentication not working in General Topics
- update-remote-system command not getting triggered in Cortex XSOAR Discussions
- Civil3D 2023 and Global Protect in General Topics
Show your appreciation!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
