Added an HDHomeRunDuo - Now HD200's do not see server....

[Slack]

Today I added an HDHomeRun Duo. To my server. Another was already in there. So went from 2 tuners to 4.

After this. My HD200s do not find the the server, all PC clients find the server just fine.

This all version 9 so far as the PCs are concerned.

What the hell. Why would the HD200s just 'check out'. It's annoying as hell.

[Slack]

For reasons unknown to me (2) HD200s no longer auto-discover my server.
I can manually add the server and define it's IP address - then the HD200s will connect. Although they will not auto-connect to the manually defined server.

The HDHomeRunDuos are on a separate NIC on the server. Separate, as in it's not the same NIC that discovery, and streaming to clients happen on.

Any ideas out there?

[BobPhoenix]

I'm not terribly good with networking so what follows may not be your fix.

I get this any time my router (also my DHCP server) looses connection to the internet. I also got it when I managed to have 2 master browsers on my Windows network.

For the first one I just call the ISP and wait for them to fix my service as it always (has so far anyway) effected more people than just me.

For the second one I set one of my unRAID Dockers to be master browser and turned off the ability on each of the windows boxes to become the master browser with the following registry entry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
"MaintainServerList"="No"

[Slack]

Originally Posted by BobPhoenix

For the second one I set one of my unRAID Dockers to be master browser and turned off the ability on each of the windows boxes to become the master browser with the following registry entry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
"MaintainServerList"="No"

From googling 'windows master browser'...

As part of the Microsoft Windows Server Operating Systems, the browser service is used to host information of other Windows computers within the same Windows domain or TCP/IP network... the Domain Master Browser coordinates browse lists from all the local browsers in a workgroup, no matter what their network segments.

I have myriad Win 7 and Win10 boxes on my network. They were present before adding tuners to the SageTV backend. I'm skeptical, but supposing I did this - are you suggesting to do it to all Windows boxes on the network?

[JustFred]

Originally Posted by Slack

For reasons unknown to me (2) HD200s no longer auto-discover my server.
I can manually add the server and define it's IP address - then the HD200s will connect. Although they will not auto-connect to the manually defined server.

The HDHomeRunDuos are on a separate NIC on the server. Separate, as in it's not the same NIC that discovery, and streaming to clients happen on.

Any ideas out there?

Was the 2nd NIC added at the time the new HDHR was added? Are both NICs on the same subnet?

Under certain circumstances, Windows behaves poorly with multiple NICS. Have you tried using a single NIC on the server?

[Slack]

Originally Posted by JustFred

Was the 2nd NIC added at the time the new HDHR was added? Are both NICs on the same subnet?

Under certain circumstances, Windows behaves poorly with multiple NICS. Have you tried using a single NIC on the server?

2 NICs were always on the PC.
They are on different subnets.
Never tried a single NIC.
Motherboard NIC is tuners. Address is link local 169.254 etc...
PCI NIC is connected to the rest of the house. Static IP.

[wayner]

Just WAG here:

IP address conflict?
Run out of DHCP addresses?

For some reason one of my SageTV servers no longer shows up with the server name, it just shows up with the IP address. I didn't do anything to cause this to change but it could be a similar issue to what you are seeing.

[Slack]

Originally Posted by wayner

Just WAG here:

IP address conflict?
Run out of DHCP addresses?

For some reason one of my SageTV servers no longer shows up with the server name, it just shows up with the IP address. I didn't do anything to cause this to change but it could be a similar issue to what you are seeing.

DHCP Seems fine.
Server IP is static, outside outside of DHCP range.
PC Client resolve the server name, version, and IP address just fine.

[BobPhoenix]

Originally Posted by Slack

From googling 'windows master browser'...



I have myriad Win 7 and Win10 boxes on my network. They were present before adding tuners to the SageTV backend. I'm skeptical, but supposing I did this - are you suggesting to do it to all Windows boxes on the network?

That is what I did but I only really had to do it to the 2nd master browser. In my case I had an unRAID server and WHSv1 server that both claimed they were master browsers. So I used the registry entry on the WHSv1 server and that fixed it. I then did it to all the other windows boxes and vms so that the unRAID server would always be guaranteed to be the master browser - even though it shouldn't have happened and wasn't really needed.

[Slack]

Originally Posted by Slack

For reasons unknown to me (2) HD200s no longer auto-discover my server.
I can manually add the server and define it's IP address - then the HD200s will connect. Although they will not auto-connect to the manually defined server.

So in some sort of cosmic rando weirdness....this got resolved.

I was attempting to scan some documents (my sage backend has a scanner on it). The scanner software was not launching correctly. So I re-installed it.
Now both HD-200s are again auto-connecting to the back end.

Seems I lived with it for 3+ years...
First world problems eh?