<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Firewall on Matt Allford</title><link>https://www.mattallford.com/tags/firewall/</link><description>Recent content in Firewall on Matt Allford</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 22 Sep 2018 02:17:29 +0000</lastBuildDate><atom:link href="https://www.mattallford.com/tags/firewall/index.xml" rel="self" type="application/rss+xml"/><item><title>Quick Post - PowerCLI Firewall Requirements</title><link>https://www.mattallford.com/quick-post-powercli-firewall-requirements/</link><pubDate>Sat, 22 Sep 2018 02:17:29 +0000</pubDate><guid>https://www.mattallford.com/quick-post-powercli-firewall-requirements/</guid><description>&lt;p&gt;Last night I was working in an environment that has a reasonably well locked down NSX distributed firewall, and I was having some issues with PowerCLI. PowerCLI 10.2 on Windows, connecting to vCenter Server 6.7, to be specific. Port 443 was allowed from the jump host to vCenter Server, but I was seeing some odd issues still.&lt;/p&gt;
&lt;p&gt;I was trying to run an &lt;a href="https://github.com/tpcarman/As-Built-Report"&gt;as built report&lt;/a&gt; for the environment, but I could not seem to establish a connection to NSX manager when running the script, and VUM cmdlets that are called in the script were also failing, such as:&lt;/p&gt;</description></item></channel></rss>