<?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: Network problem Proliant 1600 in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952881#M17304</link>
    <description>Sorry, must have missed that.  When did this start happening?  Has it always happened?  It looks like a problem with the nic.</description>
    <pubDate>Wed, 16 Apr 2003 15:07:35 GMT</pubDate>
    <dc:creator>Terry Hutchings</dc:creator>
    <dc:date>2003-04-16T15:07:35Z</dc:date>
    <item>
      <title>Network problem Proliant 1600</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952878#M17301</link>
      <description>Our Proliant 1600 works fine, but in the event log from Windows NT 4.0 and in the configuration utility network problem are seen.&lt;BR /&gt;&lt;BR /&gt;In the eventlog, every 10 seconds the warning "network link is down, check your cabling" is displayed, two seconds later the notice "network link is restored" is displayed.&lt;BR /&gt;&lt;BR /&gt;In the Compaq network configuration utility", link status interupts almost 20000 per day.&lt;BR /&gt;&lt;BR /&gt;But we don't notice any network problems working on that server, i think the error is not true, this because I changed the network cable and put in on another switch.&lt;BR /&gt;&lt;BR /&gt;I upgrade de network driver to the latest version.&lt;BR /&gt;&lt;BR /&gt;Anywhone an idea? (if you understand this very bad english :-) )&lt;BR /&gt;&lt;BR /&gt;Thans,&lt;BR /&gt;Roland</description>
      <pubDate>Wed, 16 Apr 2003 14:09:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952878#M17301</guid>
      <dc:creator>Roland Heeling</dc:creator>
      <dc:date>2003-04-16T14:09:17Z</dc:date>
    </item>
    <item>
      <title>Re: Network problem Proliant 1600</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952879#M17302</link>
      <description>Have you tried a different port on the switch.  Have you tried a plugging this into a hub or different brand of switch.</description>
      <pubDate>Wed, 16 Apr 2003 14:42:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952879#M17302</guid>
      <dc:creator>Terry Hutchings</dc:creator>
      <dc:date>2003-04-16T14:42:38Z</dc:date>
    </item>
    <item>
      <title>Re: Network problem Proliant 1600</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952880#M17303</link>
      <description>[quote]&lt;BR /&gt;Have you tried a different port on the switch. Have you tried a plugging this into a hub or different brand of switch. &lt;BR /&gt;[/quote]&lt;BR /&gt;&lt;BR /&gt;Yes, tried an 3com switch and a compaq netelligent hub, makes no differents.&lt;BR /&gt;&lt;BR /&gt;Thanks,</description>
      <pubDate>Wed, 16 Apr 2003 14:50:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952880#M17303</guid>
      <dc:creator>Roland Heeling</dc:creator>
      <dc:date>2003-04-16T14:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: Network problem Proliant 1600</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952881#M17304</link>
      <description>Sorry, must have missed that.  When did this start happening?  Has it always happened?  It looks like a problem with the nic.</description>
      <pubDate>Wed, 16 Apr 2003 15:07:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952881#M17304</guid>
      <dc:creator>Terry Hutchings</dc:creator>
      <dc:date>2003-04-16T15:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: Network problem Proliant 1600</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952882#M17305</link>
      <description>How are the NICs configured? Are you setting speed &amp;amp; duplex, or are they set at Auto/Auto? I have seen instances where the switch has the speed set, and the NIC has the speed set, there is just enough of a mismatch on the timing to cause these type of errors. Try setting to Auto/Auto &amp;amp; monitor event log to see if this corrects the issue.&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Apr 2003 12:15:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952882#M17305</guid>
      <dc:creator>Neal Bowman</dc:creator>
      <dc:date>2003-04-17T12:15:29Z</dc:date>
    </item>
    <item>
      <title>Re: Network problem Proliant 1600</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952883#M17306</link>
      <description>Sorry for the late response, i've had a holiday for a few weeks.&lt;BR /&gt;&lt;BR /&gt;it makes no difference wat the speed or duplex is, it is set on auto/auto, but i've tried, 10mbit ot 100mbit and half or full duplex.&lt;BR /&gt;&lt;BR /&gt;Still the messages are the same.</description>
      <pubDate>Thu, 01 May 2003 13:09:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952883#M17306</guid>
      <dc:creator>Roland Heeling</dc:creator>
      <dc:date>2003-05-01T13:09:24Z</dc:date>
    </item>
    <item>
      <title>Re: Network problem Proliant 1600</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952884#M17307</link>
      <description>Roland,&lt;BR /&gt;&lt;BR /&gt;You say the NIC is set to AUTO. Is the switch also set to auto? If not, you may still have a Duplex mismatch which would result in intermittent connectivity problems.&lt;BR /&gt;&lt;BR /&gt;Good Luck,&lt;BR /&gt;Greg</description>
      <pubDate>Thu, 01 May 2003 14:12:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952884#M17307</guid>
      <dc:creator>Gregory Lee_1</dc:creator>
      <dc:date>2003-05-01T14:12:55Z</dc:date>
    </item>
    <item>
      <title>Re: Network problem Proliant 1600</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952885#M17308</link>
      <description>It looks like a false message from Insight Manager.  You may need to upgrade to a newer version</description>
      <pubDate>Fri, 02 May 2003 03:17:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/network-problem-proliant-1600/m-p/2952885#M17308</guid>
      <dc:creator>Frank Kaufman</dc:creator>
      <dc:date>2003-05-02T03:17:44Z</dc:date>
    </item>
  </channel>
</rss>

