A recent change in my ISP setup forced me to deal with an issue I have been keeping on the back burner. A while back, I had to change to a new VPN client for work. I had difficulty connecting as it told me a firewall must be blocking IPSEC or UDP. Blaming it on the router I had circled thru several with some initial success but ultimately failure. Having no choice now, I have narrowed it down to my network switch. the VPN is IPsec to a cisco vpn server (port 4500 and all).
Bottom line, with switches like GS108Tv2 and GS-1100-5 between my work pc and router (currently Sophos UTM 9) no problem. But my fancy tplink t1600g-28ts, no go. it validates the password ok but can't connect the vpn itself.
Any seasoned veterans out there have an idea how this switch could be messing it up?
thanks in advance!
I'm new around here, looked for the presentation thread but haven't found any!
Anyway I hope to be able to contribute (as far as my newbie's knowledge will be useful )....
Speaking about what I'm trying to do, I have this amazing microserver gen8, on which I have 2 3tb wd red as storage and an ocz 125gb ssd on 5° port.. Installed a couple of days ago mr. PROXMOX (I'm a complete newbie to it too ) and configured the xpenology 6.0 that runs amazingly!
Now.. I'm just wondering which is the best option to configure a vpn (possibily openvpn) and from my inexperience I found a couple of options:
- try a container with turnkey debian 8 OpenVPN
- install ubuntu on a VM and setup openvpn
- try the vpn server on xpenology
or the least pleasurable
- install openvpn on my windows 10 pc and leave it turned on in way to access the microserver through vpn..
What do you think is better to do? Considering that I am a real noob and will need some guide or some tutorial (already googled something and Have found a lot of material on the openvpn site.. but honestly can't find so much about proxmox and vpn)
PS: sorry for my english, but I'm italian and I'm still learning!
thanks a lot!
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?
I am new here. I am a little desperate because despite the fact my job is IT I don't get it to work. My homeserver is running Server 2012 R2 Essentials and because somehow the AD and file shares did not work properly anymore I decided to reinstall the OS from scratch. After reinstallation I reconfigured anywhere access and reobtained my remotewebaccess.com-subdomain which worked fine except for the the remotedesktopgateway did not get the certificate properly which I fixed with this guide here. This step was not necessary when I installed the OS some years ago for the first time.
Up until the first forced reconnect from my ISP the IP-adress of my router matched with the one in the DNS-record. But after that it did not refresh anymore. The error message in the Dashboard says (I hope this matches the english version of the message): The dynamic DNS information cannot be updated. Details to this message says furthermore: The DNS-information cannot be updated because no connection to the domain name provider can not be established. Contact your domain name provider. And after the lifespan of the DNS-record expires additionally the error message appears that the domain name can not be resolved...Unsurprisingly.
The weird thing is that DynDNS for AnywhereAccess/RemoteWebAccess has never been an issue with the old and now overwritten OS installation. In desparation I made a bare metal recovery from the old OS installation to check the behaviour of DynDNS which worked still just fine. A second WS2012R2E-installation inside a VM was a bit contradictory. The original remotewebaccess.com-domain could not be reinstated but a new one registered. Though I haven't checked if the new domain can update the DNS-record.
Now with the once again reinstalled OS DynDNS acts as described above. Port forwarding (Port 443) on my router has been set up for testing purposes both via UPnP and after that manually. Didn't matter before reinstallation because it worked both ways. I deliberately left out Port 80 for security reasons.
I have searched through the eventlog and the Internet, to no avail. The only remotely useful hint was to change the Windows Live-password had no effect. And the Eventlog is so overwhelmingly packed with events of any kind I also ran several times the repair wizard from the Dashboard with always the same error. I even was unable to release my subdomain through the configuration wizard.
I can imagine that the public certificate from GoDaddy needs to be imported somewhere for authentication to make DNS-record updates possible. But that would make the Windows Live-login obsolete.
Has someone any advice how I can get the DynDNS-service back up running? Or where I have to search for more detailed hints for the cause? I have already considered that it is not a "broken service" of the OS but rather an external issue beyond my control (which suggests the error message). But that contradicts the fact that the recovered installation was able to update the external DNS-record. If the cause is really external who is the correct contact? GoDaddy or Microsoft?
Edit: Maybe do I miss some windows updates or update rollups that do not come through Windows Update? I have updated the OS only via the OS-internal Windows Update function and right after installation some with wsusoffline.
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.