<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Microsoft NLB and SRM</title>
    <link>http://communities.vmware.com/community/vmtn/mgmt/srm?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Tue, 30 Jun 2009 11:45:52 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-06-30T11:45:52Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Microsoft NLB and SRM</title>
      <link>http://communities.vmware.com/message/1298551?tstart=0#1298551</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
We currently use NLB within our VM's for alot of our reporting services and web for increased availability at our Primary site. We will be implementing SRM in the very near future and would like to know what potential issues there will be failing over these servers via srm to our DR site. Specifically with changing IP addresses.&lt;br /&gt;
&lt;p /&gt;
Does anyone have this implemented as yet&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Currently have ESX 3.5 and Virtual Centre 2.5.0.64237&lt;br /&gt;
&lt;p /&gt;
 Any advice would be great&lt;br /&gt;
&lt;p /&gt;
Thanks</description>
      <pubDate>Tue, 30 Jun 2009 11:45:52 GMT</pubDate>
      <author>ejdaly66</author>
      <guid>http://communities.vmware.com/message/1298551?tstart=0#1298551</guid>
      <dc:date>2009-06-30T11:45:52Z</dc:date>
      <clearspace:dateToText>4 months, 4 weeks ago</clearspace:dateToText>
    </item>
  </channel>
</rss>

