Not server 2016 related, but I recently have had quite a few frustrating moments with internet on a client station, windows 10 and anniversary update. The internet would stop working because I had a static IP assigned to my network adapter. It took me Quite a bit of time to figure it out and with all recent windows updates seems like the bug went a way. Resetting IP stack, constant rebooting, loading latest drivers for the network adapter, lots of fun. Something in the latest windows code and network adapter/IP stack didn't click together. The machine I had HP Z230 SFF Workstation. Thanks for sharing the 2016 experience. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of George Bell Sent: Friday, March 31, 2017 2:04 PM To: 'Blind sysadmins list' <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Windows Server 2016 I've a feeling it won't be too long before some of you may be faced with installing Windows 2016 Server. You may want to bear the following in mind as it cost us a week and much frustration before stumbling on the solution. The initial setup of a Dell PowerEdge R330 server took some time itself to get set up since its BIOS and associated iDrac needed to be set up to boot from either CD or USB drive before the hard drive. Once we found a good technical support person at Dell, that issue was soon resolved. Installing Server 2016 from the USB drive was a surprisingly easy and intuitive operation. I cannot speak for accessibility, but I was assisted by telephone a totally blind friend with much server experience. His comment was along the lines that Microsoft had finally managed to tidy the whole process up leading to Server Manager. Within a very short time - less than an hour in fact - we had one Windows 10 and 3 Windows 7 workstations all subscribed to the new domain. However, we soon found issues in accessing (or rather NOT accessing) the Internet. We checked all manner of things in Server Manager to ensure the Gateway was correct, etc., etc., etc.. We contacted our ISP, who advised us that all was well at the Router, which we could both ping and access. Finally we rang Dell, who spent over an hour going through all the same settings yet again. Eventually we found we did a Windows + R on workstations, enter \\[Domain name] see the shares there we would be able to run IE. Now bear in mind that during the 2016 server install, we had elected to use only one of the two Ethernet ports, and disable the second, and all indications in Server Manager confirmed this. It was pure chance that I had reason to look at Device Manager, and spotted that the second Ethernet port was operational and moreover had an IPv4 IP address way outside our Domain. Back to Server Manager and it said it was disabled. So back to Device Manager and disabled it there. Suddenly after a reboot, all began to work as it should. Have since reported this to our ISP and our Dell guy, and it appears they had begun to get others with the same problem - which of course they could now resolve. I hope this helps at least one of you. George. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins