Replies: 1 comment
-
|
Hi!
Yeah without --native when you just access with the site's IP you are
basically assigning different unique ports to different targets on the
remote network. So as you discovered you cant have overlapping ports for
different clients. There also is not a great way to limit certain
clients to certain ports unfortunately right now.
We definitely want to do something like that in the future.
With --native you could use a remote subnet and setup NATing like in the
docs. This would mean that each client would be able to access the
target machine with its IP address and the RDP port. But you would have
to deal with the firewalling and natting yourself.
https://docs.digpangolin.com/manage/clients/add-client#remote-subnets
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I would like to know if it is possible to set up the following configuration:
The goal is to create a VPN client that allows access to multiple Windows servers via RDP (port 3389).
However, when adding a client resource, it seems that it is not possible to define multiple servers using port 3389. This seems logical since each site is accessible via a unique IP address (example: 100.90.128.1).
My question is therefore: is this a limitation that can only be circumvented using the --native feature, which is available exclusively on Linux?
The ultimate goal is for each client to be able to access only the client resources assigned to them.
Thank you in advance for your clarification.
Beta Was this translation helpful? Give feedback.
All reactions