Hi @JaketonCuatro 

Thanks for posting in our business forum.

Winserver already provides the LAN IP as a DHCP server?

Don't seem to be a good way to place the router in.

Even if you place the router in this network, the router will create a NAT and devices in the ER605 LAN will pass one layer of NAT.

Hi @JaketonCuatro 

Thanks for posting in our business forum.

JaketonCuatro wrote

  @Clive_A 

 

Winserver already provides the LAN IP as a DHCP server? YES (DHCP IP RANGE - 192.168.10.1 - 192.168.10.199

 

Where should I place the ER605 in this network architecture and what configuration should I use?

 

I have tried to change the LAN IP of the er605 to assign it an IP within the LAN of the Windows server and set the DHCP as DHCP Relay with Server Address 192.168.10.200 but now I do not have access to the er605 from the local network of the server since it does not allow me to change its IP address of 192.168.1.1 which is fixed and does not let me change it.

 

 

 

 

 

I think there is a fundamental problem with the whole setup as far as I read.

If you want the router to host the OVPN, then the DHCP and clients should be within the 605 LAN.

Or use a full tunnel when the OVPN client is connecting to the server.

If there is a DHCP server,

Hi @JaketonCuatro 

Thanks for posting in our business forum.

JaketonCuatro wrote

  @Clive_A 

From what you say, it is not possible to use the Omada ER605 in this type of network infrastructure with a Windows server.

Do you have any switch-type device that allows direct VPN connection on the LAN?

ER605 is a layer of NAT. It is not gonna work if a device on WAN accesses a device from the LAN. It'd work if you port forward or DMZ but this is not ideal anyway as the NAT is still there.

If you already have a Winserver to work as the DHCP server, you should consider if the Winserver can also host the VPN servers so that you don't use ER605 in this network to create the VPN and the extra layer of NAT.

It does not fit anywhere in this topology and your expectations.