Homegroup Network Connectivity

Discussion in 'ESET Smart Security' started by RexG, Feb 19, 2013.

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

    RexG Registered Member

    Joined:
    Jan 23, 2009
    Posts:
    8
    I have a Homegroup/Network using a late PC Windows 7 Home Premium 64bit with a lan connection to an Aximcom MR-102N Router connected by USB 2.0 to a Telstra MAXON BP3-EXT modem for NextG internet; Laptop A Windows 7 Home Premium 64bit connected by wireless and Laptop B Windows 7 Ultimate 32bit connected by wireless. The printer etc are connected to the PC. My PC communicates perfectly with both laptops and visa versa and the printers are available and work with all three. The problem is nthe neither laptop is able to communicate. I have attached some trouble shooting details which are self explanatory. I am using the 'Interactive' mode on my personal ESET Smart Security 6 Firewall. At no time has either laptop or the PC for that matter given me any indication that intercontact has occurred. Having to manually add rules and profiles etc. is a daunting task for someone of my inexperience, eg, hoew do I obtain the IP addresses and protocols etc & etc.
    Can anyone supply some assistance or answer to this problem.

    Thanks for your help RexG
     

    Attached Files:

  2. dwomack

    dwomack Eset Staff Account

    Joined:
    Mar 2, 2011
    Posts:
    588
    Have you gone through the ESET KB Article below?

    Slow or no Internet/network/printer connection: Solution checklist

    Each step includes links to articles that will show you the step-by-step process including screenshots. You stated in your post that this may be too daunting a task for you to attempt alone. If this is the case, we do offer customer care services and our agents would be glad to walk you through the steps, if that might help. You can contact us online or by phone.
     
  3. RexG

    RexG Registered Member

    Joined:
    Jan 23, 2009
    Posts:
    8
    Thanks dwomack for your quick response, I will follow the instructions given as time permits, I have glanced at the knowledge base articles and think it could help.

    Cheers RexG
     
  4. RexG

    RexG Registered Member

    Joined:
    Jan 23, 2009
    Posts:
    8
    Hi dwomack,

    I have just done what was said in the Knowledge Base, ie, added the laptop ip's to each other and opened port 445 on both laptops, but am still where I sytarted, ie nowhere. I did manage to find out how to get the ip addresses however. Have you any more suggestions, please?

    Thanks Heaps,
    RexG
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Make sure that you have the following options enabled in the IDS setup:
    1, Multicast address resolution (LLMNR) in the Trusted zone
    2, Windows 7 HomeGroup support

    Also make sure the other computer is in the Trusted zone.
     
  6. RexG

    RexG Registered Member

    Joined:
    Jan 23, 2009
    Posts:
    8
    Thanks Marcos for that info. I will look into it abd see what happens.

    Cheers RexG
     
  7. RexG

    RexG Registered Member

    Joined:
    Jan 23, 2009
    Posts:
    8
    Thanks for the info marcos, both laptops were in the trusted zone and both were enabled with respect to Windows Homegroup support, the other box regarding (LLMNR) was unchecked and I have now enabled it on both, however I am still in the same position I was in before I tried anything. Have you or anyone else got any other thoughts on the matter, please.

    Many Thanks, RexG
     
  8. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Whenever a certain communication is blocked, please do the following:
    - in the IDS setup, enable logging of blocked communication
    - reproduce the issue
    - check the firewall log for detailed information about the reason for the block (Copy & paste the recent records here which will give us a clue.)
     
  9. RexG

    RexG Registered Member

    Joined:
    Jan 23, 2009
    Posts:
    8
    Thanks Marcos for your quick reply. I saw those boxes unchecked so I will enable and see what happens. It will probably be a couple of days before I can get back to you.

    Thanks Heaps, RexG
     
  10. RexG

    RexG Registered Member

    Joined:
    Jan 23, 2009
    Posts:
    8
    Hi Marcos,

    For your info Laptop A's iPv4 Address is 192.168.1.27 and Laptop B's address is 192.168.1.25,
    This is the log from Laptop A after I tried to open its tree in Windows Explorer on Laptop B:-

    02/2013 10:28:09 PM Communication denied by rule 192.168.1.27:54600 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:09 PM Communication denied by rule fe80::2125:9298:5410:cbec.:54598 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:06 PM Communication denied by rule 192.168.1.27:54600 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:05 PM Communication denied by rule fe80::2125:9298:5410:cbec.:54598 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/02/2013 10:28:03 PM Communication denied by rule 192.168.1.27:54600 239.255.255.250:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/

    ************************************************

    And this is the log from Laptop B after the same request from Laptop A

    24/2/13 10:25:21 PM Communication denied by rule fe80::65d6:1e1c:168c:6d2a.:62522 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:18 PM Communication denied by rule fe80::65d6:1e1c:168c:6d2a.:62522 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:14 PM Communication denied by rule fe80::65d6:1e1c:168c:6d2a.:62522 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:11 PM Communication denied by rule fe80::65d6:1e1c:168c:6d2a.:62522 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:07 PM Communication denied by rule fe80::65d6:1e1c:168c:6d2a.:62522 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:04 PM Communication denied by rule fe80::65d6:1e1c:168c:6d2a.:62522 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    24/2/13 10:25:03 PM Communication denied by rule 192.168.1.1:45880 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE


    Hope you can find something here,

    Thanks RexG
     
  11. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    It seems that only UPnP is blocked. Does allowing "UPnP for system services in the Trusted zone" in the IDS setup make a difference? If not, post here the current firewall log records from the point when the issue occurs even with the mentioned option enabled.
     
  12. RexG

    RexG Registered Member

    Joined:
    Jan 23, 2009
    Posts:
    8
    Hi Marcos,

    Did that and no difference, the two setsof logs are below:-

    Laptop A:

    26/02/2013 10:29:33 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:29:31 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:29:30 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:29:09 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:29:08 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:29:06 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:28:54 PM No application listening on the port 23.32.241.24:80 192.168.1.27:49537 TCP
    26/02/2013 10:28:28 PM No application listening on the port 65.55.69.140:80 192.168.1.27:49533 TCP
    26/02/2013 10:28:23 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:28:22 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:28:20 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:28:01 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:27:59 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:27:58 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:27:49 PM No application listening on the port 192.168.1.27:68 255.255.255.255:67 UDP
    26/02/2013 10:27:26 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:27:25 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:27:23 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:27:03 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:27:01 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:26:59 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:26:59 PM No application listening on the port 208.67.220.220:53 192.168.1.27:62167 UDP
    26/02/2013 10:26:54 PM No application listening on the port 208.67.222.222:53 192.168.1.27:64304 UDP
    26/02/2013 10:26:23 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:26:22 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:26:20 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:26:07 PM No application listening on the port 192.168.1.25:68 255.255.255.255:67 UDP
    26/02/2013 10:26:00 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:25:59 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:25:57 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:25:23 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:25:22 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:25:20 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:25:00 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:24:59 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:24:57 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:24:24 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:24:22 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:24:21 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:24:02 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:24:00 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:24:00 PM TCP packet not belonging to any open connection 192.168.1.1:5555 192.168.1.27:49483 TCP
    26/02/2013 10:23:59 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:23:50 PM No application listening on the port 192.168.1.27:68 255.255.255.255:67 UDP
    26/02/2013 10:23:25 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/02/2013 10:23:24 PM Communication denied by rule 192.168.1.27:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System

    Laptop B:
    26/2/13 10:26:04 PM No application listening on the port 192.168.1.25:68 255.255.255.255:67 UDP
    26/2/13 10:24:39 PM No application listening on the port 208.67.220.220:53 192.168.1.25:55174 UDP
    26/2/13 10:24:20 PM Communication denied by rule 192.168.1.25:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/2/13 10:24:18 PM Communication denied by rule 192.168.1.25:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/2/13 10:24:17 PM Communication denied by rule 192.168.1.25:137 67.215.65.132:137 UDP Block NETBIOS Name Service requests System
    26/2/13 10:23:55 PM No application listening on the port 192.168.1.22:5357 192.168.1.25:49241 TCP
    26/2/13 10:23:53 PM No application listening on the port 192.168.1.1:5555 192.168.1.25:49235 TCP
    26/2/13 10:23:46 PM No application listening on the port 192.168.1.27:68 255.255.255.255:67 UDP
    26/2/13 10:21:09 PM No application listening on the port 192.168.1.1:5555 192.168.1.25:49233 TCP
    26/2/13 10:21:09 PM No application listening on the port 192.168.1.1:5555 192.168.1.25:49232 TCP
    26/2/13 10:21:09 PM No application listening on the port 192.168.1.1:5555 192.168.1.25:49231 TCP
    26/2/13 10:21:09 PM No application listening on the port 192.168.1.1:5555 192.168.1.25:49230 TCP
    26/2/13 10:21:09 PM No application listening on the port 192.168.1.1:5555 192.168.1.25:49229 TCP
    26/2/13 10:20:41 PM Communication denied by rule fe80::65d6:1e1c:168c:6d2a.:61618 ff02::c.:1900 UDP Block outgoing SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    26/2/13 10:20:39 PM No application listening on the port 192.168.1.27:68 255.255.255.255:67 UDP
    26/2/13 10:20:39 PM Communication denied by rule 192.168.1.1:35691 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    26/2/13 10:20:39 PM Communication denied by rule 192.168.1.1:35691 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    26/2/13 10:20:39 PM Communication denied by rule 192.168.1.1:35691 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    26/2/13 10:20:39 PM Communication denied by rule 192.168.1.1:35691 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    26/2/13 10:20:39 PM Communication denied by rule 192.168.1.1:35691 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    26/2/13 10:20:39 PM Communication denied by rule 192.168.1.1:35691 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    26/2/13 10:20:39 PM Communication denied by rule 192.168.1.1:35691 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE
    26/2/13 10:20:39 PM Communication denied by rule 192.168.1.1:35691 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests for svchost.exe C:\Windows\System32\svchost.exe NT AUTHORITY\LOCAL SERVICE


    Thanks RexG
     
  13. Thyme Lawn

    Thyme Lawn Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    4
    Location:
    UK
    I had the same problem RexG.

    The solution was to open "Advanced setup - Network - Personal firewall - Rules and zones", click the "Setup..." button for "Trusted zones" and change the protection mode from the default "Public network" to "Home/work network".
     
Thread Status:
Not open for further replies.