https://community.cisco.com/t5/network-security/microsoft-updates-require-inbound-rules/m-p/3054053#M1015166 <P>Hi,&nbsp;</P> <P></P> <P>I am facing a strange issue with regards to Microsoft Updates. I can see connection drops in the context explorer for Microsoft updates. In the logs I can see that there is inbound traffic that is being blocked by the FTD with the source port of 443 probably from microsoft update server. Since these updates are response to the request initiated from the internal networks shouldn't the inbound traffic be allowed automatically by the firewall.&nbsp;</P> <P></P> <P>Another strange thing I found is we do not need to explicitly allow microsoft update or windows update as an application in the rules. just by allowing DNS, HTTP &amp; HTTPS it works. I can't see microsoft update application as denied application in the application statistics dashboard.&nbsp;</P> <P></P> <P>Has anyone faced a similar issue with microsoft updates on FTD 6.2.0 version.&nbsp;</P> <P></P> <P>Vaibhav</P> Tue, 12 Mar 2019 13:26:56 GMT vaibhav.parlekar1 2019-03-12T13:26:56Z https://community.cisco.com/t5/network-security/microsoft-updates-require-inbound-rules/m-p/3054053#M1015166 <P>Hi,&nbsp;</P> <P></P> <P>I am facing a strange issue with regards to Microsoft Updates. I can see connection drops in the context explorer for Microsoft updates. In the logs I can see that there is inbound traffic that is being blocked by the FTD with the source port of 443 probably from microsoft update server. Since these updates are response to the request initiated from the internal networks shouldn't the inbound traffic be allowed automatically by the firewall.&nbsp;</P> <P></P> <P>Another strange thing I found is we do not need to explicitly allow microsoft update or windows update as an application in the rules. just by allowing DNS, HTTP &amp; HTTPS it works. I can't see microsoft update application as denied application in the application statistics dashboard.&nbsp;</P> <P></P> <P>Has anyone faced a similar issue with microsoft updates on FTD 6.2.0 version.&nbsp;</P> <P></P> <P>Vaibhav</P> Tue, 12 Mar 2019 13:26:56 GMT https://community.cisco.com/t5/network-security/microsoft-updates-require-inbound-rules/m-p/3054053#M1015166 vaibhav.parlekar1 2019-03-12T13:26:56Z https://community.cisco.com/t5/network-security/microsoft-updates-require-inbound-rules/m-p/3054054#M1015167 <P>If you're not able to conclude what is the reason for drops from connection event and other then try firewall-engine-debug and initiate intended traffic from one of the machines. it would give more insight: Login to FTD device and run this command. Eg:</P> <P>&gt; system support firewall-engine-debug</P> <P>Please specify an IP protocol:<BR />Please specify a client IP address: 172.16.10.10<BR />Please specify a client port:<BR />Please specify a server IP address:<BR />Please specify a server port: 443</P> <P></P> <P>It's one of the beautiful commands to know what is happening with the traffic being sent. Hope you get some more info from this about the issue.</P> <P></P> <P>Regards,</P> <P>Dv</P> Wed, 05 Jul 2017 21:23:32 GMT https://community.cisco.com/t5/network-security/microsoft-updates-require-inbound-rules/m-p/3054054#M1015167 Dinesh Verma 2017-07-05T21:23:32Z