Sage 2.1 - Clients cannot connect

[DON3k]

I have two SageTV servers and two SageTV Clients. Both are on two totally separate networks, since they are actually located in to totally separate homes. Today I installed 2.1 over 2.0 on both Servers and Clients, and although the Servers seem fine, and the new Service started and is running with no issues, neither Client can find the server. Both clients have the correct IP, but both, immediately upon opening, just show a full-screen message that they have been disconnected from the server and are trying to reconnect, neither of which ever do.

Now, of course, the servers are on the network, can browse, and can be ping'ed from the clients with no problem. The only thing which changed in both cases was the installation of Sage 2.1.

Any clues? I have no idea what to check, since all seems perfect otherwise.

[matterw]

If you are using Windows XP with Service Pack 2, then here ya go.

This happened to be as well... Go into the control panel and look at the fire wall settings -- allow SageTV to go through the firewall in the settings...

[DON3k]

Well, I would have thought so, too, but I found the solution, or the cause, rather, just a few mins ago..

SageService... Disable SageService and you can connect with no issues at all. Both system, both dual-tuner with one client connecting. Disable the service and suddenly both connect immediately.

Here's something else SageService did, too, which I did not notice earlier. I suddenly was loaded with Scheduling Conflicts on both machines! Checking, all shows were set for PVR # 2, and non for #1. I checked, and #1 was installed, working, and had a channel line-up. Crazy. I removed both sources, added them back, but the same thing - Lots of conflicts with nothing scheduled for the 1st PVR.

Guess what? This problem vanished, too, when I disabled SageService.

Apparently that feature has some major issues. I will be leaving it disabled from now on and I would recommend others check to see if they're having something similiar to this problem, too.

[mls]

Just 2 quick notes that may help. If you're gonna run the service, you need to open the Windows firewall for both SageTV and the SageTV Service. Also, for any network drives v2.1 no longer supports mapped drives, you have to use UNC paths instead.

[meekell]

SageService... Disable SageService and you can connect with no issues at all. Both system, both dual-tuner with one client connecting. Disable the service and suddenly both connect immediately.

Here's something else SageService did, too, which I did not notice earlier. I suddenly was loaded with Scheduling Conflicts on both machines! Checking, all shows were set for PVR # 2, and non for #1. I checked, and #1 was installed, working, and had a channel line-up. Crazy. I removed both sources, added them back, but the same thing - Lots of conflicts with nothing scheduled for the 1st PVR.

You're not alone. I experienced the same thing tonight!
________
redhead girl Cams

[jptaz]

So has any found the solution to this?

I can not get the client to connect even when not running as a service.

Both machines are XP Pro SP2.

Neither have the fire wall on. The original Beta never had this issue.

John

[beautye350]

Originally Posted by mls

...Also, for any network drives v2.1 no longer supports mapped drives, you have to use UNC paths instead.

Yeah, and that sucks. My entire library is affected by this. When I try and view a recording it tells me that the file is no longer there.


Regards,

Beau

[nielm]

Originally Posted by mls

...Also, for any network drives v2.1 no longer supports mapped drives, you have to use UNC paths instead.

Originally Posted by beautye350

Yeah, and that sucks. My entire library is affected by this. When I try and view a recording it tells me that the file is no longer there.

This is only the case when running sage as a service, and it is a Windows issue: no services have access to the mapped drives...

[Opus4]

... and there is a way to switch over to UNC paths and still have access to everything with the service. (As nielm said: this is not an issue if you are not using the service, since ONLY the service cannot use mapped drive letters.)

- Andy

[beautye350]

That may be true fellas, but seeing as how I am running multiple Roslyn's I need to combat Sage crashing every couple days and the service seems to be helping and I am not even running the "never_stop_encoding" now and I am seeing no issues with the audio like I had prior.

Is the switch to UNC covered in the manual or where could I get that info?

Thanks.


Regards,

Beau

[Opus4]

Originally Posted by beautye350

Is the switch to UNC covered in the manual or where could I get that info?

I thought that was something to leave for the FAQ/forum, so I didn't put that in the manual. See this recent post; a couple posts down from there points to the FAQ entry that mentions some of it too.

- Andy

[beautye350]

Great! Thanks for the help.


Regards,

Beau