sofaware.infopop.cc
SofaWare Discussion Groups
SmartCenter Management
SmartCenter Managed Edge Device Behind NAT??|
Go
![]() |
New
![]() |
Find
![]() |
Notify
![]() |
Tools
![]() |
Reply
![]() |
|
|
Junior Member |
A remote ISP only provides us a connection via a NAT to a Public Address.
The VPN Edge device is assigned an IP in a private address range that is NATed externally. (Valid IP) ------- (ISP Router) ------- (Edge Device) Public Private Any idea how to get this to work? I tried setting the address to the private address and setting the Link Selection to the External NAT address. With this I couldn't register the device and got the error "The actual gateway IP conflicts with the configured gateway IP". I assume VPN-Edge policy server didn't like seeing traffic from the Valid IP Address that was not part of the topology. I tried the DisableIpLock=true setting, but I assume it still wants to see it from one of the gateway's IP addresses and not the NAT address that it knows nothing about. So I tried changing the external Adapter to Dynamic on the VPN-Edge Object...Now I could register the Edge Device!...but none of the VPN functionality works? Any ideas if it is possible to have a VPN Edge device that is behind a Static NAT?? Is it even possible. |
||
|
|
Junior Member |
In case anyone cares it works. There was a domains object in my policy. Although it compiled and installed ok it caused havoc on the VPN-Edge device. So DO NOT use a Domains object in a VPN-Edge Policy!
|
|||
|
| Previous Topic | Next Topic | powered by eve community |
| Please Wait. Your request is being processed... |
|
sofaware.infopop.cc
SofaWare Discussion Groups
SmartCenter Management
SmartCenter Managed Edge Device Behind NAT??
