Click for MacWindows
Last updated April 6, 2005
On this page:
For information about Windows clients and Mac OS X Server, see our Mac OS X Server Cross-platform Issues page.
Have you found an AppleShare IP problem with Windows clients? Have you found a new solution? Let us know.
The Macintosh Managers mailing list is a ten-year-old list that deals with troubleshooting issues with networks of Macs or Macs and other platforms. Note that as of April 20, 2000, the list has a new server .Anyone, including non-subscribers, can search the mac-mgrs archives.
AppleShare IP began supporting Windows clients with version 6.0, which contains a server that provides server message block/common internet file system (SMB/CIFS) file sharing, the native Microsoft file sharing service. SMB/CIFS is the Microsoft equivalent of AFP (AppleShare Filing Protocol) used in Mac file sharing.
Apple bug reports:
AppleShare IP Bug Fixes and update history
(AppleShare IP supports both Macintosh and Windows clients.)
Corruption of Windows files
Here are some descriptions of some of the known file-corruption problems (listed above), as well as possibly some unknown problems:
April 30, 1999
"[Regarding] readers who use AppleShare IP 6 server/OS 8.5 with Windows machines regarding files being lost or corrupted with PC applications using the file server: I just had this problem with a couple of AutoCad files (saved file names with 0K) and have been searching Apple Tech Exchange and other sites with little luck. I find quite a bit of evidence of recurring ASIP network problems like this with PC applications such as WordPerfect, Autocad, PowerPoint, etc but no mention of what the problem may be (nor any solution)."
April 30, 1999
"AppleShare ip 6.1 seems to be very sensitive to any form of compression running over the network. if they are running network compression software that could be the problem. We are unable at this time to run Copydoubler over the network. Sometimes files are ok, sometimes corrupt."
April 30, 1999
I too have experienced file corruption from a Windows client saving to AppleShare 6.x. The initial problem began with AppleShare 6.0 running Mac OS 8.1. Windows NT clients were causing all of the date and times of files to be incorrect. It was similar to PRAM problems on a Mac. I did not check the Windows 95 clients.
Researching the Apple tech notes revealed this to be a known problem. Upgrading to ASIP 6.1 is recommended to fix the problem. I did so and the dates stopped changing. Within a few days, I happen to experience the file corruption problem from Windows 95 when saving to the server. This time the dates were fine, but the file would not open in the application that created it. The file was a PowerPoint97 presentation and the thumbnail was visible in the web view within the Win95 desktop window.
Editor's note: this is the PowerPoint 97 bug described above.
May 5, 1999
We use a G3 Server with OS8.1 and ASIP 6.1.1 (not for long). We have had repeated corruption of mission critical data on the server when accessed with our Windows 98 clients, apparently from ASIP 6.1.1. We have done extensive testing (on and off site) eliminating all variables but that.
We use a Omnis7 database files, and it appears there is some sort of record locking/writing issue. There might be some sort of caching go on on the server that we just can't eliminate. We get duplicate Record Sequence Numbers, which is supposed to be impossible.
We are seriously considering a different OS (Linux/NT) for our server, these problems just won't go away and we can't afford to waste anymore time on them.
May 6, 1999
I have run into a problem with Drawbase (PC CAD program) with Appleshare IP. Saving files to the local machine then copying them to the ASIP 6.11 server works fine....but if we save directly to the server....file corruption occurs.
ASIP and WordPerfect corruption
May 17, 1999
Arthur Deptford from the United Kingdom is interested in feedback:
We have been having serious problems with AppleShare IP 6.1 and WordPerfect 8.
We have a new G3 server (B/W) running AppleShare IP 6.1 configured for Windows file sharing. All Macs run 8.5.1 and PCs run Windows 95. Whenever PC users save files from WordPerfect 8 onto the server and later try to reopen them, the files have become corrupted. Usually the PC freezes as soon as the document is opened and has to be rebooted.
WordPerfect works perfectly when files are saved onto a local disk or are copied onto the server via 'drag & drop' or Windows explorer (although they still have to be copied back onto a local drive before they can be opened successfully).Once there has been an unsuccessful attempt to open a WordPerfect file on the server the file is garbled and unusable. All other programs Mac and PC work perfectly for us.
Apple's server forums site has a few similar reports (including a few about CAD programs, although we don't use these).
[You can read one post here and another here.]
ASIP 6.2 fix:
(August 2, 1999) Arthur Deptford reports that AppleShareIP 6.2 fixed the problem:
We have just upgraded to Appleshare IP 6.2 and it appears to have solved the WordPerfect for Windows incompatibility completely.
May 17, 1999
We have an AWS 7350 with OS 8.5.1, ASIP 6.1.1, APS DAT drive and two Hard Drives: 4 GB internal SCSI and 4.3 GB external UW SCSI with Adaptec 2940UW card. Mac users work from their hard drives and use server only for backup. PC users mainly use Autocad LT 98 and Autocad 14 and work from files which reside on the 4.3UW.
As previously noted on Apple Tech Exchange, this is our fourth "event" (Server hangs and some recently worked on AutoCAD files go to 0.0K). The first event occurred at the same time that the AutoCAD users had filled their 1 gig SCSI hard drive to only 6% free space. The second and third occurred after their drive was replaced with an UWdrive formerly dedicated to a graphics station, but unused for the past year. A firmware patch from Adaptec for a 2940UW was downloaded and installed 23May99. After installation and restart, no more problems occurred until this morning, 10May99.
One of the AutoCAD 14.0 (I will try 14.01 patch) users was saving, got hung and apparently shortly afterward the server hung. All 4 AutoCAD stations were hung, and neither Macs or PC's could connect to the server when I was informed. I am now rethinking an error message I found with AppleShare IP FirstAid after the first crash after the UW card was installed:
- Begun: 5/10/1999 1:06:54 pm
- Analyzing PDS file·
- Verifying low-level structures·
- Max node depth: 5
- Root node index: 979
- Number of records: 19435
- First node index: 20
- Last node index: 1
- Node size: 512
- Max key length: 37
- Number of nodes: 2448
- Number of free nodes: 128
- Number of index nodes: 251
- Number of header nodes: 1
- Number of map nodes: 1
- Number of leaf nodes: 2067
- Number of used nodes: 2320
- Number of unused nodes: 128
- Number of records: 21756
- Checking the header·seems OK.
- Checking nodes·
- Bad depth on map node # 2040 (5 != 0).
- nodes seem okay.
Summary of node errors:
- Number of invalid node depths: 1
- Number of invalid node types: 0
- Number of invalid Resv2 values: 0
- ·node check complete.
- Verification complete. Problems were found.
I had been ignoring this message (and our Mac consultants could find no info on it), after the Adaptec firmware upgrade apparently fixed the problem.
I got the same message after today's crash and ASIP First Aid can't repair it. Disk First Aid found a "MountCheck" error on the 4.3UW hard drive, and repaired it. No errors found on the internal Hard drive used by Mac users and OS 8.5.1 and ASIP 6.1.1.
Does anybody know what "map node #2040" is and how(or if) it can be fixed?
One of four Autocad users working on files on server hard drive "hangs", then server and all AutoCAD users hang. After Server restarted, some AutoCAD files and backup files are 0.0K. Files can be restored from the AutoCAD file in the Temp folder on the users computer. Not all files are "zeroed", and we have found that in one of the three incidents we have experienced over the past two months, some of the files "zeroed" had not been worked on for at least 1/2 hr. prior to hang.
I spoke with Ben Thomas at Apple tech support in Austin. He reminded me that Apple Menu Options is best removed from Server's OS. We have done this (yesterday).
We also tried deliberately shutting down the Server while an AutoCAD user was connected. Error message reported unable to save, but there was no hang. When Server was brought back up, files were still complete and usable. Neither was 0.0k.
July 28, 1999
Arthur Deptford has a problem with Word files that can't be used or deleted:
As an update to an e-mail I posted about WordPerfect corruption with Applshare IP6.1. Here is a new slightly less serious, problem. Perhaps I'm being a bit harsh blaming AppleShare but It's definately server activity that's causing the problem. I would be interested in knowing if anyone knows whether Appleshare 6.2 has solved any Windows client problems.
One of our PC users has problems with some MS Word files on the server hard disk. Once he has closed the file/s and then tries to re-open them his computer tells him they are in use. The only way to use them is when
Word offers to save them under another name.
The original files are unusable by any computer on the network (Mac or PC) even when the original users PC is switched off (so no chance that the file is somehow in use). We have also been unable to move or delete these files. The files can be moved to the Trash only by physically using the server, but cannot be deleted (although we havn't had a chance to re-boot the server yet.
(Click here to read about other file corruption problems.)
Note: This is a known bug fixed with AppleShare IP 6.3.1.
May 3, 1999
After the server (Blue G3/8.5.1/ASIP6.1.1) has been running a few days, SMB clients will only see the first 6 items of any volume or folder contained on that volume. Rebooting the server (and then the client) restores normal function. This is not fun - I have to come in every 3 days late at night and reboot the server and all client workstations (~50) to insure that things work smoothly and seamlessly for the users.
I have seen no mention of this in the TIL or other discussion forums.
November 12, 1999
We have talked to many AppleShare people at Apple and they say they can NOT fix this one. We rebuilt the AppleShare Server from scratch.
After 24-30 hours of operation (pretty consistent) ALL Windows 95/98 users when accessing ANY of the 10 volumes on the AppleShare server will only display 6 folders or files per subdirectory. No More No Less. Windows NT workstation is fine and sees all folders and files. The 95/98 systems can see ALL Volumes and Files on all other NT Servers.
This seems to be a SMB problem for JUST 95/98. Refreshing, rebooting the 95/98 systems do not help. Even though you can only see 6 folders or files per subdirectory if you get into DOS on these same 95/98 systems you can see all of the folders and files when you do a DIR. Rebooting the server makes it work again.
Stock 256 meg RAM G3 Server with 2 - 9 gig HD. Stock Mac OS 8.6, stock AppleShare 6.2, fresh install of both. We have 100 Mac's and 30 Windows 95,98 and 10 Windows NT systems running on the network. The network is divided into 55 segments with Cisco and Cabletron Switches. Only 14 devices per segment. File, Web and Printing Sharing is on. e-mail off. Settings for AppleShare activity are at 85% and Cache in AppleShare is set to MAXIMUM per Apple. Virtual is OFF. Two hard drives set to 10 volumes and 70,000 files total.
All Macintoshes over AppleShare and TCP/IP, Web and Print Spoolers work fine. Never fails, nothing unusual. No speed problems. Many other Linux and Windows NT Servers which also are running fine. Pretty straight forward single ZONE AppleTalk network with about 100 users. The network uses mostly TCP/IP with about 250 Class C addresses used.
December 10, 1999
A reader maned Mathew confirms the problem of Windows 95/98 clients seeing only the first 6 items on an AppleShare IP 6.x server. However, he says that all of the items are visible from the DOS prompt. The problem is only in Windows.
March 16, 2000
We have had this problem for a long time and I found an authorized apple service place that agreed to replace the mainboard and CPU before the warranty ran out and by golly it worked. The server has been up and running for 3 weeks in a row. That is a record it has never been more than 3 days. To all those that have this problem get that mainboard replaced. I still have an open case with apple and I am about to call them back and tell them that we did this and that they should know that there is a problem.
Somewhat Similar problem
Mike Benges reports of a somewhat similar problem.
We are running Mac OS 9 servers with ASIP 6.3.
When any of the NT computers open and save a file, the attributes are changed so that the file is invisible and locked the file then disappears from the Mac server because it becomes invisible. We have 3 Mac servers and they all do the same thing. We have not be able to find any reason for this problem, but it is very consistent.
November 12, 1999
After upgrading two of my Macs that have AppleShare IP 6.2 software to 6.3, the File Server won't startup after restarting, even with the "Start Server at system startup" option checked on. I have to manually start the File Server. The Print Server starts up fine. I've trashed the prefs file and that didn't help.
The complete reinstall of AS 6.2 and doing the upgrade didn't help. It was my "Users and Groups Data File" preference file being corrupted. I replaced it with the one that is installed with the Mac OS system. I had to import my users and groups info and redefine the shared volumes. Doing that fixed my problem.
Apple fixed this problem with AppleShare IP 6.3.1 update:
The AppleShare IP Registry looks in the Users & Groups Data File for the application to launch in order to start the Web & File server. When a previous version of AppleShare IP is upgraded to AppleShare IP 6.3, the AppleShare IP Registry can no longer find the correct application to launch, and thus the Web & File server cannot start up at system startup time. The AppleShare IP Registry 6.3.1 update fixes this problem by updating the entry in the Users & Groups Data File.
Long file names and DOS
November 23, 1999 -- Alan Lok reports of a problem with AppleShare IP 6.2 and 6.3 when accessed from the DOS shell. When accessing files on the ASIP server from the PC DOS shell, the long file names of the file is permanently lost. He has this problem with Macromedia Director files. Lok's full description of the problem is on our AppleShare IP page. If you've seen this problem, please let us know.
In a FAT/FAT32 partition, DOS stores 2 names, the regular and LFN, so you are absolutely correct. In a NTFS or foreign file system (such as a network share), it is the responsibility of the server to provide a long filename as well as a 8.3 filename equivalent for legacy [16-bit apps] support.
That is what I have done to reproduce the problem:
All the long filenames are lost when you check the destination copy, even through you can do the same thing from an NT shared drive with no problems.
In fact, performing any operations in DOS Shell that involves Long Filenames will not work or give an error "Invalid Function", and doing any file operations in DOS Shell on an ASIP shared drive that has long filename will have its name truncated to FILENA~1 (or something with ~1) - effectively killing the LFN.
Whatever I say only affects DOS Shell ops done on an ASIP shared drive, and not for any other servers or drives.
I have a standard G3 400 MHz (Blue box) machine running MacOS 8.6/ASIP 6.2, and subsequently running MacOS 9/ASIP 6.3. The machine shares file just fine for the Mac clients, but when I start sharing files with Windows clients, some of my programs (namely Macromedia Director projects) that have long filename data files seem to complain of missing files.
Upon some investigation, if you access the files in DOS shell, the long filenames are gone, leaving these kind of results:
LongFi~1 <DIR> 09-05-99 12:22a
When it should have returned LongFi~1 <DIR> 09-05-99 12:22a LongFilenameDir
This also affects some program which access files the way DOS shell does.
In Director's case, it tried to resolve LongFilenameDir to a canonical name (LongFi~1), except when it ask for the canonical name, Windows Networking will return file not found because of some broken components.
I have tested this with Windows 95 OSR2, Windows 98 and 98 Second Edition.
November 29, 1999 -- A reader reports a problem AppleShare IP and file names more than 31 characters. The reader reports:
I would like to transfer a folder from a Win 98 PC to an ASIP volume. When copying, all the files with more than 32 characters generate an error (file already exists) stopping the transfer. The problem doesn't exist when backing up to a NT Server.
April 25, 2000 --
Windows clients trying to save files with more than 30 odd characters in their names are unable to do so - Windows reports that the file cannot be found. Now ASIP boasts of SMB/Windows file sharing capability, and nowhere is this limitation mentioned. This problem is a real issue for my customers - they are not prepared to accept having to count the characters of their filenames before saving them, let alone the problem with all their historical files.
May 1, 2000 -- François Trudeau is another reader experiencing this problem. He also finds the same error when accented letters are used in the names:
But that's not all. ASIP just won't support accented letters, except é. à, ç, ê, è, are all causing the same error on the ASIP server when a file named with these characters is copied to the server. Folders named with any of these characters are indeed copied to the server, but are inaccessible from the PCs after. I have to walk over to the server, delete the folder and start over my copy. We French-Canadians use these accented letters all the time, as you may suspect.
On top of that, files named using illegal Windows characters residing on the file server (created by Macs) are displayed using a DOS name. This is an unacceptable solution, IMHO. Users are very confused when they face a file named REPOR~1 instead of "Report-September". It gets even worse when a folder containing files named similarly ("Report/September", "Report-October", "Report/November", and so on) show up as REPOR~1, REPOR~2, REPOR~3...
Potential serious security hole in AppleShare IP 6.3
April 17, 2000 -- Andrew Hald reports of "a pretty severe security hole in ASIP v.6.3" that is being discussed on the AppleShare IP Mailing List. The problem was discovered by going to the http://translator.go.com/ and typing in the URL of a page served by an AppleShare IP 6.3 web server. The site translates your site into a different language, but appends but random information from the ASIP server's hard drive--including text from a user's e-mail mailbox. Hald postulates that the problem may have something to do with ASIP's web cache.
We have had reports of serveral different problems with Windows 2000 clients, which we've grouped below into Folders can't be Renamed and Windows 2000 Clients Can't See Inside Folders.
April 24, 2000 -- Hanz Makmur reports of two problems with using Windows 2000 as a client to AppleShare IP 6.2:
April 25, 2000 --Several other readers have reported also having the Win 2000 folder problem, and not only with ASIP 6.2, but with version 6.3 and 6.3.1 as well.
Tim Fisher describes it:
Logged in as Administrator from Windows 2000 Server to AppleShare IP 6.3.1 on Mac OS 9.0.4. Created folder "New Folder". Folder could not be renamed, but could be deleted. Folder could be renamed only with a Macintosh.
Actually this applies to all folders, not just ones created using Windows.
If you try to rename any folder from a Windows 2000 client you will get this error, "Cannot find the specified file," if you use Explorer or "The system cannot find the file specified." if you use the Command Prompt.
May 17, 2000
I guess I'm both reporting and looking for solution to a problem when using Win2K client to connect to ASIP Server via file sharing.
Basically Win2K clients are able to create/remove folders in shared folders but not able to rename them. Everything's fine for files and when using other Windows clients (WinNT4 and Win9x).
Others and I have posted this problem on Apple's Tech Exchange. Nothing from Apple so far.
All indications are that there's some problem in ASIP Server's implementation of SMB, but it's hard to tell, especially since Apple's has yet to officially recognize the problem.
June 1, 2000 -- Albert Varon reports that an Apple technician acknowledged that Apple is looking into this problem. The acknowledgement came in Apple's Tech Exchange forum.
July 26, 1999 -- Hanz Makmur reports of a problem with Windows 2000 Professional beta 3 as a client of AppleShare IP 6.2. If he maps a Network Drive using Microsoft Networking in Win 2000 Pro to ASIP 6.1 or 6.2, he can see only the top level folders and nothing after the first level. Without mapping the ASIP volume, he can access the entire volume. He has tried this on two different PCs with the same result. However, the problem does not occur when he tries to Map a Mac volume shared with Thursby's DAVE.
Apple recognizes the Win 2000 client bug, but still no fix.
November 21, 2000 -- Dan Feuerstein was having a similar problem. He told about about it, and Apple confirmed that it was a problem:
We cannot rename files on the Apple Share server. We can write and delete. If the server sits for awhile mapped it will not display the files in a folder and some folders also. We have contacted Apple on the problem and have not here back yet. This is from a Windows 2000 client mapping an ASIP 6.3.2 server. This has really been a huge problem for us.
Apple did validate the bug, and they said they are working with Microsoft for a fix.
Hanz Makmur first reported this problem with prelease versions of Windows 2000. ( A workaround for the problem is offered below.)
Some readers believe this problem is due to a change in SMB. This problem also occurs with SAMBA servers and Windows 2000 clients, but was fixed with SAMBA 2.0.7. (For more Win 2000 client problems, see above.)
A typical report of the problem:
October 26, 2000 -- Will O'Neal ran into trouble with his PCs accessing an AppleShare IP server when upgraded the clients form Windows NT 4 to Windows 2000:
I installed my first Windows 2000 machine on the network, and connected it to our ASIP 6.3.2 server. Our shared cross platform volume, The M Drive, has tons of stuff in it; the NT 4 machines see it just fine. The Win2K machine sees the drive, and shows the contents of the directory on the root level only (nothing in folders inside of folders in the root level) and only on the first visit to the M drive.
All subsequent visits to the M drive show an empty volume. Refreshing the display (f5) has no affect; rebooting does.
Change in SMB theory:
October 27, 2000 -- Thomas Myers sent us a possible explanation, one that doesn't bode well for a quick fix if true. He believes Microsoft has changed the SMB file sharing protocol in Windows 2000. He heard that SAMBA servers (SMB on Unix/Linux) have the same problem as ASIP:
I have reported this to Apple's bug reporter right after Win 2000 was released. I have not heard back on it yet. But it was in ASIP 6.3 and 6.3.1. I heard rumor that the problem was related to Microsoft changing the way SMB works. I guess SMB does a disconnect from the server then when a refresh is made or new navigation is started, it automatically reconnects. The way this was done has been changed on Microsoft's Server, so their client changes also. It is my understanding SAMBA also has a problem with this, but since Microsoft hasn't publish the changes, no one has come up with a fix.
New driver fixed similar problem with Win ME:
October 27, 2000 -- Andrea Marucci (working with the Italian versions of the software) had the problem with Windows ME and at first believed that Microsoft has made a change, since Microsoft recommended Win 95/98 to be updated. However, a new driver fixed the problem.
We recently installed Windows ME on one of our machines. We've an AppleShare IP server and, by now, that server was seen from Windows 98 and Win2K. Using Windows ME is almost impossible to see the server. I think that MS has changed something at the network level because they suggest to create a network diskette to install on older W95 and W98 machines otherwise they're not able to see the shared volumes of WinME. In fact, a machine with Win2K in our network see the shared volume of WinME but another one using W98 is not able to see it.
However, we solved the problem changing the driver on the Ethernet card (Realtek 10/100). The driver installed by WinME is completely faulty. We've searched on the Realtek site and found an older driver that is stated compatible with Win ME. Downloaded and installed the new driver everything is OK and fast.
ASIP 6.3.1 and 6.3.2:
October 27, 2000
I've had the same problem for some time. I posted something about it on Apple's Tech Exchange and they told me to upgrade from 6.3.1 to 6.3.2 but it made no difference. I would dearly like to find a solution to this.
October 27, 2000
Will O'Neal problem is the same problem that I have had since early April or so. I had Mac users which I migrated to Windows 2000 Dells and they stop seeing their files and folder after their first login. Nothing we try works including make the ASIP part of the workgroup. I search Apple Tech Exchange but didn't get an answer. Our solution was to move the critical data to an existing Window 2000 server and eventually replace the ASIP server with a Dell running Window 2000. Would love to hear another solution, though.
Workaround for one Win2K/ASIP problem
October 31, 2000 -- Mike Visconti suggests forcing the Windows client to remount the AppleShare IP Server. He says "Logging the user off from the server using the admin tools on the server usually works without forcing a reboot."
November 13, 2000
Will O'Neal reports that using PC MacLAN running on Windows 2000 enables a PC to connect to AppleShare IP server the problems of using the Microsoft client. This report is in line with the current theory that a change in Microsoft's SBM client (and lack of an ASIP update to deal with it) is the cause of the problems.
Workaround: adding the AppleShare IP servers to the lmhosts file on the Windows 2000 client
January 31, 2001 --
Erik Wieland sent us a workaround that involves adding the AppleShare IP servers to the lmhosts file on the Windows 2000 client:
Here's a workaround that works for us:
Add the ASIP servers to the lmhosts file on the Window 2000 client. The lmhosts file on Win2k is located in \winnt\system32\drivers\etc\. Add a line like this:
188.8.131.52 servername #PRE #DOM:domain
[IP address]<tab>[server name]<tab>#PRE<tab>#DOM:[server's domain or
Reload the NBT remote cache name table:
c:\> nbtstat -R
Right click on My Network Places and select Search for Computers...
Search for the server name that you entered in the lmhosts file
Double-click on the server name in the Search Results window, then log in if prompted.
Find the appropriate share/folder and create a shortcut to it on the desktop. Do not mount the share/folder, or this will not work.
The drawback to this workaround is that you can't use DOS programs or any others that rely on a drive letter.
November 13, 2000 -- A reader reports of a problem with Windows 98 SE clients and ASIP. He is finding files turning read-only. (A Workaround is listed below).
I've just updated to AppleShare 6.3. I have enabled the PCs to open the Mac server from their end. We can access everything but there is a catch. On some of our PCs, we can use the files with no problems. With other PCs, the files all come up Read Only in the properties of these files. When we go into the Property settings, we uncheck the Read Only button and hit apply and close the window, but when we check the properties again, Read Only is checked. I can even uncheck it on a PC that works with the server, but when I open the properties on a PC that doesn't work, the Read Only is checked again. (all these files open as an untitled document which is a pain. We're working mainly with PageMaker, Photoshop and Illustrator files)
All files I copied to the drive also become Read Only.
I've tested this on numerous machines. 2 laptops and 5 towers (as well as from different locations in the building). Three of the machines have no problems with the Read Only problem. The rest do. We're running Windows 98 SE clients on an NT/Novell Network.
November 16, 2000 -- Dan Feuerstein has a similar problem with Windows 98 clients:
We cannot rename files on the Apple Share server. We can write and delete. If the server sits for a while mapped it will not display the files in a folder and some folders also. We have contacted Apple on the problem and have not heard back yet.
November 16, 2000
Just to report that I've had this problem with AppleShare IP 6.3.x and files transferred from a Windows NT Workstation. The only difference is that I had this problem in May of this year: At the time, I put the problem down to the unique file types that we were using (all files were produced by the electronic flatplanning software Proteus -published by Print Cafe) having some "file locking issues" with ASIP. Proteus files are designed for collaborative working; in the ASIP setup we were using, the NT Workstations were unable to edit the Proteus files despite attempts to "unlock" them on Mac and PC clients.
In the end, we wiped the G4 Server and installed MacOS X Server with SAMBA. Since then, the PC and Mac clients have been able to collaborate on the same Proteus files but here's the catch: We found that, on occasions, Proteus files would corrupt. Again, we suspected Proteus' file format being less-than-robust because, where files had been edited on a PC then opened on a Mac, the files were completely wrecked!
In fact, the problem had occurred because SAMBA on MacOS X Server doesn't support file-locking and *guess what* the PCs and Macs were editing the same files, simultaneously! No wonder they corrupted...
So, I'm back at square one. If the ASIP problems were fixed, I might migrate back to that...otherwise, I'm seriously considering hosting the Proteus files on Windows 2000 Server, now that Macs can connect over IP.
November 16, 2000 -- Maarten van der Graaf proposes a workaround:
I also came across this. Files from ASIP 6.3 turn 'read-only' when you try to open them on a Windows 98 SE client (Win 98 first edition doesn't have this problem). As a temporary workaround, I found the problem disappears if you map the server volume as a network drive on the Win 98 SE client. However, if you access the server volume through the network neighborhood files will still turn read-only, so you have to be careful to only open the server volume as a mapped drive through 'My computer'.
Link to virus definitions?
December 19, 2000
I am also having a problem with documents becoming read-only spontaneously. MS Office 2000 apps report the files as being reserved by the creator of the document.
I have checked the drive for errors. This started happening long after the update to ASIP 6.3.2, and can be more chronologically associated with an update to McAfee virus definitions.
January 2, 2001 -- Steve Brown reports of a problem that reminds him of the read-only Windows files problem:
I have come across a similar problem which I tracked down to ASIP leaving Windows clients logged on forever, even though it was set to log out any idle client and another user (or even sometime the same user) had logged in again from that machine.
The files were released when the older version of the user was logged out through the admin programme.
Problems pulling files from AppleShare IP onto Win 2000.
November 13, 2000 --
Stephen Chiang reports
The other day I tried pulling a bunch of TIFF files from an AppleShare 6.3.1 server onto a MAC volume on a Windows 2000 Server with SP1. When I mount the Mac volume (Win2K) on a PowerMac G4 and try and open them up with Photoshop I get a message saying that the image was not the right type of file and Photoshop couldn't open it.
If I mount the Win2K Mac volume on my AppleShare server and push the same files on to it, then it works perfectly.
November 16, 2000. John Fountain suggested this:
Regarding the Photoshop error "file is not the correct type" this usually happens when the file is named with the incorrect file extension. If the file is a tiff then it should be named with a .tif extension. Naming it with a .tiff extension will cause the file is wrong type error.
November 16, 2000. Andrew Smith saw this problem with a UNIX server running Helios software and found a different solution:
We've had this problem opening files from a Sun server running EtherShare 2.5, and seemed to be caused by corrupt data in the .rsrc resource folder in the root of the AppleShare volume. The problem was resolved by deleting the .rsrc directory and rebuilding the desktop on the volume.
Reader report on AppleShare IP 6.3.3: fixes
Win client bugs, improves speed.
February 26, 2001
At long last, it appears that the recently updated ASIP 6.3.3 fixes the issues with Windows 2000 clients accessing an ASIP server using the SMB protocols.
Important to us cross-platform people is the SMB fixes. Win 2000 clients can now see all items in a folder, and rename a folder after naming it. I've also noticed that Win 2000 makes it much easier to map the ASIP server to a drive letter. Unfortunately, the ASIP still does not show in the Network Neighborhood, but it's at least easier to map it.
I imagine the update will be available very soon from Apple. It's currently available to registered Apple Developers on the developer site. In size, it's a 24 MB download, and installation is very similar to the ASIP 6.3.1 install where it "reinstalls" the software rather than patching it.
MacOS 9.1 must be used with ASIP 6.3.3.
I also noticed that on a G4 Dual 450, the performance of the server was *much* improved. I'm assuming this is due to both the Mac OS 9.1 update and enhancements made to the ASIP software.
December 5, 2001 -- A couple of readers report having problems similar to the problem we've been reporting with Macs saving from Word to NT Server -- except with AppleShare IP servers. David Jorgenson reports on having a problem that sounds sees it with AppleWorks:
This year in our Middle Schools we upgraded our client machines to Mac OS 9.1 (from 9.0.4) and moved to AppleWorks 6 from v.5. The server are all AppleShare IP 6.2 servers, running Mac OS 8.6, which was completely rebuilt before the start of the school year.
Mounting, searching and looking through the mounted volume is no problem, with no delays. However, when opening or saving a file in AppleWorks 6, it takes a long time to display the folder contents, and navigate to where you would like to open or save a file. There are also some MacOS 8.6 machines with AppleWorks 6 that are displaying the same symptoms, just not as severe.
AppleWorks 5 on the same machine screams, it does seem to be limited to AppleWorks 6. And if AppleWorks 6 is open, some (but not all) programs exhibit the same tendencies. I have tried updating one of the machines to 9.2.1 and tried the latest Apple Ethernet Update to no avail.
Peter Lennon says this problem was reported on the AppleShare IP discussion list at Apple's web site.
If you've seen these problems, please let us know.
December 12, 2001
Mark Miller reports a problem with Windows clients saving to AppleShare IP from Word:
Server: ASIP 6.3.2 on MacOS 9.0.4. Rock solid.
Client: Windows 98se with Office 2000
Some work just fine. But some cannot SAVE Word documents. Instead, the user gets "logged in" numerous times and the save times out and fails with a message about not enough memory and/or not enough disk space. (Server has many gigs free.)
No problems with WordPad, Excel, Word 98 on Macs, or any other programs. Not a permissions issue. To all appearances, the machines which work are identical to the ones that do not.
Also, you can save to the desktop or My Documents folder on C: and then drag the file over to the server. If you then go to a Mac with Office '98, you can open the document, no problem.
Any ideas? This is not the same as the problem with Win2K clients which can be solved by upgrading to 9.1/6.3.3, and we'd prefer not to do that, because we have had stability problems with that release.
AppleShare IP 6.3.3 and Windows 2000. May 10, 2002 --Jim Wick reports this problem with Windows 2000 clients on Apple servers:
We have found some issues with Windows 2000/XP and AppleShare 6.3.3 and are looking for workarounds:
1. When two users try to lock a file (or byte range on the file) and the second user is Windows 2000/XP - on the second lock attempt the user gets an "Unknown Network Error" instead of a file lock error.
This is logged with Apple and also affects Mac OS X servers. We do have a work around (which is to ignore/ or treat the Unknown Network error as a file lock error.)
2. We are trying to understand what is happening here but when two users are reading and writing a shared file and one of those users is windows 2000/XP, then size changes are not seen by windows 2000/XP in a timely fashion. We are not sure exactly what is going on here and were wondering if other users have seen issues with file sharing and reading/writing of files as they are being updated and changed
We have applied many registry settings to turn off caching that is being done by Win 2000, but may have missed one.
June 13, 2003
Danny Dun reports
I am responding to a post on your site re AppleShare IP 6.3.3 and Windows 2000.
We are experiencing exactly the same issue. We have a Windows 2000 SP3 MetaFrame XP FR2 Citrix Server and another Windows 2000 server in remote admin mode. These servers are attempting to access an OMNIS database file located on an ASIP 6.3.3 share. I have inspected the raw network traffic (via Network Monitor) and have found the Windows box is sending two file locks (frame 192 and 194???) and is receiving an error on the second. Note only one close followed by the open command which is then rejected. You can see this in the capture below.
The application reports a locked file.
We also notice disappearing files and empty directories from time to time. The catch is, this all worked the day the application was installed and stopped working suddenly. I am currently
If you've seen this problem, please let us know.
August 19, 2002
Karl Schoenefeld sent a report noting the different behaviors of Windows Explorer and Excel for Windows when opening files located on an AppleShare IP Server:
I just recently upgraded two office PCs to Win2K Professional SP3, and they started having trouble opening some Office 2001 Excel files located on our AppleShare IP 6.3 Server. I would get errors like "File not Found." If I copied the file to the Win 2K PC using Windows Explorer, it would open just fine. Then I was unable to "Save As" back to the AppleShare server. I would get errors like "Cannot overwrite file because it is read-only or in use or write-protected" or "Out of Memory" on Excel. Yet within Windows Explorer I could delete or overwrite the Excel file on the AppleShare Server without any errors. It seems like some sort of permissions problem that is evident in Excel but not in Explorer. To further cloud the issue, some Excel files would work, and all of the Word files that I tried also worked fine in Office.
August 22, 2002
Try making the root of AppleShare volume write enabled. MS Office needs to write temp files on the root volume when saving files and if you have disabled writing permission to the root MS Office applications will spit the dummy!
August 26, 2002
Peter Lennon doesn't think this is a good idea.
I would comment that making the whole of the root of the shared volume is far from ideal in many environments (I work in a school). Rather, make sure that there is an invisible folder called "Temporary Items" at the root level of the shared volume, and that this folder is writeable/readable by Everyone. This is the mechanism and the folder which appears to have been introduced with MacOS 9 which MS Office, Adobe Photoshop and other apps use to store temporary files.
I still fail to understand why it is implemented as it is, writing temp files to a network volume rather than to the local boot disk.
August 26, 2002
I can confirm everything that Karl Schoenefeld reported and add that I've tried to no avail:
- Deleting temp files per MS Knowledge Base article
- Recreating folders and repopulating them with problem Excel documents
- Compared document properties to see if there's a difference between the one's the open and the ones that don't. Sometimes there's a difference, sometimes there isn't
- Opening and saving a problem Excel document from a Windows 98 PC using a different file type
- Shortening file names
- Shortening the name of the server
I hope someone has a useful, server-side work-around, because dragging and dropping folders on the desktop and then back onto the server when through is a pain.
ASIP, Win2K SP3 and Office Documents
Note: This problem only affects Windows 2000 Servcie Pack 3, and is fixed in Service Pack 4 (see below).
June 11, 2003
Jerry Manning reports a problem with Office for Windows users and the AppleShare IP server:
I notice several users have posted issues about MS Office for Windows users unable to use documents located on an Apple file server. The school district I work for upgraded a number of clients from Windows 2000 SP2 to SP3 prior to my arrival and the users are unable to open Office documents. They receive different errors such as out of memory and low disk space. They can copy the document to their desktop, modify it and copy it back to the server.
June 12, 2003
I've seen this before. It's a issue with SP3, it appears to break something in Win2K as it relates to it's ability to connect properly with a ASIP server. There is no work around, other than to revert to SP2.
FYI - Win XP does not have this issue.
June 12, 2003
I've seen a problem with Windows 2000 SP3 clients trying to access a Clients and Profits database hosted on an ASIP server. It is a known issue, according to C and P's tech support (although I hadn't seen any mention of it on their web site). Apparently Service Pack 3 introduced some kind of problem for Windows 2000 and AppleShare 6.x, but I don't know the specifics.
June 12, 2003
Just following up on one of your recent stories, we've got Citrix MetaFrame XP running on Windows 2000 server and an ASIP 6.3.3 server. With service pack 2 on the Win2K server, MetaFrame clients are able to open Office documents on the ASIP server no problem, but with service pack 3 they are not. I guess it's probably an ASIP issue, as I remember something similar happening when Windows 2000 first came out and it was fixed by Apple eventually upgrading ASIP, but it's odd that the same problem doesn't occur with Windows XP SP1.
June 13, 2003
We too have run into this error, but so far it seems to only be with Excel files. Word and PowerPoint open correctly. The odd thing about it is we setup one test Win2K SP3 machine with both MS Office and OpenOffice installed on it. MS Excel still has issues, but the OpenOffice Spreadsheet app is able to open the files just fine.
It appears that something MS changed in SP3 broke Excel. I don't know what other apps your readers may be having issues with, but Excel is the only problem we've encountered (so far) in our environment.
July 31, 2003
We have the problem that Windows clients can open Word and Excel files from an AppleShare IP server (G3, MacOS 9/ASIP 6.3.3), but cannot save them back to the server. We get error messages which say there is not enough disk space or memory or similar.
Seems to have developed recently, and could relate to Win2K SP3. Also has same problem with Win XP. An older Win2K PC without latest service packs still works okay.
We cannot save Word 200 files from offending PCs, but can save out of Word as RTF files, or out of Excel as delimited text!
August 1, 2003
We have experienced this problem as well with an entire lab of Windows 2000 SP3 stations and a server running the most recent version of ASIP.
The users can't save a document to their shared storage space from within the application (Word, Excel), but can save to the desktop, and then copy and paste it into the shared storage space.
Fixed in Service Pack 4
August 7, 2003 --
This problems seems to have been fixed in Service Pack 4 - the issue about saving Word or Excel files to a Mac OS 9 server have just disappeared as if by magic? I'm not sure if the same fix is available for the similar problem with XP.
August 8, 2003
I had several Windows 2000 clients unable to access a shared Clients and Profits database that was on an ASIP Server. The access problems occurred with SP3. I had to downgrade them to SP2. SP4 has fixed the problem.
August 8, 2003
SP4 for 2000 appears to have resolved the issue!
First reported in October, 2004. Please see the Mac OS X Server Cross-platform Issues page.