Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

[Personal Alpha] No IP access to Host but ping (again)

 
SOLVED
Go to solution

[Personal Alpha] No IP access to Host but ping (again)

Hello All,

As most of you know, I successfully installed PA on my PC last month. Everything is fine, X-Windows, FTP, Telnet, everything.

I installed it on a brand new PC, same SW config (XPP SP3), same network params, etc.

I did a new PA installation on this system, then copied my virtual disks from one of the previous PCs, then deleted all my tcp*.dat conf files, then reconfigured DEcnet and TCP/IP. Node is now DTL03::

Now, I can do everything I need between the two first hosts and the three VMS systems all together. One thing does not want to work fine is any relation between the new host and DTL03::

I can ping from this PC to VMS and vice versa, but Telnet or FTP both timeout with a "remote connection closed by host" or "forced exit".

No VMS messages with reply/enable.

I double checked all the ICMP, Firewall and other params, I found nothing different but two items:

First difference is "node type : unknown" on the new PC with ipconfig/all, "broadcast" on the two others (I don't know what it means and how to change this)

Second is, the new PC had a "Tuxedo tunelling" feature that I disabled "to see". No changes.

Any clues, please ?
Merci beaucoup.
34 REPLIES 34
Hoff
Honored Contributor
Solution

Re: [Personal Alpha] No IP access to Host but ping (again)

Cross-references and URLs:

http://groups.google.com/group/comp.os.vms/browse_thread/thread/ade750b8f68bc06c#

http://forum.stromasys.com/userforum/

As for your question here...

Do you have the telnet server configured?

Do you have the telnet client configured?

What IP stack are you using? Version?

Does ping to the address work?

Does the remote host show matching traffic in its accounting and auditing and server logs, when you're encountering a failure?

Are you patched to current?

And as for changing host names, that task can be vastly more involved than a couple of files:

http://labs.hoffmanlabs.com/node/589

Re: [Personal Alpha] No IP access to Host but ping (again)

> Do you have the telnet server configured?
yes and works fine from other systems

>Do you have the telnet client configured?
yes and works fine too

>What IP stack are you using? Version?
the genuine one on the PC (HP xw4600), IP V4.

Does ping to the address work?
yes it does

Does the remote host show matching traffic in its accounting and auditing and server logs, when you're encountering a failure?
No.

Are you patched to current?
not understood.

D.
Hoff
Honored Contributor

Re: [Personal Alpha] No IP access to Host but ping (again)

Please contact Stromasys for assistance with this "hardware issue"; with what looks to be problems with documentation or with the emulation, or with the "hardware network" here.

As for "patch to current", that was intended to indicate you should apply the current ECO kits for whatever version of OpenVMS and whatever version of TCP/IP Services is in use here. That's probably not an issue here, but that (and identifying the configuration and the versions) are part of chasing down a problem.
Bill Pedersen
Regular Advisor

Re: [Personal Alpha] No IP access to Host but ping (again)

Didier:

You should have a new IP stack from Stromasys which should be installed on your new PC. It should have a new NDIS network driver. This driver needs to be enabled on the NIC you want to use and in the PA configuration panel you have the ability to set this as either SHARED or DEDICATED (or some similar term).

The Newest version is 2.0.17 of the PA.

Down loaded it today and it came up without issue.

Bill.
Bill Pedersen
CCSS - Computer Consulting System Services, LLC

Re: [Personal Alpha] No IP access to Host but ping (again)

@ Hoff: I will

@ Bill : I do have the Alpha Emulator NDIS 5 driver installed, which works fine as I said. I can do everything I wish from VMS including relationship with my other PA and its host.
To me the problem is in the PC configuration, as I'm using the same sw (PA) and the same VMS (copy of my system disk)