Serv-U dll

David Kerr ( (no email) )
Fri, 9 May 1997 16:46:29 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_01BC5C98.8AB121E0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I got it to start loging and have attached a copy of it.

>running version 4,1,0,1 of the dll
>
>home dir is 23 chars plus user name
>
>I have added the Logfile string to the registry and set it to
>d:\Serv-U\su.log but it doesn't seem to create or log anything to that
>filename.
>
>It apears the dll is authenticating just not setting up Serv-U
>
>--------
> From: Dale E. Reed Jr. <daler@iea.com>
> To: emerald@emerald.iea.com
> Subject: Re: Serv-U
> Date: Friday, May 09, 1997 3:07 PM
>
> David Kerr wrote:
> >
> > I think i may have figured out my problem with the user loging in with
ftp
> > but having no permission to do anything.
> >
> > Ummm, do you have to create the user inside the serv-u program as well
as
> > setting up emerald?
> >
> > Everything works fine if i create the user and either not enter a
password
> > or enter there real password.
>
> No. You do not have to create the user inside of Serv-U itself. That
> is what the DLL circumvents.
>
> Which version of the Serv-U DLL are you using? How long is the homedir
> you are using? If you add the logfile entry, what does the contents of
> the logfile show for the user?
>
> --
> Dale E. Reed Jr. (daler@iea.com)
> _________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.emerald.iea.com
>
> ----------------------------------------------------------
> Emerald Mailing List listserver@emerald.iea.com

----------------------------------------------------------
Emerald Mailing List listserver@emerald.iea.com

------=_NextPart_000_01BC5C98.8AB121E0
Content-Type: application/octet-stream; name="su.log"
Content-Transfer-Encoding: quoted-printable
Content-Description: su.log (Text Document)
Content-Disposition: attachment; filename="su.log"

Fri May 09 16:37:32 1997 HandleClientEvent 3: MANDY
Fri May 09 16:37:32 1997 HandleClientEvent 3: mandy
Fri May 09 16:37:32 1997 LoadUser MANDY
Fri May 09 16:37:32 1997 LoadUser Good
Fri May 09 16:37:32 1997 mandy Added to =
cache
Fri May 09 16:37:32 1997 HandleClientEvent 3: Status: 1
Fri May 09 16:37:32 1997 HandleClientEvent 24: MANDY
Fri May 09 16:37:32 1997 mandy Found in =
cache
Fri May 09 16:37:32 1997 HandleClientEvent 24: Status: =
0
Fri May 09 16:37:32 1997 HandleClientEvent 2: MANDY
Fri May 09 16:37:32 1997 mandy Found in =
cache
Fri May 09 16:37:32 1997 HandleClientEvent 2: =
\\WEB\D$\InetPub\phonet\mandy
Fri May 09 16:37:32 1997 HandleClientEvent 2: Status: 1
Fri May 09 16:37:32 1997 HandleClientEvent 13: MANDY
Fri May 09 16:37:32 1997 mandy Found in =
cache
Fri May 09 16:37:32 1997 HandleClientEvent 13: Status: =
0
Fri May 09 16:37:32 1997 HandleClientEvent 14: MANDY
Fri May 09 16:37:32 1997 mandy Found in =
cache
Fri May 09 16:37:32 1997 HandleClientEvent 14: Status: =
1
Fri May 09 16:37:32 1997 HandleClientEvent 15: MANDY
Fri May 09 16:37:32 1997 mandy Found in =
cache
Fri May 09 16:37:32 1997 HandleClientEvent 15: Status: =
0
Fri May 09 16:37:32 1997 HandleClientEvent 20: MANDY
Fri May 09 16:37:32 1997 mandy Found in =
cache
Fri May 09 16:37:32 1997 HandleClientEvent 20: Status: =
0
Fri May 09 16:37:32 1997 HandleClientEvent 1: MANDY
Fri May 09 16:37:32 1997 mandy Found in =
cache
Fri May 09 16:37:32 1997 HandleClientEvent 1: Status: 0
Fri May 09 16:37:33 1997 HandleClientEvent 10: MANDY
Fri May 09 16:37:33 1997 mandy Found in =
cache
Fri May 09 16:37:33 1997 HandleClientEvent 10: Status: =
0

------=_NextPart_000_01BC5C98.8AB121E0--