1748169 Members
4412 Online
108758 Solutions
New Discussion

Re: WIN_TCP

 
SOLVED
Go to solution
John Welsh_2
Regular Advisor

WIN_TCP

Hi all,

 

I need to change the IP address etc on a system running VMS5.5-2 and WIN_TCP

from Wollongong.

 

Can anyone help me with this ?

 

I have searched the web for WIN_TCP manuals and  have had no luck.

 

Thanks,

JohnW.

8 REPLIES 8
John Gillings
Honored Contributor

Re: WIN_TCP

John,

   Wow, a VAX? What fun!

 

  Generally speaking, there's usually no way to "change" an IP address. It's better to think of 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.

 

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.

 

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.

A crucible of informative mistakes
Steven Schweda
Honored Contributor

Re: WIN_TCP

 
John Welsh_2
Regular Advisor

Re: WIN_TCP

Thanks John.   I didn't expect to reconfigure tcpip without shuting down the system.

 

Yes I still  work with VAX VMS.

 

It looks like I will have to go through a few iterations of installing WIN_TCP on my test

box to get familiar with it before reconfiguring the live system. 

 

Thanks for your help.    Regards,  John W.

John Welsh_2
Regular Advisor
Solution

Re: WIN_TCP

Thanks Steven,

 

I have done some digging based on your advice and have succeeded in changing the

IP address and am now able  to ping and telnet into the system.

 

The version running is WIN_TCP052.

 

As suggested I edited [WIN_TCP052.NETDIST.MISC]STARTINET.COM and found the current IP

address which was associated with interface "ep0".  This is VAX device  "eza0".  Changed the address

and also the Nameserver address in the same file and bounced the system.

 

It then came up and worked with the new address.

 

Thanks for your help.

Steven Schweda
Honored Contributor

Re: WIN_TCP

 
John Welsh_2
Regular Advisor

Re: WIN_TCP

Hi  Steven, yes its fairly old.  The system disk still is labeled VAXVMS53  so it must have

been at least upgraded from that version.  And I found some files where the history comments

were dated 1988 !

 

If I run WINTCP_VERSION.exe   I  get  "WINTCP V5.2F-000  ( STANDARD kernel )

 

Regards,  JohnW.

Steven Schweda
Honored Contributor

Re: WIN_TCP

 
John Welsh_2
Regular Advisor

Re: WIN_TCP

Thanks Steven and John.   I appreciate you taking the trouble to reply.

 

On to the next challenge  !

 

JohnW.

=====