Networking
60 Topics[server 25314] External SET Team to Internal after Reboot.
I have created SET Teaming on Windows Server 25314 (actually from a previous build) using External and 3 Intel i350-T4 ports, configured for Hyper-V and external access. New-VMSwitch -Name SETSwitch -NetAdapterName "i350t4_1","i350t4_2","i350t4_3" -AllowManagementOS $true -EnableEmbeddedTeaming $true -EnableIov $true Set-VMSwitchTeam -Name SETSwitch -LoadBalancingAlgorithm Dynamic In that case, the Hyper-V VM and OS can be accessed normally, but when I restart Windows Server, all Adapters disappear from SET Teaming and are changed to the Internal setting, and network access is lost. The above logs were obtained at WPR with Profile in Network. Since the file is large, I will post a link to OneDrive. setTeamingTrouble.etl https://1drv.ms/u/s!AoGvAA_XXMTH-dJ2gkOa6E5hP4QhLg?e=7hPgLQ In addition, if the EnableIov option is set to $false, a BSOD (KMODE_EXCEPTION_HANDLED) will occur after the Switch is created. VMSWITCH.SYS 0x0000007e (0xffffffffc0000005, 0xfffff80643a95c61, 0xffffb28989f2a6d8, 0xffffb28989f29ef0) Addition 2: LBFO Teaming is working properly. I tried to send it through the Feedback Hub and could not get it to work, so I have included it here. Addition 3: Server 25324 LBFO Teaming with New-VMSwitch failed.1.6KViews1like3CommentsSMB over QUIC Roadmap
Hello everyone! I had seen somewhere back in October(?) 2022 that Microsoft plans to implement SMB over QUIC for Azure File Shares (without needing Windows Server 2022 (Azure edition). Is this part of the roadmap? I've also seen somewhere that there are plans to eventually make SMB over QUIC available for non-Azure editions of Windows Server 2022. Is this true as well? and if so, is there a roadmap to when this will be available in a Windows Server insiders build? Thank you!Solved3.6KViews1like4CommentsWhen is Network Profile Issue for Domain Controllers going to be at least acknowledged?
Since the insider builds from 25398 to the latest 26227 all have the same bug where the domain controller on the builds will show the network category as Public instead of DomainAuthenticated and the only way to fix it is to disable and re-enable the NIC after each reboot. There has been a few bug reports submitted in the feedback hub and in this community many months ago. It would be at least be nice to be acknowledged.2.4KViews1like26CommentsI can't Turn on network discovery
Hi Why in Advanced sharing settinggs the Turn on network discovery can't save the settings in Windows Server 2019 Preview? Although as an admin I turn it on and save settings, it's again off when I open Advanced sharing settinggs. The second problem is that when I click Choose media streaming optons, I get the message The page failed to load.205KViews1like21CommentsVMXnet3 Server 2025 performance issues
Had an odd one crop up today. I updated my Server 2025 template to the 26063.1 release and then sysprepped it. Converted it back to a new VM and network performance was .25 Mbps down. Both on my local lan and on the internet. I removed the VMXnet3 and put in an E1000 and performance was exactly as expected. I shut the VM down, removed the E1000 put in a new network with vmxnet3 and again got horrible performance. I have not seen this with other deployments of 2025 earlier builds.3.2KViews1like14CommentsIs Enforcing LDAP Signing enabled by default starting with Windows Server 2025?
When connecting to Windows Server 2025 (Preview) using LDAP simple bind, the server rejected the bind. 「The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection」was displayed as an error message. If you change the LDAP server signing requirement from the default value to disabled according to the page below, LDAP simple bind will succeed. https://learn.microsoft.com/ja-jp/troubleshoot/windows-server/active-directory/enable-ldap-signing-in-windows-server Is Enforcing LDAP Signing enabled by default starting with Windows Server 2025? If so, where is the announcement about enabling LDAP server signing requirements?1.8KViews0likes2CommentsDomain Controller showing network connection as Public
Notice for quite awhile now with the vnext server builds that when you promote it to domain controller it shows the network connections as public or private instead of DomainAuthenticated. Is there a networking piece that I am missing that needs to be configured35KViews0likes11Comments