- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Telnet problem
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
02-18-2002 01:53 PM
02-18-2002 01:53 PM
I could not use telnet to log into the server. Before that, there is no problem on the server. On the reboot, there are some error messages, erroras follow.
rpcbind: init_transport: check binding for tcp
rpcbind: init_transport: check binding for ticlts
rpcbind: svc_tli_create: t_getname failed; T_IDLE
rpcbind: svc_dg_create: could not get transport information
rpcbind: init_transport: Could not create rmtcall fd for ticlts
brian rpcbind: init_transport: check binding for ticotsord
brian rpcbind: init_transport: check binding for ticots
brian vmunix: NFS server (pid562@/net) not responding still trying
/usr/sbin/nfsd[627]: Setting STREAMS-HEAD high water value to 65536.
I can ping the server.
I try to telnet localhost through the console. It gives ???connection refused???.
# ps -fae | grep inetd
root 2331 576 0 21:01:39 ttyd0p2 0:00 grep inetd
# grep telnet /etc/inetd.conf
telnet stream tcp nowait root /usr/lbin/telnetd telnetd
# grep telnet /var/adm/inetd.sec
telnet allow
# netstat -rn | grep default
# grep telnet /etc/services
telnet 23/tcp # Virtual Terminal Protocol
#
I can ping default router.
There is no problem on the network. I can ping other computers in the network.
Lanscan gives follow:
0/0/0/0 0x001083FC4238 0 UP lan0 snap0 1 ETHER Yes 119
/sbin/init.d/net
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2002 02:23 PM
02-18-2002 02:23 PM
Re: Telnet problem
netstat -a |grep telnet
say?
Connection refused sounds like it's not listening for telnet.
I notice netstat -rn does not have a default route. Are we limited to the local LAN or is the router doing proxy arp for us?
Can you ping this host from your starting point? If so try unplugging the network cable on the one you want to telnet to and make sure the ping to it fails. You could have a duplicate ip address and be hitting a Windows box.
Can you telnet to the local host while logged onto the console?
telnet 127.0.0.1
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2002 02:24 PM
02-18-2002 02:24 PM
Re: Telnet problem
HTH,
Shiju
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2002 06:27 PM
02-18-2002 06:27 PM
Re: Telnet problem
You can ping the host.
telnet 127.0.0.1 gives "connection refused".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2002 06:40 PM
02-18-2002 06:40 PM
Re: Telnet problem
Few questions for you.
First are there any users that have been able to telnet to the server since the last reboot?
How many user licenses do you have?
Can you telnet to a different server?
Is the inetd service actually running?
# ps -ef | grep inetd
root 604 1 0 16:47:24 ? 0:00 /usr/sbin/inetd
HTH
-Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2002 08:47 PM
02-18-2002 08:47 PM
SolutionFrom your ps output, your inetd daemon is not running at all to allow servicing of telnet requests.
# ps -fae | grep inetd
root 2331 576 0 21:01:39 ttyd0p2 0:00 grep inetd
Check that the following files exist and the startup script begins with a capital S ie. S500inetd.
# ls -la /sbin/init.d/inetd
-r-xr-xr-x 1 bin bin 1386 Oct 27 1997 /sbin/init.d/inetd
# ls -la /sbin/rc2.d/*inetd
lrwxr-xr-x 1 root sys 18 Mar 17 2000 /sbin/rc2.d/S500inetd -> /sbin/init.d/inetd
To start your inetd daemon in your current running environment, execute
# /sbin/init.d/inetd start
Hope this helps. Regards.
Steven Sim Kok Leong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2002 02:30 AM
02-19-2002 02:30 AM
Re: Telnet problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2002 05:55 AM
02-19-2002 05:55 AM
Re: Telnet problem
Lot of people involved in to solve the issue YOU should assign points.
Thanks