Client very slow to start

[HarryH3]

Hi Sub, here are some of the things I've tried, and the results.

Ping DVR-1: Resolves address and starts pinging the IP address instantly
Remote Desktop to DVR-1: Prompts for password instantly
UltraVNC to DVR-1: Prompts for password instantly
Open File Explorer and manually enter \\DVR-1\Videos as the address: Full directory tree displayed instantly.
Launch NPVR client with DVR-1 as the server name: 60+ second delay before connecting.

Using the IP address as the "server name" in NPVR does indeed make things go much faster. But it appears that something is misbehaving in the way that NPVR queries the network for the server when it needs to resolve the server name first. All other programs resolve the name in the blink of an eye. All is good here, but I would be most happy to help with any testing.

[sub]

Using the IP address as the "server name" in NPVR does indeed make things go much faster.

Great!

But it appears that something is misbehaving in the way that NPVR queries the network for the server when it needs to resolve the server name first.

NextPVR isn't trying to resolve the name itself. It just gives whatever you've supplied (name or ip address) to the .NET remoting API, which takes care of any processing. There isn't really anything I could do any different.

Given others don't seem to have this issue, I'm still thinking it's something environmental about the setup on your machine. Maybe firewall software or something similar is contributing?