-SYSTEM-F-INVLOGIN, login information invalid at remote node

[John Abbott_2]

I think the output reveals your problem, on one node name you're looking local: then domain: the other node it's domain: then local:

I'd suggest setting both systems to the same as the first output (IT4108).

You'll find the script files in sys$startup called NET$SEARCHPATH_STARTUP.NCL

Hope this helps
Kind Regards
John.

[Daniel Fernandez Illan]

Rajeev

Are you defined IP$10.54.09.56 or IT4108 node on DECnet local database ( using decnet_register)?.
I think that this node is not defined on DECnet
because the message of ACL violation on BGTA02 node does not indicate the name of remote node (IT4108).

Saludos.
Daniel.

[Rajeev Hejib]

I have change .ncl on BGTA02 to be same sa IT4108
BGTA02> mc ncl sho sess con nam search path

Node 0 Session Control
at 2006-01-16-15:43:32.605+00:00Iinf

Characteristics

Naming Search Path =
{
[
Directory Service = Local ,
Template = "*"
] ,
[
Directory Service = Local ,
Template = "local:*"
] ,
[
Directory Service = Local ,
Template = "LOCAL:.*"
] ,
[
Directory Service = Domain ,
Template = "*"
] ,
[
Directory Service = Domain ,
Template = "*.UK.CENTRICAPLC.COM"
]
}

BGTA02>

IT4108> mc ncl sho sess con nam search path

Node 0 Session Control
at 2006-01-16-15:41:59.509+00:00Iinf

Characteristics

Naming Search Path =
{
[
Directory Service = Local ,
Template = "*"
] ,
[
Directory Service = Local ,
Template = "local:*"
] ,
[
Directory Service = Local ,
Template = "LOCAL:.*"
] ,
[
Directory Service = Domain ,
Template = "*"
] ,
[
Directory Service = Domain ,
Template = "*.UK.CENTRICAPLC.COM"
]
}

IT4108>

IT4108 is registered on DECNET using mc decnet_register as IT4108.

One thing I noticed after I changed NET$SEARCHPATH_STARTUP.NCL (I ran it mc ncl @NET$SEARCHPATH_STARTUP.NCL, then flushed the cache)

BGTA02> uaf show/proxy it4108::*
%SECSRV-E-NOSUCHPROXY, no proxy record matches your specification

BGTA02> uaf show/proxy ip$10.54.9.56::system

Default proxies are flagged with (D)

IT4108::SYSTEM
SYSTEM (D)
BGTA02> uaf remove/proxy ip$10.54.9.56::system
%UAF-E-NAFREMERR, error removing proxy from IT4108::SYSTEM to *
-SECSRV-E-NOSUCHPROXY, no proxy record matches your specification

BGTA02> uaf remove/proxy it4108::system
%UAF-E-NAFREMERR, error removing proxy from LOCAL:.IT4108::SYSTEM to *
-SECSRV-E-NOSUCHPROXY, no proxy record matches your specification
BGTA02>

[John Abbott_2]

OK, you're nearly there, the change to the .NCL script was good but you missed out the "Directory Service = Domain ,
Template = "*.trading.centrica.com"
] ,
".. bit. As this is where your IT4108 name exists in DNS. So, If you add this back in on both the .ncl scripts (look at your orig post for placement), execute & flush.. fingers crossed you're been looking good :-)

Best
John.

[Rajeev Hejib]

Thanks verymuch John.

I have made the changes. They are as below:

IT4108> mc ncl sho sess con nam search path

Node 0 Session Control
at 2006-01-17-13:41:58.280+00:00Iinf

Characteristics

Naming Search Path =
{
[
Directory Service = Local ,
Template = "*"
] ,
[
Directory Service = Local ,
Template = "local:*"
] ,
[
Directory Service = Local ,
Template = "LOCAL:.*"
] ,
[
Directory Service = Domain ,
Template = "*"
] ,
[
Directory Service = Domain ,
Template = "*.UK.CENTRICAPLC.COM"
] ,
[
Directory Service = Domain ,
Template = "*.TRADING.CENTRICA.COM"
]
}

IT4108>

BGTA02> mc ncl sho sess con nam search path

Node 0 Session Control
at 2006-01-17-13:44:30.057+00:00Iinf

Characteristics

Naming Search Path =
{
[
Directory Service = Local ,
Template = "*"
] ,
[
Directory Service = Local ,
Template = "local:*"
] ,
[
Directory Service = Local ,
Template = "LOCAL:.*"
] ,
[
Directory Service = Domain ,
Template = "*"
] ,
[
Directory Service = Domain ,
Template = "*.UK.CENTRICAPLC.COM"
] ,
[
Directory Service = Domain ,
Template = "*.TRADING.CENTRICA.COM"
]
}

BGTA02>

The weired thing now is

When I do
IT4108> dir bgta02::
%DIRECT-E-OPENIN, error opening BGTA02::*.*;* as input
-RMS-E-FND, ACP file or directory lookup failed
-SYSTEM-F-INVLOGIN, login information invalid at remote node
IT4108>

But when I do

IT4108> dir 10.8.4.23::

It works.

Here is how "name service" is set up on UCX
On it4108

IT4108> ucx show name

BIND Resolver Parameters

Local domain: uk.centricaplc.com

System

State: Started, Enabled

Transport: UDP
Domain: UK.CENTRICAPLC.COM
Retry: 4
Timeout: 4
Servers: MPCDNS1, JGCDNS1
Path: No values defined

Process

State: Enabled

Transport:
Domain:
Retry:
Timeout:
Servers:
Path:
IT4108>

BGTA02> ucx show name

BIND Resolver Parameters

Local domain: trading.centrica.com

System

State: Started, Enabled

Transport: UDP
Domain: uk.centricaplc.com
Retry: 4
Timeout: 4
Servers: JGCDNS1, MPCDNS1
Path: No values defined

Process

State: Enabled

Transport:
Domain:
Retry:
Timeout:
Servers:
Path:
BGTA02>

If you notice the local domain on IT4108 is uk.centricaplc.com and on BGTA02 its trading.centrica.com. Is that making the difference

[Rajeev Hejib]

Sorry about the earlier reply. The search paths are actually as below. Rest still stays as in earlier note.
IT4108> mc ncl sho sess con nam search path

Node 0 Session Control
at 2006-01-17-13:49:48.189+00:00Iinf

Characteristics

Naming Search Path =
{
[
Directory Service = Local ,
Template = "*"
] ,
[
Directory Service = Local ,
Template = "local:*"
] ,
[
Directory Service = Local ,
Template = "LOCAL:.*"
] ,
[
Directory Service = Domain ,
Template = "*"
] ,
[
Directory Service = Domain ,
Template = "*.UK.CENTRICAPLC.COM"
] ,
[
Directory Service = Domain ,
Template = "*.TRADING.CENTRICA.COM"
]
}

IT4108>


BGTA02> mc ncl sho sess con nam search path

Node 0 Session Control
at 2006-01-17-13:52:00.469+00:00Iinf

Characteristics

Naming Search Path =
{
[
Directory Service = Local ,
Template = "*"
] ,
[
Directory Service = Local ,
Template = "local:*"
] ,
[
Directory Service = Local ,
Template = "LOCAL:.*"
] ,
[
Directory Service = Domain ,
Template = "*"
] ,
[
Directory Service = Domain ,
Template = "*.UK.CENTRICAPLC.COM"
] ,
[
Directory Service = Domain ,
Template = "*.TRADING.CENTRICA.COM"
]
}

BGTA02>

[John Abbott_2]

Right then, so IT4108 is in domain uk.centricaplc.com BGTA02 is in domain trading.centrica.com. So we've promoted the LOCAL search path up the list on one node (add some consistency between the systems), so they're both the same.

what does a tcpip/ucx sho host it4108 & BGTA02 on both systems give ?

Also, what in the local: osi db (mcr decnet_register, option 1, for the two nodes)

[Rajeev Hejib]

On IT4108
IT4108> ucx show host it4108

LOCAL database

Host address Host name

10.54.9.56 IT4108
IT4108> ucx show host bgta02

LOCAL database

Host address Host name

10.8.4.23 BGTA02, bgta02

The with mc decnet_register

Directory Service: Local name file

Node name: LOCAL:.it4108
Phase IV synonym: IT4108

Address tower protocol and selector values:
Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_NSP (NSP)
(no selector value)
Routing: DNA_OSInetwork (CLNS)
49::00-30:AA-00-04-00-0C-C0:20 (48.12)

Session: DNA_SessionControlV3 (SC3)
00 13
Transport: DNA_OSItransportV1 (TP4)
DE C0
Routing: DNA_OSInetwork (CLNS)
49::00-30:AA-00-04-00-0C-C0:21 (48.12)


Number of nodes reported on: 1


* Press Return to continue

Directory Service: Local name file

Node name: LOCAL:.bgta02
Phase IV synonym: BGTA02

Address tower protocol and selector values:
Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_NSP (NSP)
(no selector value)
Routing: DNA_OSInetwork (CLNS)
49::00-27:AA-00-04-00-47-9C:20 (39.71)


Number of nodes reported on: 1


* Press Return to continue



On BGTA02


BGTA02> ucx show host it4108

LOCAL database

Host address Host name

10.54.9.56 IT4108, it4108
BGTA02> ucx show host bgta02

LOCAL database

Host address Host name

10.8.4.23 bgta02, BGTA02, BGTA02,pgswh1
BGTA02>

and mc decnet_register

Directory Service: Local name file

Node name: LOCAL:.BGTA02
Phase IV synonym: BGTA02

Address tower protocol and selector values:
Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_NSP (NSP)
(no selector value)
Routing: DNA_OSInetwork (CLNS)
49::00-27:AA-00-04-00-47-9C:20 (39.71)


Number of nodes reported on: 1

Directory Service: Local name file

Node name: LOCAL:.it4108
Phase IV synonym: IT4108

Address tower protocol and selector values:
Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_NSP (NSP)
(no selector value)
Routing: DNA_OSInetwork (CLNS)
49::00-30:AA-00-04-00-0C-C0:20 (48.12)


Number of nodes reported on: 1

[John Abbott_2]

Morning, sorry I couldn't post earlier...

Are you intending to just running DECnetOSI over IP ?

Something worth checking... for the node names in DNS and in decnet_register, check you're using a zero and not an 'O' by mistake. Also, on BGTA02 in DNS you have BGTA02 listed three times ? Could there be some sort of hidden binary character in the dns entry here as two entries appear the same ?

On IT4108 decnet_register you have NSP(phase IV) and TP4(phase V) towers set-up, but on BGTA02 you only have only NSP. Although I doubt if this is causing the problem, you might see some delay on connection if TP4 is selected on IT4108 1st (I think it depends on order). Best to either using only NSP or TP4 or just set them both up. I actually thought you needed TP4 towers set-up to run DECnet over IP.

I would have thought you only need to set-up a UAF proxy record specifying the node name, not the IPC$ ip addr::system. ?

Hope this helps
Kind Regards,
John.

[John Abbott_2]

Thinking about this a bit more, without the TP4(phase v & over ip) entry on BGTA02, I think you're going to get a security alarm of IP$10.54.09.56 (as pre your post) rather than IT4108. Use mcr decnet_register on BGTA02, , option 2 and modify the tower to include a TP4 transport entry.

PS. Don't be shy, you can aware points ay anytime !