HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- FTP and TELNET not working, dont think it's inetd ...
Operating System - HP-UX
1834498
Members
2539
Online
110067
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
06-11-2001 12:02 PM
06-11-2001 12:02 PM
FTP and TELNET not working, dont think it's inetd problem
Ok all of sudden neither of these services are working on my HPUX 11.0 K machine....If I try to connect to either from a remote machine (same subnet) all I see is the cursor sitting there. Therefore it connects, there is just no response. I have tryed to FTP and TELNEt from the console and it works so these services are running. This verifies that INETD is running, correct? Haven't checked the machine in a while so I'm not sure when it stopped working. All I can think of is maybe something didn't start back up after a recent reboot...Also another Oracle instance was added recently. Maybe this is a kernel configuration issue. However Oracle is working fine. I can connect to all the instances just fine.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2001 12:32 PM
06-11-2001 12:32 PM
Re: FTP and TELNET not working, dont think it's inetd problem
There's not a whole lot of info here. It could be a number of things...
Here's a few things you could check on.
1. You check ps -ef | grep inetd and it is up and running (and you have restarted it to ensure this)
2. You have confirmed it is not a bad name/ip resolution by doing nslookup on name & ip. You are sure it is not a dup ip.
3.. You telnet in and it hangs for a couple minutes before it gives you a login:
Telnets from the PCs take about 100 seconds to get a login prompt
because the K-box attempts to resolve the name of the incoming PC.
The K-box doesn't resolve it because it is not in the hosts file.
The K-box then it passes it to the DNS server, which it doesn't have
it registered either. The DNS server finally sends the usuccessful
result back to the K-box which then will give the PC a login prompt.
The way to fix this problem is to make entries in the named.boot file
on the DNS server for each leased IP that the dhcp box serves out.
Note: Restart named.
It doesn't matter what name he gives for the alias of the IP, it
can be pc1 through pc100, if there were that many boxes. Next time
the pc telnets, the DNS box will have a successful lookup and the
login prompt will appear much faster.
4. You may want to double check that rpcbind was started properly: Check the last entry of this thread:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x18ade7613948d5118fef0090279cd0f9,00.html
5. You may want to make certain your special files are ok.
Rebuild the special device files at the command prompt as follows:
insf -d ptys -n 512 512 being the number you set NPTY in SAM (10.20 and
11.0)
insf -d ptym -n 512 (10.20 and 11.0)
insf -d pts -s 512 -e -v (for 11.0 only )
That's it, your sessions have been increased to 512.
6. Ensure that /var/adm/inetd.sec hasn't somehow been set to deny ftp &/or telnet privileges.
Just a couple thoughts,
Rita
Here's a few things you could check on.
1. You check ps -ef | grep inetd and it is up and running (and you have restarted it to ensure this)
2. You have confirmed it is not a bad name/ip resolution by doing nslookup on name & ip. You are sure it is not a dup ip.
3.. You telnet in and it hangs for a couple minutes before it gives you a login:
Telnets from the PCs take about 100 seconds to get a login prompt
because the K-box attempts to resolve the name of the incoming PC.
The K-box doesn't resolve it because it is not in the hosts file.
The K-box then it passes it to the DNS server, which it doesn't have
it registered either. The DNS server finally sends the usuccessful
result back to the K-box which then will give the PC a login prompt.
The way to fix this problem is to make entries in the named.boot file
on the DNS server for each leased IP that the dhcp box serves out.
Note: Restart named.
It doesn't matter what name he gives for the alias of the IP, it
can be pc1 through pc100, if there were that many boxes. Next time
the pc telnets, the DNS box will have a successful lookup and the
login prompt will appear much faster.
4. You may want to double check that rpcbind was started properly: Check the last entry of this thread:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x18ade7613948d5118fef0090279cd0f9,00.html
5. You may want to make certain your special files are ok.
Rebuild the special device files at the command prompt as follows:
insf -d ptys -n 512 512 being the number you set NPTY in SAM (10.20 and
11.0)
insf -d ptym -n 512 (10.20 and 11.0)
insf -d pts -s 512 -e -v (for 11.0 only )
That's it, your sessions have been increased to 512.
6. Ensure that /var/adm/inetd.sec hasn't somehow been set to deny ftp &/or telnet privileges.
Just a couple thoughts,
Rita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2001 03:15 PM
06-12-2001 03:15 PM
Re: FTP and TELNET not working, dont think it's inetd problem
As soon as I corrected my IP in the hosts file on the K I could connect. It wouldn't wait a few minutes like you said. I know that my IP had changed recently but I know before that I didn't have to have a machine in the K's hosts file for telent or FTP ro work...hmm..I'll read me what you mention.
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