Local network problems since v5.0.94.0 install

Starting from my post here https://www.wilderssecurity.com/showpost.php?p=1953802&postcount=41

Since installing 5.0.94.0 I've had some really bad local network sharing problems.

1. The initial network shares show up fine and I can browse to them without any trouble.
2. Opening any folder on a network drive and the results vary.
- Sometimes it'll hang for a second and then open the folder but I can never get further down the directory structure than that.
- Most of the time I just get the Windows the network share is not available error.

I had no trouble under v4 and the only update is with ESS. Even if I disable Firewall, HIPS, Real-time protection etc on both computers I still get the issue.

There is nothing in the logs on either machine saying there has been any issues. There is nothing in the Windows logs either.

I'm at a loss as I need regular access to my fileserver (obviously).

Is there anyway to debug this and figure out what's going on?

I'm running the 64-bit version on Win 7 Pro 64. Same OS on both PCs.

Network is gigabit, running through a Netgear Smart Switch.

Cheers in advance!
Paul.

 

Double-check that everything corresponds with this knowledgebase article:

How do I resolve network connectivity issues with ESET Smart Security? (5.x)

 

Yep, had already done this. No difference. The local network is also in the exclusion list for protocol filtering and IDS.

I just tried copying a file across. It creates the file but it's zero bytes. No errors or anything in any logs.

 

OK a quick update, I found where to turn the logging on:

11/10/2011 20:50:52 No application listening on the port 192.168.0.51:64099 255.255.255.255:8612 UDP
11/10/2011 20:51:26 No application listening on the port 192.168.0.51:62208 255.255.255.255:8612 UDP
11/10/2011 20:51:26 No application listening on the port 192.168.0.51:62208 255.255.255.255:8612 UDP

Are these anything to do with it?

and on the server:

11/10/2011 20:51:24 No application listening on the port 192.168.0.51:62208 255.255.255.255:8612 UDP
11/10/2011 20:51:24 No application listening on the port 192.168.0.51:62208 255.255.255.255:8612 UDP
11/10/2011 20:50:50 No application listening on the port 192.168.0.51:64099 255.255.255.255:8612 UDP
11/10/2011 20:50:50 No application listening on the port 192.168.0.51:64099 255.255.255.255:8612 UDP
11/10/2011 20:50:44 No application listening on the port fe80::1853:c44b:aa32:ce6c.:54947 fe80::f8e1:74bb:6e3d:aa25.:2869 TCP
11/10/2011 20:50:36 No application listening on the port fe80::1853:c44b:aa32:ce6c.:54912 fe80::f8e1:74bb:6e3d:aa25.:445 TCP
11/10/2011 20:50:33 No application listening on the port fe80::1853:c44b:aa32:ce6c.:54947 fe80::f8e1:74bb:6e3d:aa25.:2869 TCP

 

I seem to get a lot of these (this machine is .51, the server is .50):

11/10/2011 20:53:45 No application listening on the port 192.168.0.50:3483 255.255.255.255:3483 UDP
11/10/2011 20:53:42 No application listening on the port 192.168.0.51:51974 255.255.255.255:8612 UDP
11/10/2011 20:53:42 No application listening on the port 192.168.0.51:51974 255.255.255.255:8612 UDP
11/10/2011 20:53:26 No application listening on the port 209.85.169.189:443 192.168.0.51:55022 TCP
11/10/2011 20:53:08 No application listening on the port 192.168.0.51:62033 255.255.255.255:8612 UDP
11/10/2011 20:53:08 No application listening on the port 192.168.0.51:62033 255.255.255.255:8612 UDP
11/10/2011 20:53:04 No application listening on the port 209.85.143.101:443 192.168.0.51:54987 TCP
11/10/2011 20:52:59 No application listening on the port 80.239.224.56:443 192.168.0.51:54848 TCP
11/10/2011 20:52:59 No application listening on the port 80.239.224.56:443 192.168.0.51:54848 TCP
11/10/2011 20:52:50 No application listening on the port 192.168.0.50:5355 192.168.0.51:65470 UDP
11/10/2011 20:52:50 No application listening on the port 192.168.0.50:5355 192.168.0.51:52543 UDP
11/10/2011 20:52:45 No application listening on the port 192.168.0.50:3483 255.255.255.255:3483 UDP
11/10/2011 20:52:34 No application listening on the port 192.168.0.51:53893 255.255.255.255:8612 UDP
11/10/2011 20:52:34 No application listening on the port 192.168.0.51:53893 255.255.255.255:8612 UDP
11/10/2011 20:52:00 No application listening on the port 192.168.0.51:53890 255.255.255.255:8612 UDP

 

I don't know if this is related, but I am still on ESS 4 with Windows 7 64-bit and I had connectivity issues this morning running squeezebox server software - the player could not find the server and the server reported some ports unavailable. My ESS logs indicated that the program modules were updated this morning, so I figure that might have something to do with it. I rebooted the computer and everything worked fine.

Anna

 

Thanks Anna. Unfortunately it's not this. It's completely random.

A few days ago networking was fine, today it jams like described earlier. I can connect over HTTP now. Except when downloading from usenet which stopped all comms to the server. The logs on the server were showing as in my previous examples, however the ports it was showing were active and were working fine before downloading started.

I'm going to be rebuilding both machines in the near future so I hope that fixes it.

I also discovered since the install various rules had disappeared on the local network.