Standalone Windows DHCP Server - "Requesting an IP address to the DHCP server in VPN"
Posted: Fri Apr 08, 2022 12:25 am
Hello All!
I'm currently experiencing issues with my Softether VPN Server Setup and can't figure out what the issue is or how to resolve it, and I'm hoping someone maybe able to help me figure it out?
--
My Goal: RemotePC-to-LAN topology that works for LAN and WAN clients. Ultimately, I would like my clients to access my corporate network so they can receive their group policies and windows updates, etc.
--
My Setup is as followed:
3 Networks involved:
Corporate Network - 192.168.5.X - DHCP and VPN Servers
LAN Network - 192.168.1.X - ESXi Host and VPN Servers
WAN - External Clients
(VPN Server: SoftEther Corporate Network is Bridged, 2nd NIC is LAN Network as Static Public IP is not an option)
Physical ESXi Host that hosts the below VMs:
Domain Controller/DHCP Server - VM - Windows Server 2016
SoftEther VPN Server - VM - Windows Server 2016
Client - Physical Machine - Windows 10 Pro - Using WiFi and 4G Networks to test LAN and WAN connections.
Notable configurations:
Promiscuous Mode enabled through Virtual Switch across all NICs
Port Forwarded 443 on Home Router for VPN Server
--
My LAB Issue:
I am able to connect my Client device to my VPN Server (using WiFi) but unable to ping other devices on the Corporate network and unable to obtain a DHCP IP Address from my DHCP Server.
I am unable to connect my Client device to my VPN Server using 4G, I receive an immediate error.
This setup worked previously, but unsure why this has happened.
--
Troubleshooting:
Checked Client side and Server Side Logs - No errors with clear indication, but noticed error code 11 server side.
Updated and Restarted VMs.
Turned off Firewalls on all devices.
Double checked Promiscuous mode was enabled.
DHCP Server not picking up client in Address Leases.
DHCP Server unable to ping client, client unable to ping DHCP.
VPN Server able to ping Client, Client able to ping VPN Server (WiFi).
Saw a forum that mentioned a regkey that may cause issues - DisableDHCPMediaSense - Non-existent on my machines.
I'm currently experiencing issues with my Softether VPN Server Setup and can't figure out what the issue is or how to resolve it, and I'm hoping someone maybe able to help me figure it out?
--
My Goal: RemotePC-to-LAN topology that works for LAN and WAN clients. Ultimately, I would like my clients to access my corporate network so they can receive their group policies and windows updates, etc.
--
My Setup is as followed:
3 Networks involved:
Corporate Network - 192.168.5.X - DHCP and VPN Servers
LAN Network - 192.168.1.X - ESXi Host and VPN Servers
WAN - External Clients
(VPN Server: SoftEther Corporate Network is Bridged, 2nd NIC is LAN Network as Static Public IP is not an option)
Physical ESXi Host that hosts the below VMs:
Domain Controller/DHCP Server - VM - Windows Server 2016
SoftEther VPN Server - VM - Windows Server 2016
Client - Physical Machine - Windows 10 Pro - Using WiFi and 4G Networks to test LAN and WAN connections.
Notable configurations:
Promiscuous Mode enabled through Virtual Switch across all NICs
Port Forwarded 443 on Home Router for VPN Server
--
My LAB Issue:
I am able to connect my Client device to my VPN Server (using WiFi) but unable to ping other devices on the Corporate network and unable to obtain a DHCP IP Address from my DHCP Server.
I am unable to connect my Client device to my VPN Server using 4G, I receive an immediate error.
This setup worked previously, but unsure why this has happened.
--
Troubleshooting:
Checked Client side and Server Side Logs - No errors with clear indication, but noticed error code 11 server side.
Updated and Restarted VMs.
Turned off Firewalls on all devices.
Double checked Promiscuous mode was enabled.
DHCP Server not picking up client in Address Leases.
DHCP Server unable to ping client, client unable to ping DHCP.
VPN Server able to ping Client, Client able to ping VPN Server (WiFi).
Saw a forum that mentioned a regkey that may cause issues - DisableDHCPMediaSense - Non-existent on my machines.