Login Error 3004-304


 
Thread Tools Search this Thread
Operating Systems AIX Login Error 3004-304
# 1  
Old 03-14-2005
Login Error 3004-304

I am trying to log on and get an error "3004-304 You are not allowed to login at this time.". This happens with both "root" and "admin" (the only other user ID on the system). System console or telnet session, doesn't matter. When I reboot the system, which I can only do with the power button since I can't sign on to issue shutdown, I can again log on, but after a day or two the problem returns. The system is obviously still running because I'm not having any problems with TSM backups. Google turns up nothing. Does anyone have any ideas?

Thanks,
Dino
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. AIX

3004-312 All available login sessions are in use.

Hello, I have a strange situation here. I am running an AIX6.1 machine and i face a problem when i am trying to login via telnet. When i use my username and password to login to the server i get the following message: 3004-312 All available login sessions are in use. The weird thing is that... (3 Replies)
Discussion started by: omonoiatis9
3 Replies

2. AIX

Users can not login with telnet 3004-031

when all the users try to login using telnet they will counter the error 3004-031 . and they can not access the system . our application is sbglobus (temenos ) (6 Replies)
Discussion started by: thecobra151
6 Replies

3. Solaris

error message rmclomv ... SC Login Failure for user Please login:

Hello World ~ HW : SUN Fire V240 OS : Solaris 8 Error message prompts 'rmclomv ... SC login failure ...' on terminal. and Error Message prompts continually 'SC Login Failure for user Please login:' on Single Mode(init S) The System is in normal operation, though In case of rain, Can... (1 Reply)
Discussion started by: lifegeek
1 Replies

4. AIX

Login Error 3004-304 aix 4.3 please help

hello, I am trying to log on and get an error "3004-304 You are not allowed to login at this time.". The server is in production level, works as a cluster under hacmp, the other server took the services but I cannot log into the first one. Please help me because I need to solve the problem as... (2 Replies)
Discussion started by: andwhat
2 Replies

5. AIX

3004-505 Cannot set process environment

Guys I have an AIX 5.3 box.I am getting following messages if i try to switch to any non root user. bash-3.00# su - sys 3004-505 Cannot set process environment. bash-3.00# su - daemon 3004-505 Cannot set process environment. bash-3.00# su - adm 3004-505 Cannot set process environment.... (4 Replies)
Discussion started by: ak835
4 Replies

6. UNIX for Advanced & Expert Users

VSI-FAX error - Cannot login to server and Connecto error to host

I encounters a VSIFAX related error: vfxstat: Cannot login to server on rsac3: Connect error to host 172.16.1.45: Invalid argument It started happening last night with a core dump. Then we can't start VSIFAX again. I am runing VSI-FAX 4.2 on AIX box (0 Replies)
Discussion started by: b_jin
0 Replies

7. UNIX for Advanced & Expert Users

RDUBLK: cANNOT FİND PROCESS id ....

Hi, we are using SCO Open Server 5.0.7 on HP ProLiant DL380 G4 Intel(R) Xeon(TM) CPU 2.8 dual processor. 2 GB MEM. The error message is : ps: RDUBLK: Cannot find process ID ....: No such device or address (error 6) Best regards, Abdullah Sekman (2 Replies)
Discussion started by: Abdullah Sekman
2 Replies
Login or Register to Ask a Question
auth.adm(1M)															      auth.adm(1M)

NAME
auth.adm - activate, deactivate, or query about HP-UX Integrated Login SYNOPSIS
tech_name [ tech_name ] [ tech_name[:tech_name]... ] [ tech_name:parameter=value[:parameter=value]... ]... [ filename ] DESCRIPTION
The command makes it easy to activate, deactivate or query about HP-UX Integrated Login. During activation, sets up a machine to obtain integrated login behavior using any of the following commands: and saves the Integrated Login configuration, specified by and arguments, in the file This configuration file specifies the authentication technologies used to authenticate users on a system. System administrators can specify the technology for system login; where this login technology is unavailable, a fallback technology for system login can also be specified. System administrators can also specify technologies for additional user authentications that will be done after a user has successfully completed the system login phase. Integrated behavior of and is obtained by replacing the current with one that specifies the behavior requested by the arguments. auth.adm provides an option of enabling the nsswitch for DCE technology. The is updated with "dce" keyword if this option has been selected. In this scenario the name service requests for user/group information will be obtained from DCE depending on the configuration. After NSS switch is enabled, an option is provided to export the DCE user/group information to and via a cron job. program could also be run manually to do this job. Upon deactivation, restores files that were present on the system before Integrated Login was installed. It also removes the configuration file. When making a query, reads the file and prints the result of the query to stdout or to filename specified by the argument. All actions performed by are logged into the file ARGUMENTS
recognizes the following arguments: activates HP-UX Integrated Login. tech_name an abbreviated name representing an authentication technology. Starting with the 10.0 release, the tech_name's supported are: for DCE Registry for /etc/passwd and other HP-UX login technologies. tech_name specifies the technology used for system login. tech_name specifies the technology used for fallback login. tech_name[:tech_name]... specifies technologies used for additional authentications after a user has been successfully logged in to a system. tech_name:parameter=value[:parameter=value]... specifies configurable parameters applicable to a technology. Parameters for different technologies can be specified by repeating the argument. Starting with the 10.30 release, the configurable parameters supported include the following: Timeout (in seconds) on communications with a technology. Default values for TIMEOUT are as follows. 180 seconds ignored Password expiration warning period (in days). If the user's password is due to expire within the specified number of days, the user receives a warning message during login. This parameter applies to DCE technology only. If this parameter is not specified, no warning is given. Password force-change period (in days). If the user's password is due to expire within the specified number of days, the user is forced to change the password before login is allowed. This parameter applies to the DCE technology only. If this parameter is not specified, a password change is not forced. Enable DCE TGT to be forwardable. When forwarding a user's DCE TGT from machine A to machine B, it enables the user from machine A to reuse its Kerberos credentials on machine B. A parameter value is required, but its content is ignored. This parameter applies to DCE technology only. deactivates HP-UX Integrated Login. makes a query about the current Integrated Login configuration. filename prints result of a query to filename. EXAMPLES
The following command activates HP-UX Integrated Login. The configuration is set to login the user upon successful password verification by DCE. In the case where DCE is not available, a fallback for login via /etc/passwd or another HP-UX technology is configured. (Note that this strategy is effective only if the HP-UX password and DCE password are identical.) The following command activates HP-UX Integrated Login. The configuration is set to login the user upon successful password verification by /etc/passwd or another HP-UX technology. After machine access has been granted to the user, the configuration specifies that a DCE login should also be done. RETURN VALUE
returns one of the following: Successfully completed Error(s) occurred WARNING
If activation or deactivation fails to complete, the error(s) should be corrected and re-execution of the activation/deactivation should be done. cannot deactivate a failed activation. NOTE
auth.adm will restart the pwgrd daemon after the ilogin daemon is started, if it was already running. AUTHOR
was developed by HP. FILES
log file containing records of actions performed by SEE ALSO
auth.adm(1M)