ESS's Firewall and Windows 7 RC 7100: can't see other systems on network.

Discussion in 'ESET Smart Security' started by DarrenDavisLeeSome, May 26, 2009.

Thread Status:
Not open for further replies.
  1. DarrenDavisLeeSome

    DarrenDavisLeeSome Registered Member

    Joined:
    Mar 23, 2009
    Posts:
    315
    Location:
    Riverside, CA U.S.A
    Currently back to using XP Pro SP3 and ESS 4.0.437.

    When I had Windows 7 RC 7100 (32-bit and 64-bit) up and running, and prior to installing ESS 4.0.437, I had no problems seeing the other systems on my network.

    After installing ESS 4.0.437, with Firewall in Automatic Mode, could no longer see any of the other systems on the network. Only solution was to disable Firewall. After Network Windows Refresh, all systems on network showed up, albeit temporarily. A reboot of Windows 7 and all systems on network would not be seen until Firewall once again disabled.

    Tried same scenario with Firewall in Interactive Mode. After putting in Password to remember rule several times, still could not see other systems on the network. Again, could only see other system after disabling Firewall, still only temporary; once rebooted, could not see other systems on the network until Firewall was disabled.

    Also noticed nothing in the ESS Network Connections Windows. Svchost.exe would show up only to disappear in 1 second or less.
     
  2. DarrenDavisLeeSome

    DarrenDavisLeeSome Registered Member

    Joined:
    Mar 23, 2009
    Posts:
    315
    Location:
    Riverside, CA U.S.A
    Okay.

    I think I figured something out.

    I'm back to using Windows 7 (32-bit) again.

    With the Firewall in Automatic Mode (with exceptions) I went into Advanced Setup and put in an IP address range in the Trusted Zone and I was able to see all the system on my network.

    So, I reckon it's all working now....

    Set up the printer located on another system. Did a little print test job.

    Shared a few files.

    Looks okay.

    Had no idea that the Automatic Mode had so many strict predefined rules. Did the ESS installation do that or could it have been done by Windows 7?
     
  3. DarrenDavisLeeSome

    DarrenDavisLeeSome Registered Member

    Joined:
    Mar 23, 2009
    Posts:
    315
    Location:
    Riverside, CA U.S.A
    This is getting ridiculous! Had it working...now it's not!! Help...please??

    WTF is going on?

    I thought I had the rules configured adequately enough so that I could see the other systems on my network.

    So I decided to make a clean install again. Erase my drive, restored an image of Windows 7 RC 7100, then installed ESS 4.0.437. Stuck the Firewall on Automatic mode with exceptions. Put in the range of IP addresses in the Trusted Zone. But this time...it just didn't work. Been in and out of the Advanced Settings>Rule editor 110 times and still cannot see the other systems on my network.
     
  4. DarrenDavisLeeSome

    DarrenDavisLeeSome Registered Member

    Joined:
    Mar 23, 2009
    Posts:
    315
    Location:
    Riverside, CA U.S.A
    Re: This is getting ridiculous! Had it working...now it's not!! Help...please??

    Okay...making some progress...I think. I wound up having to Disable 2 of the default rules just to be able to see the other systems on the network. But, I'm disturbed by the "Internet IN" and "Internet OUT". What does this mean?

    Capture.JPG

    Capture2.JPG
     
  5. DarrenDavisLeeSome

    DarrenDavisLeeSome Registered Member

    Joined:
    Mar 23, 2009
    Posts:
    315
    Location:
    Riverside, CA U.S.A
    Re: This is getting ridiculous! Had it working...now it's not!! Help...please??

    I think I got it all figgerd out now....

    Don't know why I had so much trouble in Interactive mode before.
     
  6. DarrenDavisLeeSome

    DarrenDavisLeeSome Registered Member

    Joined:
    Mar 23, 2009
    Posts:
    315
    Location:
    Riverside, CA U.S.A
    Having trouble with ESS Firewall and Windows 7...again!!!

    I just do not get it.

    I thought I had it running fine 2 days ago.

    I finally was able to see all the systems on my network. Had the Firewall in Interactive Mode: a Firewall popup appeared for Windows Explorer, Svchost, IExplorer, etc...; I chose to Remember (make rule) and Allow, hadn't set an Access Password yet so that was easy and quick enough to get all the rules into place. I was even able to reboot/shutdown, get back into Windows, open up the Network folder and there they all were.

    Then yesterday evening, I don't know if there was a module update since I am using Test Mode for updates, but, I began NOT to see the other systems on the network again when I opened up the Network folder. The only way I could see them is AFTER I went START>RUN>\\SERVER(or MACHINENAME)\SharedFolder. But it was only per Windows session. If I rebooted, logged off, shutdown, etc..., I would get back into Windows, open the Network folder and could not see the other systems until, again AFTER I did the START>RUN>\\SERVER(or MACHINENAME)\SharedFolder bit.

    Just an hour or so ago, I stopped seeing MY system in the Network folder along with not seeing the other systems. But if I did the START>RUN>\\SERVER(or MACHINENAME)\SharedFolder bit, I would see everybody, again on a per-session basis only.

    I know ESS does not support Windows 7 RC 7100 or other betas, but this is ridiculous.

    If I disable the ESS Firewall, click on Refresh in the Network folder, everybody shows up.

    I don't know if it's an instability in Windows 7 or ESS.

    If I don't install ESS at all on a Windows 7 OS with nothing on it but Windows I also have no problems seeing the other systems.

    Anybody got any ideas about what might be going on?
     
  7. xxJackxx

    xxJackxx Registered Member

    Joined:
    Oct 23, 2008
    Posts:
    4,050
    Location:
    USA
    Re: Having trouble with ESS Firewall and Windows 7...again!!!

    I don't know that your problem is Windows 7 specific. With any recent builds of this thing i can install and get about 2 or 3 trouble free days before stuff like this starts to happen to me on Vista. 1 32 bit machine and 1 64. I give up. I hope they fix these problems, but in any case I have renewed another suite that so far hasn't given me any issues. Best wishes to ESET and their users. :thumb:
     
  8. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Re: Having trouble with ESS Firewall and Windows 7...again!!!

    I'd suggest enabling logging blocked connections, reproducing the issue and then checking the firewall log for details about blocked connections.
     
  9. DarrenDavisLeeSome

    DarrenDavisLeeSome Registered Member

    Joined:
    Mar 23, 2009
    Posts:
    315
    Location:
    Riverside, CA U.S.A
    Re: Having trouble with ESS Firewall and Windows 7...again!!!

    Okay...here the Firewall log during boot-up, opening up of the Network folder, then a Refresh:

    5/30/2009 11:20:36 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:20:33 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:20:29 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:20:26 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:19:49 PM Communication denied by rule 192.168.0.100:138 192.168.0.255:138 UDP Block incoming NETBIOS requests PID=4
    5/30/2009 11:19:44 PM No usable rule found ::1.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:19:44 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:19:44 PM No usable rule found 127.0.0.1 224.0.0.22 IGMP PID=4
    5/30/2009 11:19:44 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:19:44 PM No usable rule found ::1.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:19:44 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:19:44 PM No usable rule found 127.0.0.1 224.0.0.22 IGMP PID=4
    5/30/2009 11:19:44 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:19:19 PM Communication denied by rule 192.168.0.150:138 192.168.0.255:138 UDP Block incoming NETBIOS requests PID=4
    5/30/2009 11:19:15 PM Communication denied by rule 192.168.0.150:138 192.168.0.255:138 UDP Block incoming NETBIOS requests PID=4
    5/30/2009 11:19:11 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:19:10 PM Communication denied by rule 192.168.0.150:138 192.168.0.255:138 UDP Block incoming NETBIOS requests PID=4
    5/30/2009 11:19:10 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:19:09 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:19:08 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:19:05 PM No usable rule found fe80::185d:fd7:b8ab:b523.:133 ff02::2 ICMPv6 PID=4
    5/30/2009 11:19:05 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:19:03 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:19:02 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:19:01 PM No usable rule found fe80::185d:fd7:b8ab:b523.:133 ff02::2 ICMPv6 PID=4
    5/30/2009 11:19:00 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:19:00 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:18:58 PM No usable rule found fe80::185d:fd7:b8ab:b523.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:58 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:58 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:18:58 PM Communication denied by rule 192.168.0.101:138 192.168.0.255:138 UDP Block outgoing NETBIOS requests PID=4
    5/30/2009 11:18:58 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:18:58 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:57 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:18:57 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:57 PM No usable rule found fe80::185d:fd7:b8ab:b523.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:57 PM No usable rule found fe80::185d:fd7:b8ab:b523.:133 ff02::2 ICMPv6 PID=4
    5/30/2009 11:18:57 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:57 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:18:57 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:18:57 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:57 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:18:57 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:57 PM No usable rule found fe80::185d:fd7:b8ab:b523.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:56 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:56 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:18:56 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:18:56 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:18:56 PM No usable rule found 192.168.0.101 224.0.0.22 IGMP PID=4
    5/30/2009 11:18:56 PM No usable rule found fe80::bd8c:5c68:62b9:cc02.:143 ff02::16 ICMPv6 PID=4
    5/30/2009 11:11:58 PM Communication denied by rule 127.0.0.1:59826 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:58 PM Communication denied by rule 192.168.0.101:59825 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:58 PM Communication denied by rule ::1.:59824 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:58 PM Communication denied by rule fe80::bd8c:5c68:62b9:cc02.:59823 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:58 PM Communication denied by rule 127.0.0.1:59826 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:58 PM Communication denied by rule 192.168.0.101:59825 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:58 PM Communication denied by rule ::1.:59824 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:58 PM Communication denied by rule fe80::bd8c:5c68:62b9:cc02.:59823 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:57 PM Communication denied by rule 127.0.0.1:59826 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:57 PM Communication denied by rule 192.168.0.101:59825 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:57 PM Communication denied by rule ::1.:59824 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:57 PM Communication denied by rule fe80::bd8c:5c68:62b9:cc02.:59823 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:57 PM Communication denied by rule 127.0.0.1:59826 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:57 PM Communication denied by rule 192.168.0.101:59825 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:57 PM Communication denied by rule ::1.:59824 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:57 PM Communication denied by rule fe80::bd8c:5c68:62b9:cc02.:59823 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:43 PM Communication denied by rule 127.0.0.1:59826 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:43 PM Communication denied by rule 192.168.0.101:59825 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:43 PM Communication denied by rule ::1.:59824 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:43 PM Communication denied by rule fe80::bd8c:5c68:62b9:cc02.:59823 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:43 PM Communication denied by rule 127.0.0.1:59826 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:43 PM Communication denied by rule 192.168.0.101:59825 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:43 PM Communication denied by rule ::1.:59824 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    5/30/2009 11:11:43 PM Communication denied by rule fe80::bd8c:5c68:62b9:cc02.:59823 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE



    I copied (to Notepad) the entire content of the Firewall log as you can see and then I cleared the log. Then I used Run>\\server\share then a quick Refresh of the Network folder and.....

    nothing but this so far (this is pretty much normal...even got them every now and then with ESS 3.0 with XP Pro):

    5/30/2009 11:30:13 PM Communication denied by rule 192.168.0.150:1045 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE

    As far as I can tell the above junk is just my Router's UPnP support features trying to speak it's piece with one of the other systems on my network.

    Still no new log entries.....

    As soon as I did the Run>\\Server\Share bit I could see all the systems on the network again. If I reboot I'll get pretty much the same Firewall log entries as above till I do the Run>\\Server\Share again.
     
  10. DarrenDavisLeeSome

    DarrenDavisLeeSome Registered Member

    Joined:
    Mar 23, 2009
    Posts:
    315
    Location:
    Riverside, CA U.S.A
    Re: Having trouble with ESS Firewall and Windows 7...again!!!

    Oh yeah...almost forgot.

    I installed ESS and all the updates with Windows Firewall still up and running. I was able to see all the systems on the network for a short time, like normal, ya know. But after a while the Windows Firewall was shut down automatically, by who or what, I don't have a clue. Then all this jazz with not being able to see the other systems started up again and having to do the Run>\\Server\Share bit.
     
  11. OakhurstTech

    OakhurstTech Registered Member

    Joined:
    Jun 17, 2009
    Posts:
    2
    I am experiencing the same issues with my Windows 7 RC1 x64 installation on both my notebook and desktop. The weird thing is I can browse the Vista x86 machine on my network just fine. It is just the Windows 7 machines that have problems. They are all running ESET SmartSecurity 4.0.437.
     
  12. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,779
    Location:
    Texas
    Windows 7 has not been released yet. Close, but not a full release.

    The programmers probably need some slack here on both sides.
     
  13. DarrenDavisLeeSome

    DarrenDavisLeeSome Registered Member

    Joined:
    Mar 23, 2009
    Posts:
    315
    Location:
    Riverside, CA U.S.A
    Nevermind.

    I'm pretty much through with Windows 7.
     
Thread Status:
Not open for further replies.