Totd

I had serious issues getting Windows 2016 working properly on my BL460g6 blades, but that was a NIC driver issue (Windows would blue screen when I tried to configure a virtual switch). After enough searching (And firmware patching), I eventually found a procedure to get working drivers on them.
 
If you can find a ProLiant Support Pack (Firmware DVD), it might be worth trying firmware. THe ProLiants are pretty solid. That said, the E55xx processors are practically space heaters now, so you might be better served (No pun intended) by getting a little mini PC, or even a Raspberry Pi to provide a basic VPN server. If I was sensible I would do that, but I do love the bragging rights at work

+1 to the VPN idea. I've done that at home, but one thing to definitley look out for is AES NI support on your CPU. I moved from Xeon E5530 to E5606 and the sudden increase in performance (OpenVPN on Ubuntu) was like night and day... The dl380 g6 should be around that 2009-2011 era so it's impossible to say if you have on-CPU AES acceleration.
 
FWIW: I have OpenVPN as a conventional "VPN" service, but I've also found a cool asp application called Myrtille (Sort of like a web-based RDP client) which I have found to be super helpful when I'm connecting from work. (I work in IT consultancy, so of course our internal IT department block everything except TeamViewer... )

Actually, I'd argue that it is bad. You will not damage the computer hardware, but depending on what you're doing you may actually drop important connections. It's going to be less bad that pulling out a USB drive, but there is still the possibility of corrupting a file that is mid-transfer, or interrupting your connection to the local Minecraft server - That's why the connections have a locking tab, you don't want the connection just popping out randomly.
 
In all seriousness though, you won't break anything. If you do a quick swap of a cable to change ports or something you *may* have a program complain about the interruption, but you can usually resume a download where it left off, and if you're using an application that is particularly sensitive to network drops (Like SSH or IRC) you'd probably know about it, so just close your sessions before yanking on the cord.
 

I just managed to confirm my email and get signed in, but had a similar issue. Office 365 rated the confirmation email as "High Confidence Phish". I have pulled the headers, etc. from the message so you can check any details you want (Maybe a DKIM issue?). Let me know if you'd like me to send them through and where.