• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

Kudos0

Confusing Firewall entry

Going forward, I was not going to borrow trouble looking at firewall logs. But prior to that decsion I did notice something very puzzling and a little concerning

 

It seems that when my computer is scheduled to check for microsoft updates, there will be an odd entry in my firewall log

For illustrative purposes, lets say

 my current IP address is 66.141.168.166

 

so prior to the microsoft update check, my firewall log will show

 Port Blocking allowed 66.141.168.255(3)

where the IP address is similar to mine, but ends in 255 rather than 166 and appears to use port 3(?)

Now I know that IP addresses ending in .255 are like broadcast message from the ISP used to connect to all IP address from 66.141.168.1 through 66.141.168.254 (whatever that means and whatever that is for)

But the main question I have is why would IP address  66.141.168.255(3) be showing everytime there is a scheduled check for windows update??why would my ISP have anything to do with that?

Surely it is not a coincidence each and every time?? And it only seems to happen when my computer automatically initiates the check for windows updates,  not if I run a manual check  for updates

(by the way, updates do get downloaded when they are found and connections to microsoft are noted in the internet connection log)

If anyone can help me understand it, I'd be grateful.

Thanks

Replies

Kudos0

Re: Confusing Firewall entry

Going forward, I was not going to borrow trouble looking at firewall logs. But prior to that decsion I did notice something very puzzling and a little concerning

 

It seems that when my computer is scheduled to check for microsoft updates, there will be an odd entry in my firewall log

For illustrative purposes, lets say

 my current IP address is 66.141.168.166

 

so prior to the microsoft update check, my firewall log will show

 Port Blocking allowed 66.141.168.255(3)

where the IP address is similar to mine, but ends in 255 rather than 166 and appears to use port 3(?)

Now I know that IP addresses ending in .255 are like broadcast message from the ISP used to connect to all IP address from 66.141.168.1 through 66.141.168.254 (whatever that means and whatever that is for)

But the main question I have is why would IP address  66.141.168.255(3) be showing everytime there is a scheduled check for windows update??why would my ISP have anything to do with that?

Surely it is not a coincidence each and every time?? And it only seems to happen when my computer automatically initiates the check for windows updates,  not if I run a manual check  for updates

(by the way, updates do get downloaded when they are found and connections to microsoft are noted in the internet connection log)

If anyone can help me understand it, I'd be grateful.

Thanks

Kudos1 Stats

Re: Confusing Firewall entry

Hi! Calls,

Is computer connected to internet via a router (or similare device) or to a broadband modem directly or is it dial-up?

There are some ISP's that have a server on their own network called an update server which means it will provide the exact same services as Microsoft's own update servers.  If ISP is one of those that do have an update server on their network then your computer may recieve updates from there instead of going all the way to a Microsoft update server to get the updates.  Generally ISP update servers can be configured to mirror Microsoft's and therefore provide faster downloads of updates and ease the load on Microsoft's own servers so that those who have an ISP that does not provide an update server for their customers can more readily access Micorsoft's update servers when they need to.

I hope this clears things up without confusing you more.  ;)

Kudos0

Re: Confusing Firewall entry

Thanks Tech

I have a DSL box without router or router function

Now the thing is that it does not happen all the time. Would it be possible that sometimes the microsoft up dates  come in via my ISP and sometimes not? When I get that entry

Port blocking allowed xx.xx.xx..255(3) my connection log still shows connection to microsoft. So is my ISP acting as a conduit?

And again would that just be sometimes that the ISP would work with the microsoft update downloads?

MY provider is AT&T

This thread is closed from further comment. Please visit the forum to start a new thread.