- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- remsh error
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
06-24-2003 02:36 AM
06-24-2003 02:36 AM
remsh error
Since some days, i have a problem with a HP-UX host (V 10.20). I can't connect on it from any remote host, with remsh command. The error is "remshd: connect: error 0" and error in syslog is: "connect on second port: connection timeout". All others commands work (rcp, rlogin, telnet,...) only remsh is bad and only from remote host. The command work when i use it from the local host.
Thanks for you help.
JMB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2003 03:01 AM
06-24-2003 03:01 AM
Re: remsh error
Use command "/usr/sbin/rpcinfo -n 512 -u
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2003 03:08 AM
06-24-2003 03:08 AM
Re: remsh error
as suggested have a talk with your network gui and find if they have implemented ab??ny security policy.
HTH,
Massimo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2003 03:35 AM
06-24-2003 03:35 AM
Re: remsh error
nslookup hostname
nslookup ip
B) What's in nsswitch.conf?
hosts: files [NOTFOUND=continue] dns
C) From the client side:
What's in your /etc/nsswitch.conf file for both passwd and hosts? For example:
passwd: nis files
hosts: files [NOTFOUND=continue] dns
d) Also from the client is logging enable? (* logging always adds overhead. *) Check syslog.log.
inetd -l
E) Do you have nfs mount file systems? (* NFS and remshd both use RPC services. *) If so see if you can recreate by copying a large file into nfs and remsh at the same time.
prealloc /tmp/50meg_file 50000000 (* make a 50 mb file *)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2003 07:49 AM
06-24-2003 07:49 AM
Re: remsh error
But why others commands than remsh, work without this route?
Thanks.
JMB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2003 12:53 PM
06-24-2003 12:53 PM
Re: remsh error
They should work if so long as the machines can ping each other and are at a run level that allows networking.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2003 08:59 PM
06-24-2003 08:59 PM