<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Bozteck Blog &#187; Ports</title>
	<atom:link href="http://vncscan.com/blog/tag/ports/feed/" rel="self" type="application/rss+xml" />
	<link>http://vncscan.com/blog</link>
	<description>VNCScan Enterprise Network Manager (VENM)</description>
	<lastBuildDate>Tue, 03 Apr 2012 19:18:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Disabling Firewalls for Management</title>
		<link>http://vncscan.com/blog/2008/06/disabling-firewalls-for-management/</link>
		<comments>http://vncscan.com/blog/2008/06/disabling-firewalls-for-management/#comments</comments>
		<pubDate>Wed, 25 Jun 2008 17:21:00 +0000</pubDate>
		<dc:creator>Bozteck</dc:creator>
				<category><![CDATA[how-to]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[Firewall]]></category>
		<category><![CDATA[Ports]]></category>
		<category><![CDATA[TCP]]></category>
		<category><![CDATA[vnc]]></category>

		<guid isPermaLink="false">http://vncscan.com/blog/?p=18</guid>
		<description><![CDATA[I&#8217;ve had a lot of requests for a way to disable XP firewalls on the network or at least open up the required ports to remotely manage the computers. If your workstations are protected by a NAT translating router with a decent firewall built into it, there is typically little need for the XP desktop [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve had a lot of requests for a way to disable XP firewalls on the network or at least open up the required ports to remotely manage the computers.  If your workstations are protected by a NAT translating router with a decent firewall built into it, there is typically little need for the XP desktop firewall to be running on them.</p>
<p>If you have the XP firewall enabled, there&#8217;s very little that you can do in the way of remote management for these PC&#8217;s.  Fortunately, there are was to automate the configuration of the XP firewalls on your network depending on what type of a network you are using.</p>
<p><span style="font-weight: bold;">Login Script Method</span></p>
<p>The easiest way to do this is with a login script.  If your company is using a directory services such as Novel or Active Directory, you can create a script that runs each time that a user logs in.  You can use this script to open the required firewall ports.</p>
<p>We run into a problem, however, if the user that is logging in does not have local administrative rights on his PC.  This is required to modify the settings.  For this, we can employ a nice piece of freeware called <a href="http://www.joeware.net/freetools/tools/cpau/index.htm">CPAU</a>.  Using this tool, you can do a run-as style command to make it go.  Alternatively, you can use a tool such as <a href="http://www.adminscripteditor.com/">Admin Script Editor</a> to compile your script into an executable that runs under a specific security account.  There are other tools that can do this and feel free to add them in the comments section if you would.</p>
<p><span style="font-weight: bold;">Active Directory Startup Script Method</span></p>
<p>You can also run the script using Active Directory&#8217;s group policy for the machine account.  This script runs under the context of the machine&#8217;s system account and does not need to be elevated by tools such as CPAU.  You can do this in the Group Policy Editor under &#8220;Windows Settings =&gt; Scripts =&gt; Startup&#8221;.</p>
<p>The following is a script that will open the required ports on the XP firewall:</p>
<blockquote>
<div style="text-align: justify;"><span style="font-family:times new roman;">netsh firewall set portopening udp 445 WindowsNetworking enable all</span><br />
<span style="font-family:times new roman;">netsh firewall set portopening tcp 139 WindowsNetworking enable all</span><br />
<span style="font-family:times new roman;">netsh firewall set portopening udp 137 WindowsNetworking enable all</span><br />
<span style="font-family:times new roman;">netsh firewall set portopening udp 138 WindowsNetworking enable all</span><br />
<span style="font-family:times new roman;">netsh firewall set portopening tcp 5900 VNC enable all</span><br />
<span style="font-family:times new roman;">netsh firewall set portopening tcp 5800 VNC-HTTP enable all</span></div>
</blockquote>
<p><span style="font-weight: bold;">Group Policy Method</span></p>
<p>You can set these options using Active Directory&#8217;s Group Policy, also.  You can access this in the Group Policy Editor by navigating to &#8220;Computer Configuration =&gt; Administrative Templates =&gt; Network =&gt; Network Connections =&gt; Windows Firewall&#8221;.</p>
<p><span style="font-weight: bold;">Extra Notes</span></p>
<p>As a side note, if you choose to use a scripting tool such as Admin Script Editor to compile your script, you can also choose to distribute it directly to the end users so that they can execute it themselves.</p>
<p>Make sure that you also disable <a href="http://is.gd/FLI">Simple File Sharing</a> on the remote computers.  That can be just as much of a barrier to remote administration as the firewall.  I&#8217;ll make a post about that one soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://vncscan.com/blog/2008/06/disabling-firewalls-for-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

