<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RDP Vs. Windows Load Balancing in ProLiant Deployment and Provisioning</title>
    <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-vs-windows-load-balancing/m-p/3359342#M989</link>
    <description>You are right, NLB may have problems with imaged severs if NIC driver is part of the image because they will have the same network GUID in theirs registry. Try to remove and reinstall NIC driver. For more information see: &lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;828258&amp;amp;Product=winsvr2003" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;828258&amp;amp;Product=winsvr2003&lt;/A&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 16 Sep 2024 09:34:29 GMT</pubDate>
    <dc:creator>Enes Dizdarevic</dc:creator>
    <dc:date>2024-09-16T09:34:29Z</dc:date>
    <item>
      <title>RDP Vs. Windows Load Balancing</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-vs-windows-load-balancing/m-p/3359341#M988</link>
      <description>We setup a HP BL20p blade using the RDP's canned Scripted Install for Windows 2003. We then imaged it and deployed the image to a 2nd blade using the Deploy Hardware script.&lt;BR /&gt;We set up Windows Network Load Balancing for use with IIS, using the NLB manager and everything appeared fine. We attempted to access our default web page and cannot connect. We run a ping on the NLB IP address and it times out as soon as you send an HTTP request. We believe it may be an issue with the RDP Imaging. Anyone encounter a similar problem?</description>
      <pubDate>Tue, 17 Aug 2004 17:43:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdp-vs-windows-load-balancing/m-p/3359341#M988</guid>
      <dc:creator>Joe Buerkle</dc:creator>
      <dc:date>2004-08-17T17:43:07Z</dc:date>
    </item>
    <item>
      <title>Re: RDP Vs. Windows Load Balancing</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-vs-windows-load-balancing/m-p/3359342#M989</link>
      <description>You are right, NLB may have problems with imaged severs if NIC driver is part of the image because they will have the same network GUID in theirs registry. Try to remove and reinstall NIC driver. For more information see: &lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;828258&amp;amp;Product=winsvr2003" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;828258&amp;amp;Product=winsvr2003&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Sep 2024 09:34:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdp-vs-windows-load-balancing/m-p/3359342#M989</guid>
      <dc:creator>Enes Dizdarevic</dc:creator>
      <dc:date>2024-09-16T09:34:29Z</dc:date>
    </item>
    <item>
      <title>Re: RDP Vs. Windows Load Balancing</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-vs-windows-load-balancing/m-p/3359343#M990</link>
      <description>We did find the reference to the Image vs. the NIC card and followed the guidelines. We have been able get windows load balancing in multicast mode but not unicast mode.</description>
      <pubDate>Mon, 23 Aug 2004 17:43:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdp-vs-windows-load-balancing/m-p/3359343#M990</guid>
      <dc:creator>Joe Buerkle</dc:creator>
      <dc:date>2004-08-23T17:43:53Z</dc:date>
    </item>
  </channel>
</rss>

