- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: OB II 4.0 returns invalid user/passwd
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2001 01:19 PM
12-05-2001 01:19 PM
OB II 4.0 returns invalid user/passwd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2001 02:11 PM
12-05-2001 02:11 PM
Re: OB II 4.0 returns invalid user/passwd
What do you mean by Linux 7.0 ? RedHat or SuSE ?
If you are using RedHat, you may know that "inetd" has been replaced by xinetd. Therefore, you need to create an entry for OmniBack in the related configuration directory as follows (file /etc/xinetd.d/omni) :
service omni
{
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/omni/bin/inet
server_args = inet -log /usr/omni/log/inet.log
disable = no
}
Of course, xinetd must be restarted after any change (/etc/init.d/xinetd restart).
Another clue : make sure that remote execution is enabled during the remote installation (may be rsh or rexec, but I don't remember which one runs). To do so, install the right software using Linux install CDs, then enable the service in /etc/xinetd.d and restart xinetd. Don't forget to temporarily rename /etc/pam.d/rexec or /etc/pam.d/rsh files accordingly.
Last thing : disable the securetty feature during the remote installation (rename /etc/securetty).
Good luck.
Kodjo
P.S. Don't forget to rate this answer (from 1 to 10).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2001 12:14 PM
12-10-2001 12:14 PM
Re: OB II 4.0 returns invalid user/passwd
Well I tried all you suggested to no avail. I even added .rhosts, no luck.
I read somewhere that HP officially provides the support of Linux 7.1 Client on OBII4.0, could the version be my problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2001 03:38 PM
12-10-2001 03:38 PM
Re: OB II 4.0 returns invalid user/passwd
You user root don??t have permission to use the telnet.
See the host.allow and host.any
See /etc/securetty comment the line "telnet" or tty.
Verify /etc/pam.d/telnet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2001 03:42 PM
12-10-2001 03:42 PM
Re: OB II 4.0 returns invalid user/passwd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2001 06:40 AM
12-12-2001 06:40 AM
Re: OB II 4.0 returns invalid user/passwd
BTW I have followed all the recommended steps and also consulted DOC: OV-EN004289 and still I get Invalid username and/or incorrect password.
I removed /etc/hosts.allow and hosts.deny should I have left them there and configure the files accordingly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2001 02:38 PM
12-12-2001 02:38 PM
Re: OB II 4.0 returns invalid user/passwd
Since 3.10, all OmniBack versions are correctly remotely installed on Linux clients.
Just check ALL these before proceeding the installation.
1. Make sure /etc/securetty mechanism is deactivated (rename /etc/securetty).
2. Make sure remote exec is enabled.
To do so, install rexec package, and configure it as follows :
-> /etc/xinetd.d/rexec and /etc/xinetd.d/rsh should look like this (particularly, pay attention to "disable = no" and "server_args = -h") :
service exec
{
socket_type = stream
wait = no
user = root
log_on_success += USERID
log_on_failure += USERID
server = /usr/sbin/in.rexecd
server_args = -h
disable = no
}
service shell
{
socket_type = stream
wait = no
user = root
log_on_success += USERID
log_on_failure += USERID
server = /usr/sbin/in.rshd
server_args = -L -h
disable = no
}
Of course, you have to re-start xinetd by typing /etc/rc.d/init.d/xinetd restart.
Then, you can type "netstat -a | grep LISTEN" to check if the host is listening on sockets "shell" and "exec".
-> both /etc/pam.d/rexec and /etc/pam.d/rsh should look like this :
auth required /lib/security/pam_nologin.so
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_env.so
auth required /lib/security/pam_stack.so service=system-auth
account required /lib/security/pam_stack.so service=system-auth
session required /lib/security/pam_stack.so service=system-auth
Of course after the installation, you can restore all these security features.
Good luck.
Kodjo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2001 05:36 AM
12-14-2001 05:36 AM
Re: OB II 4.0 returns invalid user/passwd
Starting installation.....
Getting list of clients for installation...
Connecting to client....
And it's still in a pending state.
Is this now a cell mgr problem, or does something else need to be done from the linux box? telnet works to and from linux.