MINIMSERVER COMMAND LINE INSTALL
Very very bad idea because I begun to have this problem with W2016, so I install again W2012 R2. The most interesting part is: it previously worked without any problem with win2012 R2 on the same hardware (it was just perfect!), but on last Friday I took the decision to go to W2016. Yes you are right, this is exactly the same: sotm sms-200 directly attched to the music server, music play with severe stuttering, like each 2 seconds I have to wait a second. The Wifi dongle should be active, but can be disconnected from the Wifi router. Solution : add a Wifi-dongle to the bridge (3-way bridge). I heard only stuttering because the speed of the network became terribly slow (see discussion here) Question : can you hear music playing? If not or if it plays with severe stuttering then you have the same problem I also had when making such a bridge. I also guess that you want to make the bridge because you have a SOTM/mR attached to one NIC and the other NIC to your router?
inf mods) with Intel's PROWINX64, like I217 & I218, but I210 should be OK if I look in it's. Under W2012R2 and W2016 some Intel NIC's cannot be installed (need. Which is simply impossible to use).CATįrom the fact that you can make the bridge I conclude that your ethernet NIC's are properly installed under W2012R2? When I create this bridge, the speed becomes very slow (around 200k/s …. I have a problem when trying to create a network bridge on Windows 2012r2 audio server (GUI mode, not core mode). Hopefully others will chime in with their LAN bridging experiences with WS2012R2. and LAN bridging is a fairly basic feature.Īs anther example, Microsoft broke LAN teaming in Windows 10, but it remains intact in WS2012R2 and Windows Server 2016.
MINIMSERVER COMMAND LINE DRIVER
The driver binaries are typically not identical between 6.50 and 6.40, so the OS is not the only difference.Īlso, with Windows 10 being newer by a few years, it is distinctly possible Microsoft has better LAN bridging code support in Windows 10 than WS2012R2, although a Server OS is supposed to fully support advanced networking features, such as VLAN, teaming, etc. Windows 10 and Windows Server 2012 R2 require different NDIS revision NIC drivers: NDIS 6.50 and NDIS 6.40 respectively. The hardware is also very good and nearly new (Intel server mainboard with Xeon processor, 2 lan card, 4GB Ram and SSD disks).ĭoes someone have such problem with Windows server?Īre the NICs on the mainboard from Intel?
MINIMSERVER COMMAND LINE UPDATE
This is a new installation of Windows 2012r2 and all update are installed. This audio server has a dual boot, the second boot is Windows 10, and the network bridge works without any problem on Windows 10 so the problem comes from the O.S Windows 2012 and not from the hardware.
I have a problem when trying to create a network bridge on Windows 2012r2 audio server (GUI mode, not core mode).
0 kommentar(er)
