Windows Server 2019 warns No Internet Access after AD, DNS and DHCP setup
Hi all. I have a Windows Server 2019 VM (HyperV) where I setup my first DC. I also setup DNS and DHCP on the server. After deploying these, the yellow warning icon appeared on the network icon in the bottom right corner, and it says "No internet access". Indeed, Internet access seems to be working normally. The only issue is the DNS sometimes unable to resolve certain random domains. It seems that unbinding IPv6 from the NIC almost solved this issue, but the warning icon and the No Internet message remains. I tried the troubleshooting tool. It is unable to diagnose the issue, and suggests a network reset. I did it twice, but it did not change anything. I took a dump of the network packets when the diagnostic tool is run, but I see nothing unusual. It finally connects to http://www.microsoft.com:80/ which I think is the normal way to determine if Internet is available. The server responds 200 Ok and some codes. I don't know where to look further. My ipconfig /all: Windows IP Configuration Host Name . . . . . . . . . . . . : SrvApp19 Primary Dns Suffix . . . . . . . : psw.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : psw.local Ethernet adapter Ethernet: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter Physical Address. . . . . . . . . : 00-15-5D-00-78-03 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 10.0.0.112(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.0.0.254 DNS Servers . . . . . . . . . . . : 127.0.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled I attach one of the diagnostic reports. Thank to anyone who can help.
DCOM was unable to communicate with the computer
i ran dcdiag on all my for dc 2,3,4,5 dc2 = windows 2016 dc3 = windows 2012 dc4 = windows 2012 dc5 = windows 2016 I get the following error DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID 19f8 (C:\Windows\system32\dcdiag.exe). An error event occurred. EventID: 0x0000272C Time Generated: 10/08/2020 11:20:39 Event String: DCOM was unable to communicate with the computer 10.10.0.1 using any of the configured protocols; requested by PID 19f8 (C:\Windows\system32\dcdiag.exe). An error event occurred. EventID: 0x0000272C Time Generated: 10/08/2020 11:21:57 Also, note that 10.10.0.1 IP does not exist and its not configured in nic or forwards Please assist
Bypass LBFO Teaming deprecation on Hyper-V and Windows Server 2022
Starting with Windows Server 1903 and 1909, Hyper-V virtual switches on an LBFO-type network adapter cluster are deprecated (see documentation). The technology remains supported, but it will not evolve. It is recommended to create an aggregate of type SET. In practice The SET is a very interesting technology that has some constraints. The interfaces used must have identical characteristics: Manufacturer Model Link speed Configuration Even if these constraints do not seem huge, we are very far from the flexibility of LBFO Teaming. As a reminder, this one has absolutely no constraints. In practice the SET is recommended with network interfaces of 10Gb or more. Therefore, we are very far from the target of the LBFO (use of all integrated boards with motherboard pro, Home Lab, refurbish). If SET cannot be used As of Windows Server 2022, it is not possible to use the Hyper-V Management Console to create a virtual switch with LBFO, as it will prompt an error saying that LBFO have been depreciated. However, it is possible to use PowerShell to create this virtual switch. First, create the Teaming of your network cards using the Server Manager, in my case the teaming will be with LACP mode and Dynamic load balancing mode. Then execute the below PowerShell Command to create the virtual switch based on the teaming created in the previous step: New-VMSwitch -Name "LAN" -NetAdapterName "LINK-AGGREGATION" -AllowNetLbfoTeams $true -AllowManagementOS $true In detail: The virtual switch will be named "LAN" The network adapter cluster teaming is named "LINK-AGGREGATION" The aggregate remains usable to access the Hyper-V host. You will see your network teaming up and running on Hyper-V host. Thats it!LBFO Teaming deprecation on Hyper-V for Windows Server 2022 - Solved
While creating a virtual switch using a teamed interface in Hyper-V for Windows Server 2022, the following error is encountered. To resolve this, NIC teaming for Hyper-V needs to be configured via PowerShell. Step 1: Delete the existing teaming manually created. Step 2: Go to PowerShell and run the command: New-VMSwitch -Name "VMSwitch-1" -NetAdapterName "Embedded NIC 1","Embedded NIC 2" (Here, I have given the switch name 'VMSwitch-1' and aggregated it with two adapters—'Embedded NIC 1' and 'Embedded NIC 2' are the adapter names in the list.) Step 3: Check the algorithm of the VMSwitch command: Get-VMSwitchTeam -Name "VMSwitch-1" | FL (This command will display the algorithm. If it's Hyper-V, proceed to the next step; otherwise, you can ignore the last step.) Step 4: Set the load balancing algorithm to dynamic: Set-VMSwitchTeam -Name "VMSwitch-1" -LoadBalancingAlgorithm Dynamic (This command changes the load balancing algorithm to dynamic. Test it using the command in step 3. The teamed interface should now appear in the Hyper-V virtual switch.) This will not help to LACP mode , so If you want LACP, Then only need to do the two step This is my recommend Step 1: First, create the Teaming of your network cards using the Server Manager, in my case the teaming will be with LACP mode and Dynamic load balancing mode. Step 2: Then execute the below PowerShell Command to create the virtual switch based on the teaming created . New-VMSwitch -Name "VMSWITCH-1" -NetAdapterName "SR-LAG-1" -AllowNetLbfoTeams $true -AllowManagementOS $true this case name of my hyperv switch given "VMSWITCH-1" and created teaming network adapter name ""SR-LAG-1"" Go to hyper-v and check the VMSwitch That's It.....On my teamed NIC, the MAC address keeps changing. How do I make it static?
Windows server 2016, 2 NIC ports, teamed with Microsoft Network Adapter Multiplexor Driver, no VMs, no VPNs, no load balancer. After rebooting, the MAC address keeps changing (based on IPCONFIG /all). Application software is based on MAC, so the application keeps failing after reboot. I've read that the Team uses the first NIC cards MAC, but I've also read that it may choose randomly based on load balancing. I cannot view the MACs of the ethernet adapters. I'm guessing this is because they're already teamed. I couldn't find good documentation on how to set the MAC address of the NIC Team, so I'm making an assumption that I do the following: NICTeam > Properties > Configure > Advanced > MAC Address > Value... and set it to whatever 12 hex characters I want (000012345678). Is this correct? Based on IPCONFIG, the NICTeam is presenting what looks like a standard MAC address. I'm assuming it's grabbing this from one of the NICs. If I use the method above and set the MAC to the same address, will I have conflicts in the future? ...or is it safer just to use 000012345678?
SQL server SSPI Handshake Failed with error code 0x80090311
Hey Team, Our company SQL server randomly has these SSPI handshake failed error which suddenly started. The full error reads "SSPI handshake failed with error code 0x80090311, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The operating system error code indicates the cause of failure. No authority could be contacted for authentication. [CLIENT:devicename]. We've been unable to solve this issue and it occurs randomly. When the issue is occuring we cant bastion or rdp onto the server and we also cant rdp from a different server in the same vnet. We're not too sure what is causing this and struggling to find a solution as this is now starting to affect all our business applications that require a stable connection to the SQL server. Any help would be greatly appreciated. Thanks
How to see who is a member of schema admin and how to add a member in
Hi All, Im currently trying to install Sccm and need to link my SCCM server to DC but due to me getting the below error I cant go any further. Im currently on the Administrator account but it seems that I still need to put this account in the Schema admin group. I cant seem to access this group I cant see it in Users or anywhere - When I search for the account I have to search the Entire directory but then cant access the properties? How do I add a user or even the admin account into this group so I can carry on doing the necessary step to install SCCM? I get this message Please help! and thanks in advance!
