<?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: WIN_TCP in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067979#M46012</link>
    <description />
    <pubDate>Wed, 15 May 2013 05:13:33 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2013-05-15T05:13:33Z</dc:date>
    <item>
      <title>WIN_TCP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067759#M46007</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to change the IP address etc on a system running VMS5.5-2 and WIN_TCP&lt;/P&gt;&lt;P&gt;from Wollongong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone help me with this ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have searched the web for WIN_TCP manuals and&amp;nbsp;&amp;nbsp;have had no luck.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;JohnW.&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2013 23:41:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067759#M46007</guid>
      <dc:creator>John Welsh_2</dc:creator>
      <dc:date>2013-05-14T23:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: WIN_TCP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067901#M46008</link>
      <description>&lt;P&gt;John,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Wow, a VAX? What fun!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Generally speaking, there's usually no way to "change" an IP address. It's better to&amp;nbsp;think of&amp;nbsp;it as a new installation. So, shutdown all your IP services and the IP stack itself and then (re)configure from scratch using the new address.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not sure why you say "running system". Does that mean you or the customer expects to be able to do this with no interruption? Purely local processes may be OK, but anything that uses the network must, by definition, be interrupted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Oh, something which MIGHT be possible. Perhaps you can define the new address as a secondary? That may achieve the same objectives, possibly with less disruption.&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2013 03:06:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067901#M46008</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2013-05-15T03:06:39Z</dc:date>
    </item>
    <item>
      <title>Re: WIN_TCP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067953#M46009</link>
      <description />
      <pubDate>Wed, 15 May 2013 04:10:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067953#M46009</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2013-05-15T04:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: WIN_TCP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067955#M46010</link>
      <description>&lt;P&gt;Thanks John.&amp;nbsp;&amp;nbsp;&amp;nbsp;I didn't expect to reconfigure tcpip without shuting down the system.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes I still&amp;nbsp; work with VAX VMS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It looks like I will have to go through a few iterations of installing WIN_TCP on my test&lt;/P&gt;&lt;P&gt;box to get familiar with it before reconfiguring the live system.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your help.&amp;nbsp;&amp;nbsp;&amp;nbsp; Regards,&amp;nbsp; John W.&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2013 04:15:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067955#M46010</guid>
      <dc:creator>John Welsh_2</dc:creator>
      <dc:date>2013-05-15T04:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: WIN_TCP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067967#M46011</link>
      <description>&lt;P&gt;Thanks Steven,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have done some digging based on your advice and have succeeded in changing the&lt;/P&gt;&lt;P&gt;IP address and am&amp;nbsp;now able &amp;nbsp;to ping and telnet into the system.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The version running is WIN_TCP052.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As suggested I edited [WIN_TCP052.NETDIST.MISC]STARTINET.COM and found the current IP&lt;/P&gt;&lt;P&gt;address which was associated with interface "ep0".&amp;nbsp; This is VAX device&amp;nbsp; "eza0".&amp;nbsp; Changed the address&lt;/P&gt;&lt;P&gt;and also the Nameserver address in the same file and bounced the system.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It then came up and worked with the new address.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2013 04:43:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067967#M46011</guid>
      <dc:creator>John Welsh_2</dc:creator>
      <dc:date>2013-05-15T04:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: WIN_TCP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067979#M46012</link>
      <description />
      <pubDate>Wed, 15 May 2013 05:13:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067979#M46012</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2013-05-15T05:13:33Z</dc:date>
    </item>
    <item>
      <title>Re: WIN_TCP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067987#M46013</link>
      <description>&lt;P&gt;Hi&amp;nbsp; Steven, yes its fairly old.&amp;nbsp; The system disk still is labeled VAXVMS53&amp;nbsp; so it must have&lt;/P&gt;&lt;P&gt;been at least upgraded from that version.&amp;nbsp; And I found some files where the history comments&lt;/P&gt;&lt;P&gt;were dated 1988 !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I run WINTCP_VERSION.exe&amp;nbsp;&amp;nbsp; I&amp;nbsp; get&amp;nbsp; "WINTCP V5.2F-000&amp;nbsp; ( STANDARD kernel )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&amp;nbsp; JohnW.&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2013 05:27:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6067987#M46013</guid>
      <dc:creator>John Welsh_2</dc:creator>
      <dc:date>2013-05-15T05:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: WIN_TCP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6068567#M46014</link>
      <description />
      <pubDate>Wed, 15 May 2013 13:35:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6068567#M46014</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2013-05-15T13:35:08Z</dc:date>
    </item>
    <item>
      <title>Re: WIN_TCP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6069195#M46015</link>
      <description>&lt;P&gt;Thanks Steven and John.&amp;nbsp;&amp;nbsp; I appreciate you taking the trouble to reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On to the next challenge&amp;nbsp; !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;JohnW.&lt;/P&gt;&lt;P&gt;=====&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2013 23:26:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/win-tcp/m-p/6069195#M46015</guid>
      <dc:creator>John Welsh_2</dc:creator>
      <dc:date>2013-05-15T23:26:08Z</dc:date>
    </item>
  </channel>
</rss>

