Saving files over 31 characters long...

to a Windows 2003 server. Everything works great as long as I'm under 31 characters.
I'm running Mac OS X 10.6.8.
Is there a default setting on either the server or the Mac to allow for this to happen?

Last, when looking at files on the server while using my mac, all file names over 31 characters are truncated to an 8.3 format. This does not happen if looking at the server from a PC.
All files on a Windows computer have an 8.3 name, along with their long name. You just don't normally see them anymore. If you write a file with the name Movies in 2012.doc to your PC or Windows server, that will be its long name, but it will also get a short name of MOVIES~1.DOC. You should be able to verify that by opening a DOS Command line box and do a file listing.
The 31 character name limit was a requirement of OS 9 and earlier. That went away with OS X, though it took a while for apps to catch up. As an example, Word X for Mac still limited you to 31 characters. It wasn't until the 2004 version that MS finally broke that barrier. That was a fault in Word X still following old rules, not OS X's. Something MS probably did intentionally as a cross-over step so users of OS X and Office X weren't sending unreadable file names to those still using OS 9.
Anyway, I'm certain the issue it at the server. It is truncating the names based on an obsolete naming rule. Whether or not your IT group can change it without upgrading the server to more current software is something I can't answer.

Similar Messages

Saving files over vs packaging.

I am curious about what the best file structure would be for files you use over year after year.
Being a publishing company and we produce updated editions each year. Each new year contains changes, corrections, new images etc.
For the past 3 years we have done a "save as" to each individual ID file and saved each file over to a new folder each year. This takes forever moving 65+ individual ID files! From my understanding is we don't move/copy paste files to the new folder since we've had problems with file corruption in the past and don't consider it the safest way. Is there any truth to that? Or any problems moving that many files? (We're on PC's only)
All these files and their images are stored on one drive so we don't have many issues with links breaking. But we've been doing a slow save as to each file for many years.
For instance 2010 Section One becomes 2011 Section One.
Each year we archive the older year's files by packaging them and moving the packaged files to a CD for backup. Then we do a save as to our 2010 files and save those files to 2011 renaming the files accordingly.
I suppose my point is what is the quickest most effective way to save files over each year? Would moving the packaged files be better? I know that would take far less time than what we've been doing, I'm just not sure at this point. Our system has worked great with no problems...it just takes forever and I don't think it's the most effective way to do this process each year. I hope I made sense here!
Thanks for any feedback!

You take about 2010 Section One to 2011 Section One?
So I presume there are more than one section? Have you not used the Book feature in Indesign, under File>New Book and then all the sections of a book go into a book file, which controls things like the pagination (if you want) and other things? You can then package the entire book (all the sections) at the same time).
You could also copy the sections to a new folder. Then use Adobe Bridge to Batch Rename all the files in the folder? Would that help? http://www.communitymx.com/content/article.cfm?cid=A4B43
From InDesign when you use File>Open there are 3 options in the bottom left hand corner - you can choose to open the Original or a Copy and the Copy will open up as Untitled, meaning you can resave it anywhere. This works well if you're doing it on a file-by-file basis, and you can then save your files to the new location without worrying about overwriting the old ones.

Saving files over VPN to mapped drive

Hi,
looking for a solution to force users to save files to a mapped drive connected over VPN running off an SBS 2008 server.
This topic first appeared in the Spiceworks Community

You take about 2010 Section One to 2011 Section One?
So I presume there are more than one section? Have you not used the Book feature in Indesign, under File>New Book and then all the sections of a book go into a book file, which controls things like the pagination (if you want) and other things? You can then package the entire book (all the sections) at the same time).
You could also copy the sections to a new folder. Then use Adobe Bridge to Batch Rename all the files in the folder? Would that help? http://www.communitymx.com/content/article.cfm?cid=A4B43
From InDesign when you use File>Open there are 3 options in the bottom left hand corner - you can choose to open the Original or a Copy and the Copy will open up as Untitled, meaning you can resave it anywhere. This works well if you're doing it on a file-by-file basis, and you can then save your files to the new location without worrying about overwriting the old ones.

Saving files over a distance

At home, 20-30 miles away from where I work, I've got a wireless router connected to an iMac G3 via an ethernet cable ( the iMac doesn't have an airport card ) I also have a 350gig network hard drive connected to the router via an ethernet cable. When I take my MacBook home, I can connect wirelessly to my network hard drive to save my work. My question is: is it possible to configure things so that I can save my work wirelessly to my network hard drive at home from any distance, and if so, how is it done? Thank you

Depends what distance your talking about, but essentially, you need better antannae(s), or repeaters/access points...
One Mile...
http://www.tuaw.com/2006/01/23/extend-your-wireless-range-to-1-mile/
Easy things...
http://guides.radified.com/magoo/guides/wireless/wirelessnetworking07.htm
http://www.networkworld.com/columnists/2005/121205nutter.html
Extending WLAN Range with Repeaters ...
http://www.wi-fiplanet.com/tutorials/article.php/1571601

Office 2007 saving documents over mapped network drive takes abnormally long

On a new Windows 8.1 Pro 64 bit computer, I have installed Office 2007. When I attempt to save documents to a mapped network drive on a peer network (saving to a Windows 8.1 Pro 64 bit computer), I have abnormally long save times. However, when I attempt
to save documents to my computer, I have no issues. I do not have any issues when opening the files over the mapped drive.
Turning off the third-party Bullguard Internet Security antivirus and firewall makes no difference. Setting as an exception the excluded mapped drive folder makes no difference either.
I have disconnected the mapped drive and re-mapped the network drive, but this makes no difference.
I had no problem with the same software on a prior computer running the same Office 2007 version. Another computer on the network has no issues either.
Please advise how to speed up the saved documents (Word, Excel).

Hi,
As the slow to save files issue, please try the suggestion below to modify the registry:
Important
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the
registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry,
http://windows.microsoft.com/en-US/windows7/Back-up-the-registry
To start the Registry Editor, press Win + R, type "regedit.exe" in the blank box, press Enter. Then add the following registry key to the machine:
[Hkey_Current_User\Software\Microsoft\Office\12.0\Word\Options]
"DisableRobustifiedUNC"=Dword:00000001
[Hkey_Current_User\Software\Microsoft\Office\12.0\Excel\Options]
"DisableRobustifiedUNC"=Dword:00000001
I hope this can help.
Regards,
Melon Chen
TechNet Community Support

42 characters long file names in iCloud 3 photo stream

Windows icloud 3, in a shared photo-stream, makes file names with 42 random characters long. It didn't do this in iCloud 2. I have installed iCloud 3 on a windows 8.0 and 8.1 machine and two Windows 7 machines. They all do the same thing. It used to give me file names like "IMG_0001.jpg" now it gives me random file names like "01a9fc3363330464233a142486180f0c1622eb9fca.jpg" all the pictures are out order. Does anyone have fix for this?

I have never found a solution for this.
I did find a Work Around. What I do when I receive a folder full of pictures from another ios iPhone user, I copy all the photos as a batch from the PhotoStream folder into a free Windows program called "FastStone Photo Resizer" from www.FastStone.org. This program allows you to resize the photos as a batch to what ever size you wish. In my case I resize them to 2560 x 1440 which fills my 27" monitor and reduces the file size of each picture from 2MB or 3MB down to about 450 KB without degrading the picture as far as what you see on the screen.
This program will also within the same batch operation, allow you to sort the pictures by "Date Taken" which is the Date and Time the picture was taken. It gets this information from the EXIF data in the jpg file. This program will then rename the files with different numbering format options including date, time, alphanumberic and with just simple numbers starting at what ever number you wish to start with. I can get files that look like this again "IMG_0001.jpg" and have all the pictures in the correct order that they were taken. At this point, I save the pictures directly to a folder on my PC. The cool thing about this is, all the EXIF data is preserved as well. I can process a 100 pictures in less that 60 seconds. I hope this helps. For me, I can now live with this iCloud numbering defect.

File extension default no longer enabled while saving

Similar to Gregg Riley's StarOffice experience, I recently noticed that default saves for various (but not all) StarOffice "pulldown file type" selections no longer save with the correct-default extension.
I now (sometimes) have to type in the correct extension, re-check the "automatic file name extension," or re-name the file (adding the extension) after the file was saved.
I am fairly certain that this behavior has only recently begun, and wonder what could cause this new behavior. Could this be a StarOffice bug or macro-virus, or a Windows XP/Vista bug or virus?
Could opening a corrupt StarOffice file cause this issue? Could a corrupt file "reset" the defaults and cause trouble saving and re-opening similar file types?
I am searching the posts for support tips, but have not yet found a "known problem."
Sure, I could have "unchecked" this feature during save, but I have no reason to "uncheck," so that's why I am wondering if this is a known problem/phenomena.

December 03 2009
I am using Star Office Ver 9.10 Build 9399 on a Windows Vista operation system.Current SO9 is 9.1.1. When you are using VISTA, you must have your permissions set correctly.
If I use a file name on a ODT file ending in numeral "6", the file type becomes "type 6" and then the file won't open except using a text editor. I can't get the "Open with" options to even list the Star office apps, and it keeps offering Adobe PDF to open with or my Chrome Browser, and Word Pad.This sounds like operating system corruption.
I guess my next step will be to uninstall and reinstall the software off the latest web download, but for now I am working around this as I am on a big project and cant take time to screw around trying to redo things at this moment.If your problem is operating system corruption, it may be risky not to get to the root of the problem.
Phil

Mac OS X: Long ( 15 min. ) Saving File from PP Linked Comp

Is anyone else experiencing a very long time when saving a AE Linked Composition from PP?
I have several from one project .. but the whole project is only 40 min long.
All SD.

The problem is unnerving.
I have one clip .. Dynamically Linked from PP.
It is 44 seconds long.
There is approx. 18 similar files .. most are longer .. in the same 'batch' project file .. which is the only way PP and AE can handle the Dynamic Link correctly ( SEE my other post from a year ago )
When I make a small change in the 44 sec. clip and try to save the file .. it takes 7 minitues to save the project. ( the "Save Project" dialog box says 18 min. inaccuratly. )
Everytime.
This is completely unacceptable .. and one of my latest giant peevs about the workflow of this "Master Suite".
Again .. from my other posts .. there is only 1/2 a core processor ( out of 12 cores ) running in the Activity Monitor .. and I have a new fast RAID running ( at least I guess its fast )
Any thoughts?

Crashing When Saving Photoshop File Over Network

Photoshop & InDesign CS3 crashes whenever I try to save a file over the network to a another shared Mac Pro computer. Another Mac Pro on the network can save to the shared computer without a problem.
SPECIFICS
- Three Macs and a 3 PC's on Ethernet network
-Problem started after upgrading to Leopard
- I have tried reinstalling the entire Creative Suite without Version Cue
- Tried deleting the com.adobe.mediabrowser.p.ist and Photoshop.plist preferences.
- If I create a new file on my computer and then immediately save it, it usually does not crash on the first save. But after I do a few things to the file and then try to save again, it hangs up giving me the spinning pinwheel with the message in the Force Quit dialog window that Photoshop is not responding.
+- I am unable to force quiet Photoshop; I have to do a hard reboot.+
Adobe tech support believes it is a network problem, any ideas what might be causing the problem?
Are there any know issues with Leopard and CS 3 with certain network configurations?

I have experienced issues with saving photoshop files over a network since upgrading to 10.5.3
This is a major issue, and one that apple seems quite about.
See related response on Adobe.com
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403815&sliceId=2

Intermittent error saving attachments from mail: "Names longer than 31 characters are not supported on the destination volume."

I am reciving intermittent errors saving attachments from mail: "Names longer than 31 characters are not supported on the destination volume."

I am seeing this too.
I Posted in similar thread 6704033
Error when saving calendar exports-names longer than 31 characters not supported on the destination volume.
Very spooky. Not always reproducible, but it happened to me while using Office365-Outlook web-based email (saving a PDF).
RE: the suggestion, checking security box "allow apps downloaded from all sites" I would really rather not do that.
On my system it is set to allow "Mac App store and identified developers."
Oh sorry, I'm on Yosemite, I see this is Mav forum...

Saved files take a long time to appear on Server or Desktop

We have a network of nearly 40 macs, Panther Server, mostly panther clients but the newer machines are on 10.4.
All of the newer machines exhibit the problem in that files saved to the server or to the desktop take a long time to appear.
It appears to be a refresh issue, as on the server other clients can see the file straight away and locally the files can be seen on the desktop via the terminal.
Force quitting the finder forces the files to appear but this is not a solution.
The clients which have the problem all run 10.4 and the Server is 10.3. The 10.3 clients do not exhibit the same issues.

I have also seen this issue at one of my larger clients (50+ workstations).
The issues seems isolated to 10.4.5 or higher. Our workstations with 10.4.2 did not exhibit this problem. It is not an issue with hardware (we have seen this on an iBook G3 and various G5 tower models). Nor does it appear to be server-related: we have seen the issue saving locally with no servers mounted. We have seen the issue when saving from Adobe CS apps, MS Office apps, and from system apps (like TextEdit). Deleting com.apple.finder.plist from the user's home Library and then relaunching the Finder gets relief for a short time but the problem returns soon after. plutil reports the file is OK. The volume directory is fine, the permissions check out, and caches have been purged, to no avail.
Like you, summersault, I am able to see the saved file on the command line, and when my users Force Quit the Finder, the file appears. Other workarounds, like the Nudge contextual menu, do not work.
I have submitted the error via apple.com/feedback and would encourage you to do the same.
Anxiously awaiting 10.4.7...
-B
Mac OS X (10.4.6)

Saving files to a specific folder

I used to be a PC, now I am a Mac, learning fast, but I have a problem in saving files from the web. I am using OS 10.4.7
I am using Firefox and Thunderbird.
When I try to save email or a picture from a web site I am presented with a Menu; Save as, Where and Format. The 'Where' is the problem.
When I click 'WHERE', I am presented with a list;
Network
Mac HD 80
Mac HD 60
Desktop
MCMP (HOME, where all my different folders are)
Applications
Movies
Music
Picures
When I click on MCMP, my home with all my sub folders, there is no way to save the file any place but just in MCMP. I have no options which folder in MCMP or sub folder of a main topic folder. Saving to MCMP just puts the file in with all my different folders.
How do I direct exactly which folder the item is to be saved into.
Thank You
WM300

wm
Spring loaded folders: Drag a file to a flder, hold it over it and the folder will open. You can use this to drop files into sub folders and so on. The timing on how long you have to hold is controlled in the Finder preferences -> General Pane.
Another possibilty for your original question is to use Default Folder X, a shareware, that makes navigating open and close dialogues very easy.
http://www.stclairsw.com/
Regards
TD

Saving file to network location

Hello all of you,
I encounter an issue with InDesign CS5 when it comes to opening and saving files to a network location. I added my company's ftp server to Windows 7 and it appears correctly in the My computer overview (there's an additional line besides the hard discs, DVD player, et cetera). The connection to the server functions fine, no issues here. No problem exists when opening files from this server from within InDesign; I can do whatever I want. Only when I try to save a file the network location isn't displayed anymore within the My computer overview in the InDesign "Save as" dialog box. The network location however appears in the pull-down menu at the top of the dialog box (and nested as part of My computer ...), but when I pick it there, it won't show the context of the server. Additionally logging onto the server (it's IP-based and anonymous logon) doesn't change a thing. Trying to save in the empty server space InDesign returns a "Can't save here" error message.
Does anyone know how to solve this issue? Building the document locally and then copying back to the server isn't a solution, because all external content that is linked in the document resides on the server.
Best regards,
Luc Peulen

Does anyone know how to solve this issue? Building the document locally and then copying back to the server isn't a solution, because all external content that is linked in the document resides on the server.
Scott is basically right. Lots of ID users work over network connections without issue, but if something is going wrong, it's the first place to look. I wouldn't have thought it possible to work in InDesign over a FTP connection!
If you can get Windows to access that server as if it were just another drive (using "Map network drive" in Explorer) then it should work normally. However, a generic Adobe phone tech wouldn't help you figure out why it wouldn't work - there are simply too many variables in a network environment for a generic first-level tech to figure out.
In the short term, the only solution I can suggest is:
Retrieve all of that external content that is linked in the document, and the InDesign document, at the same time, & store it on your local hard drive.
Do your work.
Save & package.
Upload the entire package back to the server.
Long-term, you'd need to talk to your own IT staff to troubleshoot the connection between your workstation and the FTP server. If you can get information about your network from them to post here, I bet that someone will make suggestions to pass on to your IT staff that will actually work.

EFS Encrypted Files over home workgroup network via WebDAV avoiding Active Directory fixing Access Denied errors

This is for information to help others
KEYWORDS:
- Sharing EFS encrypted files over a personal lan wlan wifi ap network
- Access denied on create new file / new fold on encrypted EFS network file share remote mapped folder
- transfer encryption keys / certificates
- set trusted delegation for user + computer for EFS encrypted files via
Kerberos
- Windows Active Directory vs network file share
- Setting up WinDAV server on Windows 7 Pro / Ultimate
It has been a long painful road to discover this information.
I hope sharing it helps you.
Using EFS on Windows 7 pro / ultimate is easy and works great. See
here and
here
So too is opening + editing encrypted files over a peer-to-peer Windows 7 network.
HOWEVER, creating a new file / new folder over a peer-to-peer Windows 7 network
won't work (unless you follow below steps).
Typically, it is only discovered as an issue when a home user wants to use synchronisation software between their home computers which happens to have a few folders encrypted using windows EFS. I had this issue trying to use GoodSync.
Typically an "Access Denied" error messages is thrown when a \\clientpc tries to create new folder / new file in an encrypted folder on a remote file share \\fileserver.
Why such a EFS drama when a network is involved?
Assume a home peer-to-peer network with 2pc: \\fileserver and \\clientpc
When a \\clientpc tries to create a new file or new folder on a \\fileserver (remote computer) it fails. In a terribly simplified explanation it is because the process on \\fileserver that is answering the network requests is a process working for a user on
another machine (\\clientpc) and that \\fileserver process doesn't have access to an encryption certificate (as it isn't a user). Active Directory gets around this by using kerberos so the process can impersonate a \\fileserver user and then use their certificate
(on behalf of the clienpc's data request).
This behaviour is confusing, as a \\clientpc can open or edit an existing efs encrypted file or folder, just can't create a new file or folder. The reason editing + opening an encrypted file over a network file share is possible is because the encrypted
file / folder already has an encryption certificate, so it is clear which certificate is required to open/edit the file. Creating a new file/folder requires a certificate to be assigned and a process doesn't have a profile or certificates assigned.
Solutions
There are two main approaches to solve this:
     1) SOLVE by setting up an Active Directory (efs files accessed through file shares)
          EFS operations occur on the computer storing the files.
          EFS files are decrypted then transmitted in plaintext to the client's computer
          This makes use of kerberos to impersonate a local user (and use their certificate for encrypt + decrypt)
     2) SOLVE by setting up WebDAV (efs files accessed through web folders)
           EFS operations occur on the client's local computer
           EFS files remain encrypted during transmission to the client's local computer where it is decrypted
           This avoids active directory domains, roaming or remote user profiles and having to be trusted for delegation.
           BUT it is a pain to set up, and most online WebDAV server setup sources are not for home peer-to-peer networks or contain details on how to setup WebDAV for EFS file provision
         READ BELOW as this does
Create new encrypted file / folder on a network file share - via Active Directory
It is easily possible to sort this out on a domain based (corporate) active directory network. It is well documented. See
here. However, the problem is on a normal Windows 7 install (ie home peer-to-peer) to set up the server as part of an active directory domain is complicated, it is time consuming it is bulky, adds burden to operation of \\fileserver computer
and adds network complexity, and is generally a pain for a home user. Don't. Use a WebDAV.
Although this info is NOT for setting up EFS on an active directory domain [server],
for those interested here is the gist:
Use the Active Directory Users and Computers snap-in to configure delegation options for both users and computers. To trust a computer for delegation, open the computer’s Properties sheet and select Trusted for delegation. To allow a user
account to be delegated, open the user’s Properties sheet. On the Account tab, under Account Options, clear the The account is sensitive and cannot be delegated check box. Do not select The account is trusted for delegation. This property is not used with
EFS.
NB: decrypted data is transmitted over the network in plaintext so reduce risk by enabling IP Security to use Encapsulating Security Payload (ESP)—which will encrypt transmitted data,
Create new encrypted file / folder on a network file share - via WebDAV
For home users it is possible to make it all work.
Even better, the functionality is built into windows (pro + ultimate) so you don't need any external software and it doesn't cost anything. However, there are a few hotfixes you have to apply to make it work (see below).
Setting up a wifi AP (for those less technical):
   a) START ... CMD
   b) type (no quotes): "netsh wlan set hostednetwork mode=allow ssid=MyPersonalWifi key=12345 keyUsage=persistent"
   c) type (no quotes): "netsh wlan start hostednetwork"
Set up a WebDAV server on Windows 7 Pro / Ultimate
-----ON THE FILESERVER------
   1 click START and type "Turn Windows Features On or Off" and open the link
       a) scroll down to "Internet Information Services" and expand it.
       b) put a tick in: "Web Management Tools" \ "IIS Management Console"
       c) put a tick in: "World Wide Web Services" \ "Common HTTP Features" \ "WebDAV Publishing"
       d) put a tick in: "World Wide Web Services" \ "Security" \ "Basic Authentication"
       e) put a tick in: "World Wide Web Services" \ "Security" \ "Windows Authentication"
       f) click ok
       g) run HOTFIX - ONLY if NOT running Windows 7 / windows 8
KB892211 here ONLY for XP + Server 2003 (made in 2005)
KB907306 here ONLY for Vista, XP, Server 2008, Server 2003 (made in 2007)
2 Click START and type "Internet Information Services (IIS) Manager"
3 in IIS, on the left under "connections" click your computer, then click "WebDAV Authoring Rules", then click "Open Feature"
       a) on the right side, under Actions, click "Enable WebDAV"
4 in IIS, on the left under "connections" click your computer, then click "Authentication", then click "Open Feature"
       a) on the "Anonymous Authentication" and click "Disable"
       b) on the "Windows Authentication" and click "Enable"
      NB: Some Win 7 will not connect to a webDAV user using Basic Authentication.
        It can be by changing registry key:
           [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WebClient\Parameters]
           BasicAuthLevel=2
       c) on the "Windows Authentication" click "Advanced Settings"
           set Extended Protection to "Required"
       NB: Extended protection enhances the windows authentication with 2 security mechanisms to reduce "man in the middle" attacks
5 in IIS, on the left under "connections" click your computer, then click "Authorization Rules", then click "Open Feature"
       a) on the right side, under Actions, click "Add Allow Rule"
       b) set this to "all users". This will control who can view the "Default Site" through a web browser
       NB: It is possible to specify a group (eg Administrators is popular) or a user account. However, if not set to "all users" this will require the specified group/user account to be used for logged in with on the
clientpc.
       NB: Any user account specified here has to exist on the server. It has a bug in that it usernames specified here are not validated on input.
6 in IIS, on the left under "connections" click your computer, then click "Directory Browsing", then click "Open Feature"
       a) on the right side, under Actions, click "Enable"
HOTFIX - double escaping
7 in IIS, on the left under "connections" click your computer, then click "Request Filtering", then click "Open Feature"
       a) on the right side, under Actions, click "Edit Feature Settings"
       b) tick the box "Allow double escaping"
     *THIS IS VERY IMPORTANT* if your filenames or foldernames contain characters like "+" or "&"
     These folders will appears blank with no subdirectories, or these files will not be readable unless this is ticked
     This is safe btw. Unchecked (default) it filters out requests that might possibly be misinterpreted by buggy code (eg double decode or build url's via string-concat without proper encoding). But any bug would need to be in IIS basic
file serving and this has been rigorously tested by microsoft, so very unlikely. Its safe to "Allow double escaping".
8 in IIS, on the left under "connections" right click "Default Web Site", then click "Add Virtual Directory"
       a) set the Alias to something sensible eg "D_Drive", set the physical path
       b) it is essential you click "connect as" and set
this to a local user (on fileserver),
       if left as "pass through authentication" a client won't be able to create a new file or folder in an encrypted efs folder (on fileserver)
             NB: the user account selected here must have the required EFS certificates installed.
                        See
here and
here
        NB: Sharing the root of a drive as an active directory (eg D:\ as "D_Drive") often can't be opened on clientpcs.
      This is due to windows setting all drive roots as hidden "administrative shares". Grrr.
       The work around is on the \\fileserver create an NTFS symbollic link
          e.g. to share the entire contents of "D:\",
                on fileserver browse to site path (iis default this to c:\inetpub\wwwroot)
                in cmd in this folder create an NTFS symbolic link to "D:\"
                so in cmd type "cd c:\inetpub\wwwroot"
                then in cmd type "mklink /D D_Drive D:\"
        NB: WebDAV will open this using a \\fileserver local user account, so double check local NTFS permissions for the local account (clients will login using)
         NB: If clientpc can see files but gets error on opening them, on clientpc click START, type "Manage Network Passwords", delete any "windows credentials" for the fileserver being used, restart
clientpc
9 in IIS, on the left under "connections" click on "WebDAV Authoring Rules", then click "Open Feature"
       a) click "Add authoring rules". Control access to this folder by selecting "all users" or "specified groups" or "specified users", then control whether they can read/write/source
       b) if some exist review existing allow or deny.
           Take care to not only review the "allow access to" settings
           but also review "permissions" (read/write/source)
       NB: this can be set here for all added virtual directories, or can be set under each virtual directory
10 Open your firewall software and/or your router. Make an exception for port 80 and 443
       a) In Windows Firewall with Advanced Security click Inbound Rules, click New Rule
             choose Port, enter "80, 443" (no speech marks), follow through to completion. Repeat for outbound.
          NB: take care over your choice to untick "Public", this can cause issues if no gateway is specified on the network (ie computer-to-computer with no router). See "Other problems+fixes"
below, specifically "Cant find server due to network location"
       b) Repeat firewall exceptions on each client computer you expect to access the webDAV web folders on
HOTFIX - MAJOR ISSUE - fix KB959439
11 To fully understand this read "WebDAV HOTFIX: RAW DATA TRANSFERS" below
      a) On Windows 7 you need only change one tiny registry value:
           - click START, type "regedit", open link
           -browse to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MRxDAV\Parameters]
           -on the EDIT menu click NEW, then click DWORD Value
           -Type "DisableEFSOnWebDav" to name it (no speech marks)
           -on the EDIT menu, click MODIFY, type 1, then click OK
           -You MUST now restart this computer for the registry change to take effect.
      b) On Windows Server 2008 / Vista / XP you'll FIRST need to
download Windows6.0-KB959439 here. Then do the above step.
         NB microsoft will ask for your email. They don't care about licence key legality, it is more to keep you updated if they modify that hotfix
12 To test on local machine (eg \\fileserver) and deliberately bypass the firewall.
      a) make sure WebClient Service is running
            (click START, type "services" and open, scroll down to WebClient and check its status)
      b) Open your internet software. Go to address "http://localhost:80" or "http://localhost:80"
            It should show the default "IIS7" image.
            If not, as firewall and port blocking are bypassed (using localhost) it must be a webDAV server setting. Check "Authorization Rules" are set to "Allow All Users"
      c) for one of the "virtual directories" you added (8), add its "alias" onto "http://localhost/"
                e.g. http://localhost/D_drive
            If nothing is listed, check "Directory Browsing" is enabled
13 To test on local machine or a networked client and deliberately try and access through the firewall or port opening of your router.
      a) make sure WebClient Service is running
            (click START, type "services" and open, scroll down to WebClient and check its status)
      b) open your internet software. Go to address "http://<computer>:80" or "http://<computer>:80".
              eg if your server's computer name is "fileserver" go to "http://fileserver:80"
              It should show the default "IIS7" image. If not, check firewall and port blocking.
              Any issue ie if (12) works but (13) doesn't, will indicate a possible firewall issue or router port blocking issue.
     c) for one of the "virtual directories" you added (8), add its "alias" onto "http://<computername>:80/"
               eg if alias is "C_driver" and your server's computer name is "fileserver" go to "http://fileserver:80/C_drive"
               A directory listing of files should appear.
--- ON EACH CLIENT ----
HOTFIX - improve upload + download speeds
14 Click START and type "Internet Options" and open the link
      a) click the "Connections" tab at the top
      b) click the "LAN Settings" button at the bottom right
      c) untick "Automatically detect settings"
HOTFIX - remove 50mb file limit
15 On Windows 7 you need only change one tiny registry value:
      a) click START, type "regedit", open link
    b) browse to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WebClient\Parameters]
       c) click on "FileSizeLimitInBytes"
       d) on the EDIT menu, click MODIFY, type "ffffffff", then click OK (no quotes)
HOTFIX - remove prompt for user+pass on opening an office or pdf document via WebDAV
16 On each clientpc click START, type "Internet Options" and open it
         a) click on "Security" (top) and then "Custom level" (bottom)
         b) scroll right to the bottom and under "User Authentication" select "Automatic logon with current username and password"
         SUCH an easy fix. SUCH an annoying problem on a clientpc
   NB: this is only an issue if the file is opened through windows explorer. If opened through the "open" dialogue of the software itself, it doesn't happen. This is as a WebDAV mapped drive is consdered a "web folder" by windows
explorer.
TEST SETUP
17 On the client use the normal "map network drive"
            e.g. server= "http://fileserver:80/C_drive", tick reconnect at logon
            e.g. CMD: net use * "http://fileserver:80/C_drive"
         If it doens't work check "WebDAV Authoring Rules" and check NTFS permissions for these folders. Check that on the filserver the elected impersonation user that the client is logging in with (clientpc
"manage network passwords") has NTFS permissions.
18 Test that EFS is now working over the network
       a) On a clientpc, map network drive to http://fileserver/
       b) navigate to a folder you know on the \\flieserver is encrypted with EFS
       c) create a new folder, create a new file.
           IF it throws an error, check carefully you mapped to the WebDAV and not file share
              i.e. mapped to "http://fileserver" not "\\fileserver"
           Check that on clientpc the required efs certificate is installed. Then check carefully on clientpc what user account you specified during the map drive process. Then check on the \\fileserver this
account exists and has the required EFS certificate installed for use. If necessary, on clientpc click START, type "Manage Network Passwords" and delete the windows credentials currently in the vault.
       d) on clientpc (through a webDAV mapped folder) open an encrypted file, edit it, save it, close it. On the \\fileserver now check that file is readable and not gobble-de-goup
       e) on clientpc copy an encrypted efs file into a folder (a webDAV mapped folder) you know is not encrypted on \\fileserver. Now check on the \\fileserver computer that the file is readable and not gobble-de-goup (ie the
clientpc decrypted it then copied it).
        If this fails, it is likely one in IIS setting on fileserver one of the shared virtual directories is set to: "pass through authentication" when it should be set to "connect as"
        If this is not readable check step (11) and that you restarted the \\fileserver computer.
19 Test that clients don't get the VERY annoying prompt when opening an Office or PDF doc
      a) on clientpc in windows explorer browse to a mapped folder you know is encrypted and open an office file and then PDF.
            If a prompt for user+pass then check hotfix (16)
20 Consider setting up a recycling bin for this mapped drive, so files are sent to recycling bin not permanently deleted
      a) see the last comment at the very bottom of
this page:
Points to consider:
   - NB: WebDAV runs on \\fileserver under a local user account, so double check local NTFS permissions for that local account and adjust file permissions accordingly. If the local account doesn't have permission, the webDAV / web folder share won't
either.
- CONSIDER: IP Security (IPSec) or Secure Sockets Layer (SSL) to protect files during transport.
MORE INFO: HOTFIX: RAW DATA TRANSFERS
More info on step (11) above.
Because files remain encrypted during the file transfer and are decrypted by EFS locally, both uploads to and downloads from Web folders are raw data transfers. This is an advantage as if data is intercepted it is useless. This is a massive disadvantage as
it can cause unexpected results. IT MUST BE FIXED or you could be in deep deep water!
Consider using \\clientpc to access a webfolder on \\fileserver and copying an encrypted EFS file (over the network) to a web folder on \\fileserver that is not encrypted.
Doing this locally would automatically decrypt the file first then copy the decrypted file to the non-encrypted folder.
Doing this over the network to a web folder will copy the raw data, ie skip the decryption stage and result in the encrypted EFS file being raw copied to the non-encrypted folder. When viewed locally this file will not be recognised as encrypted (no encryption
file flag, not green in windows explorer) but it will be un-readable as its contents are still encrypted. It is now not possible to locally read this file. It can only be viewed on the \\clientpc
There is a fix:
      It is implimented above, see (11) above
      Microsoft's support page on this is excellent and short. Read "problem description" of "this microsoft webpage"
Other problems + fixes
PROBLEM: Can't find server due to network location.
     This one took me a long time to track down to "network location".
     Win 7 uses network locations "Home" / "Work" / "Public".
     If no gateway is specified in the IP address, the network is set to '"unidentified" and so receives "Public" settings.
     This is a disaster for remote file share access as typically "network discovery" and "file sharing" are disabled under "Public"
     FIX = either set IP address manually and specify a gateway
     FIX = or force "unidentified" network locations to assume "home" or "work" settings -
read here or
here
     FIX = or change the "Public" "advanced network settings" to turn on "network discovery" and "file sharing" and "Password Protected Sharing". This is safe as it will require a windows
login to gain file access.
PROBLEM: Deleting files on network drive permanently deletes them, there is no recycling bin
       By changing the location of "My Contacts" or similar to the root directory of your mapped drive, it will be added to recycling bin locations
      Read
here (i've posted a batch script to automatically make the required reg files)
I really hope this helps people. I hope the keywords + long title give it the best chance of being picked up in web searches.

What probably happens is that processes are using those mounts. And that those processes are not killed before the mounts are unmounted. Is there anything that uses those mounts?

Quicktime on Windows clients can't open files in folders with long names!!

Hi,
we've got a really strange problem. We have an Intel Xserve with Leopard Server 10.5.4 which is sharing files over SMB. Everything works fine, except Quicktime on Windows clients (XP Pro and Vista). It looks like the length of the folder names is the problem. If a single folder in the path to the mov has a name that's longer than 8 characters, Quicktime fails with "Error -43: A file could not be found."
x:\test1234\test.mov works
x:\test12345\test.mov doesn't work
Same for UNC paths. VLC on Win and Quicktime on OS X work without problems over SMB. Also the problem doesn't exist on other Samba based fileservers.
Any ideas? Perhaps some smb.conf tweaks to fix this?
Best regards

Just found this post
http://discussions.apple.com/thread.jspa?threadID=1360461&tstart=0
Seems like a well known problem

Saving files over 31 characters long...

Similar Messages

Maybe you are looking for