Why can't I login from a PowerTerm session ....

[ChaimBu]

When I attempt to login from a specific user via my PowerTerm session to a "local" system, the login is refused. The LOGIN.COM for this account does have a restriction for NETWORK (if f$mode etc etc). However, if I issue a set host to a remote system, I am able to login! The LOGIN.COM files are IDENTICAL (I checked this. If I telnet directly from my PowerTerm to the same remote system I can also login.

What I do notice is that from my PowerTerm to my "local" system, my terminal type is a TN device. When I set host to the remote system I am a RT device.

Can someone explain to me the difference?

Thanks,

Chaim

[Jan van den Ende]

Chaim,

too many possibilities as it stands.

Obiously you can login to the system.
I hope you do have access to a privileged account.
In that, enable OPER SYSPRV and SECURITY priv, and REPLY/ENABLE.

Now, try the powerterm login.
In your privd session, you will get lots of info, most probably exactly saying what is wrong.
Usually that will also make clear how to correct things.

If there is just too much output from REPLY, you can also SET HOST/LOG into that session, and later on, you can view (and review) the replies at ease.

hth,

Proost.

Have one on me.

jpe

[Steven Schweda]

> Can someone explain to me the difference?

TN <-> Telnet (and relatives like rlogin/rsh)
RT <-> DECnet

What are you calling "local" and "remote"?
Which system is which?

[ChaimBu]

Thanks for the replies.

By the LOCAL SYSTEM I mean the system which is in the computer room here and connected to the LAN here at the computer center.

By a REMOTE SYSTEM I mean a system which is part of the WAN in a different physical location from the computer center.

Thanks,

Chaim

[Jan van den Ende]

Chaim,

(by definition) the Local Node is the node on which the process under consideration is active, the Remote Node has 2 meanings: in this case, it is the system from which a session is started on the Local Node. The second meaning is when you are performing activity on another system using network connectivity. The system that is involved in that activity is the Remote Node.

This means, that the meanings are RELATIVE to the process under investigaton.
eg, you SET HOST to "a" remote node. After logging in, you have two processes. For the second process, tha node that has beeb set host to, is the Local node, and the originating node is Remote.
From this it follows ( eg, by SET HOST 0, telnet localhost, or DIR 0:: ) that one and the same node can have both functions.

Just try to think purely egocentric, from the processes' perspective.

hth

Proost.

Have one on me.

jpe

[Volker Halle]

Chaim,

it may be helpful, if you provide the exact sequence of login attempts and the error message you're seeing.

PC - PowerTerm - TELNET to nodea - enter username and password - any error message ?

You say: 'LOGIN.COM for this account does have a restriction for NETWORK' - does this mean the LOGIN.COM has some checks for F$MODE() .EQS. "NETWORK" ? Note that if you login to any node (via DECnet or TELNET or any other network protocol) after answering the username and password prompts, this session's mode is always "INTERACTIVE".

Volker.

[Jiri_5]

have user enable local on sysuaf?

Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
Primary 000000000011111111112222 Secondary 000000000011111111112222
Day Hours 012345678901234567890123 Day Hours 012345678901234567890123
Network: ##### Full access ###### ##### Full access ######
Batch: ##### Full access ###### ##### Full access ######
Local: ##### Full access ###### ##### Full access ######
Dialup: ----- No access ------ ----- No access ------
Remote: ##### Full access ###### ##### Full access ######
Expiration: (none) Pwdminimum: 9 Login Fails: 0

[John Gillings]

Chaim,

> the login is refused

Not a very specific problem description!

Please post a transcript of the exact sequence you're attempting and the exact error message (always a good idea when reporting a problem :-)

If you can access the system some other way, I'd also like to see the audit alarm for the failed login:

$ REPLY/ENABLE=SECURITY
$ SET AUDIT/ALARM/ENABLE=LOGFAIL=ALL

now reattempt your login, capture the audit message and post it here.

If you believe you're getting as far as LOGIN.COM, then try:

$ SET AUDIT/ALARM/ENABLE=LOGIN=ALL

and compare the login audit messages for differences between your working and non-working logins. I'd expect both SET HOST and TELNET to be "Remote interactive login"

I don't think NETWORK mode is relevant, as they're interactive processes, but adding a line:

$ WRITE SYS$OUTPUT "Mode is ''F$MODE()'"

at the top of LOGIN.COM will tell you for certain.

[ChaimBu]

Thanks for the replies !!!

Unfortunately, I don't have enough priveleges to do most of the types of suggestions that you have mentined. However, I believe that I now have enough information to go to the system manager and together to figure out why I am unable to login to these particular nodes from PowerTerm.

I will post the results as soon as I have something.

Good day to ALL !!!

Chaim