Connecting a DVR Tuner to a Plex Server in Hyper-V - hyper-v

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

Related

How is browsing from a virtual machine/virtual box preventing fingerprinting or tracking?

is it increasing your internet security in terms of privacy/tracking/fingerprinting, if you are surfing with your web browser in a virtual machine enviroinment (virtual box + vpn)? Instead of surfing from your normal windows operating system...
Or is a virtual machine not helping you in fingerprinting cases? I just want to understand if you can use a virtual machine as a additional privacy tool and if yes, on what aspects would it have an impact (ip address, virus infections, fingerprinting, etc.)?
Thanks
When you're hosting a VM on your local machine, it may share the same IP as your host, as far as the outside world is concerned. Most hypervisors allow you to change how it obtains an IP address, but in typical configs it will only change on your local network, which is probably NATed behind a single address provided by your ISP. A VPN is a good way to change that, and you can configure that either inside or outside the VM, though ideally you'd no want to be sharing an IP with your host system.
Using a VM can help against fingerprinting because you can be running a different browser in a different OS in your VM than on your host system - but that instance itself can be tracked/fingerprinted, so it may be a good idea to rotate through a series of different configurations (or use a browser plugin that randomises some settings, such as reported browser version, OS, installed fonts, etc), and to throw away changes in your VM each time you use it, which will eliminate even the hardest of "supercookies" that might try to track you.
Unless your hypervisor is compromised (this has happened in the past, but it's rare), the VM itself will provide good protection from malware - for example Windows malware will have no effect on a Linux VM, and vice versa - and any malware that does infect your VM is contained by the sandbox that the VM provides - and you can simply reset it to return to a known-clean state, or throw it away and start again.

Problems logging in to Azure from SSMS

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)

Why can't my friends access my website built with Apache2?

So, I have been building this website with HTML and I decided to host it with on Apache2. It runs on an Ubuntu and me already changed the VM assigned Ip, which is 10.2.0.15, into another one. I can access it on the Mac where the VM is, but I asked my friend if he can open it, and he said it was a 404 Server not found error.
Please help!
You probably need to enable port forwarding:
https://www.howtogeek.com/122641/how-to-forward-ports-to-a-virtual-machine-and-use-it-as-a-server/
You haven't indicated what VM software you are using, but the above is for VirtualBox. VMware is a bit different. Also make sure your router is not blocking any packets or any firewall.

Remote connection to embedded device in field

I would like to ask about the way how to establish remote connection to Linux based embedded device in the field.
I have a small linux board I want to place in remote location. It has an internet access through ethernet. Than I have a Linux server with public IP to be able to tunnel connection.
And finally, I want to connect from my PC to this device.
I don't feel yet competent enough to code my own tcp sockets etc. to reroute the connection :) So what would be the easiest way to do that only with available linux tools? And BusyBox toolset on endpoints.
Thank's a lot!
I think that using OpenVPN would be a easy way to tunnel to the device. You can cross compile it and set it up as a client on the embedded device. Then you install it on your Linux box and set it up as a server.
Finally you install it on your work PC and set up as a client there.
It gives you a virtual network where all clients can talk to each other like they would be on a local network.

Setting up a server at home for Android app

I'm currently developing a simple multiplayer game app for Android and I need to have a server to which the users connect to.I'd like to set up this server at home. I have a dynamic IP address,so someone told me I'd have to set up a local DNS server or something like that. I'm not even sure where to start with setting up a DNS server, everything I found was for windows 2003 and linux. Nothing for XP? If any one can shed some light on this matter, explain a bit how setting a DNS works or supply a link with "setting up local DNS for dummies" I'd be grateful.
Also, besides setting up a DNS so I can find the server every time, how about the communication with it? I'd like for it to be as secure as possible. Another friend told me something about communicating via SSH, which is again something I am not accustomed to.
So if someone could explain some of these concepts or offer some GOOD link for that that would be great. I'm very confused :)
Thanks
EDIT
Btw, the server is in Java and currently i'm communicating from Android emulator to the server (which is localhost) via sockets.
That's not a simple thing you're trying to achive. First you have to create your own server on your machine (maybe you're done with this step), then you have to make this server available for everyone. At this point, I suggest the DynDNS service:
http://lifehacker.com/124804/geek-to-live--how-to-assign-a-domain-name-to-your-home-web-server
A local DNS by default help you to find your own servers by name instead of IP address, but if you have a usual internet service with dynamic IP, you need an external DNS provider to route your clients to your server. (read the link above for the full explanation)
About the SSH security: Yes, you will need some security settings indeed, but that could be a very hard problem sometimes. You can set your server to work with SSL sockets, which is a part of the core J2SE release. It will work against some sort of attack, but none against others. Running your own server will raise unexpected numbers of problems, prepare for that.
As already stated in the comment to your post, something like http://www.no-ip.com or http://www.dnsdynamic.org would solve the issue with your dynamic ip - You do not need a local DNS server.
With regards to communication, i believe that SSH is linux/unix only. Since you wish to use Windows for the server, FTP or Remote Desktop would be best. Choose FTP if all you want to do is manage your files, choose remote desktop if you wish to manage your entire computer. I've had good results with the FileZilla FTP server on windows (http://filezilla-project.org/)
With that said, i think you would be better off buying a simple and cheap hosted service instead of using your own computer - you can get something that can run your java app for $5/month some places, and compared with the annoyance of having a local server running in your house, it might be worth it.