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
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)
Jon Pinkley
Honored Contributor

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

Didier,

I am not sure I understand what is and is not working, because of the ambiguity of terms like "this".

Please use consistent names, for example:

XPPC1 running XPPro SP3 with (specify Ethernet interfaces)
PA1 Personal Alpha (version ?) on XPPC1
VMS1 VMS node running VMS (version with TCP version) on PA1

XPPC2 running XPPro SP3 with (specify Ethernet interfaces)
PA2 Personal Alpha (version ?) on XPPC2
VMS2 VMS node running VMS (version with TCP version) on PA2

AVMS VMS node running VMS (version with TCP version) on a real Alpha (model)

Then reword with the instances of XPPC, PA, VMS etc. stating what works and does not work.

Most likely it is something reasonably simple that is causing the problem, but without an accurate understanding of what works and does not work, troubleshooting is severely crippled. In fact, just by documenting things and writing them down for us, you may discover the problem. At least this has been my experience on many occasions; i.e. documenting something for a bug report and generating the log file of what does and does not work (with real captured output), has often led to me discovering something simple I had not considered, that was the cause of the problem.

Jon
it depends

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

Hi John

*you* solved my previous PA issue (no PING because ICMP was not activated), so I'll do my best for you to phrase correctly (please remember that English is not my mother tongue).

today, I have the following HW and SW config:

Network is behind an ADSL router.

o XPPC1 running XPPro SP3 with Intel Pro 100 VE Network connection Interface, address 192.168.1.20
o PA1 Personal Alpha version 2.0.16 on XPPC1
VMS1 VMS node running VMS 8.3 with TCP version V5-6.9 on PA1, address 192.168.1.101
o PA1 NDIS interface in share mode

o XPPC2 running XPPro SP3 with Ethernet interface BroadCom NeteXtreme Gigabit Interface, address 192.168.1.14
o PA2 Personal Alpha version 2.0.16 on XPPC2
VMS2 VMS node running VMS 8.3 with TCP version V5-6.9 on PA2, address 192.168.1.103
o PA2 NDIS interface in share mode

all four IP addresses are fixed ones.

What is fine today:

any connection between PC1 and PA1
any connection between PC1 and PC2
any connection between PC1 and PA2
any connection between PC1 and the Internet
any connection between PC2 and the Internet
any connection between PA1 and the Internet
any connection between PA2 and the Internet

What is to be solved:

no connection between PC2 and PA2 but ping in both sense.

Better John?
Thanks

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

Some more data:

PC1
C:\Documents and Settings\Didier Morandi>ipconfig/all

Configuration IP de Windows

Nom de l'hote . . . . . . . . . . : MAISON
Suffixe DNS principal . . . . . . :
Type de noeud . . . . . . . . . . : Diffusion
Routage IP active . . . . . . . . : Non
Proxy WINS active . . . . . . . . : Non

Carte Ethernet Connexion au reseau local:

Suffixe DNS propre a la connexion :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Adresse physique . . . . . . . . .: 00-13-D4-58-8F-46
DHCP active. . . . . . . . . . . : Non
Adresse IP. . . . . . . . . . . . : 192.168.1.20
Masque de sous-reseau . . . . . . : 255.255.255.0
Passerelle par defaut . . . . . . : 192.168.1.1
Serveurs DNS . . . . . . . . . . : 80.10.246.2
80.10.246.129

C:\Documents and Settings\Didier Morandi>

PC2
C:\Documents and Settings\Administrateur>ipconfig/all

Configuration IP de Windows

Nom de l'hote . . . . . . . . . . : PERMANENCEZERO
Suffixe DNS principal . . . . . . :
Type de noeud . . . . . . . . . . : Diffusion
Routage IP active . . . . . . . . : Non
Proxy WINS active . . . . . . . . : Non

Carte Ethernet Connexion au reseau local:

Suffixe DNS propre a la connexion :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Adresse physique . . . . . . . . .: 00-26-55-3E-20-27
DHCP active. . . . . . . . . . . : Non
Adresse IP. . . . . . . . . . . . : 192.168.1.14
Masque de sous-reseau . . . . . . : 255.255.255.0
Passerelle par defaut . . . . . . : 192.168.1.1
Serveurs DNS . . . . . . . . . . : 192.168.1.1
80.10.246.129

C:\Documents and Settings\Administrateur>
Jon Pinkley
Honored Contributor

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

Didier,

Thanks, now I think I understand what works and does not.

Just curious, why does PC2 have a different set of DNS servers? I don't think this is the cause of your problems, just curious if that was intentional.

PC1
Serveurs DNS . . . . . . . . . . : 80.10.246.2
80.10.246.129

PC2
Serveurs DNS . . . . . . . . . . : 192.168.1.1
80.10.246.129


When you telnet from VMS2 (on XPPC2) to VMS1 (on XPPC2), what ip address is displayed from VMS1$ show user/ful (user logged in from VMS2)

Also, can VMS2 telnet/ftp to itself? It should be able to.

Was the system disk for VMS2 (DTL03 if I understand correctly) the clone of VMS1's system disk "then copied my virtual disks from one of the previous PCs", with the TCP config redone?

Please capture the output of these VMS commands from the VMS2 (DTL03) node, and paste into notepad, save as DTL03.txt file and attach to your next note: (use the Browse button below the ITRC reply text box to select the DTL03.txt file and it will be sent when you press submit. At least that is what is supposed to happen.)

Oh, and to reduce stress, always copy the text you have in your reply to notepad before you press submit, since ITRC isn't the most reliable server, and you may need to resend it.

$ @sys$manager:tcpip$define_commands
$ ifconfig -a
$ netstat -rn
$ netstat -n
$ show net /ful
$ tcpip show services /ful
it depends

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

This is from the system which has the bug
=========================================
System> $ ifconfig -a
LO0: flags=100c89
inet 127.0.0.1 netmask ff000000 ipmtu 4096

SE0: flags=c43
*inet 192.168.1.103 netmask ffffff00 broadcast 192.168.1.255 ipmtu 1500

TN0: flags=80

TN1: flags=80

System> $ netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface

Route Tree for Protocol Family 26:

Route Tree for Protocol Family 2:
default 192.168.1.1 UGS 0 0 SE0
127.0.0.1 127.0.0.1 UHL 1 0 LO0
192.168.1/24 192.168.1.103 U 1 0 SE0
192.168.1.103 192.168.1.103 UHL 0 0 SE0
System> $ netstat -n
System> $ show net /ful

The following network services are available at this time:

Product: DECNET Manufacturer: Hewlett-Packard Company
Node: DTL03 Address(es): 1.103
Network Type: DNA IV Interface(s): net 0


Node Volatile Characteristics as of 6-DEC-2009 13:13:52

Executor node = 1.103 (DTL03)

Identification = HP DECnet for OpenVMS Alpha
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 60
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V4.1.0
Maximum links = 32
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = nonrouting IV
Routing timer = 600
Broadcast routing timer = 180
Maximum address = 1023
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 30
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Maximum buffers = 100
Buffer size = 576
Nonprivileged user id = DECNET
Nonprivileged password = CACTIMPHS
Default access = incoming and outgoing
Pipeline quota = 4032
Alias maximum links = 32
Path split policy = Normal
Maximum Declared Objects = 31




Known Link Volatile Summary as of 6-DEC-2009 13:13:52

No information in database



Node Counters as of 6-DEC-2009 13:13:52

Executor node = 1.103 (DTL03)

0 Maximum logical links active
0 Aged packet loss
0 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject



Product: TCP/IP Manufacturer: Hewlett-Packard Company
Node: dtl03.home Address(es): 192.168.1.103
Network Type: TCP/IP Interface(s):

HP TCP/IP Services for OpenVMS Alpha Version V5.6
on a DEC 3000 Model 400 running OpenVMS V8.3


Port Remote
Device_socket Type Local Remote Service Host

bg35 STREAM 21 0 FTP *
bg38 STREAM 23 0 TELNET *

Communication Parameters

Local host: dtl03 Domain: home

Maximum Current Peak
Proxies 20


Remote Terminal
Large buffers: 0
UCBs: 0
Virtual term: disabled

System> $ tcpip show services /full

Service: FTP
State: Enabled
Port: 21 Protocol: TCP Address: 0.0.0.0
Inactivity: 5 User_name: TCPIP$FTP Process: TCPIP$FTP
Limit: 1000 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$FTP_RUN.COM
Flags: None

Socket Opts: Rcheck Scheck
Receive: 0 Send: 0

Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
File: SYS$SYSDEVICE:[TCPIP$FTP]TCPIP$FTP_RUN.LOG

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

Service: TELNET
State: Enabled
Port: 23 Protocol: TCP Address: 0.0.0.0
Inactivity: 1 User_name: not defined Process: not defined
Limit: 10000 Active: 0 Peak: 0

File: not defined
Flags: Listen Rtty IPv6

Socket Opts: Keepalive Rcheck Scheck
Receive: 3000 Send: 3000

Log Opts: Actv Dactv Conn Error Logi Logo Mdfy Rjct
File: not defined

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0
System>

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

And this is from the system which works fine
============================================

DTL> $ ifconfig -a
LO0: flags=100c89
inet 127.0.0.1 netmask ff000000 ipmtu 4096

SE0: flags=c43
*inet 192.168.1.101 netmask ffffff00 broadcast 192.168.1.255 ipmtu 1500

TN0: flags=80

TN1: flags=80

DTL> $ netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface

Route Tree for Protocol Family 26:

Route Tree for Protocol Family 2:
default 192.168.1.1 UGS 0 1 SE0
127.0.0.1 127.0.0.1 UHL 7 44 LO0
192.168.1/24 192.168.1.101 U 2 202 SE0
192.168.1.101 192.168.1.101 UHL 0 0 SE0
DTL> $ netstat -n
Active Internet connections
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp 0 0 127.0.0.1.705 127.0.0.1.49152 ESTABLI
SHED
tcp 0 0 127.0.0.1.49152 127.0.0.1.705 ESTABLI
SHED
tcp 0 0 127.0.0.1.705 127.0.0.1.49153 ESTABLI
SHED
tcp 0 0 127.0.0.1.49153 127.0.0.1.705 ESTABLI
SHED
tcp 0 0 127.0.0.1.705 127.0.0.1.49154 ESTABLI
SHED
tcp 0 0 127.0.0.1.49154 127.0.0.1.705 ESTABLI
SHED
tcp 0 639 192.168.1.101.23 192.168.1.20.1579 ESTABLI
SHED
tcp 0 0 127.0.0.1.705 *.* LISTEN
udp 0 0 192.168.1.101.123 *.*
udp 0 0 127.0.0.1.123 *.*
udp 0 0 *.123 *.*
udp 0 0 *.161 *.*
DTL> $ show net /ful

The following network services are available at this time:

Product: DECNET Manufacturer: Hewlett-Packard Company
Node: DTL01 Address(es): 1.101
Network Type: DNA IV Interface(s): net 0


Node Volatile Characteristics as of 6-DEC-2009 11:50:27

Executor node = 1.101 (DTL01)

Identification = HP DECnet for OpenVMS Alpha
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 60
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V4.1.0
Maximum links = 32
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = nonrouting IV
Routing timer = 600
Broadcast routing timer = 180
Maximum address = 1023
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 30
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Maximum buffers = 100
Buffer size = 576
Nonprivileged user id = DECNET
Nonprivileged password = ADDALLYNIA
Default access = incoming and outgoing
Pipeline quota = 4032
Alias maximum links = 32
Path split policy = Normal
Maximum Declared Objects = 31




Known Link Volatile Summary as of 6-DEC-2009 11:50:27

No information in database



Node Counters as of 6-DEC-2009 11:50:27

Executor node = 1.101 (DTL01)

0 Maximum logical links active
0 Aged packet loss
0 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject



Product: TCP/IP Manufacturer: Hewlett-Packard Company
Node: dtl01.home Address(es): 192.168.1.101
Network Type: TCP/IP Interface(s):

HP TCP/IP Services for OpenVMS Alpha Version V5.6
on a DEC 3000 Model 400 running OpenVMS V8.3


Port Remote
Device_socket Type Local Remote Service Host

bg35 STREAM 21 0 FTP *
bg42 DGRAM 123 0 NTP *
bg43 DGRAM 123 0 NTP *
bg44 DGRAM 123 0 NTP *
bg50 DGRAM 0 0 *
bg55 STREAM 705 0 *
bg56 DGRAM 161 0 SNMP *
bg61 DGRAM 0 0 *
bg64 STREAM 49152 705 127.0.0.1
bg66 STREAM 49153 705 127.0.0.1
bg77 STREAM 49154 705 127.0.0.1
bg81 STREAM 705 49152 127.0.0.1
bg82 STREAM 705 49153 127.0.0.1
bg83 STREAM 705 49154 127.0.0.1
bg85 STREAM 23 0 TELNET *
bg87 STREAM 23 1579 TELNET 192.168.1.20

Communication Parameters

Local host: dtl01 Domain: home

Maximum Current Peak
Proxies 20


Remote Terminal
Large buffers: 0
UCBs: 0
Virtual term: disabled

DTL> $ tcpip show services /full

Service: ESNMP
State: Disabled
Port: 705 Protocol: UDP Address: 0.0.0.0
User_name: not defined Process: ESNMP

Service: FTP
State: Enabled
Port: 21 Protocol: TCP Address: 0.0.0.0
Inactivity: 5 User_name: TCPIP$FTP Process: TCPIP$FTP
Limit: 1000 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$FTP_RUN.COM
Flags: None

Socket Opts: Rcheck Scheck
Receive: 0 Send: 0

Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
File: SYS$SYSDEVICE:[TCPIP$FTP]TCPIP$FTP_RUN.LOG

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

Service: NTP
State: Enabled
Port: 123 Protocol: UDP Address: 0.0.0.0
Inactivity: 0 User_name: TCPIP$NTP Process: TCPIP$NTP
Limit: 1 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$NTP_RUN.COM
Flags: None

Socket Opts: Rcheck Scheck
Receive: 0 Send: 0

Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
File: SYS$SPECIFIC:[TCPIP$NTP]TCPIP$NTP_RUN.LOG

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

Service: SNMP
State: Enabled
Port: 161 Protocol: UDP Address: 0.0.0.0
Inactivity: 0 User_name: TCPIP$SNMP Process: TCPIP$SNMP
Limit: 1 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$SNMP_RUN.COM
Flags: None

Socket Opts: Rcheck Scheck
Receive: 0 Send: 0

Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
File: SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$SNMP_RUN.LOG

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

Service: TELNET
State: Enabled
Port: 23 Protocol: TCP Address: 0.0.0.0
Inactivity: 1 User_name: not defined Process: not defined
Limit: 10000 Active: 1 Peak: 1

File: not defined
Flags: Listen Rtty IPv6

Socket Opts: Keepalive Rcheck Scheck
Receive: 3000 Send: 3000

Log Opts: Actv Dactv Conn Error Logi Logo Mdfy Rjct
File: not defined

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0
DTL>

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

(sorry I missed the "attach request)

As for your questions, here are some answers:

Just curious, why does PC2 have a different set of DNS servers? I don't think this is the cause of your problems, just curious if that was intentional.

it's just an error. I built the new PC "by heart". 1.1. is the ADSL gateway and DHCP server (that I do not use).

> When you telnet from VMS2 (on XPPC2) to VMS1 (on XPPC1), what ip address is displayed from VMS1$ show user/ful (user logged in from VMS2)

DTL01>
%%%%%%%%%%% OPCOM 6-DEC-2009 12:05:41.38 %%%%%%%%%%%
Message from user INTERnet on DTL01
TELNET Login from Host: 192.168.1.103 Port: 49152

DTL01> sh use/nod/full
OpenVMS User Processes at 6-DEC-2009 12:06:13.90
Total number of users = 1, number of processes = 2

Username Process Name PID Terminal
DTL DTL 0000012C TNA2: (Host: 192.168.1.20 Port: 1579)
DTL _TNA3: 00000134 TNA3:
(Host: 192.168.1.103 Locn: _OPA0:/SYSTEM)
DTL01>
(the first user is logged in into VMS1 via Kea-VT from PC1)

> Also, can VMS2 telnet/ftp to itself? It should be able to.
Yes, it can and works fine.

Was the system disk for VMS2 (DTL03 if I understand correctly) the clone of VMS1's system disk "then copied my virtual disks from one of the previous PCs", with the TCP config redone?
yes it was.

Thanks all for your time!
Bill Pedersen
Regular Advisor

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

Didier:

You mention differences on the report from ipconfig/all between the two PCs but then do not provide the listing of the two reports. If the problem is in fact the PC config it would be helpful to see these reports.

Thanks,

Bill.
Bill Pedersen
CCSS - Computer Consulting System Services, LLC
Jon Pinkley
Honored Contributor

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

see note with timestamp

Dec 6, 2009 09:57:52 GMT

which has ipconfig/all output
it depends

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

@ Bill
They are (in French) in my post dated 09:57.
Jon Pinkley
Honored Contributor

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

From DTL03 (VMS2/PA2) you can telnet to DTL01 (VMS1/PA1) as shown by your Dec 6, 2009 12:37:53 GMT post.

From DTL01 can you telnet to DTL03? (I think you said no).

This seems to be a firewall issue, because you can establish connection from DTL03 to DTL01 (therefore two way connectivity), but something is blocking the establishment of connections coming the other way.

Let's look at the low level stuff.

You are running DECNET IV, therefore it is changing the MAC address (I would expect it to be aa-00-04-00-67-04 given DECnet address 1.103)

From PC2 ping 192.168.1.103 (you said this works). Then issue

> arp -a

what MAC address is associated with 192.168.1.103?

From DLT103

$ ping 192.168.1.14

$ tcpip show arp

Do you see MAC address 00-26-55-3E-20-27 associated with 192.168.1.14?

Just to make sure. Have you rebooted PERMANENCEZERO (PC2) after installing PA and configuring DTL03?

Does PERMANENCEZERO have any "internet security" software? Is there something other than just the firewall built into XP SP3 that may be interfering with inbound connections?

Can you remote make a remote desktop connection from PC1 to PC2?
it depends

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

> From DTL03 (VMS2/PA2) you can telnet to DTL01 (VMS1/PA1) as shown by your Dec 6, 2009 12:37:53 GMT post.

Yes I can

> From DTL01 can you telnet to DTL03?

Yes I can

> This seems to be a firewall issue, because you can establish connection from DTL03 to DTL01 (therefore two way connectivity), but something is blocking the establishment of connections coming the other way.

No. As I said, everything between the two Alpha is running fine.

> Let's look at the low level stuff.

let's do that.

> You are running DECNET IV, therefore it is changing the MAC address (I would expect it to be aa-00-04-00-67-04 given DECnet address 1.103) From PC2 ping 192.168.1.103 (you said this works). Then issue

> arp -a

> what MAC address is associated with 192.168.1.103?

C:\Documents and Settings\Administrateur>arp -a

Interface : 192.168.1.14 --- 0x10003
Adresse Internet Adresse physique Type
192.168.1.1 00-15-56-0a-3e-d1 dynamique
192.168.1.20 00-13-d4-58-8f-46 dynamique
192.168.1.103 aa-00-04-00-67-04 dynamique

C:\Documents and Settings\Administrateur>

> From DTL103

$ ping 192.168.1.14

$ tcpip show arp

Do you see MAC address 00-26-55-3E-20-27 associated with 192.168.1.14?

DTL03> tcpip
TCPIP> ping 192.168.1.14
PING 192.168.1.14 (192.168.1.14): 56 data bytes
64 bytes from 192.168.1.14: icmp_seq=0 ttl=128 time=6 ms
64 bytes from 192.168.1.14: icmp_seq=1 ttl=128 time=2 ms
64 bytes from 192.168.1.14: icmp_seq=2 ttl=128 time=1 ms
64 bytes from 192.168.1.14: icmp_seq=3 ttl=128 time=1 ms


----192.168.1.14 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 1/2/6 ms
TCPIP> sh arp
Cnt Flags Timer Host Phys Addr
1: UC 4 192.168.1.14 00-26-55-3e-20-27
2: UC 15 192.168.1.20 00-13-d4-58-8f-46

Yes I can.

> Just to make sure. Have you rebooted PERMANENCEZERO (PC2) after installing PA and configuring DTL03?

Yes I did.

Does PERMANENCEZERO have any "internet security" software? Is there something other than just the firewall built into XP SP3 that may be interfering with inbound connections?

No. The PC2 is a real mirror of PC1 but the network interface which is not the same. Maybe we should have a look at that card ?

Can you remote make a remote desktop connection from PC1 to PC2?

The remote terminal window pops up, then an error message sez that the target PC closed the connection.

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

remote access from PC1 to PC2 is now fine. I forgot to enable it on PC2. Sorry for that.
Jon Pinkley
Honored Contributor

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

What can you do from PC1 to VMS1 (DTL01) that you can not do from PC2 to VMS2 (DTL03)?

Examples: ftp, telnet

Please show log of failures.

What can you do from VMS1 (DTL01) to PC1 that you can't do from VMS2 (DTL03) to PC2?

It is harder for me to think of things you would do, unless you have some services running on the PC.

Please show log of failures.
it depends

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

Good morning Jon,

> What can you do from PC1 to VMS1 (DTL01) that you can not do from PC2 to VMS2 (DTL03)?

> What can you do from VMS1 (DTL01) to PC1 that you can't do from VMS2 (DTL03) to PC2?

I can do everything dealing with TCP/IP communications between PC1 and VMS1 in both directions

I can do everything dealing with TCP/IP communications between PC1 and VMS2 in both directions

I cannot do anything between PC2 and VMS2 but
ping.

After a telnet attempt from PC2 to VMS2, network logfile sez:
2009-12-07 11:49:51 OPEN TCP 192.168.1.14 192.168.1.103 1145 23 - - - - - - - - -
2009-12-07 11:50:57 CLOSE TCP 192.168.1.14 192.168.1.103 1144 23 - - - - - - - - -

nothing else.

I will save my system disk on PC2/VMS2, then reinstall PA, then create a new VMS system disk. I come back later.

The only difference between these two configurations is to me the network interface.

If the previous operation gives the same results, I will remove my Ethernet card from PC1 and plug it in PC2 and see.

Talk to you later.
Thanks.
Vadim Model
Occasional Visitor

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

I would try to disable TOE (TCP/IP Offload Engine) features on NetExtreme board, just in case ...
Gregory Reut
Occasional Visitor

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

Hi Didier,

Network adapter could be a root cause, we don't know exactly how its dirver handles the MAC address change (forced when DECNET comes up). Another possible reason is the network switch. Are both of your systems connected to the same switch, or to different ones?

Before switching network adapters I would try what Vadim recommended (TOE off). Than I would copy the PA disk image from PC1 (where everything works) to PC2 (where it does not work), configure Windows networking on PC2 exactly as on PC1, boot VMS, and check the communications between Windows and VMS. If it works, we prove the network adapter is innocent, if it does not, proved guilty, and you could proceed with a replacement.

By the way in production environments sharing of the network adapters is not supported.

Best regards,
Greg
Stromasys
Jon Pinkley
Honored Contributor

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

Didier,

I think Vadim Model may have found your problem. It is at lease worth a try before moving hardware. Create a system restore point before the change; it could make reversing easier.

It seems more likely that the adapter is the issue than the switch it is plugged into, because the other PC can communicate ok, all the way "into" the VMS instance running it the virtual alpha. So it isn't obvious to me how the switch could be the problem.

Ping may work due to the small default size and the fact that ICMP isn't a TCP protocol; it is an IP protocol. Perhaps that is why it is treated differently. It would be interesting to see if larger ICMP packets fail to traverse the PC2 VMS2 path, especially ones that are larger that the MTU and must be fragmented.

First verify that you can send a max sized ping from PC1 to VMS1

PC1 > ping -l 65500 192.168.1.101 ! that's a lowercase L for payload length (windows ping size is payload size, not packet size)

If that doesn't work, see what the largest size is (try -l 1400, -l 1472 (1472 is the largest packet that can be sent without fragmenting with an MTU of 1500, the packet will be 1500 length, 20 byte ip header 8 byte ICMP header 1472 bytes of payload), 1500, 32000, etc.) My guess is that 65500 will work.

Then try pinging from PC2 to VMS2 with the max size packet that worked above.

PC2 > ping -l 192.168.1.103

I won't be surprised if that fails, but it may work. If it doesn't work, it is more evidence that the adapter isn't as transparent as the one in PC1.

Here are some links I found with Google concerning TCP offload

Several recommendations for method 2 in following Microsoft knowledgebase article 948496.

http://support.microsoft.com/kb/948496

http://www.windowsreference.com/networking/enabledisable-tcp-task-offloading-to-nic-in-windows/

http://social.technet.microsoft.com/Forums/en/winserverPN/thread/a55b795c-d171-4ef8-8a85-ca685d9b536d

http://www.google.com/url?q=http://social.technet.microsoft.com/Forums/en/winserverPN/thread/814a4a85-3f36-4fe3-826f-fedf7fa23a44&ei=0IodS_n5OovClAfn0dHyCQ&sa=X&oi=forum_cluster&resnum=4&ct=result&cd=1&ved=0CBEQrAIoADAD&usg=AFQjCNEEBJ8ZJLkbnzM5U_iZMEo4Ze5ZgQ


The following was vmware related, but it was concerning bridged mode and TOE and Broadcom (and disabling TOE fixed problem)

http://communities.vmware.com/thread/191085;jsessionid=CE0A767EE03AFFD9070C95493741ECA0

Once you discover the cause, make sure to update this and the Stromasys forum.

Good luck,

Jon
it depends

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

Both tests on the two PCs give more or less same results. On PC2 I have:

Microsoft Windows XP [version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Didier Morandi>ping -l 65500 192.168.1.103

Envoi d'une requête 'ping' sur 192.168.1.103 avec 65500 octets de données :

Réponse de 192.168.1.103 : octets=65500 temps=97 ms TTL=64
Réponse de 192.168.1.103 : octets=65500 temps=115 ms TTL=64
Réponse de 192.168.1.103 : octets=65500 temps=116 ms TTL=64
Réponse de 192.168.1.103 : octets=65500 temps=110 ms TTL=64

Statistiques Ping pour 192.168.1.103:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 97ms, Maximum = 116ms, Moyenne = 109ms

C:\Documents and Settings\Didier Morandi>

I do not know where can TOE be turned off. I have a look and come back.