The VPN client shows a green tick. You’re connected. But the shared drive won’t open, Remote Desktop times out, and the accounting software can’t find its server. This is one of the most common remote-working problems, and it almost always comes down to one of seven causes.
Work through them in order. Each one includes a quick test so you can confirm the cause before changing anything.
First: gather three facts
On the remote PC, open Command Prompt and run:
ipconfig /all
Write down:
- The IP address of the home or hotel network adapter (for example
192.168.1.25) - The IP address given to the VPN adapter
- The DNS servers listed for the VPN adapter
You’ll also need the IP address of the office server you’re trying to reach, for example 192.168.1.10 or 10.20.0.5.
1. The home and office networks use the same IP range
This is the most common cause. Many home routers and many small offices both use 192.168.0.x or 192.168.1.x. When the server’s address is in the same range as your home network, your PC thinks the server is on the local Wi-Fi and never sends the traffic through the VPN.
Test: compare the first three numbers of your home IP and the server IP. If they match (for example 192.168.1.25 and 192.168.1.10), this is your problem.
Fix:
- Best long-term fix: move the office network to a less common range, such as
10.20.0.0/24or172.20.0.0/24. Plan this carefully, because it affects DHCP, printers, servers and firewall rules. - Quick fix for one user: change the home router’s LAN range to something else, such as
192.168.77.x. - Temporary workaround: some VPN clients let you prefer the VPN for that subnet, but this is fragile.
2. Names don’t resolve, but IP addresses work
Test: try to reach the server by its IP address and by its name:
ping 10.20.0.5
nslookup fileserver
If the ping works but nslookup fails, or returns a public address, the VPN isn’t giving you the office DNS server.
Fix:
- Configure the VPN to push the office DNS server (usually the domain controller) to clients
- Add the office DNS suffix (for example
corp.example.com) so short names resolve - As a test, try the full name:
\\fileserver.corp.example.com\share
See our guide to DNS problems for more DNS checks.
3. Split tunnelling doesn’t include the server’s subnet
With split tunnelling, only traffic for specific office networks goes through the VPN. If the server’s subnet is missing from that list, traffic goes to the internet instead.
Test:
route print
Look for a route to the server’s network (for example 10.20.0.0) pointing to the VPN adapter. If it’s not there, the VPN isn’t routing that subnet.
Fix: add the server’s subnet to the VPN’s split-tunnel or “accessible networks” list on the firewall or VPN server. If you have several office subnets (servers, VoIP, printers), add each one you need.
4. Firewall rules don’t allow VPN users to reach the server
Many firewalls create the VPN but don’t automatically allow VPN users into the internal network, or allow only some ports.
Test: use PowerShell to check whether a specific port answers:
Test-NetConnection 10.20.0.5 -Port 445
Test-NetConnection 10.20.0.5 -Port 3389
Port 445 is file sharing (SMB), and 3389 is Remote Desktop. TcpTestSucceeded : False means something is blocking the connection.
Fix: on the office firewall, add a rule from the VPN address pool to the server’s address, allowing only the ports needed. Keep it specific. VPN users don’t need access to the whole network.
5. Windows Firewall on the server blocks the VPN range
Even when the office firewall allows the traffic, the server’s own Windows Firewall may only accept connections from the office subnet.
Test: check the server’s inbound rules for file sharing or Remote Desktop and look at the Scope tab. If “Remote IP address” lists only the office network, VPN clients will be blocked.
Fix: add the VPN address pool to the scope of the rules you need. Don’t turn the Windows Firewall off.
6. The server has no route back to VPN clients
Traffic needs a path in both directions. If the VPN is terminated on a device that isn’t the server’s default gateway (for example, a separate VPN appliance), the server may send its replies to the wrong place.
Test: from the server, run tracert to a VPN client’s address. If the replies go to the internet router instead of the VPN device, the return route is missing.
Fix: add a static route on the main router or firewall for the VPN address pool, pointing to the VPN device. Alternatively, terminate the VPN on the main firewall.
7. MTU and fragmentation problems
If small things work (ping, short web pages) but large transfers hang, such as opening big files or Remote Desktop freezing after login, packets may be too large for the VPN tunnel.
Test: send a ping with a fixed size and “don’t fragment” set, reducing the size until it succeeds:
ping 10.20.0.5 -f -l 1400
ping 10.20.0.5 -f -l 1300
If 1400 fails but 1300 works, MTU is the likely cause.
Fix: lower the MTU or enable MSS clamping on the VPN server. Most firewall vendors have a setting for this on the VPN interface.
Other quick checks
- Is the server actually up? Ask someone in the office to check.
- Is the VPN connected to the right site? Users with several VPN profiles sometimes connect to the wrong one.
- Did your password expire? Mapped drives may fail silently with old credentials. Lock and unlock the PC after connecting the VPN to refresh them.
- Do you need “connect before logon”? On domain laptops, some settings only apply when the VPN connects before Windows sign-in.
Quick summary
| Symptom | Likely cause |
|---|---|
| Home and office IPs look the same | Overlapping IP ranges |
| IP works, name doesn’t | VPN not pushing office DNS |
No route to the server’s subnet in route print | Split tunnel missing the subnet |
Test-NetConnection fails on the needed port | Office firewall rule |
| Works from the office, not via VPN | Server’s Windows Firewall scope |
| Server can’t reply to VPN clients | Missing return route |
| Small things work, big transfers hang | MTU |
For the bigger picture on securing remote access, see our firewall hardening checklist. This guide is also our Fix It Friday #05 on Instagram.

