<?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: ISEE connectivity issue in Insight Remote Support</title>
    <link>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789621#M800</link>
    <description>&lt;BR /&gt;&lt;BR /&gt;Daniel,&lt;BR /&gt;&lt;BR /&gt;When installing/reinstalling ISEE, do you uninstall the old version first?  It has been my experience that the only way I can get some installs to function properly is to completely deinstall the older version with swremove first.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 18 May 2006 18:15:23 GMT</pubDate>
    <dc:creator>DCE</dc:creator>
    <dc:date>2006-05-18T18:15:23Z</dc:date>
    <item>
      <title>ISEE connectivity issue</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789617#M796</link>
      <description>I have problems trying to upgrade from ISEE from A.03.50.854 to A.03.95 on some servers.  Sometimes when I'm configuring it, the system handle and serial information is missing on the client so I have to add it manually following which ISEE works properly. But on some boxes when I open the ISEE web page to the client through port 5060 the system handle and serial information fields are missing from the configuration options template, so I am unable to add the information. As a result the spop server does not appear to accept any emails from the client or the client does not try to send an email I cannot see. &lt;BR /&gt;The previous installation of ISEE was working, we attempted to reinstall the original version but that also failed with the same problems.&lt;BR /&gt;There appears to be a correlation between the server having originally been built using ignite and getting this problem when we try to upgrade ISEE.</description>
      <pubDate>Wed, 17 May 2006 07:39:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789617#M796</guid>
      <dc:creator>Daniel Cooke</dc:creator>
      <dc:date>2006-05-17T07:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE connectivity issue</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789618#M797</link>
      <description>Daniel,&lt;BR /&gt;&lt;BR /&gt;Please keep this in mind " The Entitlement section is downloaded from the SPOP, if you do not see this section, this means you are not able to communicate with the SPOP". &lt;BR /&gt;&lt;BR /&gt;The mad.log should give you some indications of the problem when it tries to send the data to the SPOP.&lt;BR /&gt;&lt;BR /&gt;There are a few things you can check:&lt;BR /&gt;&lt;BR /&gt;1. If the Clients can resolve the SPOP's address.&lt;BR /&gt;2. Is there a firewall between the SPOP and Clients, then port 80 must be open.&lt;BR /&gt;3. Can the Clients do traceroute to the SPOP?&lt;BR /&gt;4. One more important thing is speed &amp;amp; duplex on the SPOP NIC card must be set to right the speed (i.e. 100 MB Full), do NOT set it as Auto.&lt;BR /&gt;&lt;BR /&gt;Let me know if anyone of those helps to solve your problem, please continue with 3.95.026 version.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;</description>
      <pubDate>Wed, 17 May 2006 09:37:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789618#M797</guid>
      <dc:creator>Liem Nguyen</dc:creator>
      <dc:date>2006-05-17T09:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE connectivity issue</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789619#M798</link>
      <description>Thanks for your reply. lots of things to go on there.&lt;BR /&gt;The server was already configured to use the old version of ISEE which worked fine. we tried the upgrade to the new version which wouldnt work so hp support recomended an swremove of the old version and an install of the new version. this had problems so we tried to put the old software back on and this is failing in the same way the new  version does.&lt;BR /&gt;there isnt any firewalls in the way and it is configured to see the spop and port 80 works as well. attached is the details from the mad.log&lt;BR /&gt;&lt;BR /&gt;thanks for you help on this</description>
      <pubDate>Wed, 17 May 2006 10:58:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789619#M798</guid>
      <dc:creator>Daniel Cooke</dc:creator>
      <dc:date>2006-05-17T10:58:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE connectivity issue</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789620#M799</link>
      <description>Daniel,&lt;BR /&gt;&lt;BR /&gt;The only useful info in mad.log is:&lt;BR /&gt;170506 12:50:26.567 ERROR,[Comm] NetworkException (10): Socket::write(): send() timeout [[ip address]]&lt;BR /&gt;&lt;BR /&gt;It's timing out during a connection to your SPOP. Please make sure to check the SPOP for Speed &amp;amp; Duplex as said above.&lt;BR /&gt;&lt;BR /&gt;Let me know if this works or not so I can provide futher info.&lt;BR /&gt;&lt;BR /&gt;Regards,</description>
      <pubDate>Thu, 18 May 2006 06:57:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789620#M799</guid>
      <dc:creator>Liem Nguyen</dc:creator>
      <dc:date>2006-05-18T06:57:15Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE connectivity issue</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789621#M800</link>
      <description>&lt;BR /&gt;&lt;BR /&gt;Daniel,&lt;BR /&gt;&lt;BR /&gt;When installing/reinstalling ISEE, do you uninstall the old version first?  It has been my experience that the only way I can get some installs to function properly is to completely deinstall the older version with swremove first.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 18 May 2006 18:15:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-connectivity-issue/m-p/3789621#M800</guid>
      <dc:creator>DCE</dc:creator>
      <dc:date>2006-05-18T18:15:23Z</dc:date>
    </item>
  </channel>
</rss>

