HP-UX 10.20 login problems

[Keith Takeda]

I have a HP 9000/J210, running 10.20. When trying to login as root or any other user, it accepts the login/password, the initial screen clears, and then hangs at the next screen where there is the small terminal window in the upper left section of the screen. It does not get past this point.
We've "accidentally" found that if we leave the PS2 mouse unplugged on bootup that the CDE graphic login does not appear but just a console login prompt.
At this prompt however, we are unable to login as root, but as secman, and then we have to su -root to login as root.

I've seen some posts about DNS name resolution. Could this be the case here? Where should I check?

Thanks!
cc

[AwadheshPandey]

see this link: http://www1.itrc.hp.com/service/james/search.do?todo=search&searchtext=dt+error&from=forums&submit.x=8&origin=0&wpa=forums1.itrc.hp.com%3A80&submit.y=8&searchcategory=ALL&hpl=1&searchcriteria=allwords&rn=25&source=7000&presort=rank&chkServStor=on&esc=us.support.itrc.hp.com&admit=-682735245+1145820528184+28353475
for issues.
check /.dt/*.log, if you find xdevice error pls put mouse at port then reboot the server. ur problem will be solved else post the error logs u will found in /.dt directory.

Cheers,
Awadhesh

[Alex Glennie]

Sounds bad .... ;-)

You can get a console login by disconnecting the mouse because the Xserver is failing to start and grab the console .... we need X running for CDE to start however.

Qus .... what changed ? Is this a trusted or NIS enviroment ?

As user secman login from the cli

more /.dt/startlog ?

tail /var/adm/syslog/syslog.log ?

run dr_dt > /tmp/dtlog ... examine.

perhaps try editing /etc/nnswitch.conf to use only file and move resolv.conf our of /etc for a test.

check hostname resolution and run a bdf ...
c

[Tom Henning]

If you are getting no messages to the screen at all, since this sounds a lot like what happens when you login with an expired, but not yet locked out, password. Or, come to think of it, safe mode in 10.20. I aggree with checking on the name resolution issue, as secman do a nslookup of the hostname of the system and a nslookup with the IP address of the system. They repsonses should match. If it is a trusted system try a getprpw (in /usrt/lbin I believe but an not certain with 10.20) and check for locked users.