nrecord.exe needs access to internet

[Jerome]

Ok...while trying to solve another problem I noticed a lot of internet activity. Concerned because I had given nrecord.exe the right to access a dns server earlier I shut it down in a client machine and a server machine. Internet activity immediately stopped on both machines. Any idea why nrecord.exe would need continuous access to the internet?

[whurlston]

It's not actually accessing the Internet (except for possibly EPG updates and some plugins like Weather if you have them configured). NRecord constantly talks to NextPVR.exe and NTray.exe via TCP/IP on the local machine. In a client/server setup, the client and server are in constant communication via TCP/IP as well.

[sub]

It doesnt communicate outside the machine, but the nextpvr.exe front end process and the nrecord.exe backend process communicate with each other using TCP/IP, which depending on your firewall software may show up as network access even though its local to the machine. From memory, zonealarm used to do this with GBPVR, and would report the same for NPVR.

EDIT: what he said...

[Jerome]

That would make sense...I've been trying to set up client/server access (not working well, or actually at all). EPG updates are turned off, no weather access either. My concern was it didn't ask for local access like 192.168.1.XXX it asked for outside access 8.8.8.8 (Google DNS server on one machine), and something else on the other...I think it was a DNS server, don't remember the number...no info in firewall log on actual IP, I allowed at the time because I was trying to get client/server set up.

If it was using TCP/IP to communicate with the other machine wouldn't it have asked for access to that machine 192.168.1.XXX? I did grant access to local machines every time it asked. I even shut down firewall on both machines trying to make the client/server work.

[whurlston]

It could just be checking the dns server to resolve the computer name. You could run Wireshark to snoop the activity or for a quick check, run the following from a command line:

netstat -b