sagetv discovery

[sflamm]

Setup a new server and client.
Have the firewalls off on both.
For some reason the client can not discover the server?!
If I manually enter the IP it is fine.

Both are Win7 running Java 7.

Any ideas?

Thanks in advance.

[KeithAbbott]

Maybe this???

http://forums.sagetv.com/forums/showthread.php?t=59715

[sflamm]

Both machines are in the same Windows domain. The network show as the domain. And the firewall is off for the domain.

I fired up wireshark and I am not even seeing a UDP broadcast for the SageTV server. However the second I enter the server IP I see a boatload of TCP traffic.

Looks like the UDP request isnt even going out?!

[KeithAbbott]

The server that you are talking about isn't the network encoder server, is it?

[sflamm]

I could not get the the SageTV server to discover any network encoders from the SageTV network encoder server so I decided to try something simpler... let a SageTV software client try to auto discover the SageTV network encoder server (which is configured to accept sagetv clients). The SageTV software client cannot discover the SageTV network encoder server at all either (or even my normal server for that matter). So I fired up wireshark and I do not even any UDP traffic coming from the sagetv client - was expecting to see a discovery request on Port 8270.

[sflamm]

Just installed a new sagetv client on another machine and same result. It cannot discover any SageTV servers... but can connect when the IP is entered.

Any idea what is going on?

[sflamm]

OK - fired up a Windows XP SageTV client (also in the domain) and it immediately discovers both the new SageTV encoding server as well as my production SageTV server.

The problem seems specific to Windows 7 - for some reason it must be blocking the protocol even though the firewall is off.

Anyone know how to address this?

[KryptoNyte]

You mention it's Win7 specific - is the Windows Homegroup enabled on the server?

[sflamm]

No - no homegroup running on either client or server.
Both homegroup listener & provider services are disabled.

The problem seems to be on the Windows 7 client side.
As the Windows XP client autodiscovers perfectly.

[KryptoNyte]

Yeah ... when I search for similar issues, everything I find is Firewall related.

[sflamm]

It is pretty certain it is firewall related - especially since the traffic doesnt show on wireshark which implies it is dropped before it hits the network.

Any idea on how to fix?

[gplasky]

Check the network. Does it think it is on the Home network or the Public network? Change it to the Home network for all machines involved.

Gerry

[sflamm]

It saw it as the Domain network. For all machines involved.

Out of curiosity - how do you change the network it uses? (domain/private/public)

I just installed a fresh Win7 and joined it to the domain (back on the Domain network). Installed SageTV and voila - works now!!

Works with both the firewall on and off.

Go figure... not sure what changed.

[Skirge01]

Originally Posted by sflamm

Out of curiosity - how do you change the network it uses? (domain/private/public)

Control Panel->Network and Sharing Center

Under "view your active networks", click the network designation (e.g. Home Network, Work Network, Public Network) and a box will pop up allowing you to choose one.

[sflamm]

unfortunately that does not do anything for me. see attached picture - the types are not selectable (clicking does nothing).

[Fuzzy]

Originally Posted by sflamm

unfortunately that does not do anything for me. see attached picture - the types are not selectable (clicking does nothing).

being in a domain changes the way windows handles network 'zones' I think. either way, you should be able to disable the firewall no matter what your zone is, you just have to make sure you are disabling it for the proper zone (it is different settings for each one).

More specifically, for domain based settings, I think you have to configure it in group policy. The domain has the capability to both forbid firewalls, and enforce them. I don't think it CAN be changed locally on the workstation.

[sflamm]

As long as there is no group policy that overrides the local setting then it can be configured in the local machine policy (by turning off the firewall for the 'zone').
I disabled for domain 'zone' without issue.