Question about blocked communication

Can someone please tell me what this means and if my firewall is supposed to be doing this? It does the ( Block incoming ICSLAP (UPNP) requests ) about once every 20 seconds. I can't see whether it has any effect on the way my computer runs or not. I'm just curious as to what it is and if I should do something about it.

9/21/2007 9:22:22 PM Communication denied by rule 192.168.0.1:1066 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM

9/21/2007 9:21:52 PM Communication denied by rule 192.168.0.1:1900 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests d:\windows\system32\svchost.exe NT AUTHORITY\LOCAL SERVICE

 

It seems that I still have a problem with my home network. When I click on "My Network Places" I can access some of the shared files but as usual the list is incomplete. Also the printer is sharing. Then when I click on "View workgroup computers" to view the whole list I get this error message:

"Mshome is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The list of servers for this workgroup is not currently available."

In my firewall log I find a lot of entries. These are a few. I tried not to post duplicates here. There are a number of each of these entries usually a few seconds apart. There were others that I didn't post.

9/22/2007 9:09:11 AM Communication denied by rule 192.168.0.1:1077 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
9/22/2007 9:07:58 AM Communication denied by rule 192.168.0.1:1076 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
9/22/2007 9:07:25 AM Communication denied by rule 192.168.0.1:1075 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
9/22/2007 9:06:25 AM No usable rule found 192.168.0.100 224.0.0.22 IGMP
9/22/2007 9:06:24 AM Communication denied by rule 192.168.0.1:1900 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests
9/22/2007 8:24:12 AM Communication denied by rule 192.168.0.100:137 12.120.1.254:137 UDP Block outgoing NETBIOS requests system NT AUTHORITY\SYSTEM
9/22/2007 8:24:11 AM Communication denied by rule 192.168.0.100:137 12.120.1.254:137 UDP Block outgoing NETBIOS requests system NT AUTHORITY\SYSTEM
9/22/2007 8:24:08 AM Communication denied by rule 192.168.0.100:137 199.106.212.28:137 UDP Block outgoing NETBIOS requests system NT AUTHORITY\SYSTEM
9/22/2007 8:24:03 AM Communication denied by rule 192.168.0.100:137 63.240.249.39:137 UDP Block outgoing NETBIOS requests system NT AUTHORITY\SYSTEM
9/21/2007 9:25:29 PM Communication denied by rule 192.168.0.1:1068 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM

 

Could you please contact the Eset's support via the internal form and list this thread's url in the subject? By doing so we'll be able to see what rules you have created and advise further.

 

Thanks for the help Marcos. I filled out the Technical Support Query but when I clicked on "finish" I didn't see anything happen so I'm not sure whether it sent or not. I'm unable to call up the Technical Support Query (web form). I hope that's not the one you wanted. I've never been able to call up the websites listed in help.

As I said in my previous post everything seems alright except the "View workgroup computers" link. I have quite a few shared files that don't show in "My Network Places". The other computer can access the files that it can see but this computer doesn't show up in the workgroup.

 

I'm not an firewall expert and I don't quiet understand the information you've posted, but I got my File-Sharing working again. Maybe you can try the same method to solve your problem, probably worth a try if you haven't allready.

You can find it in your previous thread:

https://www.wilderssecurity.com/showthread.php?p=1082593#post1082593

I hope it works, good luck.

 

I really wish I knew if the report I sent to ESET went through. It looks to me like it might not have. Could somebody please let me know about this?

Correction: It shows in the log that it did go through. It didn't show up right after it sent so I didn't know. I guess they're working on it.

 

I realize I have two threads about the same issue. When I started the second I thought the first was all squared away and I had a second issue. If one of the moderators want to kill one or merge them that would be good.

https://www.wilderssecurity.com/showthread.php?t=185194