hyper-vDHCP & VPN
hyper-vDHCP & VPN
i set up a basic virtual network using Hyper-V. i created three new virtual machines—two running Windows Server 2016 and one with Windows 10. you can see everything in the attached image. the first VM became our router, the second served as the DHCP server, and the third was just a standard client PC. all configurations I’ll discuss here are the ones i believe were correct. i ensured proper firewall rules and IP addresses across all four machines, including my main host PC. this allows pinging and sharing files between them. my host can reach the V-Windows 10 machine, but the V-Windows 10 machine cannot access my host. that’s one of my issues. the second issue involves a VPN on the Windows Server 2016 RRAS machine with routing and remote access enabled. the VPN range is from 192.168.31.2 to 192.168.31.254. when trying to connect to the VPN from my host to reach the 192.168.30.0 network, it fails. anyone have any suggestions to resolve these problems?
Initially we lacked a DHCP server and no VPN was set up. I couldn't share files; for instance, PC X could open shared files from PC Y, but vice versa failed when using the ping command. Eventually I stopped trying to use the sharing feature in either direction. That's why I decided to add a VPN later on.
It doesn't need a VPN; just ensure each machine's Windows firewalls permit TCP 445 (SMB). This isn't the default setting. It doesn’t appear you need a VPN... though you can set one up, but without proper RRAS setup and split tunneling, success is unlikely. A VPN might seem unnecessary for a local network outside the WAN.
i added a vpn just to understand it better. i realize i probably don’t need it anymore. i’ve confirmed that mt tcp smb is open on the firewall across all my devices, with both inbound and outbound connections set properly.
Check if the port accepts connection via telnet; for instance, telnet 192.168.0.1 445. Replace 192.168.0.1 with the target IP to verify connectivity. If it connects successfully, the issue likely lies not with Windows firewall but with security settings or group policies on the device, possibly due to outdated SMBv1/v2 protocols. Ideally, all systems should use SMBv3+. Regarding VPN setup, that's great, but RRAS isn't the best platform for learning. I’d suggest building a pfSense or vyOS VM and practicing with real routing/firewall tools.
I previously used the telnet command but couldn't establish a connection. The output showed: connecting to 10.4.30.31... could not open connection to the host, on port 23: connect failed. I'm not very familiar with RRAS. Our teacher is explaining it this way. At first, the Windows Server 2016 machine we were using was just a regular PC, and later we upgraded it to act as our router. Thanks for your time.