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 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 have a piece of software I have written that talks to a web service over it's Wifi connection on a Casio WinCE handheld.
Unfortunately the Wifi network and the network created by WMDC (or ActiveSync) to host the debugger connection clash, they are both 192.168.55.0/24. So I can't have them both connected at the same time.
Does anybody know if you can reconfigure WMDC to use a different address range?
I've hunted through the registry but can't see anything obvious, and Google is not turning up anything useful.
Thanks,
James.
Is the development PC on teh same network as the WiFi connection? If so, I'd abandon ActiveSync/WMDC altogetehr and just use ethernet debugging over the same connection that it's using for the web service calls.
I have a USB modem on a server which occasionally needs to be turned off/on again to receive SIM updates and I can't reboot the server as we rely on it to serve various web pages.
Is there any way to do this programmatically? An AT command? Power down the USB port?
I don't always have access to the server so unplugging it and plugging it back in isn't an option unfortunately.
We're coding in C++/CLI if that makes a difference.
It would be great if someone knew of a generic solution to this, but for the Option Globetrotter 452 I'm using, the manufacturer reports that issuing an AT_ORESET command will instruct the device to reboot ...just in case anyone else wants to do this.
I have a windows 2008 Server with hyper-v enabled. I can't seem to load any network adapter into the virtual machine, it always says "Load Failed". Im really not sure what I'm doing wrong, or where to start.
Try to remove your network cards and re-connect them, I would also try to find updated drivers.
What type of card is it, It may not be supported.
Try adding a new virtual switch and select that one instead.
Here is how: http://www.eightforums.com/tutorials/19359-hyper-v-virtual-switch-manager.html
I write this just in case it can help someone, I had a similar problem, I wasn't able to see my network adapters in my windows server 2008 hyper-v machine, so the problem was the external switch couldn't be a normal one it has to be legacy external switch, so the steps I followed to resolve this were:
1- Create vm with windows server 2008 and not connected switch.
2- Goes to settings in my virtual machine an remove the not connected network adapter.
3- In settings add hardware - add legacy network adapter and connect to the external switch I had created.
And that's all. It should work like this.