HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: remshd: login incorrect - due to alternate hos...
Operating System - HP-UX
1837239
Members
2099
Online
110115
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
04-07-2005 01:20 AM
04-07-2005 01:20 AM
remshd: login incorrect - due to alternate host name
I get the login incorrect and have followed many of the suggestion in the forums (thanks all) and have figured out that what is happening is that the server that one can't rcp from is using the wrong ip address.
We have MC-Serviceguard, thus are running packages with their own IP addresses. This works fine on our production boxes, but for some reason when rcp'ing from the development box, the other machines are seeing the ip (and name) of the first package instead of the host and it's ip address.
In this example, the ip/host is 10.28.38.225/t21aldu1, and the package is 10.28.38.14/t21aldrt
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan2 1500 10.28.36.0 10.28.38.224 2475512 0 24289677 0 0
lan0 1500 192.168.1.0 192.168.1.221 140206 0 141976 0 0
lo0 4136 127.0.0.0 127.0.0.1 1103262 0 1103262 0 0
lan2:1 1500 10.28.38.0 10.28.38.15 10262507 0 8087420 0 0
lan2:2 1500 10.28.38.0 10.28.38.14 747816 0 6289147 0 0
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan2 1500 10.28.36.0 10.28.38.224 2475512 0 24289677 0 0
lan0 1500 192.168.1.0 192.168.1.221 140206 0 141976 0 0
lo0 4136 127.0.0.0 127.0.0.1 1103262 0 1103262 0 0
lan2:1 1500 10.28.38.0 10.28.38.15 10262507 0 8087420 0 0
lan2:2 1500 10.28.38.0 10.28.38.14 747816 0 6289147 0 0
Yet, on the other boxes (after running inetd -l and tail -f /var/adm/syslog/syslog.log) I saw that the incoming ip/host was the lan2:2's 10.28.38.14/t21aldrt
Any ideas why this is happening? I'm sure there's something on t21aldu1 I need to fix.
We have MC-Serviceguard, thus are running packages with their own IP addresses. This works fine on our production boxes, but for some reason when rcp'ing from the development box, the other machines are seeing the ip (and name) of the first package instead of the host and it's ip address.
In this example, the ip/host is 10.28.38.225/t21aldu1, and the package is 10.28.38.14/t21aldrt
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan2 1500 10.28.36.0 10.28.38.224 2475512 0 24289677 0 0
lan0 1500 192.168.1.0 192.168.1.221 140206 0 141976 0 0
lo0 4136 127.0.0.0 127.0.0.1 1103262 0 1103262 0 0
lan2:1 1500 10.28.38.0 10.28.38.15 10262507 0 8087420 0 0
lan2:2 1500 10.28.38.0 10.28.38.14 747816 0 6289147 0 0
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan2 1500 10.28.36.0 10.28.38.224 2475512 0 24289677 0 0
lan0 1500 192.168.1.0 192.168.1.221 140206 0 141976 0 0
lo0 4136 127.0.0.0 127.0.0.1 1103262 0 1103262 0 0
lan2:1 1500 10.28.38.0 10.28.38.15 10262507 0 8087420 0 0
lan2:2 1500 10.28.38.0 10.28.38.14 747816 0 6289147 0 0
Yet, on the other boxes (after running inetd -l and tail -f /var/adm/syslog/syslog.log) I saw that the incoming ip/host was the lan2:2's 10.28.38.14/t21aldrt
Any ideas why this is happening? I'm sure there's something on t21aldu1 I need to fix.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 04:19 PM
04-12-2005 04:19 PM
Re: remshd: login incorrect - due to alternate host name
Make sure that ip and user entry in .rhosts file in the user's home directory is correct. I think the remote machine is not resolved as you think it's resolved, that's why you get "login incorrect" message.
Server1 Server2 (.rhosts here)
rcp ---------------->
Server1 Server2 (.rhosts here)
rcp ---------------->
I don't give a damn for a man that can only spell a word one way. (M. Twain)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 11:04 PM
04-12-2005 11:04 PM
Re: remshd: login incorrect - due to alternate host name
Looks like it had something to do with the subnet mask...but you were on the right track Alex as it was "easier" to use the virtual ip address for name resolution.
Thanks for helping out.
Thanks for helping out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 11:05 PM
04-12-2005 11:05 PM
Re: remshd: login incorrect - due to alternate host name
HP and I found the solution of the subnet mask.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP