<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>RPC to Go v.2</title><link>http://blogs.technet.com/networking/archive/2008/12/04/rpc-to-go-v-2.aspx</link><description>This post is an update to &amp;#8220; RPC to Go v.1 .&amp;#8221;&amp;#160; I assume that you have read v.1 and have a basic understanding of how the RPC protocol works.&amp;#160; We&amp;#8217;ll take a closer look at the architecture, End Point Mapper bind and the RPC bind.&amp;#160;</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Excellent information on RPC especially the network capture details</title><link>http://blogs.technet.com/networking/archive/2008/12/04/rpc-to-go-v-2.aspx#3167634</link><pubDate>Fri, 12 Dec 2008 21:04:53 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3167634</guid><dc:creator>edz314</dc:creator><description>&lt;p&gt;This is very helpful information on RPC, especially the details what shows up in a network capture. I've slogged through a number of network captures involving RPC and trying to piece together what each command means - every piece of information helps! I've read the documentation, and found it difficult to follow, so this smaller, focused example is useful.&lt;/p&gt;
</description></item><item><title>RPC to Go v.3 – Named Pipes</title><link>http://blogs.technet.com/networking/archive/2008/12/04/rpc-to-go-v-2.aspx#3232169</link><pubDate>Wed, 29 Apr 2009 00:29:29 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3232169</guid><dc:creator>Microsoft Enterprise Networking Team</dc:creator><description>&lt;p&gt;In this blog I’d like to give some information on what Named Pipes are, what a Named Pipes connection&lt;/p&gt;
</description></item><item><title>re: RPC to Go v.2</title><link>http://blogs.technet.com/networking/archive/2008/12/04/rpc-to-go-v-2.aspx#3256142</link><pubDate>Thu, 18 Jun 2009 10:08:54 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3256142</guid><dc:creator>jack123</dc:creator><description>&lt;p&gt;I captured IPv6 packets on Windows 2008, and got &amp;quot;DOD IP&amp;quot; zero. DCE RPC 1.1 didn't mention anything about IPv6. Are there any specs update for IPv6?&lt;/p&gt;</description></item><item><title>re: RPC to Go v.2</title><link>http://blogs.technet.com/networking/archive/2008/12/04/rpc-to-go-v-2.aspx#3256144</link><pubDate>Thu, 18 Jun 2009 10:10:45 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3256144</guid><dc:creator>jack123</dc:creator><description>&lt;p&gt;I captured IPv6 packets on Windows 2008, and got &amp;quot;DOD IP&amp;quot; zero. DCE RPC 1.1 didn't mention anything about IPv6. Are there any specs update for IPv6?&lt;/p&gt;</description></item></channel></rss>