Your best friend for file transfer.

Fetch application logoFetch

password rejections (7 posts)

  • Started 16 years ago by erinmckenna
  • Latest reply 16 years ago from erinmckenna
  • erinmckenna Member

    All of a sudden some of my shortcuts, where the passwords have been saved are giving me a "server rejected the password" error. There is no common thread to the servers that are not working now - they are different companies that provide the hosting to the sites I'm having problems with. I am using a Mac running OS 10.4.9 and connecting wirelessly using Airport Extreme.

    Here is the info from the Fetch Transcipt window from one of these failed connections:
    Fetch 5.2 (5C121) PowerPC running on Mac OS X 10.4.9 (8P135) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X001-7PPZ-4RUH T
    Update check skipped at 05/14/2007 06:49 PM (next check after 05/22/2007 02:01 PM)
    Connecting to 205.178.145.176 port 21 (Mac OS X firewall is off) (5/14/07 6:53:44 PM)
    Connected to 205.178.145.176 port 21 (5/14/07 6:53:47 PM)
    220 Serv-U FTP-Server v2.5n for WinSock ready...
    USER erinmckenna%004c04e
    331 User name okay, need password.
    PASS
    530 Not logged in.

    Posted 16 years ago #

  • Scott McGuire Administrator

    Hi,

    We're sorry to hear you're having problems.

    In regards to the transcript you posted, I notice that it says the username Fetch tried to use to log in with was "erinmckenna%004c04e", which seems unlikely - do you recall if your username for this server is actually that, or is it just "erinmckenna"?

    Knowing the answer to that question will help us determine what the problem might be.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 16 years ago #

  • erinmckenna Member

    Yes, that is the username, I know it seems weird, but the server is through network solutions and all of their usernames use that weird naming convention. You aren't even able to change anything after the percent sign when creating your username.

    Here's the transcript from another that is giving me the same issue, but is on a different server with a different company:

    Connecting to 65.108.231.76 port 21 (Mac OS X firewall is off) (5/15/07 12:30:47 PM)
    Connecting to 208.56.91.1 port 21 (Mac OS X firewall is off) (5/15/07 12:33:43 PM)
    Connected to 208.56.91.1 port 21 (5/15/07 12:33:46 PM)
    220 ProFTPD 1.2.9 Server (ProFTPD Default Installation) [host5.globalnameservers.com]
    USER stephenv
    331 Password required for stephenv.
    PASS
    530 Login incorrect.

    Posted 16 years ago #

  • Scott McGuire Administrator

    Hi,

    Thanks for the reply. I'm glad to hear that is the correct username, I was concerned that the shortcuts file had gotten corrupted, but I don't think that's the case.

    Can you still connect to some servers successfully? Or is everything you've tried not working?

    You said that you have saved the passwords for the shortcuts in question. What happens if you do the following:

    * Choose File > New Connection
    * In the New Connection dialog, choose one of the non-working shortcuts from the Shortcuts pop-up menu (the one with a heart icon).
    * Delete the password that is filled out automatically, and type in the password manually.

    Can you connect successfully if you do that?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 16 years ago #

  • erinmckenna Member

    Even if I create a new connection, and type all of the information in manually, it gives me the same response. The weird thing is, I can connect to some of the other sites, even ones that are held on the same servers as the ones I can't connect to. I'm so baffled...

    I can't even pinpoint anything that had changed, like an update I performed or any type of maintenance that would maybe point me into a direction as to why this might be happening...ugh.

    Posted 16 years ago #

  • Scott McGuire Administrator

    Hi,

    Unfortunately, we're not quite sure what the problem might be, but here are two more things to try:

    * If you have access to another Macintosh, try connecting to one of the problem servers from the other Macintosh, and see what happens. If you can connect successfully from another Macintosh, but not yours, let us know and we'll try to figure out why.

    * Pick one of the problem servers, and contact the folks who run and maintain the server to see if the problem is with the server. It seems odd that several would stop working at once and all be server problems, but we recommend contacting one and seeing if they can fix the problem. If the problem does turn out to be with the server, then you should start contacting the other problem servers.

    Please let us know how it turns out.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 16 years ago #

  • erinmckenna Member

    Okay, I'll give it a shot on another machine and let you know how I make out.

    Thanks!

    Posted 16 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.