Error 451 Append/Restart Not Permitted

[TMowreader]

Hello I've got a SNAP 4500 running GuardianOS 4.0.228 SP2 that is giving the following error message when trying to access files via FTP.

The error is, "Error 451 h12bcode.b Append/Restart Not Permitted" h12bocde.b is the file name.

The FTP client is accessing the server via a username that is an admin will full privs.

This may be related or not, but there is also an issue with a PC that is accessing the server and it is supposed to append data to a file that is in all lower case, h12bcode.a and it is adding a new file instead called, H12BCODE.A. Same file, but it's all upper case. So, there are two files with the same name in the same directory, one is upper case and the other is lower. This is causing issues because 6 of the 8 clients that are supposed to be appending to this lowercase file, are appending to the upper case file instead of the one that is lower case. On the server end, it is looking to grab the data from the file that is all lower case, wich is empty because all the data is in the uppercase file. There for the info never gets to the system.

I imagine I'll be able to figure things out on the client end so that it adds to the lower case instead of creating an upper case, but I'm curious is anyone knows whey the server would allow two files with the same name in the first place?

Any ideas anyone?

[Phoenix32]

Not me, outa my league. David?

[TMowreader]

Update:

The problem is DEFINATELY related to upper and lower case file names being able to take place in the same folder. I am not able to create the same filename, upper or lower case, in Windows, but scanning upload program, SGW, is. I'm told that the SGW program is written in visual basic.

So, to recap, windows can not create the same file name with any case, but this program, written in VB, communicating through windows, not FTP, apparently can.

The problem is definately with 4500 snap servers because we were using a 4100 that worked fine, but when replaced with this 4500, thats when the problem started. The problem stopped when I changed the config settings of this SGW program to send the scans to the lowercase file name, h12bcode.a.

I have 2 4500's and both of them did the same thing.

If you have a 4500 you can verify this by trying to access it via FTP in windows. Here is what I did. (I changed my server and username to generic ones)

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>ftp 10.152.12.28
Connected to 10.152.12.28.
220 ProFTPD 1.2.9 Server (Snap Appliance FTP Server) [servername.domainname.com]
User (10.152.12.28none)): "username"
331 Password required for "username".
Password:
230 User "username" logged in.
ftp> cd SHARE1
550 SHARE1: No such file or directory
ftp> cd share1
250 CWD command successful.
ftp>

Tyler

[joebloggs99]

Aha! Dear old Unix! Guardian OS is a Unix-derived system. One of the 'features' of the UNIX system is that upper and lower case characters are treated as distinct. This is true in the file system, as well as on the command line and all other places. So...

You need to find a way to force your clients to a common standard. You don't say what versions of Windows are running on your clients - there may be something there to look at further.

[TMowreader]

All PC's except 1 are Windows XP Pro. That 1 is Windows 98.

I am going to go verify that all configuration files on all PC's are set to lowercase files, but I'm pretty sure they already are.

The file on the server that holds the scans get's modified by 8 different PC's at the same time (all constantly uploading scans through out the day) and then our corporate system comes and takes all the scans out of the file via FTP.

If all client PC's are set to upload to a lowercase file, then could it be that the client, the FTP "pickup" server, or the snap server itself is creating this uppercase file because it can't handle all the transactions?

Again, this was not a problem on the Snap 4100 server that we had and has onlyl become a problem with this 4500....

Thank you for your help!

Tyler

[TMowreader]

OK, so, ALL PC's had the uppercase settings in them. I changed all the PC's to use the lowercase file, but there is another issue.

In the configuration settings for the client SW, I type in the file name and the SW appends the .A extension. The problem is that appends just that a ".A" extension and not a ".a" extension. SO instead of there being an "h12bcode.a" file and an "H12BCODE.A" file, there is a "h12bcode.A" file. Putting us in the same perdicament we were in before.

Does anyone know if this 'feature' is fixed in an update of the OS?

Otherwise we may have to look into reprograming the client SW(don't know if thats even possible), or we'll have to buy another update server... .


Tyler

[blue68f100]

OK, I'm here. Had a Myleogram today ran on my low back, so I have beed out of pocket.

The 4500 runs on Redhat Linux, Liniux/UNIX is case sensitive. So the files are treated as 2 or how many varitions.

To correct the code you need to force the file name to lower case if htat is what you need.

FTP 550 error is what you get when passive/active is not set correctly. If your behind a firewall you want active. And/Or you do not have hte full path to their share.

It does not matter which OS or whether you connect ftp or through SAMBA v3, the Guardian OS is case sensitive. I do not recall if there is some flag under advanced settings that can clear the cases sensitivity.

The snapOS was based on BSD which is also case sensitive. The differents is the SnapOS used Samba v2 where the GuardianOS uses Samba v3. This is more that likely where your problem lies.