-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-14-2013 04:41 PM
05-14-2013 04:41 PM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-14-2013 08:06 PM
05-14-2013 08:06 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-14-2013 09:10 PM
05-14-2013 09:10 PM
Re: WIN_TCP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-14-2013 09:15 PM
05-14-2013 09:15 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-14-2013 09:43 PM
05-14-2013 09:43 PM
SolutionThanks 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-14-2013 10:13 PM
05-14-2013 10:13 PM
Re: WIN_TCP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-14-2013 10:27 PM
05-14-2013 10:27 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-15-2013 06:35 AM
05-15-2013 06:35 AM
Re: WIN_TCP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-15-2013 04:26 PM
05-15-2013 04:26 PM
Re: WIN_TCP
Thanks Steven and John. I appreciate you taking the trouble to reply.
On to the next challenge !
JohnW.
=====
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP