Killer 1535 and Hyper-V woes

Hi,
I am having some difficulties with a Killer 1535 card and Hyper-V on my XPS 9570 running Windows 10 Pro x64

If I connect one of my virtual switches to the external network (ensuring that the allow management operating system to share this network adapter), I lose all network connectivity on the host device. The VM is fine.

When I fire up the killer control centre it cannot find the card, yet if I disconnect the virtual switch from the external network it appears to run ok.

I have run the latest driver pack downloaded today from the killer website, and any help would be greatly appreciated.

 

Send a message explaining your issue to support@rivetnetworks dot com

I find their support to be quick and very good.

 

@Killer_Networking will help the OP.
I had similar issue wherein I solved it by disabling Startup item of KCC.

 

Hello blu3cat,

It's normal for the Killer Control Center to show "No Killer Network Interfaces Connected" if you are connected to the Internet through a Hyper-V virtual adapter. This is because that virtual adapter reroutes all data away from the normal Windows networking stack, and our bandwidth filter cannot detect the data that is moved that way. It's effectively bypassing the Killer Control Center.

As long as the Killer Control Center shows "No Killer Network Interfaces Connected," the Killer Control Center is not manipulating your connection in any way. This issue is likely not related to either the network adapter's drivers or the Killer Control Center. You might try resetting your network stack, as detailed here - https://www.killernetworking.com/ki...3-resetting-network-devices-and-network-stack. If that doesn't work, I suggest uninstalling Hyper-V and all virtual adapters, using the Windows Network Reset (click Start, type Network Reset, click Network Reset, then follow the prompts) and the reinstall Hyper-V and your virtual adapters.

You're also welcome to submit a support ticket here - https://www.killernetworking.com/killersupport/contact - with a diagnostic, where I can take a look and see if anything stands out, but I think the issue is likely not related to our hardware or software.

-- Anthony with Killer Networking

 

I am using Hyper-V with a Killer 1535 without issues all i did was change the Vswitch mac address, in fact i am using hyper-v right with my killer 1535 in an external vswitch typing this to you.

Also killer control panel will not detect the Wireless card until its unbridged from the vswitch, which is normal.

As for your issue make sure you External Vswitch has the "Allow management operating system to share this network adapter" box checked that along with the MAC address change in the Mac Address Range area of the VSwitch settings should get you up and running again.

 

What did you change the MAC address to? Any guidelines which I can pass to other users that might have these issues?

-- Anthony with Killer Networking

 

@Killer_Networking

Basically i was having an issue at the time getting the Guest VM's Mac address to show in the Router DHCP which makes port forwarding and static IP's a right pain in the butt, even with the correct settings applied to allow the Guest VM to show its Mac address to the network.

But what i did was changed it to something other then the default Mac Address poll to something like 00-17-1D-01-20-00 -> 00-17-1D-01-20-FF,
this then fixed the Reporting to the Router issue so my only guess was a Registry glitch somewhere and changing the MAC address rewrote that key.

Hyper-V has had a known issue with Wireless cards since Windows 8.1 and has never been fixed since.

So if you have a client that is having issues using Static IP at router DHCP level or port forwarding issues as they can't assign a IP to a mac address that is not showing the above fixes the issue.

I now change the MAC address poll every time i make a clean install of Windows which is normally on major builds or 6 months after the last clean install (Yep Microsoft likes to mess things up and break stuff so i beat them to the punch).

With the above i am now able to host my Teamspeak server, Testing server, Driver modding OS (OS dedicated to making drivers work on old systems), even have a Ubuntu Build server for firmware for mobiles and routers.