I used to run a Win Home Server V1, then an Amahi Home Server and now I have built a Home Server based on Win 10 Pro.
I have got everything running really well except for the VPN for remote access. For some weird reason, I can connect remotely to my Home Server by VPN and it gives me an IP address on the home network ok, but I can't see, access or ping the Home Server itself - yet I can access every other piece of kit connected to the home network (printer, router, other PCs, etc.) through the VPN by entering their IP address into my browser or by pinging them through the command line Ping command with their IP address.
It's as though, by providing access the the rest of the network, the Home Server has become invisible to itself and so I can't access anything on it.
I have used the built-in Windows VPN on Win 10 Pro, rather than using a third party package. I have been using Terry Walsh's "How to Build a Windows 10 Pro Home Server" e-book which has been excellent so far, except that on this, it tells you how to set up the VPN and then just says - go ahead and connect to your remote Home Server - but doesn't address any potential problems - like this one.
Is this something anyone has seen before? Any ideas what the problem could be?
At my home office i have a HP Microserver N40L and i use “Windows Server 2012 R2 Essentials”.
On the past i had some initial configuration and instability problems with Anywhere Access + VPN, but somehow i finally have them working properly and stable for the last months.
But last week i needed to format the server and install a brand new and clean “Windows Server 2012 R2 Essentials”.
I have made the installation, then made all the updates, then i have added some roles and features and then i went to setup Anywhere Access + VPN and it’s giving me 2 errors (one saying that i have port 80 and 443 blocked and other saying i have more than one router on my network).
Both errors do not exist, because besides manual confirmation that ports are open, no network configuration was changed since last week. And if all was working in the past, now all should also work.
I have already try to turn all off and then try again to run the Anywhere Access + VPN repair wizard and the errors are still the same.
I have already pass too many hours trying to identify what is wrong… and i can’t wait to much longer.
So i have 2 requests to make to anyone reading this:
1- If anyone has any idea of what is the problema, and wants to share the advice, great! Please do.
2- I’m willing to hire and pay to an expert to remote login my server and solve the problem. I can provide remote access and be your remote eyes so you can see all the network setup. If you can do this, please reply to this thread with your email or send me a PM.
My network setup is as follows:
ISP Router (in bridge mode) > Router TP-Link ER-5120 > Smart Switch TP-Link TL-SG108E
Then Smart Switch then connects:
- Port 1 to Router
- Port 2 to Access Point TP Link TL-WA901ND (with QVLAN enable for private and public wifi networks)
- Port 4 to Unmanaged Switch TP-Link TL-SG1016
Then the Unmanaged Switch connects to my server and my home office computers.
After I have setup my office network and installed the “Windows Server 2012 R2 Essentials” Connector on all the Windows 10 desktop computers, all the desktops connect auto-connect to the server using the desktop Connector. The internal LAN is setup as a private domain network.
But with the Connector installation, I have noticed that it has also been created a VPN on all my desktop computer, inside my office on my internal LAN network that is disabled by default.
In a simple way and to resume, all my desktop computers connect properly to the server using just the desktop connector, with the VPN disabled.
I just use / enable the VPN on the laptop computers, always when I’m outside the office.
So my question is if I should also always enable the VPN by default on all my desktop computers that are located inside my office on my internal LAN network?
Can anyone advise me on this? Are there any kind of advantages vs disadvantages on having the VPN on vs off inside the internal LAN?
I’m setting up my small office network and on my server I will use the “Windows Server 2012 R2 Essentials” and I will want to enable and use the “Anywhere Access” and “VPN” build in features to have remote access to my server from outside.
Regarding this, my router uses as factory default the port 80 to access the admin interface.
But I think I should change this in order for my router not to be visible from outside world, and also not to conflict with any of the Windows Server services, correct? It’s a best practice to do this correct?
If yes, I really don’t know which port I should use. I’m think on using port 8080 so the router access from inside my network will become: http://192.168.0.1:8080.
So can anyone please share your advice on which port I should use for my router admin interface access?
It must be a port that can only have access from my internal network and it must be a port not used by common services in order not to create conflicts.