<?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>PeteStilgoe.com &#187; Firewalls</title>
	<atom:link href="http://www.petestilgoe.com/category/firewalls/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.petestilgoe.com</link>
	<description>&#34;Be fearful when others are greedy, be greedy when others are fearful.”</description>
	<lastBuildDate>Mon, 30 Jan 2012 14:28:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
		<item>
		<title>K2 Blackpoint Blackpearl: Communication with the underlying transaction manager has failed</title>
		<link>http://www.petestilgoe.com/2011/04/k2-blackpoint-blackpearl-communication-with-the-underlying-transaction-manager-has-failed/</link>
		<comments>http://www.petestilgoe.com/2011/04/k2-blackpoint-blackpearl-communication-with-the-underlying-transaction-manager-has-failed/#comments</comments>
		<pubDate>Wed, 27 Apr 2011 10:30:09 +0000</pubDate>
		<dc:creator>peter.stilgoe</dc:creator>
				<category><![CDATA[Firewalls]]></category>
		<category><![CDATA[K2 Blackpearl]]></category>
		<category><![CDATA[K2 Blackpoint]]></category>
		<category><![CDATA[Windows / Active Directory]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[Firewall ports]]></category>
		<category><![CDATA[MSDTC]]></category>
		<category><![CDATA[RPC]]></category>

		<guid isPermaLink="false">http://www.petestilgoe.com/?p=913</guid>
		<description><![CDATA[

When deploying a new K2 Blackpoint or K2 Blackpearl you may get the following error:
(K2Project) SmartObject Server Exception: Could not publish SmartObject Definition to server: Error refreshing Service Instance &#8216;WorkflowReportingService&#8217;. Service returned : &#8216;Workflow Reporting SO Service: Communication with the underlying transaction manager has failed.
SmartObject: [Test - Process Instances]
If you do checking the following may [...]]]></description>
		<wfw:commentRss>http://www.petestilgoe.com/2011/04/k2-blackpoint-blackpearl-communication-with-the-underlying-transaction-manager-has-failed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sharepoint &#8211; How to setup a one way trust &amp; required ports</title>
		<link>http://www.petestilgoe.com/2011/04/sharepoint-how-to-setup-a-one-way-trust-required-ports/</link>
		<comments>http://www.petestilgoe.com/2011/04/sharepoint-how-to-setup-a-one-way-trust-required-ports/#comments</comments>
		<pubDate>Fri, 01 Apr 2011 05:36:38 +0000</pubDate>
		<dc:creator>peter.stilgoe</dc:creator>
				<category><![CDATA[Firewalls]]></category>
		<category><![CDATA[Ports]]></category>
		<category><![CDATA[Sharepoint / MOSS / WSS]]></category>
		<category><![CDATA[Sharepoint 2010]]></category>
		<category><![CDATA[Windows / Active Directory]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[Windows Trust Relationship]]></category>
		<category><![CDATA[Firewall ports]]></category>
		<category><![CDATA[object picker]]></category>
		<category><![CDATA[one way trust]]></category>
		<category><![CDATA[people picker]]></category>

		<guid isPermaLink="false">http://www.petestilgoe.com/?p=882</guid>
		<description><![CDATA[

1.  Open Command Prompt.
2.  Type: netdom trustTrustingDomainName/d:TrustedDomainName/add
TrustingDomainName &#8211; Specifies the DNS name (or NetBIOS name) of the trusting domain in the trust being created.
TrustedDomainName &#8211; Specifies the DNS name (or NetBIOS name) of the domain that will be trusted in the trust being created.
• To perform this procedure, you must be a member [...]]]></description>
		<wfw:commentRss>http://www.petestilgoe.com/2011/04/sharepoint-how-to-setup-a-one-way-trust-required-ports/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Firewall Port Forwarding for H.323 video</title>
		<link>http://www.petestilgoe.com/2007/11/firewall-port-forwarding-for-h323-video/</link>
		<comments>http://www.petestilgoe.com/2007/11/firewall-port-forwarding-for-h323-video/#comments</comments>
		<pubDate>Fri, 23 Nov 2007 12:24:32 +0000</pubDate>
		<dc:creator>peter.stilgoe</dc:creator>
				<category><![CDATA[Firewalls]]></category>
		<category><![CDATA[Video Conferencing]]></category>

		<guid isPermaLink="false">http://www.petestilgoe.com/?p=192</guid>
		<description><![CDATA[

H.323 uses a single fixed TCP port (1720) to start a call using the H.225 protocol (defined by H.323 spec) for call control. Once that protocol is complete, it then uses a dynamic TCP port for the H.245 protocol (also defined by the H.323 spec) for caps and channel control. Finally, it opens up 2 [...]]]></description>
		<wfw:commentRss>http://www.petestilgoe.com/2007/11/firewall-port-forwarding-for-h323-video/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Typical ports used for video conferencing</title>
		<link>http://www.petestilgoe.com/2007/11/typical-ports-used-for-video-conferencing/</link>
		<comments>http://www.petestilgoe.com/2007/11/typical-ports-used-for-video-conferencing/#comments</comments>
		<pubDate>Fri, 23 Nov 2007 08:58:23 +0000</pubDate>
		<dc:creator>peter.stilgoe</dc:creator>
				<category><![CDATA[Firewalls]]></category>
		<category><![CDATA[Video Conferencing]]></category>

		<guid isPermaLink="false">http://www.petestilgoe.com/?p=191</guid>
		<description><![CDATA[

Typical ports that need to be opened on the firewall:
80 (TCP)
 HTTP
 Optional for external administration
389 (TCP)
 LDAP
 ILS registration
1503 (TCP)
 T.120
1720 (TCP)
 H.323
 H.323 call setup
1731 (TCP)
 H.323
 H.323 audio call control
1024-65535 (UDP)
 H.245, RTP, RTCP
 Various audio/video controls
As the above list shows, opening the required ports can leave a number of large &#8220;holes&#8221; [...]]]></description>
		<wfw:commentRss>http://www.petestilgoe.com/2007/11/typical-ports-used-for-video-conferencing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

