Client stopped working when using Service mode

[srothwell]

Hi.....

I recently switched to Service mode for SageTV, now my client (on a different machine) can no longer connect.

Whether I use the machine name or the direct IP address it says it cannot reach the server.

If I stop using Service mode and just go back to regular, it works just fine.

Any ideas?

Thanks,

Stacy

[Opus4]

Did you check your firewall settings to make sure the service is given a pass to get by the checkpoint w/o being stopped?

- Andy

[mls]

If using the Windows Firewall, I believe you'll have to open ports for both SageTV and for the Sage Service for the client to work. Also, you can not use mapped drives with the service and need to use UNC paths instead. Not sure if either of these applies to your situation though.

[srothwell]

Sorry to sound dumb, but what ports are they and how do I open them?

Thanks

[Opus4]

Using ZoneAlarm, I simply allowed access for the service. But on p. 179 of the v2.1 manual, it lists:

sagetv_port

port to use for TCP/IP connections between the SageTV Client & SageTV

On my system, that value is: 42024

- Andy

[srothwell]

I verified the sageproerties file and made sure that both server and client were both set to port 42042.

I also enterted that port into both the server and client firewalls (XP SP2 firewall).

Still won't work.

If I stop using service mode *OR* if I turn off Firewall on the server, it works great.

I'm reluctant to stop using service mode. I got hosed big time last week. While my wife and I were off on vacation in Italy, the server software locked up (running in non-service mode) last Sunday morning (best as I can tell). When we got back, not one single show recorded last week (!!!!!!!!!!!).

Assuming it was fault of the UI, I decided to use the sevice so if the UI locked up it wouldn't affect recordings.

Any idea why this won't work?

Thanks,

Stacy