Cgray
asked on
Suse 9.1 FTP install works with Anonymous access but fails with username / password access
I have an FTP server setup with a basic Anonymous account and a basic username and password account.
The problem is after attempting to download to CD1\driverupdate file it seems that the username and password account fails. This
resaults in the following error:
Cannot read package data from installation media. Media Error?
- ERROR: No Proposal
Keep in mind that I have done the Anonymous install several times. Even after getting the error above.
Also the FTP server logs files look the same until the attempt to download the CD1\driverupdate file (This file doesn't exists).
The problem is after attempting to download to CD1\driverupdate file it seems that the username and password account fails. This
resaults in the following error:
Cannot read package data from installation media. Media Error?
- ERROR: No Proposal
Keep in mind that I have done the Anonymous install several times. Even after getting the error above.
Also the FTP server logs files look the same until the attempt to download the CD1\driverupdate file (This file doesn't exists).
Is your FTP server chrooting the logged in user to their home dir? That's commonly done as a security precaution and it would cause a difference in what's available between anonymous and authenticated FTP access.
ASKER
They both have the same home directory. The only difference between the Anonymous user and the auth user is that the auth user has a username and password.
ASKER
btw the ftp server is running on windows 2003 (non microsoft ftp server).
Is CD1\driverupdate in that directory or elsewhere? If in the directory are the permissions set to allow the authenticated user access? Can the authenticated user access other data?
ASKER
It's not a permission issue. I have found and addressed the problem and you are not close.
Okay, what was it?
ASKER
I wonder if I can answer my own question??
ASKER
The answer is as follows:
I was logging in this the username: xxx@xxx.com
Which when send a user name and password via ftp in a string it looks like:
ftp ftp://$USER:$PASSWORD@$SERVER/$DIRECTORY/$FILE
Thus if my user name was xxx@xxx.com
ftp ftp://xxx@xxx.com:$PASSWORD@$SERVER/$DIRECTORY/$FILE
Which crashes the Suse install.
This also explains why the Anonymous user worked ( NO @ ).
I was logging in this the username: xxx@xxx.com
Which when send a user name and password via ftp in a string it looks like:
ftp ftp://$USER:$PASSWORD@$SERVER/$DIRECTORY/$FILE
Thus if my user name was xxx@xxx.com
ftp ftp://xxx@xxx.com:$PASSWORD@$SERVER/$DIRECTORY/$FILE
Which crashes the Suse install.
This also explains why the Anonymous user worked ( NO @ ).
user@domain.spec is valid in a URL, but isn't an FTP username. So it isn't surprising that it failed.
Since you found the problem yourself and provided the answer I'd suggest that you allow me to PAQ the question and refund the points. As a Page Editor I can do that if you want.
Since you found the problem yourself and provided the answer I'd suggest that you allow me to PAQ the question and refund the points. As a Page Editor I can do that if you want.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.