DECnet V over TCP/IP

[Oleg I. Kovalev]

Hi all!
I installed DECnet Plus on my OpenVMS v7.3-2 server. On server I configured DECnet run over TCP/IP. Also I installed DECnet over TCP/IP (DECITOT) protocol on Windows XP computer from CD PATHWORKS v7.3. There is mapping record in the DECITOT.dat file for OpenVMS server.
I have no problem when I connect to a server from this WinXP computer through the PowerTerm to the DECnet address .
But when I run on a WinXP computer a command
NCP LOOP NODE
I receive the following message
Error on connect to remote server: Connect failed, Connection rejected by object
Where is problem?

[Michael Yu_3]

Hi,

The reason for the failure was "connection rejected by object". This normally means the connect request did reach the destination object on the destination node, but was rejected because of access control.

On the OpenVMS server, please check the following.

ncl> show session control application mirror all

Then see if the attribute called "user name" has a valid username assigned.

Thanks and regards.

Michael

[Oleg I. Kovalev]

Hi,
I executed
ncl> show session control application mirror all
The following output was received:

Node 0 Session Control Application MIRROR
at 2005-10-25-06:59:40.627+00:00Iinf

Identifiers

Name = MIRROR

Status

Process Identifiers =
{
}
UID = 68CAE300-4523-11DA-844F-AA0004001108

Characteristics

Client =
Addresses =
{
number = 25
}
Outgoing Proxy = False
Incoming Proxy = False
Outgoing Alias = False
Incoming Alias = True
Node Synonym = True
Image Name = SYS$SYSTEM:NET$MIRROR.EXE
User Name = "MIRRO$SERVER"
Incoming OSI TSEL =
OutgoingAlias Name =
Network Priority = 0

Counters

Creation Time = 2005-10-25-06:48:54.515+00:00Iinf

[Ian Miller. · Accepted solution]

I think you need to specfiy a username and password when connecting to mirror
LOOP NODE nodename USERNAME user PASSWORD pass

[Karl Rohwedder]

In your output you see 'incoming proxy' and 'outgoing proxy' set to FALSE, so you have
to specify username/password.

regards Kalle

[Volker Halle]

Oleg,

there is no problem with user identification on the remote node, otherwise you should get the following error message:

%NCP-W-MIRCTF, Mirror connect failed , Access control rejected

Can NCP do DECnet-over-IP commands, as it is a DECnet Phase IV tool ??

On your OpenVMS V7.3-2 DECnet-Plus system, can you do a local application loopback:

$ MC NCL loop loopback application name xxx

Try xxx = local:.
or xxx = DOMAIN:localhost

Look in the default directory of your account MIRRO$SERVER for any error messages in NET$SERVER.LOG

In addition, you could also try to audit DECnet-connections with SET AUDIT/ALARM/ENA=CONNECTION and REPLY/ENABLE

Volker.

[Stanley F Quayle]

You have to configure the PWIP driver in TCP/IP. It's under "Optional Components" off of TCPIP$CONFIG.

[Michael Yu_3]

Hi,

You have to check, using authorize, and see if the user called "MIRRO$SERVER" is there. If it is there, the loopback will use this user on the OpenVMS server and run the image net$mirror.exe.

Since the loopback was rejected by the object (according to your original descritopn), it must have reached the destination. Hence DECnet over IP should be working.

Other than the access control rejection, the other thing I could think of is to check if the IP address of your Windows system can be resolved to a name on the OpenVMS system. See if tcpip show host ip-address of Windows can give you a name. Or perhaps a CDI trace will on the OpenVMS server will gives more information.

Turning on the opcom messages will also give you some hints. Reply/enable.

Hope the above helps.

Thanks and regards.

Michael

[Oleg I. Kovalev]

Hi all!
I have success after execution on remote WinXP computer.
LOOP NODE nodename USER username PASSWORD pass.

UAF have "MIRRO$SERVER" user record.
On my OpenVMS V7.3-2 DECnet-Plus system, I ran a local application loopback:

$ MC NCL loop loopback application name local:.ds20

After this, I looked [SYS0.MIRRO$SERVER]NET$SERVER.LOG.

--------------------------------------------------------

Connect request received at 26-OCT-2005 17:19:43.25
from remote process DS20::"0=SYSTEM"
for object "SYS$COMMON:[SYSEXE]NET$MIRROR.EXE"

--------------------------------------------------------

%CML-E-EMAAPROB, error returned from VMS EMA agent
MIRRO$SERVER job terminated at 26-OCT-2005 17:19:43.26
Accounting information:
Buffered I/O count: 62 Peak working set size: 2128
Direct I/O count: 42 Peak virtual size: 171664
Page faults: 297 Mounted volumes: 0
Charged CPU time: 0 00:00:00.05 Elapsed time: 0 00:00:00.12
[End of file]