688 13:46:31 16/04/2015 127.2961102 Unavailable 192.168.1.67 239.255.255.250 SSDP SSDP:Request, NOTIFY *  {HTTP:159, UDP:158, IPv4:66}
689 13:46:31 16/04/2015 127.2963913  FE80:0:0:0:E9E5:E038:4E5A:99E1 FF02:0:0:0:0:0:0:C SSDP SSDP:Request, NOTIFY *  {HTTP:161, UDP:160, IPv6:47}
690 13:46:31 16/04/2015 127.9491966 Unavailable 192.168.1.67 239.255.255.250 SSDP SSDP:Request, NOTIFY *  {HTTP:159, UDP:158, IPv4:66}
691 13:46:31 16/04/2015 127.9496419  FE80:0:0:0:E9E5:E038:4E5A:99E1 FF02:0:0:0:0:0:0:C SSDP SSDP:Request, NOTIFY *  {HTTP:161, UDP:160, IPv6:47}
692 13:46:32 16/04/2015 129.1669244 Unavailable 192.168.1.67 239.255.255.250 SSDP SSDP:Request, NOTIFY *  {HTTP:159, UDP:158, IPv4:66}
 

 

According to Microsoft Network Monitor, there are an awful lot repeated blocks of transactions like above running on my home network at the moment.

 

Who is the "Destination" 239.255.255.250 ? Some say Firefox, some Norton.

 

Should I be worried about the fact that the system identifies the name of the process resident on my desktop  as "Unavailable".

 

 

Nick
 

Edited 16 April, 201511 yr by Clunkclick

http://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol

It's a multicast address used for service discovery - probably completely normal activity.

What worries me is that its using HTTP port 159 and UDP 158, which in days gone by used to be prime targets for hackers.

 

Why is the process name "Unavailable"  ?

 

Would there be a Microsoft process that was reported as "Unnamed" ?

 

Would a correctly installed and loaded third party application be able to omit or withhold a process name ?

 

 

Nick

Which device is 192.168.1.67

 

TCP services are not windows or Microsoft services, unnamed just means the port in use does not have a common service allocated to it. There are 65536 IP ports, some have services but most are free to use by anything as they see fit.

 

http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

 

I am going to hazard a guess and say the the device 192.168.1.67 is essentially broadcasting its available services on your LAN waiting for other connected devices to discover them, for example DLNA etc. and most likely nothing to worry about at all. Windows does this all the time with home networks, and its why when connected to a domain network (business) the broadcasts are disabled by Windows automatically.

 

You could try this

 

http://en.kioskea.net/faq/20880-windows-7-disable-the-ssdp-discovery-service