David/Guy,

I have figured out my issue. Thanks for the help. The problem was that
the customer had decided to change their password to be case
sensitive. My FTP script had the password in all caps.

So when i changed my Script to have password in lower case as follows it worked

USER APPUSER password

As far as authenticating twice, I have no idea why i am seeing the
credential on my system in the FTP output. When i issue the FTP
command it defaults to the user id on my system kthiruma. That profile
does not exist on the other system. Which is why i have to use the
USER command or as Guy pointed out i could have just used

APPUSER password

On 9/29/05, David Gibbs <david@xxxxxxxxxxxx> wrote:
> Krish Thirumalai wrote:
> > What you see in the output file is just my login id on the system i am
> > trying to FTP from. The system i am connecting to is  prompting me to
> > enter a user id. I get the same issue if i am sending a save file or a
> > member. I made sure that the source file exists on the other end also
>
> In the example you gave before ... you provided two sets of credentials
> ... kthiruma and appuser.  kthiruma was used to connect to the remote
> system, but then you tried to 're-authenticate' using appuser.
>
> This is what I'm confused about.
>
> david
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>


--
Krish Thirumalai


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.