Access Your PC from Anywhere
Run your Windows PC from your Mac over the Internet


Mac OS X 10.3 (Panther) Cross-Platform Reports

Last updated April 16, 2007


On this page:

NOTE: Issues with Virtual PC and Panther are listed on our Virtual PC 6 and Virutal PC 5 pages.

Related pages at MacWindows

For issues with Mac OS X Server and Windows Clients, see the MacWindows Mac OS X Server Cross-platform Issues page.

For information on Active Directory integration, see the MacWindows Active Directory Reports page.


An Introduction to Panther's Cross-platform Features

With Panther (Mac OS X 10.3), Apple continued adding Windows compatabiility features. (Apple has a list of Panther's Windows compatibility features at it's web site.) However, there are also some problems. First, the good news.

MS Kerberos authentication is now supported.

Integration with Microsoft Active Directory. Active Directory integration is supposed to be easier in Panther. Your home directory can now be an SMB volume on a Windows server. As with Jaguar, Panther also lets you keep a home directory on an AFP volume.

Bereskin told us that the Address Book application can now tap into Active Directory, and can synchronize your local contacts with Exchange Server.

Mail support Exchange via IMAP. The setup is easier. Exchange is now an option when you create a new account. Mail will pick up your account from Active Directory, if installed on the network.

Cross-platform printing. Printing to SMB-shared printers has been enhanced by the addition of two features. The first is SAMBA 3, which adds SMB printing. The second is that the open source Gimp Print drivers are now included with Mac OS X 10.2.3.

In Panther, shared Windows SMB printers appear in the Mac OS X Printer Setup Utility. You can add them to the Mac's local printer queue, as you would add other printers.

Panther lets you share your printers with PC users--Panther makes your printers appear as Postscript printers to PC users.

VPN IPsec. Panther supports L2TP IPsec, which is one particular implementation of the secure IPsec protocol. You access this feature through the Internet Connect utility, the same place you access PPTP.

Unix compatibility

Read NTFS disks. Panther can read NTFS-formatted drives connected to the Mac. This is a read-only capability; Panther can't write to NTFS drives.

Panther's confusing file sharing dichotomy
NOTE: This appears to have been rectified with the 10.3.3 update. See Version History below.

URL volumes mount, browsed volumes don't. October 29, 2003 -- A number of readers complained about the inconsistent file sharing behavior of Mac OS X 10.3, a point that we neglected to make in Monday's report. The confusion arises in the fact that not only are there now two different locations and methods of logging on to the same file server (AFP or SMB), but the behavior changes depending on how you logged on.

If you use the Connect to Server dialog in the Go menu to logon by typing a URL, the server will behave as it always has since Macintosh file sharing began around 1986 -- the server will act like a drive, mounting on the desktop and becoming available through the Open and Save dialog box. Dragging the server to the Trash is the logoff.

However, the behavior is completely different if you browse for an AFP or SMB volume in the Network icon. To start with, a different logon screen appears, with no way to add the password to the Mac OS X Keychain. When you double-click a server, it will not act like a drive, but as folders at this location:

/private/var/automount/Network/ServerName/ShareName

Browsed servers that you logon to won't mount on the desktop. To access the server in an Open and Save dialog, you have to click through the directory structure (through AppleTalk Zones if you have them). In fact, there is no real indication that you are connected to the server other than seeing folders on the server--a problem if you're using a notebook and aren't continually connected to a network, as disconnecting can result in long periods of the spinning beach ball.

We also discovered that these two methods of logging on can be used at the same time--that is, you can be logged on to the same server twice.

Yesterday, we spoke with an Apple executive (who did not wish to be named or quoted), who acknowledged that Panther indeed has two server logon behaviors, that this was not a bug, but was indented. As an explanation, he told us that business users were expected to type in a URL, and that home users are expected to browse.

(We found this explanation as perplexing as Microsoft's old contention, long abandoned, that Outlook for Mac was for business users and MS Office was for home users.)

Panther Problems

Readers have reported a number of new problems with Panther, including SMB file sharing browsing, problems with Outlook, and problems with virtual private networks. These problems, along with suggestions and workarounds, are described below in the Reader Reports section.

Top of page

Version History

Mac OS X 10.3.7 client, server claim network, AD improvement. December 21, 2004 -- On December 15,Apple released Mac OS X Update 10.3.7, Mac OS X Combined Update 10.3.7, and Mac OS X Server Update 10.3.7 and Mac OS X Server Combined Update 10.3.7.

The client update promises "improved AFP support for saving documents with long file names." The Server update offered several cross-platform improvements, including:

MacInTouch, however, reports problems with networking.

10.3.6 fixes some cross-platform problems. November 10, 2004 -- Apple released Mac OS X Update 10.3.6, also available via Software Update. Apple said that the update provides "improved file sharing for Mac (AFP), UNIX (NFS) and PC (SMB/CIFS) networks" as well as "more reliable network automounts and launch of network applications."

Henrik Ahlberg of Sweden reports that 10.3.6 fixed the problem of Mac users not being able to empty the Trash while connected to Active Directory.

If you can verify that 10.3.6 fixes the trash/AD problem, or that it fixes other cross-platform problems

Mac OS X 10.3.5. August 13, 2004 -- Apple released the Mac OS X 10.3.5 update in three versions.

Apple describes the two Delta updates at its web site.

10.3.4 Update for OS X and OS X Server may fix AD binding. May 28, 2004 -- Apple has released 10.3.4 updates for Mac OS X and for Mac OS X Server. Among the bug fixes and improvements, Apple lists this for the Mac OS X 10.3.4 Update:

The Mac OS X Server 10.3.4 Update refers to Active Directory integration:

In addition, several readers have reported that the 10.3.4 update clears up a problem OS X 10.3.3 has with binding to Active Directory.

Mac OS X 10.3.3 a "Panther 1.0" for file sharing issues. March 16, 2004 -- Yesterday, Apple released Mac OS X 10.3.3, a hefty (59 MB) update that addresses some of Panther's major problems with cross-platform networking. Available as a separate download as well as through Software Update, the update includes dozens of enhancements, many of them in the networking area. (However, this version did create a problem with binding to Microsoft's Active Directory, a problem that was fixed in 10.3.4.)

The cross-platform improvements include the following:

Elimination of the File Sharing Dichotomy

Network volumes logged on through the Finder sidebar's Network icon are now available in the Finder sidebar and desktop. With previous versions of Panther, only volumes logged on using the Connect to Server dialog would appear in the sidebar and in the desktop. Servers logged on to from the Network icon can now be disconnected by dragging desktop icons to the Trash or or by clicking the Eject icon in the Sidebar -- behavior before only afforded to servers logged on via Connect to Server.

(We don't yet know if 10.3.3 still permits double logon through both the Network icon and Connect to Server dialog.)

Apple notes that AFP (Apple File Protocol) Authentication options are now available to the user.

"Improved" Cross-Platform File Sharing

Apple says that the upgrade improves file sharing and directory services for Windows networks using SMB/CIFS, Unix NFS networks, and Mac AFP networks. We don't know if that means that some of the bugs reported on our Panther special report page have been fixed, however.

Improved Active Directory and Directory Services Access

Enhances an Open directory plug-in, which is used in network environments: The Active Directory plug-in is no longer sensitive to the case of the domain; the plug-in now works in ".local" domain environments; the plug-in is now less sensitive to DNS records that don't have matching reverse lookup.

However, a number of readers have reported problems with Active Directory binding. (See our Active Directory Reports page.)

AppleTalk Browsing is now on by default

Previous Panther versions had AppleTalk browsing turn off by default, even when AppleTalk was turned on. You need to turn in on in the Directory Access utility.

Duplex Issue

Apple says the update "addresses issues, such as a lost network connection, that could occur when connecting to a network device that forces the network speed and/or duplex setting (known as a 'locked' device)."

Mac OS X 10.3.2. December 23, 2003 -- Last week, Apple released Mac OS X 10.3.2, its second update to Panther in as many months, promising that it fixes some of the cross-platform problems we have been reporting on our Mac OS X 10.3 Report page. Readers report that some problems are fixes, others aren't.

Apple claims that a number of bug fixes were made in this update. The first two were problems reported at MacWindows:

Mac OS X 10.3.1. November 18, 2003 -- Less than a month after shipping Panther, Apple has released Panther's first update, v10.3.1 for Mac OS X and Mac OS X Server. Apple describes the update:

[The] update delivers enhanced functionality and improved reliability for FileVault, Printing, WebDav, and FireWire 800 drives. This update also includes the latest Security Updates.

Top of page


Reader Reports

SMB file sharing problems

October 29, 2003 -- Readers are reporting problems browsing and logging on to SMB file sharing volumes in Mac OS X 10.3. We have also experienced these problems ourselves, and have seen the problem reported at various user forums around the web, including Apple's Discussion Forums and MacNN forums.

There are several suggestions below. But the one seems to work for most readers is the suggestion by Greg Noneman.

Jay Brewer describes the basic problem:

We can't seem to browse the Windows network any longer [in Panther]. We can SMB to specific shares but if you don't know the name, you can't browse the directory to find it.

Gibbons Burke has the browsing problem, but also cannot use a URL:

I haven't been able to share files with or get files from a Windows machine running 98(SE). The vaunted browsing doesn't yield it, and typing in SMB URLs in the Go To Server... Finder command isn't working either.

Jim Solderitsch reports broken SMB browsing and a problem with the Keychain

I am having 2 problems with Windows networking:

1. For my office network, network browsing does not work. I do not see any machines in my company's domain even thought there are plenty of machines exporting shares (as evidenced by what I see on my Windows XP box's network neighborhood). In fact the domain itself does not even show up as a folder that contains machines with shares.

I did check the system.log file that is available through the console application and I see repeated messages of the form:

Oct 27 14:11:59 localhost DirectoryService[206]: Unable to browse contents of workgroup (<company-domain-name>) due to 192.168.101.5 returning NT_STATUS_ACCESS_DENIED

In place of <company-domain-name. I see the actual domain name of course.

2. I can mount shares with the Connect to Server option in the Finder but my login credentials are not saved in the Keychain even though I click the option to do so.

I suspect that these are 2 separate problems. Since I most often connect to the same machine each day, I could live without browsability but having to authenticate each time is a bit of a pain. So I would appreciate learning of a workaround for problem 2.

November 3, 2003
Pinet Cherdhirunkorn notes the problem:

I use OS x 10.2.8 and I am also have that problem, but before I could see a list of PC in server list pretty well. But with Panther, I can't see PC in the list of connect server, even I try to install a clean OS X again, I still wonder why I still unable to see a PC in server list. but if I type "smb://ip address" of PC, I can mount it drive.

December 11, 2003
Andy Davison describes another symptom:

Unfortunately, I can't provide a solution to the broken SMB problems, but I can add an experience of my own. While my system.log returns 'Nov 3 17:05:34 localhost DirectoryService[319]: Unable to browse contents of workgroup (<workgroup>) due to xxx.xxx.xxx.xxx returning an error', I can mount shares by name, either by using the format

'smb://Server/Share', or by creating a script to tell the Finder to mount said share.

Similarly, browsing for printers is flawed in the same way. A way around this is to use the Advanced setting (Option-click Add in the Print Centre) and add in the address of the shared printer manually. An oddity is that yesterday, Network browsing came to life for an hour - only to be killed off by a restart later in the day.

December 11, 2003
Blair Hicks

In my experience so far the SMB browse problem is related to having 2000 or 2003 Server. The Mac I have been working on for a client can login to Active Directory and even mounts the user's Windows home directory on the desktop. You can connect to any other share as long as you know the correct name. While trying to browse the network using Finder the workgroups/domains show up but when you click on them nothing is listed. The 2000 Domain controller is the Master Browser for this network, there is a specific error message received in the console log NT_STATUS_ACCESS_DENIED when the request for computers on the browse list is denied by the Domain Controller "this is where the problem is" Many people have suggested turning off client signing on the domain. This stuff is turned off by default and if it had been turned on then Jaguar would not work either. This computer was joined to Active Dir using the new Active Directory setup in Directory Access, all this worked fine. Another interesting fact is that when a user logs in, a Event is generated in the 2000 security log that the "user" failed logon however is logged in correctly. There is also a logon failure listed for the computer account "computername$" as failing to logon.

If I take this computer to a XP NT4 Server network the Network browse in Finder works correctly.

The console error message shows up all over the web in relation to Linux and samba on Windows networks. However I have not been able to find an exact fix, apart from all the "simple" stuff.

Suggestions and workarounds

November 3, 2003
Darrell Kienzle has a fix based on the NetInfo Manager:

I read your discussion of problems with access to SMB shares in Panther. Here's something I discovered when working with one of the betas.

Fire up NetInfo Manager and browse to /users/yourname/passwd. The passwd _should_ be "******". This is a representation of a shadow password (a feature added in Panther). If you see something like "YW3273hhs," that's a standard hashed Unix passwd (which Jaguar used).

If you have a hashed passwd, use System Preferences to change your password (you can give it the same value it used to be). Reload NetInfo Manager and you'll see it has changed to "******"

I found that this helped enormously when trying to connect to Windows and SAMBA shares.

November 3, 2003
Sean Sperte points to the Directory Access utility:

One thing that helped my painful SMB browsing experience in Panther was to set the correct workgroup in the Directory Access utility app (found in the Utilities folder in the Applications folder). Once I did this, problems accessing "folders" (or drives) more than one time were solved.

November 3, 2003
Dave de Groot offered the same idea, but called it a partial solution:

I found that you need to add your domain to the SMB WorkGroup on your Mac. You can do this by opening the "Directory Access" app in the Applications:Utilities folder, clicking on the lock to authenticate, clicking on SMB, clicking on Configure, and then typing your workgroup (or domain) into the WorkGroup field.

After doing this, you should be able to browse for servers in that domain. Furthermore, your servers will show up in the Network area of the Finder.

The only drawback is that if you have a home network, you need to change that workgroup setting again when you get home.

November 3, 2003
Phil Sandiford also called his suggestion a partial solution:

Add me to the list of users that have lost SMB with 10.3. When I browse our large network using Cmd-K (the Go menu), I get a partial server listing that will not refresh. This list shows around 20 percent of the servers available.

In 10.2.x the browser would partially list, pause, then complete the server list.

I installed Jaguar onto an old drive and booted from it, browsed for the network using the "Go" menu, jotted down the URL, and rebooted into Panther.

The short is; Yes, I could log on using the correct URL (smb://share.domain...). However, the "Go" browser will hang (beach ball of boredom) if I try to view the hierarchy.

I then found a fix for SMB browsing on my company's network.

We use Active Directory, which is switched off on 10.3. You can switch it on using Directory Access (in the Utilities directory). I can see 1,104 of my servers...the rest will not load their alias.

November 3, 2003
Andrew Cunningham had a similar experience:

Although, as you point out, there are two methods to mount a SMB volume (either by browsing or by Connect...), both are working perfectly on our Windows 2000 Server network. "Network" shows the various domains/workgroups on our LAN.

I did enter my Domain Name in the "WorkGroup" in the utility "Directory Access" in the SMB configuration, though I would like some explanation as to why this funny option still exists.

December 11, 2003
Adrian Fry offers this solution:

I think I've found a remedy to the inability on some 10.3 installations to browse SMB networks.

The fault seems to lie in corrupt cache files; I did an archive and install upgrade of 10.2.8 on our iMac, after which I couldn't browse the SMB network.

I tried all the usual remedies - repairing permissions in Disk Utility, checking the settings in Directory Access and Sharing, to no avail.

The I ran Panther Cache Cleaner, and selected the 'Deep Cleaning' option in the Cache cleaning section. After rebooting, lo and behold, all the shares returned! I presume something is getting mangled during the update process - I did a clean install on another machine, and got SMB browsing available immediately, which points to something going wrong in the update process from 10.2 to 10.3.

Don Daeges had limited success by adjusting Active Directory on a Windows server:

We have three Panther Installs on a Win2K network. We've played with the various settings to use Active Directory and had reasonable success. SMB Browsing is working, except browsing our primary Win2K server. The Mac sees the Server, but when I click on the connect button, nothing happens other than the connect dialog disappearing. It never lists the share volumes. It does have quite a few share volumes on the server, maybe Panther can't deal with too many shares on an SMB server. The server is the main Win2K, AD domain controller as well.

December 11, 2003
Daniel J. Swartz

I too am having the issues with Panther and Server browsing. I can put in the url (smb:\\server\share) that works fine. However in browsing I don't see anything. I went into Directory services and put in my domain still nothing. I tried the domain as a FQDN and also as the domain in Pre Windows 2000 mode. I get the same results. Nothing.

I do get a very interesting phenomenon that I have not seen mentioned anywhere. When I open the browse window sometimes I see my domain's shortcut listed as a folder. I click on it and there is nothing there. I go back one level and the folder disappears. I let it sit there for a few minutes (1 or 2) and the folder with my domain pops in and out.

I own my domain and have only one windows 2000 server nothing funny, just Win2K, MS DNS, and Exchange (all current patch levels too). I know all DNS is correct and my Mac uses DHCP with all the correct parameters.

As a side note, nothing I do allows me to bind Panther to my active directory. I get domain name or DNS name errors. Like I stated above I know it is all correct but this does not work either.

December 11, 2003
Kathy Gill can't get browsing to work, but has some theories as to why it might:

If people are reporting that this is working for them the only 3 reasons I can think off:

1. The 2000/2003 Domain Controller is not the master browser on their network or

2. The 2000/2003 Domain Controller has a different level of Service Pack or patches. "The one I am using is completely up to date" or

3. "Lucky them" until the 2000 Server becomes the master browser

Hope you can work through the ramblings.

I can successfully navigate to my Win2K Server using the

<smb://login@servername> syntax, but I, too, cannot browse.

Interestingly, I was only offered one share as an option, although two shares are configured (it ignore the default C:/Microsoft UAM Volume).

My password was already "shadowed" (NetInfo Manager) and my workgroup was already correct in Directory Access (workgroup being the default name).

A suggestion that resonates with readers: delete share icons from Network icon.

February 4, 2004
Greg Noneman

I thought I would pass this along in case it helps others out.

Ever since I upgraded to 10.3, I have not been able to access files on my company's Windows 2000 server. My particular symptoms were as follows:

I could see and log on to the server. Shares would appear, yet upon opening the volumes, no files could be viewed.

None of the fixes that have been suggested over the past months (or updates, currently running 10.3.2) has solved the problem.

Recently I tried the following: Once I was logged-on and viewing the shares, I threw all the shares into the trash. I restarted the computer then re-logged into the server. Voila! The shares reappeared and could be opened normally, allowing accessibility to all files.

I'm not sure what in 10.3 caused the apparent corruption of the networking information, but apparently the above procedure clears the problem. The same procedure resolved problems on both my PowerBook G4 and desktop (Quicksilver) G4.

If you've tried this, please let us know.

February 6, 2004
Joe Becker said the above suggestion worked:

I too have had problems with my PowerBook G-4 running Panther 10.3 seeing our Windows 2000 server. While, I am able to use the Connect to Server function to view share folders and the file they contain, I have had continuing difficulty browsing shares and folders in Finder. Sometimes it would work but mostly it would not. I'm tried several of the tips posted on MacWindows for solving the share browsing issue but they too have worked only intermittently. This most recent tip posted on 2/4 by Greg Noneman seems to have solved the problem for me. It's only been one day but the tip as explained worked the first time I tried it. I'll continue experimenting with this fix on my other laptop and desktops in our office to resolve the Panther/Windows Server connection issue.

February 17, 2004
Phil Sandiford

Your 4 Feb piece "Suggestion for Panther file sharing" notes the networking shortcuts need to be trashed and recreated (I think). I agree, if I understand the author's point.

I've had to trash the "Network" drive's icon and its contents several times since I loaded Panther. Each time, the icons are recreated when logging in and will work until I drop the network connection. After that it is a crap shoot if the icons will link correctly on the next log-in.

February 17, 2004
Cindy Dietrich:

This worked perfectly for me!I had tried everything, I was considering wiping the drive and starting from scratch, it drove me crazy. I am using G4 800 iMac running 10.3.2 and G4 450 Power Mac running the same both had problems seeing contents of different Windows shares, I applied fix per Greg's tip, now both see share contents fine.

February 17, 2004
Olivier Karfis:

I just ran into the same problem myself (it started happening I think after I upgraded from 10.3 to 10.3.2). Using Greg Noneman suggestion, I was able to see the Windows files again. Thanks!

February 17, 2004
Andy Bernstein

This worked for me, too. Thanks guys.

July 2, 2004
Jason Turner

After spending a couple hours trying to determine the source behind SMB file sharing inconsistency, I finally hit pay dirt (via Google) with your page, Greg Noneman's suggestion worked as advertised. Please pass my thanks to him too!

Network duplex settings problem under 10.3

October 29, 2003 -- David Toub reports that the solution for an Ethernet duplex problem that worked in Jaguar no longer works in Panther:

I work in a Win2000 environment using an iBook. The network switch, which runs on full duplex, is autosensed incorrectly by OS X as half duplex. Under Jaguar, I was able to fix this and achieve full 100BaseT speeds by either using Cocktail or typing the following in the Terminal:
sudo ifconfig en0 media 100basetX mediaopt half-duplex; sudo ifconfig en0

media 100basetX mediaopt full-duplex; ifconfig

This always worked, and prevented my iBook from crashing during large file uploads to the network.

Under 10.3, however, this series of network commands does not work. In fact, it drops my network connection entirely until I restart. I should also add that the Networks preference panel indicates 100 Base T and full-duplex, but if one types ifconfig in terminal.app, half-duplex shows up instead.

Cocktail, which also would change my card settings under 10.2, also no longer keeps me on the network. It does convert me to 100 base T and full duplex, as does the Unix command line as above, but drops me from the network. Renewing the DHCP lease also does not work.

If you've seen this, please let us know.

Readers can't get Panther VPN client to work.

Several readers are having difficulties using Mac OS X 10.3

October 29, 2003
Fergus Hammond says Apple told him that the built-in client should be used with Panther Server:

We've had no success regarding Panther's native PPTP and IPSec/L2TP support and Cisco 3000. In fact, we received an email yesterday from Apple, stating that Apple only recommends using Panther's VPN support with Panther server. We are disappointed by this but Apple has made huge improvements in OS X's cross-platform support, so hopefully this is something that will change soon.

However, this is quite different than what Apple says at its web site, which is that the builti-in client "is compatible with popular VPN servers, including those from Cisco and Microsoft."

October 29, 2003
Steve Aghazadeh also is having trouble with the built-in client

I have had complete success on my 15" PowerBook G4 1Ghz/Ti with 10.3 and the Cisco VPN Client 4.0.2C connecting to a Cisco VPN 3000 Series concentrator.

However, I have not been able to get the built-in client working.

October 29, 2003
J M Roegner is too:

I can report that the Cisco OS X 4.0.2 VPN client works just fine under Panther. I have not, however, been able to use the new, built-in VPN client to connect to our network.

Panther/Netlock VPN success. October 29, 2003 -- Jim Rossman notes that the Netlock VPN client works in Panther:

I'm running Panther on a 17" Powerbook and having no problem connectingto my company's Nortel VPN switch using Netlock's Contivity Client for Nortel. We are using Netlock client version 2.1.2.

Cisco VPN client issues with Panther

Below, we have a solution from Cisco.

First problem report

October 27, 2003
Michael Friesen reports that Cisco VPN Client 3.7 is incompatible with Mac OS X 10.3:

Panther has broken the Cisco VPN 3.7 client (no surprise). I have tried to use the built-in L2TP VPN client, but I am not having any luck. Since there are only 3 fields to enter info in (Server address, Account name, and Password) I'm not sure if I am just missing something, or does it not work the same way that the Cisco client works.

Has anyone else had trouble or success with either a Cisco client, or the Panther VPN clients?

We note that on its web site, Apple claims that Panther's new IPsec client is compatible with Cisco VPN systems.

Suggestions

October 29, 2003 -- Some five dozen readers reponded to the above report of problem with using a Cisco virtual private network in Mac OS X, some five dozen readers. (More responded after -- Thanks to everyone who wrote in.) During the past two days, a total of 53 readers wrote to say that they are successfully using the Cisco Virtual Private Network Client for Mac OS X, from version 3.7 to 4.2c (includes REL versions), for the Cisco VPN3000 as follows:

Number of readers

Version of Cisco Client for Mac OS X

11

3.7

1

3.7.2

3

3.7.3

3

3.7.3A

14

4.0

1

4.0C

3

4.0.1

2

4.0.1A

9

4.0.2

12

4.0.2C

However, 3 readers also had the problem. First, the problem reports:

Richard Bliss

Since updating to Panther, the Cisco VPN Client 4.0Rel 'Failed to establish a TCP connection.'

I guess I'm out of a VPN connection until Apple or Cisco fixes this. Apple's Internet Connect application has no fields to enter Group data requested by the Cisco VPN server.

John Harkin doesn't work

I'm confirming that it doesn't work for me. Cisco VPN Client Version 4.0.2 (C) MacOS 10.3 A window comes up instead of connecting. It says "Warning 201: The necessary VPN sub-system is not available."

Brendan Deasy said "Panther has broken the Cisco VPN 4.0 client as well."

Suggestions for Cisco VPN 3000

Several of these 53 luckier readers had advice for those having problems. Eric Weasner said:

I use the 4.02 Cisco VPN Client with no problems on my freshly installed Panther iMac 17. I did not try the Apple IPsec VPN, but in addition to IP Address, username, password, you will also need the "shared secret" code that was entered in the Cisco VPN Firewall.

Joe Schnide:

I've been running the vpn-darwin-3.7.Rel-GUI-k9 from Cisco on most all the Panther betas and now on the Panther relase on 3 Macs with no problems at all.. Did the user remember to uninstall and re-install the client?

Gene Halverson:

I was able to get Cisco VPN Client 4.0 (REL) working under Panther. I did an install to a Firewire drive with an existing OS X 10.2.6 installation on it. The 10.2.6 disk did not have any previous VPN installs on it.

After the upgrade/install, I installed the Cisco VPN Client 4.0 (REL), copied my existing profile (.PCF) to /etc/CiscoSystemsVPNClient/Profiles/ and restarted. (I am using group authentication.) Cisco VPN client worked after that. As usual, my problems seem to be self-inflicted.

See these threads for more info (might require registration).

Mark Friedel:

I don't know about version 3.7, but I've been using their 4.0 client with Jaguar with no problems.

BTW: You don't have to set up the new client if you remember to copy the working .pcf file from /etc/CiscoSystemsVPNClient/Profiles to the new machine/OS.

I found the 4.0 client at this site: http://www.netcom.utah.edu/helpdesk/vpn/macosx.html

Mike Wilson:

I did an Archive & Install load of Panther on a Jaguar iBook that was already running Cisco VPN Client 4.0.2c successfully. After loading Panther the VPN Client launched but the Connection Profiles were missing. In trashed the Client, re-installed it, the Connection Profiles were restored and everything has been OK since then.

David Barnes notes that he is using the Citrix ICA client over VPN connetion:

I am using Cisco VPN 4.0.2 with Panther and nary a problem (it's the only way for me to remote access into my work network and it was the first this I tried after the install). Other software is Netscape 7 and the Citrix ICA client.

Blake McCormick:

I was able to successfully use the Cisco VPN Client 3.7.2 and the 4.0 version. My company's "supported" configuration is 3.7.2, but unfortunately, that's the one that has the loss of network connectivity after sleep (even when you haven't run the VPN). 

The GUI elements seemed to be somewhat broken by Panther, so I reinstalled and it works.

Steve Maratea just needed to reboot:

After installation, I needed to reboot before I could use the VPN client. VPN client upgrades are free for registered users.

Fergus Hammond agrees:

One suggestion I would make is to reboot after installing this client. The installer doesn't recommend it but the client often fails to run (with an error regarding the VPN subsystem) unless a reboot has been done.

Christopher S. Foote

I can report that the Cisco vpn 3.7 client works perfectly on my Aluminum G4 Powerbook in Panther. The installation over an existing system (or in a clean install) is not completely trivial (nor was it in Jaguar).I had to manually drag the init file in from the old installation in Previous System. After installing, use find, and search for "Cisco" with visibility set to "both". It's down in .etc. Drag it into the current system in exactly the same place (and throw away the example). Even using the deinstaller doesn't clean out the system enough to avoid this step.

Michael Krutsch

We use the CISCO VPN client (release 4.0) where I work. I had to reinstall it (my Panther install walked on my previous installed version -- even with an archive and install) but after reinstallation, reconfiguration, and reboot it works fine.

Fredrich Dengel notes that configuration files are in a new location in Panther:

There was a very simple solution to the apparent Cisco VPN client failure with Panther. Doing a full uninstall using the Cisco instructions from the terminal. First time around I did a "save certificates, etc." uninstall leading to failure and premature dismissal of Cisco v. 4.0 (release) compatibility with Panther. Apparently configuration files are stored new location in Panther. Now the tunnel builds faster than ever and the tunnel remains stable under all conditions I have encountered.

Chuck Sholdt:

I did find that you must thoroughly "scrub" the OS of any Cisco VPN files by trashing everything Cisco including invisible files and invisible directories and then reinstall Cisco VPN. Import your .pcf profile followed by an immediate restart.

Sometimes VPN tells me it can't connect, but, if I try again, it immediately finds the tunnel and I'm working away.

Niraj Shah:

Panther and Cisco VPN 3.7 works for me and several others. You may have to move your Profiles over from your older system (if you did an Archive and Install)

Mark Johnson

The Cisco VPN client 4.0.2c (latest I believe) works fine with Panther. Only issue is a bug whereby if you set the preference to maintain window position, the window will move up the screen every launch. Hopefully Cisco can fix this issue, but functionality is all there and works fine.

Successful, but noting problems, and solutions

Michael Finney

There is definitely an incompatibility with Cisco 3.7 and 3.7.2 that started with OS X 10.2.8. Specifically, when waking from sleep (in 10.2.8) or at startup (Panther) the Ethernet interface will have its MTU set to 0. This kills all use of the interface. If you use DHCP you will fail to get an address.

The workaround in all cases is to go into the Terminal and type:

sudo ifconfig en0 mtu 1500

(or 1492 if you have DSL/PPPOE). After this, if you have DHCP the first net access request will fail but the second will succeed. If you have a static address, you may have to reset the address manually in the network preferences pane. The problem will recur, and you will have to use the workaround again.

I have seen this problem on both a PBG4 with 10.2.8, and a G5 with 10.2.8. I did a clean install of Panther on the G5 and the problem went away. I then installed the Cisco client, and the problem returned. A friend who has Cisco's 5000 client reports the same problem, which started when he upgraded to 10.2.8.

I have just obtained Cisco's client 4.0.2C, and will see if this makes a difference.

I would also love to know if Apple's IPSec implementation can be made to work with a Cisco 3000.

Robert R. Fox notes a problem with PowerBooks:

Version 4.0.2 of the Cisco VPN client runs fine under Panther on a TiBook. It does have an occasional problem when sleeping the PowerBook. The connection is dropped as expected, but the connection can not be reestablished after waking from sleep. A workaround is to reset the network connection. The easiest method is to switch networks. I'm using VPN over wireless. Using the location manager to witching to Ethernet (not physically connected) then back to Airport resets Airport and enables the VPN to work again. A hassle, but better than the alternative, which is no connection.

Cisco VPN5000 client advice

Craig Campbell:

The Cisco VPN5000 client version 5.2.2 works on Panther BUT you must have had it installed BEFORE upgrading to Panther.

If you try to install it on a system which already has Panther installed on it, I've found that it wont install properly. The installer seems to go OK, but after you restart, you will get a message saying that "VPN5000.kext" kernel extension was not installed properly and cannot be used. 

I went into /System/Library/Extensions where this kext lives, and found that the permissions and ownership were different from in Jaguar. I tried fixing all the permissions manually but it didn't help :-( Maybe doing a repair disk permissions would work, but I didn't try that.

Chris Nowak:

Not my fix, but passing it along...

The Cisco 5000 client wouldn't install properly on my machine with a clean install. Or, It would install, but wouldn't run after the reboot.

To fix it just "chown -R root:wheel /System/Library/Extensions/VPN5000.kext" and reboot.

A solution from Cisco

March 30, 2004
Paul McDermott (of London)

Further to your information on the Cisco VPN Client on your Panther Cross-Platform page:

We found a supported Cisco fix regarding an incompatibility with Panther.

Error: The VPN client fails to connect with "Secure VPN Connection terminated locally by the Client Reason: Unable to contact the security gateway".

Solution: add UseLegacyIKEPort=0 to each profile (.pcf file) found in the

/private/etc/CiscoSystemsVPNClient/Profiles/ directory.

Check here for information at Cisco's web site.

Panther problems with Outlook 2001

Readers are reporting problems with Microsoft Outlook 2001 since upgrading to Panther, Mac OS X 10.3. (Outlook 2001 runs in Classic mode. There is no Mac OS X version of Outlook, though Entourage now has some of the features of Outlook.) The problem has something to do with OS X permissions in OS X 10.3.

November 6, 2003
Gerald Gigliotti said that Apple acknowledged the problem:

I updated my G-5 to Panther. Outlook 2001 client which was previously running fine under Classic will not startup. Had an Apple SE on site. He confirmed that it is some issue with permissions. It seems that Panther will not let anything write to the System. It is really a pain using Outlook web access when I am used to the regular client.

November 6, 2003
Tim Blanco discovered that repairing permissions doesn't solve the problem.

Several of my clients are having problems with Outlook 2001 after upgrading from 10.2.8 to 10.3.

Outlook 2001 had been working fine in Classic mode before 'upgrading' to Panther. After the upgrade Outlook will no longer load complaining that "The set of folders can not be opened. The attempt to log on to the Microsoft Exchange Server has failed." We have verified connectivity to the MS Exchange server via the Outlook Settings Control Panel.

Here's where it gets interesting. Boot into OS 9 (if you can) and Outlook works fine. Boot back into 10.3. Still does not work with the same error as above. Copy the Outlook 2001 Application folder to another drive or shared volume and the application runs fine. This sounds like a permission problem but repairing the permissions (OS X and OS 9) does not seem to help.

Others on the net are having this issue as well, and we do not know of a solution yet--unless you have a second partition or drive to run Outlook off of.

November 6, 2003
David Findley reports that he can't logon to Outlook in Panther:

Since 10.1 came out, I've been a pretty happy user of Outlook 2001 in Classic. While it's not stable compared with Mac OS X itself, it rarely crashed. But it always worked.

Now, with Panther, it can't seem to log in. I'm having a similar problem that I've seen reports for: the Outlook Settings control panel allows me to create the profile and certainly sees the server, because it resolves my name and puts the server name in the settings.

But Outlook 2001 just comes up, claims that it can't log into the Exchange server, and quits. Running a packet sniffer shows that it's not even trying to send any data, so I suspect that it can't resolve the name properly. That also seems to be a common problem, but I can't figure out just what name it's trying to resolve. I'm usually pretty good at debugging these sorts of things, but I spent about 6 hours on it today with no success, so I'm back to using my PC at work for e-mail (instead of my Mac).

I do have Entourage, but my Exchange Server is at 5.5 and won't be upgraded for about 3 more months, so I can't even try that option. Since my work group relies very heavily on the integrated calendar, I have to use a program that supports it.

Workarounds and fixes

November 6, 2003
Morgan Terrinoni found a workaround -- install Outlook on a separate drive partition:

I've been running Outlook 2001 for years with no problems. I first upgraded my TiBook to 10.3 and had no issues. With that, I upgraded my main machine, a new G5. Well, now Outlook can't connect to the exchange server. In the Outlook settings app, it does the test, my profile is fine, but when launching the actual app, it says "Folders could not opened. The attempt to log onto the Microsoft Exchange computer has failed."

So I tried to reinstall, but it gave me a weird couldn't write to this disk error for the pref file in the system folder (classic system). Using the old one, I could launch the app but it still won't connect. My theory thus far is that Classic on the G5 might be different than running a real bootable system on my Ti.

Following a post on the apple discussion boards, I installed Outlook on a separate drive (well, my iPod for now) and it worked fine. What didn't work was installing Classic on a separate drive. It seems that the application itself needs to live elsewhere.

November 11, 2003
Jenson Yu verified a workaround directly above

We too have this problem. But thanks for Morgan Terrinoni's tip of installing Outlook on separate partition, we made it working by creating a disk image -- read/write of course -- and copy Outlook program onto it.

November 11, 2003
J. C. Thorpe

  1. Go for a preference hunt and eliminate all Outlook prefs, both in System 9 folder and the various Library/Preferences directories.
  2. Move your "Personal Folders" and "Personal Address Books" files to your Documents folder.
  3. Nuke your Outlook Folder and its contents.
  4. Use Disk Utility to create a Read-Write disk image named "Outlook Volume."
  5. Drag the Outlook folder from its installation CD to the "Outlook
  6. Volume"
  7. Run Outlook to recreate your profile. Add your Personal Folders using the Add Services pane of the Profile Properties window (Or whatever it's called.)
  8. Goto System Preferences Accounts pane. On your account add the "Outlook Volume" to your startup items.

November 11, 2003
John Parnaby of the UK

Looks like the permissions problem that is causing this has to do with write access to the Outlook 2001 folder. At launch Outlook 2001 updates a small file - rpcreg.bak. My Outlook folder was read-only - thus preventing this file changing. I'll have to investigate a little further about how restrictive I can get with the permissions on this, but opening up the main folder to Read/Write permissions solved the problem for me.

November 11, 2003
Jonathan Becker notes that you can fix permissions with Disk Utility:

With regards to the Outlook permissions problem, there's a menu item in Disk Utility which says Fix OS 9 Permissions. I didn't see this until I wiped my drive (which for me needed to be done anyway). Another thing to check is to make sure if they've not given themselves Admin privileges to completely configure Outlook as a client using admin privileges before configuring for anyone on workstation without.

November 11, 2003
Aram Heller was mostly okay after a reinstall:

Regarding Outlook on Panther. I had the same problem that many of your readers were experiencing after UPGRADING Jaguar 10.2.7 to Panther on a G5 1.8 Ghz. I actually could not get Classic to start running. I got an error that said something to the effect that "Your Disk is Locked" Basically I wasn't able to write to disk w/Panther.

What solved this was an erase and reinstall of the entire system, applications etc. Draconian, yes, but I got a clean start, and was able to make it all work.

However, I occasionally do have problems with the Exchange Server when Outlook is hidden. It will toss up a message saying: The Client Event Failed. I quit and restart Outlook, and find new messages. Also a few other glitches, mostly not getting notification of new messages or them not showing up in my In Box. Sometimes starting a new message will cause spooled messages to download into the In Box.

Making Cross-platform SMB printing work

One reader reported a problem with Panther's SMB printing features, and in response, several readers offered suggestions.

Problem report

November 3, 2003
William Plasencia

Cross-platform printing on Panther does not work. At least it doesn't work the way it was promoted. I upgraded to Panther solely because it would let me share my Brother MFC-9700 laser printer with my wife's PC and laptop, both which run Windows XP.

A solution that was supposed to work out of the box didn't AT ALL.

First off, the documentation sucks. Nowhere does it tell you how to mount a SMB printer from Windows -- something Apple just assumes you know. O.K., I can give them slack for that.

But now, to get my printer to work I had change the printer driver both on my Mac and on the PCs to a Postscript driver (any will do) other than the Brother driver. In this case, I had to set my Brother printer in Panther and

XP to use the HP LaserJet III driver. In the process, I lose any capability the Brother driver gave me on my Mac unless I switch back. Using the Brother driver on Windows sends the print job into the ether never to be seen again.

Suggestions

December 4, 2003
Joel Donaldson

I haven't had any problem with this. Works great. I will agree that the documentation stinks. (See Apple Knowledge Base Article 32315.)

You don't have to change the driver (at least on mine) on the Mac. It uses the same driver that it has always used (HP DeskJet 840C). I did let the installer update it when I upgraded to Panther.

For the PC side, I used a generic HP Color LaserJet PS driver as according to the documentation that I was able to find, the Windows shared printer is a postscript version. My printer doesn't have a lot of fancy features and the fact that I can print on it in my home network is great.

December 4, 2003
Joe Kaufman

Printing to a SAMBA printer can work. When Clicking the Add Printer icon in the Print Manager, hold down the Option key. Now the printer type dropdown will have an "Advanced" option. Select that, and on the subsequent list, choose "Windows Printer via Samba". Enter the URL to the Samba printer such as:

smb://<server>@<printer queue>

I think that is the correct syntax, but cannot verify from work. Do aGoogle search on printing via Samba...there are a few web pages with more elaborate instructions.

This worked for my HP 4L LaserJet printer.

December 4, 2003
Todd Barber describes his use of SMB printing in his enterprise setting:

We have several HP Jet Direct 4000 Print Appliances in our enterprise. This appliance from HP supports several LPR print queues without hosting shared printers on your servers. HP has never claimed support for Macintosh clients with this product. This has not stopped me from trying to make it work. I did not have any success making it work in 10.2.x. I now have 10.3 installed and with the Windows printing feature I was able to print to one of the queues on this device.

I was able to browse to the HP Print Appliance from the Printer Setup Utility. I was prompted for a username and password. I entered my NT logon and was then able to browse all of the print queues on the appliance. I selected a queue and selected a driver and the printer was setup and I could successfully print through the appliance to the printer.

This is great news for us as we are standardizing on these print appliances and we prefer all of our clients go through a queue for management. We are currently setting up OS X clients with direct IP printing which offers no centralized management.

Panther 10.3.3 NT_STATUS_ACCESS_DENIED error with Windows printers.

March 25, 2004
Mark Edwards is having a problem with printing to Windows network printers:

Now I have a new problem with Panther 10.3.3. I used Print Setup Utility to attempt printing to Windows network printers. The only way my PowerBook could see them was through Open Directory. I added printers, both from the print server and a shared printer from a Windows 2000 workstation, but whenever I tried to print I got the error message:
NT_STATUS_ACCESS_DENIED.

I was logged into the network as an administrator

If you 've seen this problem or have a suggestion, please let us know.

Solutions

March 30, 2004
Mark Edwards

In Print Setup Utility nothing was showing up under Windows Printing and all our printers showed up under Open Directory, but gave the NT_STATUS error

I found the following solution. I accessed 'advanced' by holding the Option key and clicking 'Add' printer and chose "Windows Printer via SAMBA."

Using the following format for URL (different from Jaguar):

smb://username:password@server.domain/printername

(NOTE: A reader below says this also works with Tiger.)

March 30, 2004
Todd Miller

I was not able to print via SMB to a Windows computer sharing a printer either. I go around this problem by installing UNIX print services (Add/Remove Programs in the control panel, then Add a Windows Component) on the PC and then turning on anonymous printing.

March 30, 2004
Kit Pierce offered

Printing to a shared printer on XP without a valid username for the XP box in the Print Utility interface results in this error. Even if there's no password set for that user on the XP box, there must be a valid username specified in the windows printer sharing or the connection will fail with the NT_STATUS_ACCESS_DENIED error.

March 30, 2004
Jason Silbernagel had a different solution:

I have dealt with this error attempting to print from OS 10.3.x to a Linux/samba shared printer (HP LaserJet 1100). The fix had to do with permissions on the Linux server. Once permissions were set it printed every time.

March 24, 2006
Eric Bozman enters a fake user name:

On this page they discuss connection problems involving the NT_NETWORK_ACCESS_DENIED showing up when trying to print.

I also had a similar problem. I finally fixed the problem by entering a fake username (even though our network does not need a username or password for the PCs to connect to that printer) and checking to keep it in the keychain.

It consistently works with a username (any name) and does not work without a username.

May 24, 2006
Daniel Williams

Mark Edwards' solution dated March 30, 2004 definitely works. Using 10.4.5 and was able to enter smb://username:password@server.domain/printername using the CUPS webmin at http://localhost:631/admin (if prompted for password try your Mac login or root login). I setup the printer first in System Preferences. Then using the CUPS webin, I clicked this series of links: Administration -->Manage Printers-->select Modify Printer for the respective printer-->Configure-->choose Windows Printer via Samba, and Enter this: smb://username:password@server.domain/printername

For the username, I used a user my user name from the XP box, but when I was looking at the printer que on the actual XP box it showed guest---so you could probably use anything. Leave password blank (eg., smb://johnny:@server).  I have a domain setup on my network but I assume you could use smb://johnny:@server/printername

Command line file sharing problem with Panther.

December 11, 2003
Dr. Michael J. Modesitt describes a problem with webdav file sharing from the Unix command line:

I want to post a problem I have discovered under 10.3 and 10.3.1 that I have not seen directly addressed. Some similar issues appear in other posts. In 10.2.4+ I used an AppleScript to mount webdav volumes via "do shell script" commands. These commands still work under 10.3.X with a few important caveats:

1. The icon does not appear on the desktop without restarting the finder (this was a problem in early 10.2).

2. After restarting the finder and the webdav volume cannot be dismounted except via the command line. (On the bright side, the mount is stable and works fine)

3. After using the command line to "umount" the volume and "rmdir" the mount point, again you must restart the finder to get the icon to leave the side panel. The icon will usually disappear from the desktop following the above command lines without a finder restart, but not always and certainly not immediately.

After a bit more testing I found that the problem only occurs when the mount point name ("/Volumes/Share") does not match the server's original share name. For example, on a server named www.server1.com with a webdav share called thisshare1, if I mount it using "Connect to Server..." I get the directory "/Volumes/thisshare1" and and desktop icon named thisshare1.

On the other hand, if I use the following command line entry (this worked in 10.2)

mkdir /Volumes/mysharename
mount_webdav http://www.server1.com/thisshare1 /volumes/mysharename

the problem described below occurs. I have not tested this with AFP, NFS or SMB.

If you've seen this, please let us know.

RDC and Panther on Dual-Processor Macs.

Microsoft Remote Desktop Client 1.0 and 1.0.1 don't work with Mac OS X 10.3 running on dual processor Macs. Remote Desktop Connection 1.0.2, released in late December, 2003, fixes the problem.

November 11, 2003
Rick Felter

I've run into a problem with MS RDC under a clean install of Panther on my Dual G4 1.42 FW800 system. While RDC is able to establish and maintain connections, the application will freeze on exit, drawing about 185 percent CPU usage in Activity Monitor. It is necessary to 'Force Quit' the application in order for it to exit -- which loses any changes to the session that have not yet been saved. This will happen approximately 95% of the time (if not more) and is easily reproduced. For experimentation, I installed a clean install of Jaguar 10.2.4, then applied Software Updates to 10.2.8 and RDC in that scenario worked flawlessly.

December 23, 2003
Andrew Holowka

I too have noticed this problem. However, on further inspection and testing on a TiBook 400, 667, 1 GHz, I found that it only affects the Dual Processor models.......I tested on my MDD FW400 DP 1 GHz and the application freezes on exit. on a single processor version of the same Mac, no problem.

December 23, 2003
Hamish Blair

Like some of your readers, I was able to connect to a Windows Terminal Session over the Internet (ADSL) under Jaguar using Microsoft's Remote Desktop Client. However after an archive install of Panther, I could no longer connect. I also had some trouble with Internet banking using Safari or IE.

I did a full reinstall of Panther over the weekend - backed up my files to my web server, reformatted the hard drive and then dragged all the files back. RDP and Internet banking work fine now using standard 10.3 install - I have a number of software updates to run still.

A bit of a pain, but at least I'm back on line.

Mac OS X 10.3.3 fixes many SMB problems, looses the "file sharing dichotomy"

March 18, 2004 -- Reaction from MacWindows readers to the Mac OS X 10.3.3 update is mostly positive. This release seems to deliver much of Apple's promises for cross-platform compatibility, while fixing some of the file sharing problems that plagued the previous 10.3 releases.

(Unfortunately, a number of readers are also reporting problems with Active Diretory integration. For those reports, see our Active Directory Reports page.)

March 18, 2004
Richard Jenkins addresses the question of whether 10.3.3 still permits double logon through both the Network icon and Connect to Server dialog:

Running 10.3.3 on client and server. If I use cmd-K to connect to my server then go to the network icon in the sidebar and browse for my server, I get the connect button. If I click connect I don't need to re-authenticate, but am presented with a list of my share points.

Behavior is consistent going the other way as well, so it's all a much nicer and consistent all round. The server only shows me as being connected once.

March 18, 2004
Paul Levitt says that 10.3.3 fixes Entourage & SMB bugs

OS X 10.3.3 seems to have addressed two issues that have been a daily annoyance for the entire time I've been using OS X.

1 - I am now able to create an appointment on Entourage and have it successfully synch to Exchange/Outlook. Until now I could only enter events on my Palm or on the Windoze box. Appointments originated in Entourage would throw an error when synch was attempted.

2 - I can now copy entire folders and multiple files to our NetApp RAID mounted under SMB. Previously I could only copy a single file to the RAID. Attempts to copy a directory resulted in an error message and a single, empty folder on the RAID.

Much better - and it's about time !

However, upon more investigation, Levitt became convinced that Entourage was not fixed by 10.3.3, but by a solution he stumbled on. (More on this below.)

March 18, 2004
Jeff Hobbs found that the upgrade helped with Outlook 2001:

Microsoft Outlook 2001 seems to work when installed upon the MacOS X 10.3.3 boot drive, in "/Applications", for instance -- whereas before I had to use some odd workarounds to make it work, the "best" of which was making a disc image with the Outlook 2001 application on it and running the app from there.

March 18, 2004
Dave Scott

Just login at work ( Tibook on large window network, running active directory) and found that I can now browse and connect to any server on our domain - via Network icon on Finder.

I haven't been able to do this since before 10.2.8 (and before the company LAN went to Active Directory).

Up until yesterday I could only see local subnet via Network icon - but not actually make any connections. Today I can - and I haven't had to set up active directory plugin at all. Major improvement.

Previously I could connect if I knew IP address of server, and used

smb://ipaddress via "connect to" dialog box

So now one happy person.

March 18, 2004
Gavin Garnham is not so happy with SMB browsing:

Have Apple really improved the way OS X browses Windows SMB shares? I don't think so. It looks to me as if they gave up on fixing the problem.

Before, you could either use Connect to Server, enter the remote computers address and a list of its available shares would pop up and you would choose one, this share would mount and show up in the finder sidebar or your desktop, depending on your preference settings. Or, you could use the Network browser to see the available computers, connect to one and all of that computers shares would show up for browsing in the finder.

With 10.3.3, when you use the Network browser and you select a computer to connect to, it pops up with the same dialogue you get when using Connect to Server. You can only choose one share at a time and its mounted to your sidebar/desktop. This, in my opinion, defeats the object of having the Network browser. The only benefit of the Network browser now, is that you get to see a list of available computers to connect to without knowing their IP address.

What has happened to the browse functionality? Have they given up on it?

Panther 10.3.3+ Finder bug with Win 2000 Server: crashing Finder.

May 18, 2004 -- Anthony Soroka reports of a strange (and annoying) problem that began with the Panther 10.3.3 update:

We upgraded all of the Macs here to OS X 10.3.3 about two weeks ago. Since then we have had intermittent issues where a Mac user tries to move or copy files from folder to folder on the same server and the Finder completely crashes (the window closes) and the file they were moving is gone. This server is used by Macs only at least 98 percent of the time. A virus scan has found no virus on the server, a Windows 2000 Server with a Windows 2000 domain.

May 28, 2004
Richard Bodman

I have experienced the same problem on my mixed Mac and PC local network.

Sometimes when trying to copy a file from my G5 to my PowerBook 17" G4, the file will start to go, (which starts with the deletion of any duplicate file in the receiving folder) then there is a crash. The result is that there is no longer any older copy of the file I was trying to send on the receiving machine.

The problem has occurred many times.

August 2, 2004
Mel Walker

I've seen a similar problem when opening a different folder on a Windows server. The finder will crash/restart, the window will close. It seems that certain folders shouldn't be viewed, except that which folder(s) seems to change each time I login to the server.

The machine is used by Macs and Windows machines of all kinds; it's a major production server. Unfortunately, I only know that it's a Windows server of some kind.

August 3, 2004
Daniel Stone has a slightly different experience:

I have this problem. When I access certain folders on the server the Finder crashes and restarts with no message or dialog. Unlike your other poster however, it is pretty much the same folders that I can't access whenever I log on. The weird thing is that the two other Macs in my company (some 800 PCs) do not get blocked out of the same folders, but different ones.

August 3, 2004
Holland Rhodes

I have this problem, but it's not even Windows server. It's just Windows XP Pro. I can't really figure out what causes it, but in most cases if I make the share read-only it won't crash. If its a share that has images and Finder is set to display thumbnails, that often causes it to crash regardless of if the share is read only or read/write, but not always.

If you've seen this problem

August 5, 2004
Darrin Pertschi sends an observation:

I do not have a similar experience to mention, however; I would like to suggest that users take notice of the method to which they connect to Windows; AFP or SMB. I'm guessing these problems will exist under AFP connections.

Panther uses AFP version 3.1, Microsoft uses version 2.x. (Something's not going to work right.)

An Apple engineer told one of my colleagues that this AFP version mismatch is the source of a problem we have with picture usage in Quark. I suspect it is the source of other unsolved mysteries such as those mentioned here.

August 9, 2004
Jack Stoller

A folder on Windows 2000 Server contains file X. Somehow file X gets lost to AFP and does not appear in the listing. Now I take a local copy of file X and copy it up to the server. The Finder crashes. If I use SMB to connect to the server, the file is there and can be deleted. Once I do that, I can copy the file with AFP and the Finder does not crash.

How does the file on AFP get in that state? I'm still not clear on that one.

Responses from Group Logic and Apple

August 13, 2004
Geordie Korper of Group Logic does not think the problems are differences in AFP versions, as one reader theorized. He also offers a theory of his own:

The main additions to AFP 3.1 are support for: filenames over 31 characters, Unicode filenames instead of the local language subset, file sizes over 2GB, and support for Unix permissions. There are also many other less visible changes to the protocol. Although we suggest using a server that can support AFP 3.1, if you are using a file server that does not have support for the newer protocol the Mac OS X client should then successfully fall back to using AFP 2.2 for its communications with that server.

The more likely cause of these Finder crashing problems is that for some reason the TCP/IP connection between the Macintosh and the Windows server is deadlocking and the window size for sending additional data goes to 0.

Eventually the Macintosh will time out. When the Macintosh times out, it attempts to reconnect to the server automatically and crashes, since the currently open connection is hung.

Geordie Korper
Senior System Engineer
Group Logic, Inc.

August 13, 2004
We also receive this message from an Apple tech support staffer, who encourages readers to submit bug reports to Apple. He describes how:

Do any of the folks reporting this have crash reports of the crashes and have they been submitted as bug reports to Apple? Without more specific data it is not even certain that the reports all refer to the same problem or at which level of the system the problem lies.

If they do not have crash reports the best way to get them would be to attach to the Finder with gdb before inducing the crash This can be done in the terminal. The first thing to do is find the pid (process id) of the Finder. This can be done using the top tool or by:

ps -aux | grep Finder (followed by return).

This will produce more than one line of output such as:

peter 511 0.0 1.7 187836 18096 ?? S 29Jul04 0:16.36
/System/Library/CoreServices/Finder.app/Contents/MacOS/Fi
peter 1254 0.0 0.1 31844 660 std UV+ 6:32AM 0:00.24
grep Finder

The first line is the one you want (the second is the grep tool running to produce this output). Then launch gdb and when you reach the prompt do attach 511 followed by return (in this example) and then continue followed by return.

When the crash happens you will drop into the Terminal. To capture a complete picture of what is going on at the point of the crash do:

thread apply all bt (followed by return).

This output can then be submitted in a bug report to Apple.

"._" files are locking up the real files; can't move or delete folders

August 9, 2004
Jason Scott describes a problem he is having with altering files on from a Mac with SMB connections to a Windows Server:

I'm having increasing problems trying to move or delete items from a Windows 200 server connected via SMB. I keep getting error messages.

The weird thing is after I click OK the item is removed anyway. The problem is when your trying to delete a folder full of stuff it only deletes the last item in the folder. The thing is I know the stuff isn't in use anywhere else on the network. It seems like Windows 2000 isn't freeing up items that someone else may have touched at some point.

Scott has begun a thread at the Apple discussion forum which gives more details. He says of the thread:

At this time no one has posted any solution at all except trying third party apps like DAVE or ExtremeZ-IP.

-- Two readers responded to last week's report on "._" files on SMB locking up the real files. (Macs leave "._" files on the server when accessing Windows servers using SMB.)

August 17, 2004
Sean Hartwell

Same problem here. It's just as the other users have described it. Managing folders and files on a Windows 2000 Server from a Mac OS X computer is just an exercise in frustration. Moving folders seems to agitate users here the most. Some deletion issues have arisen as well.

Apple really should address this soon as it seems to be something to do with how Panther is handling the resource forks on different OS platforms.

August 17, 2004
Matthew Kelly

The only solution I have found that allows these files to be deleted is to reboot the Windows machine.

August 23, 2004
Sam Boychuk

I'm getting this problem too - basically if any OS X 10.3 user touches any file or folder on the network they cannot delete or move that item (access is denied) - if I do a netstat from the Windows server it says that the file is open even though it is not - essentially the only way to close a connection to a file on a Windows share is by logging the machine out. Still looking for a solution before the users decide to have me fired!

August 23, 2004
Matthew Kelly speculates on a cause.

Perhaps it is not the platforms, or protocol, but the network cards. Since we know that files can be move or deleted once the Windows machine is rebooted, maybe the file data is not being released by the network cache?

We are using 3Com 3C996 Gigabit Server cards. I would like to know what others that have this problem are using as network cards.

These are managed cards, and I know little of how they work, but it is my understanding that they buffer and cache data. Perhaps the cards do not know how to handle "._*" files.

August 30, 2004
Olivier Nguyen Van Tan sees the problem with a Linux server:

I have the exact same problem using a SNAP server. Files are locked and even a reboot is of no use. Seems like the SMB thing is OX X 10.3.5 is bugged...

Use DAVE to workaround the problem

Two readers say that the Panther problem doesn't occur with DAVE from Thursby Software.

August 25, 2004
Sam Boychuk

I've started using DAVE, which fixes up the problem right away. However, you need to re-associate all the files you tried to open in Mac OS X. For example, if you've opened or created a PDF in OS X before DAVE, you have to use Get Info (Apple-I) and re-associate Acrobat with PDF's, otherwise it will open it as a text file.

Furthermore, since the files that are all left open on the server are all the second half of the resource fork, it may make sense to write some batch file on the server to shut down all open files beginning with ._ .

This may sound like a painful workaround, but a simple net stat and lmod should take care of it. Or, find in DOS and then pskill the open files and you should be sweet if you get the users to run it.

August 25, 2004
Todd Miller

I worked on this for a long time and finally bought DAVE because I didn't have time to mess with it anymore.

I was watching the server for open files and I think this has something to do with the view. I don't think you'll see the problem if you switch to ICON view instead of the column view or the list view. I was not noticing these files being left open when in icon view. I did not do anything close to scientifically testing this, and I don't really have time too, but it might point some of your readers towards an idea to try. What I suspect is happening is that the column view is leaving the enclosing folders open and then you can't make any changes in the whole path. It would take some further investigation to see if this is true.

If you'd like to comment on this theory

September 1, 2004
Jason Scott, who was the first to report the problem, agrees with some other readers that Thursby's SMB clients don't have the problem:

I started this discussion so I thought I'd chime in with my progress. I've also found DAVE or ADmitMac to be a solution to the ._ file problem. So it seems we have a solution, even though it means spending more money.

Use ExtremeZ-IP as a workaround

September 7, 2004 -- We've previous reported that the problem with "._" files are locking up the real files can be avoided by using Thursby's DAVE SMB file sharing client on the Mac. We should also mention that the problem is avoided by using the AFP file sharing protocol instead of SMB. Reid Lewis of Group Logic points out:

Can I suggest that your readers consider ExtremeZ-IP as an alternative to the Mac OS X SMB client? Because it uses the latest Apple technology, AFP v3.1, ExtremeZ-IP does not have the "._" Dot Underscore problem or any of the other know limitations of the OS X SMB client.

ExtremeZ-IP is an AFP file and print server that runs on Windows servers.

A theory on what's happening

November 23, 2004
Jamie Kettlewell believes that it is double-logons that cause this problem.

I can confirm that I get occasional issues with any one of my three Mac OS X clients being unable to delete or move folders on the Windows 2003 server.

From what I can ascertain, the problem occurs when one of the OS X clients gets a double login or login session. This generally means that one of the sessions gets read locks on the '._' files and then subsequently these files cannot be moved or deleted until I close the open file lock.

This does seem to ONLY happen with MAC logins that get 2 login sessions. As I write this, I am looking at the server and again, one of the MAC users has a double login; this will no doubt cause a phone call sometime this afternoon due to one of them being not able to move or delete a file or folder.

Either there is an intermittent bug in OS X which stops the double login or the double login IS the bug. Either way, the off shoot of this is that '._' files are left locked and subsequently stops folders being moved or deleted.

A better solution

September 12, 2005 -- Branko Collin offers a workaround for the problem of "._" files left on SMB servers locking up real files, and where folders can't be moved or deleted:

I don't know if this has been solved yet, but some of your readers pointed out that the only way to solve the problem of the extraneous file locks is to reboot the Windows Server.

Windows 2003 has a tool called File Server Administration (or something similar; I translated this from its Dutch name) that will allow you to delete the file locks. No reboots necessary.

(Of course one has to be careful with this; you probably do not want to delete legitimate file locks.)

September 16, 2005
Matt Bogen clarifies the fix:

I was glad to see this tip on MacWindows this morning; I actually only discovered this workaround late last week, myself.

Just to clarify what Mr. Collin had noted: The tool is called "File Server Management" (I access it by clicking the "manage this file server" link on the Manage Your Server pop-up windows that comes up by default when you log onto a Win2003 server). One of the options on the left-hand side of this tool is "Open Files (Local)." Click there, and from the resulting file list, select all ._ files that are causing problems. Click the "Close Open File" link that can be found to the left of the list of those filenames. After you do this, you can delete the ._ files, and more importantly, OS X users can then rename files, save files, and do other things they weren't able to do because of the file lock.

I've been doing this as a preventative maintenance step each morning since I found out how to do this. We have about a dozen Mac OS X users hitting a Win 2003 file server, and it saves time and stress during the day just to clear all ._ files before they even get on their workstations in the morning.

Slow access to Windows Server due to "icon caching"

November 8, 2004 -- Michael Curtis reports a performance problem with the first Mac OS X access to a Windows server, which he thinks seems to be some sort of caching behavior:

Mac sharing to a Windows 2000 or Windows 2003 server is so slow the first time you go to a folder that contains lots of files/folders and is even worse when those files are making thumb nails.

It does not happen to Mac OS X Server or with ExtremeZ-IP. It seems that Mac OS X is doing caching of Windows Server items. Is there any way to turn this off? You can tell when it is doing it, as all the icons are lighter while they are "cached."

When you return to that folder, access will be quick. But once you log out the "cache" seems to be lost.

November 10, 2004
John Gettlers has a workaround for Panther: use column view and turn of icons.

In response to Michael Curtis's email. I have found what may be the solution or work around, tested on OS X 10.3.2. When browsing folders in OS X stored locally, but especially on servers, the speed it fills in the list has been slower than on OS 9. The speed of actually copying / opening / saving files is not the problem. It has been the Finder file browsing that has been slow. The more items in a folder, the longer it will take to display.

Workaround:

You must be in column view, not list or icon view, and turn off Show icons. (View menu, select Show View Options.) This will dramatically speed up the display when in column view. This appears to a user-wide setting. There appears to be no way to turn off the icons in list view.

There appears to be no big speed lag caused by the 'Show preview column' being left on, so you might as well leave it on.

So if you mainly browse in column view, you can wiz through folders full of files very fast. Of course, the bad part is that you wont see the icons which can sometimes be helpful. In general you can turn this option on and off on the fly, when needed either way.

Unfortunately, this setting does not affect the column view of the Open and Save dialog boxes, which are still slow due to the drawing of the icons. If anyone knows of a hack to set this flag, for the list view in the Finder, and also for the open and save dialog boxes, that would be great.

If you know of such a hack

November 10, 2004
Michael Curtis, who first reported the problem,

I've also seen the problem on both ExtremeZ-IP and Mac OS X Server, BUT, it won't stop you working. You can see the dim folders, but at least you can scroll. You can't scroll the view while it is "caching." It does it when connecting to Windows 2000 and Windows 2003 servers.

The Finder only seems to "cache' the files that are in the view, so it seems you have to scroll the window to get the other folders cached.

November 10, 2004
Jaap van den Dries of the Netherlands thinks the problem may have to do with an old version of the Apple File Protocol (AFP):

It's terribly slow, especially with 10.3; 10.2 was somewhat better. On several places on the Internet there are threads about this problem, but until now there's no clear solution. Maybe it has something to do with the fact that Microsoft doesn't supports AFP 3.x but sticks to 2.x (without support for long filenames, another very annoying problem).

November 10, 2004
Darrin Pertschi agrees with van den Dries on the cause:

Yes, I can absolutely second Michael Curtis experience. Folders on a MS 2000/2003 server, with more than a couple dozen files and folders within, take a lot longer to scroll through, in list view, than on OS 9 booted machines. The folders appear properly immediately as expected, but the Finder produces a 'ghost image' of file icons briefly and then it snaps into the full color of the proper creator app. icon.

And yes, once you scroll fully through the folder and it's drawn properly; you can go in and out of the folder and experience hesitation free scrolling. Once you disconnect from the server and reconnect, your back to slow icon redraw the first time in any given folder. I see this on multiple machines running 10.3.4.

I suspect it's the AFP version mismatch; desktop-v3.1, server-v2.2.

November 10, 2004
Jordi Parera of Barcelona, Spain, describes more symptoms:

We have exactly the same slow access to our W2000 Server that Michael Curtis reports when we try to access the first time to a directory. I feel it's due to the 'intelligent redrawing' the Mac OS X is making of the different icons; for example, when the files are locked for the user, the icon appears with a specific icon, and it seems W2000 it's serving this information quite slow.

In Excel (Mac OS X), when you try to open a file from your W2000 server, it takes a longtime to show the files in a directory (as long as 5-6 seconds in our case). When you page-scroll in the open dialog box, you have to wait also at each 'page-down'. If you quit Excel, reopen it and try to open a file in the same W2000 directory, speed improves a lot (without being impressive anyhow).

November 10, 2004
Jonathan Tillick describes the versions of Mac OS X that exhibit the problem:

We're definitely having this problem and it's a real pain. It takes a second or two or longer for large lists of files, and is noticeable even on short lists. We're Running 10.3.5 and 10.3.6 clients connecting through AFP to a straightforward Windows 2000 fileserver. It seems to have happened since upgrading to 10.3.x from 10.2. Still a problem in 10.3.6

If you're in column view you notice that it's slow and even seems to only load the files that are visible - you can leave it a few seconds to "catch up", but even then when you scroll down it's still slow. It doesn't seem smart enough to preload the rest of the folders files until you scroll down.

November 10, 2004
Fabienne Tierce of France:

We're seeing very low speed between a shared folder on Windows Server 2003 and Mac OX 10.3.6 (G4) computers. To open the window of the folder "IMAGES" (on server NAS) and copy the pictures in EPS on the desktop of the G4, it takes an abnormal amount of time.

A description of the problem: Group Logic on slow icon drawing with Windows AFP servers

November 23, 2004
Michael Curtis asked Group Logic, makers of ExtremeZ-IP, about the problem of slow AFP access to Windows Servers due to "icon caching" on a server running Group Logic's ExtremeZ-IP. Reid Lewis of Group Logic replied with a discussion of the cause:

MC: I have tested ExtremeZ-IP and it is wonderful. Why when using 10.3.x sharing to a Windows 2000 or 2003 server is it so slow the first time you go to a folder that contains lots of files/folders? It's even worse when those files are making thumb nails. Is their anything that can be done? What is happening?

RL (Group Logic): Yes, we are aware of this behavior and we think that we understand it. We think that its the result of a slow process of icon and preview generation. The problem affects all file servers but appears to be worse with AFP v2.2 than with AFP v3.1 [used in EZ-IP].

There are two cases, the Finder and other applications, such as Quark. In the case of the Finder, when you are browsing in column view, the Finder can _optionally_ show an icon and a preview. Generating the icon and the preview are the slow activity. If you go to the View menu, and choose View Options CMD-J, and disable Show Icon and Show Preview, the slowness will disappear along with the icon and the preview.

Under an application, such as Quark, you may not be able to disable the icon and preview and are therefore stuck with the performance.

In either case, having the latest version of ExtremeZ-IP supporting the latest AppleShare protocol, AFP v3.1, will likely give you the experience closest to Xserve, which also uses AFP v3.1. The Windows File Services for Macintosh, SFM, uses the older AFP v2.2

Broken aliases to SMB Win Server

November 29, 2004
A reader reports a problem with aliases to folders on a Windows SMB file server:

For the past few months, after one of the Mac OS X 10.3.x upgrades, I am no longer able to create a functioning alias to a Windows NT server mounted via the SMB protocol. It doesn't matter whether I mount the share via Command-K or by browsing. The mounting itself works flawlessly.

But every alias created by either command-L or by dragging the window title of the share opened in the Finder gives me the message when trying to open it: "The alias 'xxx' could not be opened, because the original item cannot be found."

Interestingly, I still have two older aliases to shares on the same server which still work (they are not real Finder aliases since they were created by dragging a mounted share into a Drop Drawers drawer). When using them, the share mounts in /Volumes as it does when using Command-K.

However, with Command-K the share name appears in small letters, using my old 'alias', the name appears in capital letters.

And, creating an alias from a share on a different server mounted via AFP still works.

December 7, 2004
Kris Nybakken notes that the problem is not limited to Windows NT

ALL of my SMB shares, including browsing from the "network" tab, produce that alias error. I can't log into ANY of my Windows 2000 servers. Yikes!

December 7, 2004
Erasmus Schneider

I also have the problem that when I do a network browse: I can see the alias to the Win machine, but when I try to connect I get the same error message of ""The alias 'xxx' could not be opened, because the original item cannot be found." I can mount the PC just fine if I know either its name or IP address and connect directly.

I am using 10.3.6, but can't tell when exactly the problem first appeared.

December 30, 2004
Salvador Manzo had some interesting observations:

I've run into this problem as well with 10.3.6. The odd thing is, when I get the error, the remote volume IS mounted and is accessible via Terminal.app, but Finder can't do a thing with it.

As an addendum, I've run into this problem both with an alias and (once only) when connecting directly via Command-K.

December 30, 2004
Ed Stanisz faults the error message for being misleading:

The error The alias 'xxx' could not be opened, because the original item cannot be found." Is because the OS thinks the drive is already mounted or because it still is just not on desktop.

I can replicate the error all the time if I try to mount a drive I already have mounted. It is a poorly written error message that may or may not mean multiple things.

Workarounds

December 7, 2004
Todd Miller

I have seen the problem mentioned in the Nov 29th edition of MacWindows with broken aliases to SMB shares. The server we have problems connecting to is also NT 4.

I do not have a fix for this problem, but do have a workaround. You can make an AppleScript to mount the share.

tell application "Finder"

mount volume "smb://username:password@machinename.local/sharename"

end tell

The "username:password@" is optional. If omitted, the user will be prompted. This works great every time.

December 23, 2004
Nancy Jaquith Kneiss that the AppleScript worked:

My OS X connections to our Win server here would work fine one day, then not at all on other days. Completely unpredictable, and it only happened with some of the servers and not others. Same thing with the aliases on the desktop.

I ran the AppleScript as suggested for the workaround and it went off without a hitch. I've never written an AppleScript before in my life but it was a piece of cake with ScriptEditor (built into Panther). Not the most convenient solution every time, but at least it works!

December 23, 2004
Name withheld

The AppleScript solution you posted works fine for me (as it should, since it's just a wrapper around the Command-K method in the Finder).

As an additional note, using this AppleScript, or Command-K in the Finder, you don't have to store the password in cleartext in the address. Keychain will store it for you, at least if the username is part of the address. And for those who aren't aware of it, you can access hidden shares (shares that will not show up in browsing mode, 'even' when browsing from a Windows machine) by adding a '$' behind the sharename.

January 3, 2005
Jeremy Matthews offered some advice for using the AppleScript:

We hit this problem so frequently it drove us nuts, then we started using the AppleScript to automatically connect to volumes (FTP, AFP, SMB, etc.)...

Now you DO have to authenticate the first time you launch the script (if not previously authenticated), but you can check the box on the login prompt to store the ID/Pass in the Keychain. You can store the ID and password in the script, but I recommend against storing passwords in this insecure manner...

This way we can create a startup item as well (System Preferences ->Accounts -> Startup Items), so users automatically connect to all network shares upon login. This saved us a ton of headaches. We also left a copy on the users' desktop in case shares drop out or the user accidentally ejects them.

-----------

However, the AppleScript did not work for several users:

December 23, 2004
Kris Nybakken

The workaround didn't seem to work for me. But what DID work is turning AppleTalk on on the Windows 2000 machines. SMB shouldn't require it, and it did not require it before, but it seems to work. If I have to make a choice, I choose to know it works rather than know why!

December 23, 2004
Dan Nigrin also had no success with the AppleScript:

The AppleScript workaround posted by Todd Miller is also not working for me. I keep getting error type -36 when trying that approach. This is also the error I get when trying to connect via previously created aliases.

When I browse the network, I can "see" all the machines I used to be able to connect to, but when I double-click them, I get "Alias couldn't be opened, because the original item couldn't be found" errors.

The Windows servers in question are Win 2003 Servers, and I'm on OS X 10.3.7.

December 30, 2004
Mike Pryer describes how he deals with the of problem:

I have the broken alias issue come up while running 10.3.5 connecting to a Windows 2003 server. Like other's reports, this problem is random.

My kludgy workaround has been to go back to the "Connect to Server" menu and "clear" the recent connections button. This puts the recent connections in the Trash. I then drag the "connections" I want to keep out onto the desktop. Maybe these are actually scripts created by the OS that I'm just salvaging.

December 30, 2004
Jack Stoller offers another workaround:

I'm not sure why one would need to create a script. What I do for my users is type the following into TextEdit (or anyplace else where you can select and drag text):

smb://myacct:mypswd@server/share

I select the text and drag it to the desktop. It becomes an Internet location file, which will mount the volume (and prompt for the password if you leave the :mypswd off) when double clicked. The file name should be changed, as it will have the above as the name by default. BTW, this also works for AFP mounts.

Caution: You can mount the same share twice if you double-click the file twice. The Finder will not be able to dismount the second one.

Another caveat is that if someone else has physical access to your machine, and drags the file back into TextEdit, your password will be revealed. You can leave out the password, and then you'll be prompted. An AppleScript that was a run-only app would avoid this security issue if it's a concern.

If you've seen this problem,

Suggested fix

April 16, 2007
Daniel Weikert fixed a problem with a problem with aliases on Windows servers. We've reported the problem with Mac OS X 10.3 and with Mac OS X 10.4. His approach:

I just thought I'd share one cause I discovered for the "The alias [servername] could not be opened, because the original item cannot be found" error. My server has two NICs and if both have the AppleTalk Protocol enabled, you need to verify which one has "Accept inbound connections on this adapter" selected. It can only be enabled for one adapter at a time and if it's enabled for an adapter that's disabled, or doesn't have a network cable plugged in.

Right click on My Network Places and select Properties. Right click on the appropriate Network adapter and click Properties. Click on AppleTalk Protocol and click Properties. Verify the checkbox for "Accept inbound connections on this adapter" is checked.

Even if the second adapter is disabled, I've had it revert to the other adapter. To play it safe, I only have AppleTalk enabled on one adapter.

I have a Window Server 2003 R2 (though I don't think the R2 makes any difference).

Apple Security Update fixes Samba issues

March 29, 2005
Steve Maser reports that the recent Apple Security Update 2005-003 for Mac OS X updated Samba (SMB file sharing) and solved a problem he was having with VirusScan on Windows clients:

Many months ago I ran into an issue with VirusScan 8.0i not able to go through Internet Explorer to connect to my Mac OS X Server. It's reproducible and has to do with a bug in the VirusScan "scriptproxy.dll" file.

This was against Samba 3.0.5, which is part of OS X 10.3.8. I got confirmation from users on the Samba mailing list that they were seeing this with VirusScan 8.0i as well.

Apple released a security update that (finally) bumped Samba up to 3.0.10. This specific problem is now gone.

Updating Samba should also apply to people running Samba services on Linux.

March 29, 2005
Jason Dunn reports that another Samba problem was fixed:

Security Update 2005-003 seems to have fixed the Samba issue with Windows search. I have tested it successfully on two server machines and plan to update the remainder of my servers soon.

If you've seen the Security Update 2005-003 fix these or other SMB problems

See also our report on Jaguar problems and

our report on Mac OS X 10.0-10.1.5 issues.


| Top of this Mac OS X Special Report Page |

Other MacWindows Departments

| Product Solutions | Special Reports | News Archives | Site Map |
|
MacWindows Home |


This site created and maintained by
Copyright 2003-2006 John Rizzo. All rights reserved.