B
Bryan Malone
We have a 2016 Hyper-V server that is running 2 2016 VMs. The Domain Controller VM hosts the file shares for the domain. Every time we reboot the server the SMB shares are not accessible over the network.
You can still ping the server and on the DC if you go to \\<servername> it can see it's own shares.
The server has onboard broadcom nics which we have disabled and replaced it with an Intel nic. I have also go in and enabled netbios over TCP/IP which didn't resolve the issue either.
The second VM doesn't suffer from this issue so it appears isolated to this on VM.
The only way I've found to resolve this is shut down the VM and remove the virtual nic. Then boot the VM so it can see that the nic is gone. Then shut down the VM again then add a virtual nic. Boot the server and setup TCP/IP addresses again.
I am assuming there's an update that has caused this behavior that the 2nd server doesn't have.
The other part of this is the 2019-06 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4503267) fails to install. I had hoped an update would fix the NIC issue. But after a couple of hours of downloading and installing the update. It reboots to apply the update and then fails.
It seems to fail after the trusted installer is processing. The event log shows The winlogon notification subscriber <TrustedInstaller> is taking long time to handle the notification event (CreateSession).
Any advice or suggestions?
Continue reading...
You can still ping the server and on the DC if you go to \\<servername> it can see it's own shares.
The server has onboard broadcom nics which we have disabled and replaced it with an Intel nic. I have also go in and enabled netbios over TCP/IP which didn't resolve the issue either.
The second VM doesn't suffer from this issue so it appears isolated to this on VM.
The only way I've found to resolve this is shut down the VM and remove the virtual nic. Then boot the VM so it can see that the nic is gone. Then shut down the VM again then add a virtual nic. Boot the server and setup TCP/IP addresses again.
I am assuming there's an update that has caused this behavior that the 2nd server doesn't have.
The other part of this is the 2019-06 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4503267) fails to install. I had hoped an update would fix the NIC issue. But after a couple of hours of downloading and installing the update. It reboots to apply the update and then fails.
It seems to fail after the trusted installer is processing. The event log shows The winlogon notification subscriber <TrustedInstaller> is taking long time to handle the notification event (CreateSession).
Any advice or suggestions?
Continue reading...