Network setup - Hyper-V
-
That VMQ thing can be an issue on 1 GB NICs with out-dated firmware/drivers. The info of affected drivers and NICs and the resolution can be found here:
This is a good write-up and how to resolve it. Or you can just run firmware and driver updates.
VMQ should be disabled on 1 GB NICs. The issue with the broadcoms is that it's enabled by default, and shouldn't be.
-
The implementation of VMQ was rolled out so badly.
I ranted on it in a thread more than a year ago.
https://mangolassi.it/topic/8358/i-hate-vmqYou can disable it on the NICs quite easily.
Get-NetAdapterVmq | Disable-NetAdapterVmq -
Even if you disable it on the NIC, you may/will still need to disable it on the VM.
-
I have unteamed, and disabled VMQ on the Hyper-V settings. I haven't disabled it on the NIC yet. No change so far.
I assume the powershell command will take them offline for a moment... Do I need to have the VM's shut down first before running it?
-
HyperV VMQ setting doesn't matter with 1g NICs.
-
@tim_g said in Network setup - Hyper-V:
HyperV VMQ setting doesn't matter with 1g NICs.
It has mattered with 1 Gbps NICs just more with Broadcom devices.
-
@tim_g said in Network setup - Hyper-V:
HyperV VMQ setting doesn't matter with 1g NICs.
This is provably false. You have said it repeatedly.
Yet I have posted clear proof in the previously linked thread.
-
@dbeato said in Network setup - Hyper-V:
@tim_g said in Network setup - Hyper-V:
HyperV VMQ setting doesn't matter with 1g NICs.
It has mattered with 1 Gbps NICs just more with Broadcom devices.
No, what matters is the NIC setting, not the HyperV setting.
-
@jaredbusch said in Network setup - Hyper-V:
@tim_g said in Network setup - Hyper-V:
HyperV VMQ setting doesn't matter with 1g NICs.
This is provably false. You have said it repeatedly.
Yet I have posted clear proof in the previously linked thread.
I know for a fact it doesn't matter with 1G NICs.
You are talking about the setting in the NIC properties. I'm not. I'm talking about the setting in the HyperV VM Settings.
-
@tim_g said in Network setup - Hyper-V:
@jaredbusch said in Network setup - Hyper-V:
@tim_g said in Network setup - Hyper-V:
HyperV VMQ setting doesn't matter with 1g NICs.
This is provably false. You have said it repeatedly.
Yet I have posted clear proof in the previously linked thread.
I know for a fact it doesn't matter with 1G NICs.
You are talking about the setting in the NIC properties. I'm not. I'm talking about the setting in the HyperV VM Settings.
That's different.
-
Even if it doesn't matter. I have run the powershell command and it's still running slow. Any other ideas?
-
@ccwtech said in Network setup - Hyper-V:
Even if it doesn't matter. I have run the powershell command and it's still running slow. Any other ideas?
Is it slow accessing the application via IP and DNS?
-
The way the app is installed is that essentially all the server is doing is hosting a file share. You place a shortcut to the .exe file on the desktop.
-
@ccwtech said in Network setup - Hyper-V:
The way the app is installed is that essentially all the server is doing is hosting a file share. You place a shortcut to the .exe file on the desktop.
Is the shortcut path and target starts with
\\ip-address\... or \\dns\...? -
Got it! I have tried both. No noticeable change.
-
@ccwtech said in Network setup - Hyper-V:
Got it! I have tried both. No noticeable change.
Tried disabling antivirus and maybe firewall on the workstation that is accessing the application?
-
@black3dynamite I should have by now, but no. Let me give that a shot.
-
@ccwtech said in Network setup - Hyper-V:
@black3dynamite I should have by now, but no. Let me give that a shot.
I would then try accessing via IP and DNS to confirm if that helps too.
-
@ccwtech said in Network setup - Hyper-V:
The way the app is installed is that essentially all the server is doing is hosting a file share. You place a shortcut to the .exe file on the desktop.
can you elaborate this bit. where the application files reside?! when you say access app via netwrok are you talking about a client server topology or are you doing something more exotic?!
-
Files are on a server (Hyper-V in this case). Quite literally on each desktop you navigate to the UNC path and do a right click on the main exe and choose send to desktop.
It seems fast when they are closed, but slow when they are open (and everyone is using it). They only have 9 PC's however. The server is way above min and even recommended spec's for the software.
Their network switch is a Netgear GS748Tv5 and I upgraded the FW to the latest version.
