I had put my computer into sleep mode before leaving it for the day. When I returned it apparently something from Norton 360 may have woke up the desktop from sleep mode. Looking through the security history there is one message that is continiously appearing and this same message goes on for hours. It apparently woke itself up when an Identity function apparently updated itself and from there after there is a LiveUpdate session followed by this message that is constantly appearing.
The message is:
Firewall rule was matched:
Rule name: Default Block UPnP Discovery
Rule action: rejected
Rule severity: normal
Traffic Details:
Protocol: UDP(17)
Direction: Inbound
Local Host:
Local IP:239.255.255.250
Local Service: Port ssdp(1900)
Remote Host:
Remote IP: 192.168.0.1
Remote Service: Port ssdp(1900)
Remote MAC: --
Adapter Index: 11
Process Information:
Process ID: 1104
Process Path: C:\\Windows\System32\svchost.exe
Would anybody have any information on what this function might be? It has been doing this all day and is still continuing to try to access the system.
I had put my computer into sleep mode before leaving it for the day. When I returned it apparently something from Norton 360 may have woke up the desktop from sleep mode. Looking through the security history there is one message that is continiously appearing and this same message goes on for hours. It apparently woke itself up when an Identity function apparently updated itself and from there after there is a LiveUpdate session followed by this message that is constantly appearing.
The message is:
Firewall rule was matched:
Rule name: Default Block UPnP Discovery
Rule action: rejected
Rule severity: normal
Traffic Details:
Protocol: UDP(17)
Direction: Inbound
Local Host:
Local IP:239.255.255.250
Local Service: Port ssdp(1900)
Remote Host:
Remote IP: 192.168.0.1
Remote Service: Port ssdp(1900)
Remote MAC: --
Adapter Index: 11
Process Information:
Process ID: 1104
Process Path: C:\\Windows\System32\svchost.exe
Would anybody have any information on what this function might be? It has been doing this all day and is still continuing to try to access the system.