2018-09-01, 08:23 PM
G'day mates...Well I guess my celebration was premature. With everything working well this morning, this afternoon the issue came back. I am still getting the "unable to communicate blah blah" thing but the TV Guide is populated. When I click to watch something I get a new Red X error stating that "an attempt was made to access a socket in a way forbidden by its access permissions 192.168.10.38:8968". This is the server addy but where is it getting the 8968 socket from? It is supposed to be the default 8866 right? I put that addy into a web browser and get nothing but when i change the port to 8866 I get the server. I ran Currports and TCPEye to watch what is going on connection wise with the client firewall off only. Sure enough both programs indicated to me that a connection was being established bu NPVR using socket 8968. So why and how is that possible. However, with firewall off everything works fine. Any help?
Thanks johnsonx42 I will give that a try and see if that speeds uo the connection process and fixes the other problem as well. Cheers!
Thanks johnsonx42 I will give that a try and see if that speeds uo the connection process and fixes the other problem as well. Cheers!
(Client) Windows 10 Pro 1803 Custom Box, I7-4790 Quad Core, 8GB Ram 64-bit
(Server) Windows Server 2016, I7-4790 Quad Core, 16GB Ram 64-bit
WinTV Hauppauge Quad Tuners
(Server) Windows Server 2016, I7-4790 Quad Core, 16GB Ram 64-bit
WinTV Hauppauge Quad Tuners