![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Advanced UNIX and Linux questions go here. Expert-to-Expert. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| USB Console access on Solaris 9 x86 | com2com | SUN Solaris | 1 | 03-10-2007 12:26 AM |
| sftp problem with user id of no telnet session allowed | superdougl | UNIX for Advanced & Expert Users | 2 | 10-30-2006 06:28 AM |
| cant telnet to aix 5.2 and not even access through serial console | linuxnightowl84 | AIX | 0 | 05-25-2006 09:28 PM |
| Connecting as CONSOLE using Telnet. | mahatma | UNIX for Dummies Questions & Answers | 3 | 03-05-2006 09:39 PM |
| Access with console. | liliput | HP-UX | 3 | 10-21-2003 01:54 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
|||
|
Just took over a UNIX Server from someone who left our company.
Having problems with access by some existing users as well as new users. I get the following message from telnet sessions, when attempting access at the "Login:" prompt: "UX:in.login:ERRO: Login incorrect" "telnetd:Unable to invoke login scheme" Also, when I log on to the server console with the problem users or any new users I create, I get: "UX:login:ERROR: Login incorrect". This is confusing since I can log in those users, that didn't work through standard "Login:", using the "su -" command from a user that does work. Also new users that I create, either through "sysadm" or "useradd" will exhibit the same problem. The Server is using: UNIX System V/386 Release 4.2 Version 1.1.2. UNIX Systems Laboratories, Inc. I believe this is Novell's UnixWare. |
| Forum Sponsor | ||
|
|
|
|||
|
Login Issus!!!
You may want to ask the previous Admin if he/she done anything to corrupt the File System(libraries) or Kernel.
A sign of this is if the system takes a long time or hangs to bring you to the console login screen after booting init or hangs after you try login in w/ your user/pass. Is the Disk space %100 capacitated!!! You should take a look at the syslog messages, history commands, and importantly boot log. Try booting into runlevel 1 single user maintainance mode!!! Check for Memory leaks also - "free" , "vmstat 1" , "top". You may want to back up "tar -zcvf" your config files on a seperate partition and reinstall the OS on the root partition. |
|
|||
|
With the use of truss we were able to isolate the problem to a corrupt /var/adm/lastlog file.
Removal of the file and its re-creation solved the problem. THANKS for your suggestion and all who helped !! |
|||
| Google The UNIX and Linux Forums |