Client Live TV: "Failed to connect to remote server"

[Reddwarf]

And you are sure you have the same version with all patches on both server and clients? Nevertheless of firewall status, have you tried to open the relevant ports in your firewall on both sides?

[cncb]

Yes, same exact version on clients and server. I have added firewall exceptions (trusted apps) for all the NPVR EXEs on the server and clients so as far as I know all no ports are blocked for NPVR. Also, one of my clients occasionally (and inexplicably) is able to watch Live TV??

[cncb]

I temporarily installed the old hard drive on the client and Live TV still works fine with the same server. With the new hard drive I uninstalled Comodo completely and still get the error? Any ideas on how to track this down?

[sub]

So you have one client that never works (always giving 'failed to connect to remote server'), and one that fails intermittently?

If so, you could try creating a c:\temp directory, and setting HKEY_LOCAL_MACHINE\Software\NPVR\LogClientStream=1, then reproduce problem on the client that always fails and post the c:\temp\stream.log

[cncb]

Unfortunately this is all there is in stream.log:

Code:

17:43:39.555    Connect()
17:44:00.587    Failed to connect to host

Note the recording is always started on the server and the .ts file is left around.

[sub]

It doesnt tell us too much. It does tell us it is the winsock connect() call that's failing though, right at the beginning of the process, so either the name/ipaddress or port is wrong, or it's unable to resolve the server name, or firewall is stopping the connection from completing.

I'm not sure this file is still compatible with 2.4.3, so backup your original file before trying this patch. It'll log GetLastError() when connect() fails, which might give some more clues.

[cncb]

This is what it produced:

Code:

17:59:15.588    Connect()
17:59:36.611    Failed to connect to host. rc=10060

[sub]

WSAETIMEDOUT 10060

Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

[cncb]

Well, I'm not sure what is different with my new hard drive/setup that is causing it not to work (other than Comodo which I have uninstalled and still get the same error).

[sub]

Unfortunately I'm not really sure what to suggest.

You could maybe try running wireshark to log the attempted connection on working/non-working machines to compare. It might give you something more to go on.