Windows Update on Perimeter & DMZ broke (Full Version)

All Forums >> [ISA 2006 Firewall] >> Access Policies



Message


SyberWizard -> Windows Update on Perimeter & DMZ broke (7.Mar.2007 4:57:32 PM)

Server has four NIC: Internal, External, Perimeter (for a 20-station computer repair bench), and DMZ (for ISP servers). Internal works fine for Windows Updates. Perimeter and DMZ however, will not. I have even created an access rule to allow All Protocols to both Perimeter and DMZ, and it still does not work. I've seen suggestions to use WSUS, but the issue is the computers on the repair bench are not ours, we are just fixing them. As a courtesy, we go ahead and apply all updates. I do not know how WSUS would fit with this scenario. I must be missing the bigger picture of how this worked flawlessly in 2004, and seems perfectly broken in 2006. And I am assuming that it must be something I've done, else I would see tons of posts here about it. Advice, suggestions?




matheesha -> RE: Windows Update on Perimeter & DMZ broke (11.Mar.2007 6:30:30 AM)

What protocol traffic are you seen failing? Is it https packets to the windows update servers?




spouseele -> RE: Windows Update on Perimeter & DMZ broke (11.Mar.2007 8:54:01 AM)

Hi SyberWizard,

check out Multi-Networking WPAD Support in ISA 2004.

HTH,
Stefaan




SyberWizard -> RE: Windows Update on Perimeter & DMZ broke (13.Mar.2007 7:37:10 PM)

Finally got it to working.  The Perimeter network was set to Route instead of NAT.  As soon as I changed it to NAT, everything started working fine.

Now if I can just get the SBS SharePoint working the way I want it too ...




Page: [1]