been reading through this forum, and also 2012 r2 essentials, but somehow i am not getting my vpn to work
gen8 with 2 nics connected and ilo4 nic connected. Nic 1 is connected to internet, nic 2 to my internal network
nic 1: 192.168.2.200, with gateway
nic 2: 192.168.10.229, no gateway
nic 1 is connected to 4g router. Portforwardings for ports 80, 443, 1723 to ip 192.168.2.200
after installation of server 2016e activated a remotewebaccess.com adress at microsoft, and installed remotewebacces and vpn.
remotewebacces with /remote option is working
my windows 7 laptop is in the domain of my server, client connector installed, and backup etc working.
when i am at my office, or connected via a hotspot of my iphone, i want to make a vpn connection.
everytime i start this, i see shortly that username and login are checked, but that is it, connection stops.
i know i am overlooking something, but as allways, the longer you look, less change of finding it.
any suggestions?. No need to hurry, i can only test this again on saturday.😩😏. Have to work tomorrow.
any help is appreciated
Hi all, new here and WSE noob.
So I have a server running WHS2011 and I want to go WSE2016 (or WSE2019 if it will still offer client backups, web access etc.). So I installed a evaluation and am testing with old unused computers. Now I know that there are two things some talk about when using WSE in a SOHO setting: not joining the domain and not having WSE as the DNS server.
Now my question is basically this: I connected a client with defaults (so no hacks) and now I am wondering "why bother"? I don't understand what the reasoning is behind not joining the domain for instance. As far as I can tell, the user sees no difference between connecting to WSE2016 or WHS2011. But people are talking about it so there must be a catch I don't get.
Edit: My clients would be both fixed PCs as laptops which would have to be able to work on other networks (but not connected to other servers or anything).
Background: I had a WHS that I used as a backup machine for several PCs in my house. That one finally bit the dust a few years back with hard drive failure. Due to life I didn't rebuild it and when with an NAS for backup.
As one of my client PC's drive was failing a few years after WHS crashed, I did a local back up of that PC to an external hard drive. I used the "backup" software that was on the PC and thought I saved myself.
Looking at that backup drive now, I'm seeing what appears to be a backup created by a WHS with references to multiple PCs from my home network. I can't find a restore program that can access those files properly and now I'm wondering if I need to try the WHS client restore app. Unfortunately, I don't have the CD's any more.
1. Is there a way to positively identify this back up as a WHS style backup? The top level of the drive has a file called QSM_VolumeID and a folder named DE. In the folder named DE are two folders named "folders" and "shares". There's also a file named DEguid.
2. Is the client recover software from WHS V1 available anywhere for download?
Any other thoughts, ideas or help would be appreciated. Also, if there's another topic that addresses this, pls point that out as I'm happy to read to save everyone's time.
Per my signature, I have WHS 2011 installed on a HP N54L that I built and have had in service since March 2013. I have a CorsAir 60Gb SSD HD running on SATA #5 with the modded bios to allow WHIS to install on this small OS hard drive.
I have a WD PCI-e USB 3.0 card with a 3 yr old Seagate Backup Plus 2Tb drive connected that WHS places the Server OS backups to.
With Windows updates, the 60 gb SSD has only 5 gb space available and I'm getting warnings as such. So, I want to install a new Sandisk 240 gb SSD to replace it. When I run the WHS Server disk, the restore server OS process either locks up looking for the files on the Seagate usb drive or does not discover the files and the scan just runs and runs.
I remove all my storage drives from the N54L four bays. Swap the old 60gb OS SSD for the new 240 GB SSD Plug in my LG portable DVD drive into the rear USB 2.0 and use it to spin the WHS disc Connect the Seagate Backup Plus USB 3.0 Drive to the N54L (this is where it takes four paths and all fail) (bios is configured prior for proper boot sequence of DVD first, new OS SSD 2nd) Since USB drives are backwards compatible, if it is connected to the N54L 2nd remaining 2.0 USB from boot up (post screen shows the DVD, the new SSD and the Segate USB Drive), I select Restore Files in the back up menu the screen goes black except for the WHS background image. Sits and never resolves. Or leave the Seagate USB drive unconnected until I get to the Restore Files menu, connect, then select restore files/etc. The scanning for back up files dialog runs this time and never finds the files. Only way to get out is to hard reboot the server. Same as #2 but skip the initial file search and click advanced. Connect the USB dirve and then click refresh and nothing shows up. Click scan and it too will run forever and not see the drive with the backup files. Or resort to installing the PCIe drivers via a thumb drive and then connect the drive to the PCIe USB 3 and it will not recognize it in the list. Click search and it searches without success.
I'm thinking I need to transfer the WHS OS Backup files on the Seagate Backup Plus USB drive onto another bare hard drive and insert into one of the N54L HD bays and see if it will then find the backup files. Thus eliminating the whole USB 3/2 interface.
Thanks in advance.
Once in a while, I write something, not expecting much. Months later, I realize the article's popularity continues to grow. Here's just such a piece, from back in Sep 2013 called:
Rufus takes 5 minutes to create a UEFI bootable USB 3.0 flash drive for Windows 8.1 installation
Visitor davepermen was reading an article about using Rufus to create a bootable ESXi USB drive, for installation to itself. He apparently also owns a Surface Pro, decided to give Rufus a go, and found success, then typed up this comment.
Free software, no adware, no catch. Just a simple and effective and fast utility I thought I'd share. Especiallyl given there seems to be less and less of it for Windows these days.