Watchguard Firebox Edge and how to configure it to allow Microsoft Windows Updates

Can't get Microsoft Windows Updates to pass through my Firebox Edge.  Thoughts?

Here's an error message that I see frequently on the log:
deny in eth0 40 tcp 20 255 64.4.21.61 xx.xxx.xx.xx 80 38532 ack rst (Non-est TCP)
LVL 1
atroutcatcherAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
dpk_walConnect With a Mentor Commented:
From the navigation bar, select Firewall > Outgoing; Edit HTTP. From the Edit Policies page, select the Outgoing tab; set Incoming Filter drop-down list to Allow; in From leave it to Any; in the To field add all the microsoft server public IP addresses one by one; click Submit.

This service would have precedence over the HTTP proxy for outbound traffic to microsoft update servers.

Please implement and update.

Thank you.
0
 
dpk_walCommented:
Have you enabled HTTP proxy on Edge; if yes, then you can create a service to allow connection from internal network to the the microsoft update server (all of them, public IP address); sometimes the proxy might prevent traffic.

The log you have posted indicates that the packet has come from internet when the session is not established.

Can you provide some details if you have proxy enabled or not.

Thank you.
0
 
atroutcatcherAuthor Commented:
Hi and thank you.

The HTTP proxy IS enabled on the Edge.
0
KuppingerCole Reviews AlgoSec in Executive Report

Leading analyst firm, KuppingerCole reviews AlgoSec's Security Policy Management Solution, and the security challenges faced by companies today in their Executive View report.

 
dpk_walCommented:
Would it be possible for you to disable HTTP proxy or create custom service to allow traffic to Microsoft update servers?
0
 
atroutcatcherAuthor Commented:
I will gladly try it.  Do you have the specifics on what to setup?  

The Windows Update servers seem to constantly rotate and/or change.

Please advise about how to configure for the services to work.
0
 
atroutcatcherAuthor Commented:
Update:

I've been adding IP addresses as you suggest, but the IP addresses change EVERY time I attempt the download of an update.  Thus, this scheme could take months to finish.  Is this correct?

Also, is there a list of the public Microsoft servers somewhere?  Or is this information protected?

Maybe this system is not the one I should be using?  Not only are Windows Updates not coming through, but the Adobe players won't download either.

Thanks for your help.
0
 
dpk_walCommented:
Yes it can take long to add each and every IP address; but if you have a single machine which should download all the download and then distribute it to all the internal server; then we can open all the traffic for this server only; configure service as below instead:
From ip-address-of-internal-server; To ANY

please note for the above machine there would be no filtering at all.

Please see if this help you.

Thank you.
0
 
atroutcatcherAuthor Commented:
Update - still working on this.  Still haven't been able to get the flow of information to work properly and/or consistently.
0
 
dpk_walCommented:
I am sorry, I know the solution is not the most elegant one; but this is all what we can do.
0
 
atroutcatcherAuthor Commented:
Thanks.  Lengthy process but it appears to be working.  Best regards.
0
 
dpk_walCommented:
Happy I could be assistance! :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.