08-27-2002
What ftp daemon are you running? Some of them try a reverse dns lookup to get the hostname. From the server can you do a nslookup on the ip address of the client? When the clients switched to dhcp did they wind up on a different subnet? Could you be running tcp wrappers or something like that on the server? Is there a firewall between the server and the client? This could be a firewall issue.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Solaris Server (V880) version 8
Brand new box just installed O/S, what do I need to do in order to get FTP working.
I have updated the /etc/hosts.equiv file
Problem - When trying to ftp to the server I get a login incorrect message, this is with the root user.
Are there some... (1 Reply)
Discussion started by: miredale
1 Replies
2. Cybersecurity
I just started a new job and inherited a Fedora core 3 server. I wanted to open the ftp ports and I wanted to verify this code before I mess things up. From my reading the two lines below should allow ftp access can anyone confirm my attempt.
iptables -A INPUT -p tcp - sport 21 -m state - state... (0 Replies)
Discussion started by: mungaz
0 Replies
3. Solaris
Hi all,
i am not able to connect the ftp through userA.
Can you please tell me what are the possible ways to troubleshoot
this issue?
Regards
krishna (2 Replies)
Discussion started by: krishna176
2 Replies
4. SCO
I have problem with ftp connection on SCO UNIX 5.0.7, it is work slowly. How I can
make accelerate. (6 Replies)
Discussion started by: draganmi
6 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Anyone encounter whereby when you FTP from an Unix server (Solaris 8) to another server (Window Server 2003), you tend to wait a long while when you do a "ls" and you get a timeout after that. However, when you FTP again and do a "ls", the result of "ls" shown immediately. All connection are... (5 Replies)
Discussion started by: ahlude
5 Replies
6. Shell Programming and Scripting
I am getting the error in this command when i am pitting it in shell script
ftp -nvi jcmpcor1.abc.com >/work/test98.dat << EOD
error:-
invalid command.
but when i am writting it from outside it work fine. (7 Replies)
Discussion started by: ravi214u
7 Replies
7. UNIX for Dummies Questions & Answers
Can anyone point me in the right direction..
I have a test system which requires vxWorks to be loaded via TCPIP
I am using a Sun ultra10 box with Sol 9.0 installed as the server
I have configured the server and am able to load the boot image without any problems. I assume it is using the... (0 Replies)
Discussion started by: shortsrkt
0 Replies
8. HP-UX
Hi,
Have anyone seen this problem, there is one remote side where their ftp connection to our server will always fail with connection closed by remote host and the second connection will be working.
is this an OS issue or network issue?
Thanks
Robert (4 Replies)
Discussion started by: robertngo
4 Replies
9. Solaris
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies
10. Shell Programming and Scripting
Hi I am trying to execute a shell script which is in unix server gs1. The script is below which basically connects to another unix server q15 and tries to get a file using FTP .
But i get error as "ftp: connect: Connection refused
Not connected.
Not connected."
Please help with if the below... (8 Replies)
Discussion started by: samrat dutta
8 Replies
cups-lpd(8) Apple Inc. cups-lpd(8)
NAME
cups-lpd - receive print jobs and report printer status to lpd clients
SYNOPSIS
cups-lpd [ -h hostname[:port] ] [ -n ] [ -o option=value ]
DESCRIPTION
cups-lpd is the CUPS Line Printer Daemon ("LPD") mini-server that supports legacy client systems that use the LPD protocol. cups-lpd does
not act as a standalone network daemon but instead operates using the Internet "super-server" inetd(8) or xinetd(8). If you are using
inetd, add the following line to the inetd.conf file to enable the cups-lpd mini-server:
printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd
-o document-format=application/octet-stream
Note: If you are using Solaris 10 or higher, you must run the inetdconv(1m) program to register the changes to the inetd.conf file.
If you are using the newer xinetd(8) daemon, create a file named /etc/xinetd.d/cups containing the following lines:
service printer
{
socket_type = stream
protocol = tcp
wait = no
user = lp
group = sys
passenv =
server = /usr/lib/cups/daemon/cups-lpd
server_args = -o document-format=application/octet-stream
}
OPTIONS
-h hostname[:port]
Sets the CUPS server (and port) to use.
-n
Disables reverse address lookups; normally cups-lpd will try to discover the hostname of the client via a reverse DNS lookup.
-o name=value
Inserts options for all print queues. Most often this is used to disable the "l" filter so that remote print jobs are filtered as
needed for printing; the examples in the previous section set the "document-format" option to "application/octet-stream" which forces
autodetection of the print file format.
PERFORMANCE
cups-lpd performs well with small numbers of clients and printers. However, since a new process is created for each connection and since
each process must query the printing system before each job submission, it does not scale to larger configurations. We highly recommend
that large configurations use the native IPP support provided by CUPS instead.
SECURITY
cups-lpd currently does not perform any access control based on the settings in cupsd.conf(5) or in the hosts.allow(5) or hosts.deny(5)
files used by TCP wrappers. Therefore, running cups-lpd on your server will allow any computer on your network (and perhaps the entire
Internet) to print to your server.
While xinetd has built-in access control support, you should use the TCP wrappers package with inetd to limit access to only those comput-
ers that should be able to print through your server.
cups-lpd is not enabled by the standard CUPS distribution. Please consult with your operating system vendor to determine whether it is
enabled on your system.
COMPATIBILITY
cups-lpd does not enforce the restricted source port number specified in RFC 1179, as using restricted ports does not prevent users from
submitting print jobs. While this behavior is different than standard Berkeley LPD implementations, it should not affect normal client
operations.
The output of the status requests follows RFC 2569, Mapping between LPD and IPP Protocols. Since many LPD implementations stray from this
definition, remote status reporting to LPD clients may be unreliable.
SEE ALSO
cups(1), cupsd(8), inetconv(1m), inetd(8), xinetd(8),
http://localhost:631/help
COPYRIGHT
Copyright 2007-2011 by Apple Inc.
4 August 2008 CUPS cups-lpd(8)