I have built a 2016 server running Hyper-V, 1 NIC for data and 4 others for iSCSI. I have setup a vswitch (no VLANs) but when I point the switch to the data network card it kills my server. I have to remote in via iDRAC to disconnect the vswitch from that particular NIC and point it to another NIC to power it back up. The NIC drivers are the latest versions and there doesn't seem to be a great deal of comment on the WWW about this issue or much within the KBs. Has anybody else encountered and more importantly resolved this issue?
The vSwitch NIC requires the IP address that was previously assigned to the data NIC which then deals with all of the traffic. This is contrary to thinking that the data NIC passes the data to the vSwitch.
Related
is there a way to connect a dvr tuner to a Plex Server hosted in Hyper-V?
I have searched but could not find a Question about this topic.
My build is a Win22 Datacenter Server running Plex in Hyper-V. A Hauppauge dualHD is connected to the Win22 Datacenter Server via USB.
Thanks for your help!
Current Answer
I'm updating my answer as I didn't realize it was a tuner and not a DVR box connected to your TV.
From what I'm seeing online, your best bets are:
use Enhanced Session Mode to connect the device over RDP (which only supports some devices)
use a third-party tool such as Donglify (this is from results on Google. Buy at your own digression) to allow USB passthrough
use a Type 2 hypervisor (VirtualBox, VMware) to run your instance of Plex instead
run Plex outside of Hyper-V on the same system with a sandboxed user
run Plex on another device entirely, such as a Raspberry Pi.
I can't help with the first, as it requires some gpedit.msc magic I cannot do, or second as I have never used one.
3rd option will reduce program speeds which may cause slowdown if multiple people stream at once.
4th option is my personal recommendation, as you bypass the need to use a hypervisor entirely and keep on the same device.
5th is only good if you use a USB-based drive and have a decent bit of experience with Linux.
Old Answer
Kept for the sake of archival.
You'll want to use Powershell and the Add-NetNatStaticMapping cmdlet to allow inbound connections to the Hyper-V server. This will need a vNAT adapter set up. See the linked blog post (not mine) if you need help with that, too.
Assuming the vEthernet connection has an internal IP of 192.168.10.2 and a NAT network name of NATSwitch, with Plex on the default port of 32400:
Add-NetNatStaticMapping -ExternalIPAddress "0.0.0.0/24" -ExternalPort 32400 -Protocol TCP -InternalIPAddress "192.168.10.2" -InternalPort 32400 -NatName NATNetwork
You will most likely need to replace the internal IP, port, and NAT name.
After this is set up, you'll need to point your DVR to the IP of the Windows Server box.
Sites referenced:
Plex support page on ports to forward
A GitHub user's blog, specifically a post on port forwarding
I had this problem previously (but didn't know the cause) and had to reformat my machine to eliminate the problem. Now I a pretty sure I know the cause:
I have both a wired and wireless internet connection. If I unplug my wired connection I cannot use SSMS to connect (forcibly closed by the remote host) to my Azure database (even though the wireless connection to the internet is fine). I can still connect using sqlcmd over the wireless connection.
By simply plugging/unplugging the Ethernet cable I have confirmed that this is the problem. I have checked my firewall rule for 1433 and it is supposed to be interface independent.
I've tried turning Firewall off completely and forcing TCP in the SQL connection properties.
Has anyone else found this to be a problem and found a solution? Is there a way to specifically tell SSMS to communicate over a specific network interface? Otherwise, I will have to reformat my machine again (and never use a wired Ethernet cable, since it worked fine before I ever plugged in an Ethernet cable) to eliminate this problem.
My guess is that you may be fighting (unbeknownst to you) network protocols.
https://www.connectionstrings.com/define-sql-server-network-protocol/
in the above URL, find the section labeled "Network protocol codes"
"Network Library=dbmssocn"
The above network-library is the 'tcp' one..and is the most common (in 2019) version. (I started sql-server when named-pipes was the biggest player and learned the hard-way about network-protocols ! )
That is how you "force" a certain network protocol in a connection string.
You can also set this value in Sql Server Management Studio.
See here:
https://kb.intermedia.net/article/1893
Find the sentence
"2. If it does not work with default settings, go to Options > Connection Properties tab. And choose TCP/IP in the drop down menu for Network Protocol."
Try experimenting with that.
APPEND:
Your first two screen shots are really hard to read. You have alot of blue space. I'd suggest making your ssms window smaller, then taking the screen shot.
Are you using these credentials naming style?
myazuresqlservername.database.windows.net,1433
MyUserName#myazuresqlservername
Could it be this??
Impossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12
Turns out this doesn't seem to be a problem with SSMS at all. Although Windows responded that I had the latest Network Driver, I discovered that the manufacturer had a new driver and that seems to have solved the problem.
http://support.killernetworking.com/knowledge-base/clean-install-killer-control-center/
Product Type Killer(R) Wireless-AC 1550 Wireless Network Adapter (9260NGW) 160MHz
Product Type Killer E2500 Gigabit Ethernet Controller
My Hardware:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: Alienware
BIOS: 1.6.5 (type: UEFI)
I am using Hyper-V for the first time (running Windows 8). When I create a new virtual network switch, external, it bridges the VMs network adapter with the WiFi - and that for some reason kills the WiFi's internet connection. Why, and what could I be doing wrong?
Thanks,
A.
If you have VirtualBoxinstalled, check if any of the Hyper-V virtual adapters/bridge connection has the VirtualBox Bridged Networking Driver ticked in the connection properties. If they do, simply untick this service where it is present and this should fix it up for you. No need to uninstall VirtualBox.
I had a static ip-address in my ethernet adapter.
Removed the static entry.
Made my external virtual switch.
Had the extra vEthernet adapter, made my static entries (ip-address, dns-server) in this adapter.
Everything is working fine now.
Chris
I had the same problem, it takes a couple of seconds to setup the connection again. Check this tutorial: https://superuser.com/questions/469806/windows-8-hyper-v-how-to-give-vm-internet-access
I just ran into the same problem, losing the internet connection when creating the virtual switch. Uninstalling VirtualBox which I had installed at the same time fixed the problem for me (just disabling the VBox adapters was not enough), so they seem to be unable to happily coexist.
I ran into the same problem recently when creating an external switch in Hyper-V. Long story short, every time an external switch was created, it would bring my ethernet connection down on my host laptop. I had wifi connection option also but disabled it to just strictly troubleshoot the ethernet network adapter.
I brought down the VM, once turned off, deleted the external network adapter from hyper V virtual switch manager. On the host machine, disabled and re-enabled the network adapter from within network connections (ethernet). Once connected, I brought the VM back online FIRST, then created the external switch second which connected with no issues. Verified I was able to access outside world aka internet on both host and VM.
Maybe you unchecked by accident the Allow management OS to share this network adapter setting that is enabled by default. Disabling this setting will leave your hypervisor OS without network connectivity.
I was able to fix such an issue by disabling Internet sharing on the wireless adapter, creating an Internal virtual switch in Hyper-V first, then disabling VMWare bridge on all involved interfaces, then I made a bridge in Network sharing center by selecting my internal switch and Wi-Fi adapter and after that I was able to select external network in Virtual switch manager in Hyper-V
I ran into the same problem too. I don't know for sure, but after trying all of the solutions above and any others I could find, I renamed my virtual switch to 'realtek' (the type of network card I have installed) instead of taking the default name that I think was 'new virtual switch'. Something else I did may have solved the problem (I modified everything I could find for two days), but I think renaming it is what finally gave me internet access to the vm.
I'm trying to develop an interface to an application that doesn't run on Windows 8. Hence, I've created a VM with Windows 7 running the integration service and another service running on the Windows 8 host.
I have three Virtual Network scenarios configured for Hyper-V: Wireless, Shared and Internal. Where Wireless allows all VMs and the host to connect to a wireless network (External), Shared let's the VMs connect through the host via a VPN (Internal) and Internal creates a network within the host where the VMs don't have network access (Private).
When I'm in Wireless (External) mode and there's a wireless network to connect to, everything works fine as if I were testing using to physical PCs on a wireless network. However, today I had a situation where I wasn't connected to a network but still wanted to do some testing and I could not get the VM to see the host and vice-versa. This scenario was quite straight forward to create on VMware which I used before switching to Hyper-V...
Has anyone managed to make Client Hyper-V VMs and the host communicate without a network? Can you guide me how to set it up?
Wireless networking under Windows 8 Hyper V can not communicate with multiple VM the Wireless NIC is assign to only one Hyper V internet connection,
Meaning only one Hyper V can connect to the Internet preventing others from connecting unless you use multiple Nic's Wireless Network Cards or USB Wireless Network.
It is only after you restart or shut down your computer that Hyper-V problems start.
So if you can not connect any of your Hyper VMs then you problem could be due to a shutdown error that Hyper-v in counted Try restarting the whole computer then Hyper- VMs your problem should fix itself.
Might want to try this. I am having similar problems as you and all signs point to this particular solution working, but for me it is not. Might help you, though.
http://blogs.technet.com/b/doxley/archive/2008/07/07/disconnecting-hyper-v.aspx
The solution that DID end up working for me was this:
http://www.elmajdal.net/Win2k8/Enabling_Wireless_Network_For_Hyper_V_Virtual_Machine.aspx
I'm running Server 2008 64bit with Hyper-V. I've created a virtual machine with Vista 64bit and installed it. I can't get the Vista virtual machine to see the network adapter.
I've set-up an external network on the Virtual Network Manager (Hyper-V) and associated that with the virtual machine (Vista). I've also tried using a Legacy Network Adapter but that didn't work either although that time the Vista machine saw the network card but couldn't connect through it.
This is (obviously) the first time I've tried to set-up a virtual machine.
Any ideas?
EDIT: I notice that this question has been voted down a couple of times. I know that it's not a programming question but I'm a developer setting up a virtual machine to test my C#/ASP.NET code on and thought that other developers may hit this problem as well when they're doing this...
I don't know Hyper-V, but I know in VMWare you can create a network connection in Bridged mode (meaning the VM will get it's own IP address via DHCP if that's enabled) or host-only mode (meaning the VM can only communicate with the host). When Vista could see the card, could it communicate with the host machine (which would indicate a host-only connection was specified)? What kind of IP address did it have (I would guess Hyper-V has a built-in DHCP server like VMWare does?) -- that might give additional clues.
Sorry I don't know Hyper-V better...
Make sure you have the Hyper-V Tools installed on the Guest VM. You shouldn't need the legacy adapter.
You also may want to make sure you have all of the latest updates which may have addressed your issue. Particularly, KB950050
http://support.microsoft.com/kb/950050
It turns out that Vista x64 running as a VM through Hyper-V doesn't support the virtual network connection/card and that you have to set it up as a legacy network card. When I eventually got the config settings correct for the legacy network and disable the virtual network it connected.
Thanks for the help guys - much appreciated!