Excessive networkservice.exe connections..

[ccc1005]

I am seeing a few new connections every second with Outpost Firewall, it appears that the connections are from a random port all to port 8129. The destination and from address are both localhost. I have the streaming server turned off, any ideas whats going on here?

[Bigbird999]

Somebody had the same issue recently. see tis thread .tmp Files with 4.4.0

BB

[ccc1005]

I am still seeing this and its wasting resources with my firewall logging. I have disabled the media server so there is no reason there should be all these connections... Here is just a small sample of what is going on...

12:24:47 PM btvnetworkservice.exe IN TCP localhost 3920 Allow activity for application BTVNETWORKSERVICE.EXE 2.5 KB 45 Bytes
12:24:47 PM btvnetworkservice.exe OUT TCP localhost 8129 Allow activity for application BTVNETWORKSERVICE.EXE 45 Bytes 2.5 KB
12:24:47 PM btvnetworkservice.exe IN TCP localhost 3919 Allow activity for application BTVNETWORKSERVICE.EXE 268 Bytes 44 Bytes
12:24:47 PM btvnetworkservice.exe OUT TCP localhost 8129 Allow activity for application BTVNETWORKSERVICE.EXE 44 Bytes 268 Bytes
12:24:46 PM btvnetworkservice.exe IN TCP localhost 3918 Allow activity for application BTVNETWORKSERVICE.EXE 2.5 KB 45 Bytes
12:24:46 PM btvnetworkservice.exe OUT TCP localhost 8129 Allow activity for application BTVNETWORKSERVICE.EXE 45 Bytes 2.5 KB
12:24:46 PM btvnetworkservice.exe IN TCP localhost 3917 Allow activity for application BTVNETWORKSERVICE.EXE 268 Bytes 44 Bytes
12:24:46 PM btvnetworkservice.exe OUT TCP localhost 8129 Allow activity for application BTVNETWORKSERVICE.EXE 44 Bytes 268 Bytes
12:24:45 PM btvnetworkservice.exe IN TCP localhost 3915 Allow activity for application BTVNETWORKSERVICE.EXE 268 Bytes 44 Bytes
12:24:45 PM btvnetworkservice.exe OUT TCP localhost 8129 Allow activity for application BTVNETWORKSERVICE.EXE 45 Bytes 2.5 KB
12:24:45 PM btvnetworkservice.exe IN TCP localhost 3916 Allow activity for application BTVNETWORKSERVICE.EXE 2.5 KB 45 Bytes
12:24:45 PM btvnetworkservice.exe OUT TCP localhost 8129 Allow activity for application BTVNETWORKSERVICE.EXE 44 Bytes 268 Bytes

[bnflaherty]

Has nothing to do with the UPNP Server.

It basically comes down to -- a Check of the network services... it's Pinging Itself -- like a Keep Alive service of sorts.

This had been used do to other people's problem with Web Admin not being accessable -- as well as Link issues.

If you can set that to be ignored -- or just Allowed -- you'll be all set.

[ccc1005]

Thanks for the reply. Is it necessary to ping like this multiple times every second? Wouldn't a ping every 5-10 seconds be just as good, or sustaining a single connection? I understand the need for it, but the current setup seems a bit excessive IMHO.

[parisology]

I see these connections being created and closed very rapidly. I think there is something wrong with this design. Some of the connections are not being closed, so I end up with hundreds of these connections on the host.. and I think this might have something to do with Link hanging after a while. When Link hangs, the host machine shows all of these connections in a zombie state with <non-existent> process status -- and I can only kill them by rebooting -- so Link is somewhat useless. Any chance a tech support person will follow up?

Edit: After a few thousand(!) unclosed WAIT_CLOSE connections, Link appears to get really bogged down, then hangs completely. I have to kill the process. Then on the host, if I then close BTV, it complains there is 1 open Link connection. I close BTV anyway to try and clear up the network, but then all the WAIT_CLOSE connections are zombied and can't be cleared without a reboot (I've tried). Link will not connect again until the host is rebooted.

What I would like is for one or 2 other users here to run Link and watch a recorded program for about 1/2 hour and then run sysinternals tcpview on the BTV server and tell me what you see. I always see several thousand unclosed sockets to the client machine. (There are so many connections listed that the status counters in the status bar have the numbers cutoff because the text windows aren't wide enough.) I'm pretty sure this has something to do with the problem. Either that or maybe it's my firewall/router but I don't know. I use 4.8.2 but any 4.x version will do.

[Terminal]

Originally Posted by parisology

I use 4.8.2 but any 4.x version will do.

You meant 4.9.2 right? If not then I suggest you upgrade.

[parisology]

Originally Posted by Terminal

You meant 4.9.2 right? If not then I suggest you upgrade.

Thanks for suggestion - I run 4.8.2. What I am asking for is that one or 2 people run tcpview for me on their server as I described - I need to gain some confidence as to what is going on. I know it's a huge favor to ask. I'd prefer not to run a newer version unless the newer version is known to solve this specific issue.

[Terminal]

If you back up your settings using the backup function, it should be a simple matter to go back to the previous version if it does not fix your problem. I very seldom watch anything through link any more, not due to any problems, I just prefer to sit in a comfy chair in front of the big screen if I am going to watch TV. My server is by the main TV. I have never had a problem as you describe with Link locking up, in any version.

[parisology]

Originally Posted by Terminal

If you back up your settings using the backup function, it should be a simple matter to go back to the previous version if it does not fix your problem. I very seldom watch anything through link any more, not due to any problems, I just prefer to sit in a comfy chair in front of the big screen if I am going to watch TV. My server is by the main TV. I have never had a problem as you describe with Link locking up, in any version.

Same network problem with 4.9.2. Link eventually hangs up.