Connection established via VPN but unable to access any devices or services.
Connection established via VPN but unable to access any devices or services.
Hi there, I'm trying to figure out why my company's setup isn't working. We use Fortinet/FortiClient for VPN access, but the connection is successful yet I can't reach any network shares. Even a ping doesn't work. On mobile devices it functions fine on the same Wi-Fi as the PC and LTE too. I can access all shares normally on my phone, but Windows seems to have issues. I've tested on Windows 7, 8.1, and 10 (1709). Any suggestions? Thanks in advance.
This appears to be a firewall problem. Setting up your Windows network to public access may prevent pinging, and it could also block other types of communication.
This system operates by connecting directly to a server on a machine inside the office, allowing external access through specialized software. The setup involves configuring the network and ensuring secure communication channels. Yes, it functions effectively, and I confirmed it runs with administrative privileges.
I'm experiencing some success currently. If I configure my router to assign IP addresses within the range of 10.0.0.XXX, adding "192.168.0.1 her-dcfile" to the Windows HOSTS file allows me to access the shares. However, if I allow the router to distribute 192.168.0.XXX, it clearly causes conflicts. PS the software generates a fresh virtual adapter each time a connection is established, using these specific IP settings.
It seems like a network setup problem might be at play. From the image, it looks like the software is giving the virtual interface an IP from the office router. That’s unusual since the DNS is set as your default gateway. I’m not very familiar with VPNs, but I understand tunneling concepts. It would be odd if DNS were directed to your default gateway and only then forwarded to a DNS server. If you change DNS to match what you’d see inside the office, would that help? Also, checking your IP settings on mobile and comparing them to this virtual interface could provide clarity. Maybe Windows is altering the DNS settings—honestly, I’m running out of ideas and might be mistaken.
I resolved the issue by adding another router (archer c7) in front of their ISP router, which assigned IP addresses within the 10.0.0.XXX range. Fixes the problem, though it's costly at a larger scale.