that should work, provided that you replaced netbiosname with the actual CIFS server name and you didnt turn off file filtering thru the cifs.EnableFileFiltering param
[@ ][@ ] Where: = file extension that you want to filter. = name of the share to which you want to apply the filter. The is an optional part of the filename. If you do not include a , the filter is applied to all shares on the Data Mover. = NetBIOS name to which you want to limit the filtering. The element is an optional part of the filename. If the share is available on multiple NetBIOS names, this name element limits the filtering to a particular NetBIOS name.
The most important is " [@ ][@ ]" where sharename and netbios name are optionnal.
i try
mp3 -> ok, it work mp3@share1 -> ok it work mp3@share1@server1 -> ok it work mp3@server1 -> doesnt work
In documentation, @sharename is between "[ ]" caractere which mean optionnal but "extension@netbios" syntax doesnt work
OK. I just tried this in my lab and it worked fine. THe file in .filefilter is named mp3. The contents are mp3@srhs_source ( One of my cifs servers on that datamover) I cannot place an MP3 file in any of the shares on that cifs server. I can on shares to other cifs servers however.
One thing to remember is to use notepad, not wordpad. Wordpad leaves an invisible ^M at the end of the line that can cause issue in a UINX world.
As an administrator however, I can place any file I want in the share. This is becasue the filter does not by default apply to administrators. Look at the permissions on the mp3 file and see what it lets you do. This is also discussed in teh .pdf doc on this feature.
I too have an issue with the file filtering and it does not work.
I went to the control station and placed a file such as this: /nas/quota/slot_2/.etc/.filefilter -rw-r--r-- 1 root root 0 Aug 7 09:45 wav@testfs_win
When I try to place the .wav file onto the testfs_win share, it allows me to drop the file. What am I missing?
I'm reasonably sure that you can't apply the filefilter in this way. You need to open C$ of the share in CIFS and traverse into the /.filefilter folder (or /.etc/.filefilter on a VDM). From there, you can create the empty file "wav@testfs_win". Also, as previously noted, @ is not a valid combination, so if "testfs_win" is a netbios name, this filefilter will not work. The NetBIOS tag is only valid if you have @ where "sharename" is visible on multiple NetBIOS names, and you want to limit the filtering to one NetBIOS name. You would then use @ @ .
Again, the only valid combinations are:
...........................................filters that ext on all shares @ ....................filters that ext on that share @ @ ..limits that filter to only that netbios name when ...................................................share is visible on multiple netbios names
[@ ][@ ] Where: = file extension that you want to filter. = name of the share to which you want to apply the filter. The is an optional part of the filename. If you do not include a , the filter is applied to all shares on the Data Mover. = NetBIOS name to which you want to limit the filtering. The element is an optional part of the filename. If the share is available on multiple NetBIOS names, this name element limits the filtering to a particular NetBIOS name.
The most important is " [@ ][@ ]" where sharename and netbios name are optionnal.
i try
mp3 -> ok, it work mp3@share1 -> ok it work mp3@share1@server1 -> ok it work mp3@server1 -> doesnt work
In documentation, @sharename is between "[ ]" caractere which mean optionnal but "extension@netbios" syntax doesnt work
The documentation is indeed confusing, but it's not incorrect. It says that if you want to include NETBIOS name, it would only function if the share is visible on multiple NETBIOS names, and you want to limit it to only one NETBIOS name. However, you cannot use NETBIOS name by itself, because there is no share specified which is visible on multiple NETBIOS names.
Recall what it says:
If the share is available on multiple NetBIOS names, this name element limits the filtering to a particular NetBIOS name.
The share has to be available on multiple NetBIOS names in order to narrow it to a specific NetBIOS name.
It should be made clearer that NetBIOS name cannot be used by itself. Possibly, they could list it as:
{@ [@ ]}
This would show that @netbios_name is only optional when included with @sharename.
This is why all of the combinations above work, with the exception of @ .
Rainer_EMC
6 Operator
•
8645 Posts
640
0
Posted June 13th, 2007 07:00
see https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1/en_US/Offering_Technical/Technical_Documentation/300-002-675_a01_elccnt_0.pdf