From owner-freebsd-questions Tue Jan 14 16:16:49 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50DF537B401 for ; Tue, 14 Jan 2003 16:16:46 -0800 (PST) Received: from blacklamb.mykitchentable.net (207-173-226-118.bras01.elk.ca.frontiernet.net [207.173.226.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30EB843F1E for ; Tue, 14 Jan 2003 16:16:40 -0800 (PST) (envelope-from drew@mykitchentable.net) Received: from tagalong (unknown [165.107.42.110]) by blacklamb.mykitchentable.net (Postfix) with SMTP id 83DCCEE721; Tue, 14 Jan 2003 16:16:32 -0800 (PST) Message-ID: <009901c2bc2b$5a29a710$6e2a6ba5@tagalong> From: "Drew Tomlinson" To: "John" Cc: "FreeBSD Questions" References: <00b001c2baab$4ebd7bd0$0301a8c0@bigdaddy> <1042447170.88109.69.camel@localhost> <00f901c2bb17$4ee975c0$0301a8c0@bigdaddy> <006a01c2bc27$786b9ca0$be22410a@corporate.amfam.com> Subject: Re: ftpd and Internet Explorer 6 Date: Tue, 14 Jan 2003 16:16:28 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "John" To: "Drew Tomlinson" Sent: Tuesday, January 14, 2003 3:48 PM Subject: Re: ftpd and Internet Explorer 6 > Drew- > I missed the orig post somehow.. > So I'm curious how you attempted to use MSIE to get the file via FTP. > > If FTPD was configured correctly, it should have been as easy as typing this > in the address bad: > ftp://USER:PASS@ftp.site.com/dir/file.name > or just to the dir.. it should show up. It was. Everything was there except the symlink. As a workaround, I copied the files to the user's home directory and he was able to retrieve them. It's just the symlink that wouldn't show. > One thing to check, is that passive FTP is checked in Tools -> options -> > advanced tab. I didn't check that but it shouldn't matter as I could get the rest of the files. AFAIK, passive/active ftp settings wouldn't discriminate on symlinks only. They work on the connection as a whole and the fact that I could see or get anything means that this wasn't an issue. Thanks for your response. Drew > HTH, > John Ricker > > ----- Original Message ----- > From: "Drew Tomlinson" > To: "James Pole" > Cc: > Sent: Monday, January 13, 2003 9:20 AM > Subject: Re: ftpd and Internet Explorer 6 > > > > ----- Original Message ----- > > From: "James Pole" > > To: "Drew Tomlinson" > > Sent: Monday, January 13, 2003 12:39 AM > > > > > > > On Mon, 2003-01-13 at 15:27, Drew Tomlinson wrote: > > > > I was attempting to allow a user to get some files via ftp from my > > FreeBSD > > > > 4.7 box using the ftp client built into MS Internet Explorer 6 (IE). > I > > > > created a guest account and set the shell to /sbin/nologin. That > > appears to > > > > work fine. Then I created a symlink to the directory that contains > the > > > > files for the user but the symlink doesn't appear in the files list in > > IE. > > > > All of the .files that were created by the adduser script do show. My > > > > directory looks like this: > > > > > > Why not just use Apache and get the user to get the file via HTTP. MSIE > > > is a web browser and not a FTP client, after all... > > > > Your idea is good for a ongoing permanent solution. However my situation > is > > more of a "one time" thing. As such, I just copied the files into the > guest > > account and the user was able to get them. But I still wonder if there is > a > > way... :) > > > > Thanks, > > > > Drew > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message