Client does not connect

[flavius]

The client on my htpc crashed while I was managing the library of imported files. Even since I have not been able to connect again.

Telnet to 42024 works. The other clients work. I have tried repair of installation, and a new install of the client, reboot, changed IP of the box..

Over the network connection to the server is fine.

What else could I try? Is there a tool to clean the registry?

[mdmint]

Originally Posted by flavius

What else could I try? Is there a tool to clean the registry?

Yeah, unfortunately it's rather data destructive: fdisk, format, re-install everything.

[Opus4]

Have you tried restarting SageTV on the server? Maybe the client's crash left the server thinking that client was still connected. (I don't know if it could do that, but I thought it might be worth trying if you haven't done so already.)

- Andy

[flavius]

Originally Posted by Opus4

Have you tried restarting SageTV on the server? Maybe the client's crash left the server thinking that client was still connected. (I don't know if it could do that, but I thought it might be worth trying if you haven't done so already.)

- Andy

I did just that - there must have been a hanging thread or so - and that fixed it.

[kruzerman]

I am having this same issue on a clean install of XP. I have tried the current client download and an older version that i used to set up my first client. The first client is connecting just fine. I have restarted the server just in case and still nothing. I have tried every variation of server name that i can think of plus the IP. Any help here? I've looked through all the threads and no one seems to have any ideas.

[Opus4]

A few possibilities: the client & server versions must match; you can't use the same client license on multiple PCs; and make sure there is no firewall (XP SP2 has one built in) preventing the client or server from accessing your network.

- Andy

[kruzerman]

I'm just using a trial version (2.1) right now. This is the same version that i am using on the current working client, it is also the same download from february. Do i have to update current server and clients from 2.1 and use a current 2.2 client to get the new box connecting?

[Opus4]

The versions just need to be the same for server + client. I don't know if there are any other limitations with atrial in use -- you could check w/tech support.

Have you checked your firewall to make sure the new client + server can connect? You may be able to copy files, but SageTV & the client still need persmission to talk to the other PC.

- Andy

[JasonEngel]

My client won't connect either, unless I turn off the Windows Firewall on the server computer.

Server: Winxpsp2.
Client: winxpsp1.

Now, I've tried to set up an exception port 42024 in the windows firewall exception list. That allows the client to connect, but it can not display any audio or video - gets an error. Turn off the firewall on the server and the client connects perfectly.

Any suggestions?

[flavius]

There's probably another port(s) involved. I remember seeing a list in the pdf.

[JasonEngel]

Originally Posted by flavius

There's probably another port(s) involved. I remember seeing a list in the pdf.

Would you please be more specific? I just read through the PDF installed with the app. It does not mention anything about ports (read straight thru, and did a search in the doc to no avail).

[oaamaas]

I've been busy trying to get the client (V2.2) to connect the past few days. Even though this is an old thread I put out my findings as well (since the last post ended with an open question). JasonEngel is right - the documentaion says nothing about how to enable the Client when using a Firewall, only a few problems with the EPG is addressed.

However. In order to get the client connected the port 42024 (type TCP) should be added as an exception when using the XP SP2 firewall. I simply activated logging on the firewall, started the client and read how XP dropped the packages from the client PC in the log (port number is shown in the log). I'm not quite sure whether it is necessary to add exceptions for the SageTV and SageTV Service Control as well - tried to remove this and ended up with menues but no picture/sound. This is probably due to a faulty HD on my htpc that has troubled me all day, but who knows ...

[nielm]

Depending on your firewall, you can either except port 42024, or SageTV.exe, or if you are using the service SageTVService.exe (The SageTVServiceControl is merely an app which enables/disabled the service).