NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR Support Legacy (v4.x and earlier) v
« Previous 1 … 263 264 265 266 267 … 433 Next »
Unable to receive signal due to VMware Player installation (HDHomeRun Prime, Win 8)

Unable to receive signal due to VMware Player installation (HDHomeRun Prime, Win 8)
mikkle
Offline

Junior Member

Posts: 5
Threads: 1
Joined: Mar 2013
#1
2013-03-21, 12:31 AM
Hi,

First of all, thanks for your hard work on this project.

I installed NextPVR yesterday for the first time and was unable to view any channels, but I think I've figured out the source of the problem. My setup is fairly straightforward: HDHomeRun Prime on local network, SchedulesDirect subscription, latest NextPVR + all patches on Windows 8 64 bit.

For the longest time, I was unable to watch any channels on Live TV (black screen, no sound). I noticed that NextPVR was able to create a .ts file in the appropriate folder but the file was always zero bytes. I did quite a bit of searching and found out that this usually happens when NextPVR is unable to communicate with the HDHomeRun tuner. I then proceeded to add explicit firewall exceptions, then disable all firewalls, disable antivirus protection, etc. to no avail: still no picture, no sound, and a zero-byte .ts file.

Eventually I looked through the logs to see if I could glean anything useful and the following message caught my eye:

Code:
Executing: C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe 13xxxxxx set /tuner0/target rtp://192.168.76.1:36322

You see, my local network is actually on 10.0.* -- not 192.168.* . It seemed NextPVR was asking HDHomeRun to send the data somewhere other than my desktop. A quick call to IPCONFIG cleared that up as it revealed the following entry:

Code:
Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::1493:xxxx:xxxx:xxxx%21
   IPv4 Address. . . . . . . . . . . : 192.168.76.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

For some reason, NextPVR was trying to route the stream to the VMware Player virtual network adapter. Once I disabled the virtual adapters (there are two of them) from the Windows Control Panel, NextPVR then called hdhomerun_config using the proper IP address and I was able to watch Live TV!

How does NextPVR determine which network adapter to route traffic to? I can't find an option to explicitly specify this in the Settings UI, so I assume this is some sort of bug? Let me know if you need any additional info to troubleshoot.

Cheers!
johnsonx42
Offline

Posting Freak

Posts: 7,298
Threads: 189
Joined: Sep 2008
#2
2013-03-21, 01:41 AM
I've seen this before with other software and those VMnet adapters (and with other virtual adapter types that have an IP assigned). Effectively with those virtual adapters installed you have a "multi-homed" system just as if you had multiple physical adapters installed. This often presents a problem as Windows doesn't seem to have a mechanism to determine which IP address is the default one. In theory it could work with the listen port at 192.168.76.1:36322 even if the HDHR is at 10.0.0.1; it's just that the HDHR doesn't know how to reach 192.168.76.1, and sends the packets to the default route which is probably your internet router. If you could tell the HDHR a static route for the VMnet network, it would work.

I guess the fix from the NPVR side would be to have a config.xml setting <DefaultListenIP> that would default to Auto, and would allow users with multi-homed systems to override the default IP address.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
mikkle
Offline

Junior Member

Posts: 5
Threads: 1
Joined: Mar 2013
#3
2013-03-21, 02:44 AM
Thanks for the reply!

"route print" on my system shows a metric of 10 for the route from the gateway (router) to my default adapter, while every other route (including the virtual adapters) has a metric of over 250. (Routes with lower metrics have precedence.) Perhaps there is a way to retrieve this information programmatically to make sure the correct interface is used?

Thanks again!
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,724
Threads: 767
Joined: Nov 2003
#4
2013-03-21, 03:18 AM
I've made a change for the next release which should fix this.

That release should be this weekend.
mikkle
Offline

Junior Member

Posts: 5
Threads: 1
Joined: Mar 2013
#5
2013-03-21, 04:28 AM
That's great to hear, thanks to you both for your help!
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)



Possibly Related Threads…
Thread Author Replies Views Last Post
  Unable to access tuner after hibernation bm_00 1 1,230 2022-12-12, 02:00 PM
Last Post: mvallevand
Photo How to setup Multidec with HDHomeRun HDHR4-2DT spin35 7 2,507 2021-09-18, 02:12 AM
Last Post: sub
  Issues with Signal? Tularis 6 2,374 2021-05-01, 11:09 AM
Last Post: shspvr
  HDHomerun recording bizzarely not working Jean0987654321 3 2,040 2021-03-27, 03:23 PM
Last Post: Jean0987654321
  Need help with unable to find capture device please? Deandar1 2 1,696 2021-01-29, 07:17 AM
Last Post: sub
  unable to delete recording manic_biker 9 2,723 2020-12-01, 09:41 PM
Last Post: mvallevand
  Need help with unable to find capture device please thebigz 5 3,340 2020-06-15, 02:05 PM
Last Post: mvallevand
  No data delivered/failed to lock a signal? from Hauppauge HDHR/DCR-2650 bishoph 8 3,630 2020-04-13, 09:55 PM
Last Post: sub
  hdhomerun dvb-t channels is not fount by nextpvr Ernoth 1 1,787 2020-03-25, 02:12 PM
Last Post: mvallevand
  unable to communicate with recording service MaxOne72 9 3,371 2020-03-07, 11:59 AM
Last Post: Graham

  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode