Unable to communicate with recording service

[sub]

Post the client logs and I'll take a look. I suspect it wont have any solid clues though. It should hopefully rule out other unrelated errors though.

Even though you've said its disabled, I still suspect it's firewall or antivirus related.

[gonzo90017]

Where are the logs located for Windows XP? I looked in C:\Program Files\NPVR but don't see anything.

[Reddwarf]

Where are the logs located for Windows XP? I looked in C:\Program Files\NPVR but don't see anything.

What has worked besy for me is to share the NPVR directory itself and point directly to it on the server.

[sub]

Where are the logs located for Windows XP? I looked in C:\Program Files\NPVR but don't see anything.

I cant remember the exact path on XP. Something like "c:\documents and settings\all users\shared data\....". Just search for npvr.log.

[gonzo90017]

What has worked besy for me is to share the NPVR directory itself and point directly to it on the server.

Which folder exactly? There are 2 folders for NPVR. One in program files and one in the Users folder. And where exactly in the settings do I point to the folder?

[Reddwarf]

Which folder exactly? There are 2 folders for NPVR. One in program files and one in the Users folder. And where exactly in the settings do I point to the folder?

The NPVR data folder I mean, and in the Database Share field (on the client) you type \\<ServerName>\NPVR

[gonzo90017]

Here are my logs.

[sub]

Its not the error I was expecting to see in your logs:

2010-11-19 20:44:50.734 [ERROR][1] Unexpected error calling ReloadSettings(): System.Runtime.Remoting.RemotingException: Tcp channel protocol violation: expecting preamble.

I have no idea what this error means means, but I tried googling it. There wasnt a lot of useful information. Some posts suggesting it might be firewall's interfering with communications.

Might also be worth doing a "netstat -b" on the server to ensure there isnt some other app listening on port 8968, causing unexpected results when the .net remoting tries to speak to NRecord.exe which it expects to be listening on this port.

[Reddwarf]

Its not the error I was expecting to see in your logs:
I have no idea what this error means means, but I tried googling it. There wasnt a lot of useful information. Some posts suggesting it might be firewall's interfering with communications.

Might also be worth doing a "netstat -b" on the server to ensure there isnt some other app listening on port 8968, causing unexpected results when the .net remoting tries to speak to NRecord.exe which it expects to be listening on this port.

I'd suggest opening port 8968 on both computers, and also port 8866 (NEWA port).

[gonzo90017]

I ran netstat -b and noticed Orb.exe was using port 8968. So I closed Orb.exe and ran netstat -b and this is what I got:


I then opened up both 8969 and 8866 following these instructions:
http://maximumpcguides.com/windows-7/ope...-firewall/
http://support.microsoft.com/kb/308127

I then ran NPVR on the client system but still got the same error.