GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- FTP problems
Operating System - HP-UX
1847211
Members
2509
Online
110263
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
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
02-01-2008 12:31 PM
02-01-2008 12:31 PM
FTP problems
I have migrated a development server from the old machine to a new machine. After the new machine is setup, its ftp is not working for remote clients. Users inside here in the premises can still do ftp but remote users are not able to do that. I think the problem is in inetd.sec file.
How that problem can be solved. Do I just copy the old inetd.sec file from the old server to the new one or I need to do some thing else?
Can some one please tell me the step by step proceedure to perform this task. Like what services need to be started and what services need to be stopped before copying the file.
How that problem can be solved. Do I just copy the old inetd.sec file from the old server to the new one or I need to do some thing else?
Can some one please tell me the step by step proceedure to perform this task. Like what services need to be started and what services need to be stopped before copying the file.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2008 01:46 PM
02-01-2008 01:46 PM
Re: FTP problems
what do you have in "inetd.sec" now?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2008 02:51 PM
02-01-2008 02:51 PM
Re: FTP problems
lots of addresses for different clients. Actually i have installed it from the image of a diffenet machine because the previous machine doesnt have the tape drive. So it took all the settings from the previous machine.
My question is that if I replace the current inetd.sec with the old inetd.sec, do I need to restart the inetd?
My question is that if I replace the current inetd.sec with the old inetd.sec, do I need to restart the inetd?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2008 07:17 PM
02-01-2008 07:17 PM
Re: FTP problems
> what do you have in "inetd.sec" now?
> lots of addresses for different clients.
So, what's different?
> [...] do I need to restart the inetd?
I know nothing (including your HP-UX version),
but if "man inetd" tells you to do a "kill
-HUP" ("inetd -c") when you change
"/etc/inetd.conf", then I'd assume that you'd
need to do it if you changed "inetd.sec".
This should be a bit less disruptive than
actually stopping and restarting inetd.
> lots of addresses for different clients.
So, what's different?
> [...] do I need to restart the inetd?
I know nothing (including your HP-UX version),
but if "man inetd" tells you to do a "kill
-HUP" ("inetd -c") when you change
"/etc/inetd.conf", then I'd assume that you'd
need to do it if you changed "inetd.sec".
This should be a bit less disruptive than
actually stopping and restarting inetd.
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 2026 Hewlett Packard Enterprise Development LP