Last updated September 17, 2008
On this page:
Send us your experiences with DAVE.
DAVE from Thursby Software Systems is Macintosh software that enables Macs to participate in Microsoft networks, giving Macs access to file and print services. DAVE enables Macs to log into Windows NT/2000 domains. It also lets PC users access Macs drives or folders and printers. To a Windows server, DAVE clients look like Windows clients.
More specifically, DAVE is implements the Microsoft SMB/CIFS (sever message block/common internet file system) file and print sharing protocols on the Mac. DAVE also implements NetBIOS over TCP/IP for the name service. Macs can access drives on Windows servers and workstations. No additional software is installed on PCs.
Monday, April 7, 2008 -- Thursby Software Systems last week released , upgrades to the Active Directory integration and SMB file/print sharing software for Mac OS X. Both feature completely rewritten Dfs module that is smaller and faster than the previous version.
The Dfs modules allows the Mac user to access Microsoft's Distributed File System, which stores shares on multiple servers. Thursby's Dfs module in AdmitMac and DAVE enables the Mac to see the share as a single folder on a server.
ADmitMac 4.1 also includes an improved deployment tool that enables administrators to install ADmitMac on multiple systems from a single workstation using a common set of installation parameters.
DAVE 7.1 also adds the ability to configure volumes that mount at login.
Both ADmitMac 4.1 and DAVE 7.1 can do secure SMB file sharing without the problems of the built-in Mac OS X Leopard file sharing client. ADmitMac adds the ability to integrate with Active Directory, with more features than Apple's Active Directory plugin.
ADmitMac 4.0Thursby releases Leopard-ready ADmitMac 4.0, DAVE 7.0. Thursday, December 27, 2007 -- Thursby Software Systems has released DAVE 7.0, a new version of its Mac OS X software for integrating Macs into Active Directory environments. The company also released downloads, a new version of the NTLMv2-compatible SMB file/print client/server for Mac OS X. Both new versions add compatibility with Mac OS X Leopard 10.5.
AdMitMac 4 now has an option to automatically disconnect after a specified period of inactivity. It also adds some new options in ADmitMac Deployment Utility, including the ability to turn off ACL support, Dfs drill down, and symbolic link support. You can also now setup volumes to mount at startup, choose the location of sysvol, and modify the update interval of local mcx cache.
The DAVE 7.0 update adds an option to disconnect after a specified interval of inactivity. It fixes problems browsing over a VPN connection, among other improvements.
The updates for ADmitMac and DAVE are free ADmitMac for CAC for customers with active support agreements or who have purchased either product after July 31, 2007.
public betas of upcoming versions of ADmitMac and DAVEThursby posts public betas for ADmitMac and DAVE Leopard update. Monday, October 29, 2007 -- Thursby Software has released . The updates are for Leopard compatibility. The company said that the new versions would be "major updates."
ADmitMac is Mac OS X software that integrates Macs into Active Directory with needing a Mac OS X Server or changes to the Windows server registry. DAVE is Mac OS X software that provides an enhanced SMB file/print client/server.
ADmitMac 3.2.2AdmitMac and DAVE, updated. June 26, 2007 -- Yesterday, Thursby Software releases DAVE 6.2.2, an update to the Mac OS X software for integrating Macs into Active Directory networks. Thursby also released Common Access Cards, an update for the SMB file and print sharing software for Mac OS X. (ADmitMac includes DAVE’s functionality.) Thursby also offers a version of ADmitMac that supports the US Department of Defense ADmitMac 3.2 and DAVE 6.2.
The new versions boost performance and improve functionality for support of Windows Vista, as well as fix minor bugs. ADmitMac 3.2.2 adds the ability to use certificates instead of passwords to authenticate to a domain. Another new feature is the ability to assign local administrator rights using nested groups.
Both ADmitMac and DAVE upgrades are Intel and PowerPC native.May 31, 2006 --Thursby Software Systems today released free updates to ADmitMac and DAVE, the company’s Mac software for compatibility with Windows networks. Active Directory Reports page are now universal binaries that run natively on Intel-powered Macs as well as PowerPC Macs. The new versions also include increased performance and stability on PowerPC Macs.
DAVE is an SMB file sharing and printing client/server. ADmitMac combines the SMB capabilities of DAVE with Active Directory integration features.
(For more on integrating Macs and Active Directory, see our DAVE 6.0.)
Thursby ships a Tiger-compatible DAVE 6. September 14, 2005 -- Thursby Software has shipped " + contact + ", a new version of the SMB/CIFS file and print sharing software for Mac OS X and for Mac OS 9. The new version is compatible with Mac OS X 10.4.
DAVE has features not found in Mac OS X, including support of Distributed File System (Dfs). DAVE stores both resource and data forks of a Mac file in a single filename, just as Microsoft's services for Mac does. Tiger simply deletes resource forks, which can result in the loss of metadata.
If you've tried DAVE 6
DAVE 5.x incompatibile with Tiger 10.4.0. May 2, 2005 -- Thursby Software announced that its workaround at it's web site. Thursby described the changes in networking:
The vastness of Apple's enhancements to critical parts of the system (both the kernel dealing with network transports and the file system) are requiring a major effort to obtain compatibility.
Thursby reports that when upgrading to Tiger when ADmitMac is installed, the Mac can fail to boot. Thursby provides a DAVE 5.1.
Thursby said that part of the problem is a bug that Apple has acknowledged, and that Tiger compatible versions of ADmitMac 3.0, due on August 8, and DAVE 6.0, due in late August, were dependent on Apple's bug fix.
DAVE 5.1 update for more recent Panther and Office versions. November 18, 2004 -- Yesterday, Thursby Software Systems released DAVE 4.02p1 (free upgrade for 5.x users), the cross-platform file and print sharing software for Macintosh computers. Enhancements include:
DAVE 5.0 adds support for Win Server 2003 and Panther. January 6, 2004 -- DAVE 5 (US $119) adds support for Mac OS X 10.3 and access to Windows Server 2003 using NTLMv2 and SMB signing. (It is also available for Mac OS 9.) DAVE 5 provides three security options: local-level, share-level or user-level.
DAVE 4.02p1 fixes OS X problems. March 21, 2003 -- Thursby has released DAVE 4.0.2, a maintenance patch to its cross-platform SMB file and printer sharing program for Mac OS 9 /OS X. Included in the update are the following fixes for Mac OS X:
DAVE 4.0.2 maintenance update. December 20, 2002 -- DAVE 4.0p1 for Mac OS X and for Mac OS 8.6 - 9.2 are free downloads to DAVE 4.0 customers. The new version includes these improvements:
Thursby releases patch for DAVE 4.0: fixes lockup bug--October 18, 2002, 3 pm PST -- Thursby Software is a patch that fixes two problems:
1. Copying files to or from the master browser of the workgroup/domain of the Macintosh could cause the Mac network traffic to cease.
2. Renaming a shared folder and then editing the original share in the DAVE Sharing preference pane could cause System Preferences to unexpectedly quit.
Charles Whilen forwarded a technical support alert from DAVE v4.0 describing one of the problems with DAVE 4.0:
We have become aware of a situation that can cause the Macintosh to lock up when copying files to/from a server that is acting as a Browse Server. We are aware that this is a serious problem and are working to provide a patch for this situation as soon as possible.
To work around this problem, be sure that the server you're using is not a Browse Server for your domain/workgroup. On small networks (with only one workgroup/domain), disable the Browse Service for that computer. On larger networks (with multiple workgroups/domains), change the Macintosh workgroup/domain to one other than the server uses (this can be done in the DAVE Network preference pane).
Thursby releases DAVE 4.0--adds NT domain login. September 26, 2002 -- Thursby Software Systems today released Download here (US $149), a new version of the cross-platform file and printer sharing software for Mac 8.6-9.2 and Mac OS X 10.1.5-10.2 on Windows-based networks. DAVE 4.0 goes beyond the SMB file sharing features of Mac OS X 10.2, and supports these features on all the versions of Mac OS it supports. For instance, DAVE 4.0 won't leave "dot underscore" files on the server. Features of DAVE 4 include:
Like previous versions, DAVE 4 is two-way, letting Macs access Windows PCs and visa versa.
Patch for DAVE 3.1p2 February 19, 2002 -- (log in "DXCannotInnitCIFSD" problem -- no info at the Thursby web site). The Readme file says that the patch is designed to fix kernel panics that can occur in some circumstances, including when deleting folders, importing MP3 files into iTunes to a DAVE volume, and when using NetBarrier X. The patch also fixes a problem when DAVE 3.1 would report that it couldn't delete all of the items because some files were locked, when they weren't.
However, the Readme file warns that the patch should be only used if necessary:
DAVE 3.1p2 has not been formally tested. Therefore, you should only use this patch kit if you are experiencing the problems listed below which have been corrected with this patch kit.
-- DAVE 3.1 for OS X 10.1 and OS 8.6/9.2, shipped on November 12, 2001. This is the version that runs on Mac OS X 10.1. It comes with separate installers for Mac OS X 10.1 and for Mac OS 8.6-9.2. Features include:
Here is a more techincal description of DAVE 3.1 for OS X from a Thursby Systems customer newsletter:
The services that DAVE provides to you had to be completely rewritten for OS X. We wanted to integrate our Windows network file client directly into the OS X operating system. Fortunately, we drew heavily on our experience writing networking protocols for UNIX systems. Thursby Software got its start providing protocol stacks such as DECnet and LAT to the Macintosh and UNIX systems...
DAVE 3.1 for OS X has two components known as KEXTs that operate inside the OS X kernel. One provides network and security services to other parts of the product. The other provides the file system that allows you to mount PC shares on your OS X system. By putting crucial networking, security and file services inside the kernel, DAVE can provide the highest performance while using the least amount of system resources.
There is another major benefit of putting DAVE inside the operating system. We can provide file services that understand the needs of Macintosh users. Our file system provides built-in support for Macintosh file resource forks and other meta data (such as file creator and type). This allows us to access and store data on Windows NTFS volumes just like Microsoft's own Services for Macintosh, and like previous versions of DAVE. In fact, DAVE strictly follows Microsoft methods for storing Macintosh files on NTFS. This provides our customers with a very high level of interoperability with Services for Macintosh, allowing seamless access to files stored with both OS X and older versions of the Mac OS.
Other OS X file services such as NFS, Sharity or Apple's own SMB must rely on a "compatibility layer" to provide the special needs of Macintosh files. This "compatibility layer" actually makes files services that use it LESS compatible with Microsoft's Services for Macintosh (and DAVE). You might also notice that it leaves lots of extra files laying around on your server. A file named "OurLogo.jpg" will also have an extra file named "._OurLogo.jpg" in the same directory. These extra files have been known to increase the anxiety level of Windows system administrators. Macintosh users really don't want to make PC administrators anxious.
DAVE also relies on other new technologies in OS X. We provided a directory service plug-in to support browsing your PC network from the Finder's Connect To dialog. We also provided print serving support for all OS X print drivers by integrating with the new Tioga print architecture.
-- DAVE for OS X 10.0.4 version 3.0a8, released August 9. Fixes the free download.
-- DAVE for OS X 10.0.4 was relased July 17, 2001 as a . This free release only works with Mac OS v 10.0.4 (and not earlier versions) and is not a "preview" release or a beta. There is no formal support for this first version of DAVE for OS X. Thursby plans to issue a commercial release of OS X at a later time, which will also add new OS 9 features, such as support for long file names and for large files sizes.
-- DAVE 2.5.2 was released in March, 2001. New features included:
-- DAVE 2.5 was released in October, 1999. New features of DAVE 2.5 included:
What are Node types?
In PC networking, node type refers to the method a PC will do NetBIOS name resolution (matching a computer name to an IP address), or, how PCs find each other on the network using NetBIOS name resolution. (In general networking terminology, a node is a device with a network address, such as a computer.)
NetBIOS name resolution is different than DNS name resolution, which also can occur. NetBIOS names are the names given to PCs and PC servers (and Macs running DAVE or DoubleTalk). NetBIOS name resolution can occur with a WINS server (Windows Internet Name Server), or with PCs communicating directly with each other.
(NetBIOS is sometimes confused with NetBEUI. NetBEUI is a network transport protocol, an alternative to TCP/IP. NetBIOS is not a network transport protocol: it is a Microsoft name resolution technology that can be used with TCP/IP or other protocols.)
The two most commonly used node types are B-nodes and H-nodes
What is a B-Node?
B-node is short for "broadcast node." B-nodes broadcast name resolution information to all the other workstations on the network to discover what PCs are on the network. Instead of using a WINS server, all of the PCs communicate with each other. (Similar to the way AppleTalk does it.)
B-nodes are typically used on small networks that may not have a WINS server.
What is an H-nodes?
H-node is short for "hybrid node." H-nodes first look for a WINS server to resolve a computer name to an IP address. If it doesn't find a WINS server, it uses the B-node technique of broadcasting to all the other PCs on the network.
H-node is commonly used for networks with Windows servers, and is the default for Win32 clients.
Are there other node types?
Yes, there are two other node types that are not commonly used. These can be useful for troubleshooting mode, but are not recommended for daily use with DAVE or DoubleTalk.
P-node is short for point-to-point, in that it only queries a WINS server, and never communicates with workstations for name registration. P-node is the opposite of b-node.
M-node is the opposite of h-node--it first broadcasts name resolution, then switches to P-node (looking for WINS server) if no answer is received. (M is short for mixed.)
How do I change the Node type in DAVE?
Use the NetBIOS control panel, Mode Pull-Down menu.
The NetBIOS mode default is dependent on the WINS settings on the Main control panel. See the WINS Check Box section in this chapter. If a primary WINS is set, H mode is the default. If a primary WINS is not set, B mode is the default.
For further information, see Microsoft KnowledgeBase article Q119493, article Q142042 and article Q160177. There's also a NetBIOS reference page with more technical details.
(Thanks to Chris Champion, Richard Laframboise, John Lockwood, Mark Notarus, Linden Siahaan, Ian Sokoloff, Fred Tsui, Francis Uy for helping with this article.)
Permissions and views in DAVE 2.1.
September 10, 1999 --
A reader reports a problem with DAVE that has been confirmed by Thursby Software Systems. It is a problem with permissions on the desktop database. When a user expands a folder on a network volume, other users accessing that volume they can see the expansion. There is no way to prevent this.
September 13, 1999 --
Thursby Software Systems' Customer Support Manager Carl Ketterling responded by saying that when a user expands a folder on a network volume, other users accessing that volume they can see the expansion. Ketterling explains:
This situation is not considered a bug. View settings are saved with the folder, so that if a user has write privileges to a network folder, any view settings he sets will be saved (for all users). One customer compared our product to Services for Macintosh in this scenario and pointed out that with SFM, views are not saved unless the user 'owns' the folder. Unfortunately, we are not able to find such information from the Windows network.
I apologize if any of your readers have been mislead, and we welcome any suggestions your readers may have related to this problem.
September 27, 1999 -- B.J. Stahlin is having this problem with DAVE 2.1:
Has anyone reported a problem with the DAVE Sharing Extension? Our corporation is using DAVE v2.1 (Client 2.1p). Our corporation's symptoms is a system stall. When command-option-shift is pressed the offender is always the DAVE Sharing Extension.
Thursby claims this is a WINS issue. However, the LMHost file is accurate, as well as the WINS configuration throughout the NT domain.
We are using DHCP, quite successfully, on NT 4 (sp4). Whether or not sharing is disabled in the control panel seems inconsequential.
October 8, 1999. James L. Loeb offers this advice:
Make sure the LMHosts File is in the correct directory.
Also make sure that the NT server is NOT multi-honed. DAVE had a problem with this. This is most likely the problem.
October 12, 1999
Charlie Marorelli sent us another possible explanation for the problem of Thursby's DAVE stalling that we've been reporting. He said that Thursby tech support told him it was a problems with clocks being out of sync. Marorelli set the clocks of the Mac and Windows PC to the same time and the problem disappeared, but reappeared a week later. Marorelli then discovered that reinstalling Windows 98 fixed the problem.
December 8, 1999 -- Keith Billy noticed that users have the option of viewing hidden shares on Windows NT servers: He thought that this might be a security problem.
I have been evaluating the recently released version of Dave 2.5. While some of the new features are nice additions to the product, they have added one option that I particularly don't care for. Anyone using the new version now has the option to view hidden shares on the servers. I don't know if I'm being overly paranoid about security, but to me this feature has the potential to create a major security problem. I always figured that they were called hidden shares, because they were supposed to be "hidden".
When I contacted Thursby's support department to find out if there was a way to disable this option and was told, "NO", unless I wanted to run ResEdit on the application to remove the option from the menu.
However, Carl Ketterling of Thursby Systems says that this is not a security risk, and that Windows utilities can also make hidden shares visible:
In Windows, '$' is a special character when used as the last character of a share name. When this is done, the share is not displayed in a browse list -- thus calling it a 'hidden share.' By default, DAVE does not display hidden shares. However, there is an option in the DAVE application to allow these to be listed. The customer would like to disable that option for his users (which is not currently possible).
We do not consider this option to be a security risk. The names of hidden shares are transmitted over the network in plain text, and the network client is responsible for filtering these names from the list.
Any user with access to the network is able to get a complete list of shares by using a trace utility. Though I believe there are simple utilities that will list these shares on Windows, I cannot find any currently.
Customer Support Manager
January 10, 2000 -- Dr. Robert Henry Arnott is using DAVE on his Mac to access an emulated Windows NT network environment running on a UNIX box: Totalnet Advanced Server running on Solaris 2. It generally worked, but Arnott ran into a problem with permissions on files placed by Windows users:
This may be of interest to you. It certainly took us a little while to understand.
I am a lone Mac user in a Windows environment and use DAVE to interact with a Windows NT network emulation (Totalnet Advanced Server, TAS) running over Unix (Solaris 2).
We happened to notice (following a server problem) that files placed on the fake-NT Unix server have different permissions from those placed by my Windows coworkers. The NT server is divided into "services" areas within which are various directories. We are a multidisciplinary research institute so, for example, in a service area called ".groups" there are a number of directories, "neuro", "epi" and so on, containing group-specific shared resources. Users have read/write permission for their own files and others' files in their group directory but just read permission for files in other group areas. Thus a user would create a file -rw-rw-r-- in his/her own group area and could modify coworkers' files by virtue of being a member of the same group.
For a historical reason to do with upgrading TAS, the system administrator had instructed the server to set permissions at the level of directories rather than of services. This worked appropriately with PC users. DAVE, however, wrote files with permissions set to -rw------- in directories where the server was supposed to impose -rw-rw-r--. This was only rectified when the sysadmin altered the TAS configuration to impose -rw-rw-r-- permission at the services level. It thus appears that DAVE is able to circumvent TAS's directory-level settings in an un-PC-like way.
I thought this rather esoteric finding might be of interest.
We realized this was happening because I am using part of the fake-NT server as a website and transferred html files from my Mac into the website directory. The server had crashed shortly before and the web server program's user and group attributes had become altered (it pretends to be me when retrieving my html files). Thus the web server was only able to pass new files where I had done chmod 666 because, even though the web server was a member of my group, it couldn't access my TAS-defying -rw------- files!
Connectix reports a problem with Virtual PC networking when running DAVE on the same Mac. For details, see our .
August 28, 2000 -- Jean Pierre Savoie reports that DAVE has a problem with Quark Xpress files: "When opening a file from a Mac station, this file is not locked, which means the file can be opened by another person on a Mac and a PC."
There is a major issue with DAVE 2.x regarding locking files for exclusive use. That issue is happening with Quark Xpress (and Passport too). When opening a file from a Mac station, this file is not locked, which means the file can be opened by another person on a Mac and a PC. That kind of environment is a risky one because the last man standing is saving the latest changes. That issue forced us to uninstall the software on our 50 Macintosh.
Except for that, the DAVE client is an efficient tool for accessing large volumes and with new feature as disabling the auto refresh ( 2.5), it solves a lot of issues with binding large volumes with Macs. (We are accessing an HP Surestore 1200x which is a 237 platters MO.) With that feature, the community is not frozen when a request is done and the library is updated, otherwise as an AppleTalk Volume, everybody is freezing because of the auto refresh.
November 2, 2000 --
Director Customer Support
We've decided to make a change in the response that is returned to an application when an open file command fails because the file is in use. In the past, our response caused QuarkXPress to immediately request the file be opened read-only, but QuarkXPress would not notify the user of this detail. Now, the error we return causes QuarkXPress to notify the user that the file is in use and cannot be opened. This will most likely address 99 percent of the QuarkXPress vs. DAVE problems that customers are having. This change is included in which is available on our website.
September 22, 2000 -- A reader named Janet is having problems with using DAVE and NetBIOS on a virtual private network:
I think I've run into a problem that I can't resolve trying to configure DAVE. I'm using a brand new G3 PowerBook, going through a Time Warner RoadRunner cable modem, using my company's VPN software, and I cannot get NetBIOS to work.
The problem is that NetBIOS takes the first IP it sees upon BootX of the machine (I've naturally got DHCP turned on). So, it's picking up an IP from the cable modem.
But I need to boot up my machine, then evoke my VPN software, do the password protection stuff, and then my work server gives me an IP number. In order to use NetBIOS, I have to figure out a way to get that final IP number into the NetBIOS control panel, yes?
For the life of me, I can't figure out a way to do this. I tried booting up the machine with NetBIOS turned off, then turning it on after I was into my VPN connection, but NetBIOS still grabs an IP from the cable modem.
One saving grace is that I can click on DAVE in my Chooser, let it time-out and tell me my Master Domain is not answering, and then force it to connect me to servers at work with their known IP numbers. Then, I alias the server icons, and use those from then on out to connect to my servers.
Any ideas on how to make NetBIOS work in this environment?
November 2, 2000 --
Director Customer Support
I haven't seen this personally, but I think I understand what's happening. I believe the VPN software is actually setting up a new IP address for the Macintosh using multi-homing. Because DAVE uses the first address of the Macintosh, the customer is not getting the results she is expecting.
One workaround for this situation may be to change the broadcast address in DAVE's NetBIOS Control Panel (Administrator Settings) to be valid for her work network. Another workaround would be to use WINS or LMHOSTS and Commonly Used Servers as is common for Windows file sharing over wide area networks.
March 12, 2001
I've got a G4 desktop and a PC laptop that uses a SkyLINE PC card. They both play "together" when used with my AirPort Base Station; they both can grab an IP address from DHCP and use NAT to access the Internet. Both machines can surf at the same time when I use the modem on the Base Station.
However, I really need to share file between the two machines. I thought Dave might be my solution here...Dave 2.5.1 stalls just when the Finder is about to load completely.
Marquez also wondered if there was some special DAVE configuration needed for AirPort networks. If you have any advice, please .
March 14, 2001
Yes, we have had some problem with DAVE over AirPort also. Our trouble was getting DAVE to mount volumes.
One solution was to create aliases of mounted volumes beforehand (when connected with an Ethernet cable) and use those aliases to mount the volumes we wanted to browse.
The other was to use the mount manually option. This would probably work for Roy Marquez. He could manually mount his PC C$ drive and make an alias of it. Then in the future he just needs to use this alias.
March 14, 2001
If Mr.Marquez uses 9.1, he may need the latest patch for Dave Client (2.5.7) and NetBIOS (2.5p6) at www.thursby.com. I've never experienced his problem on my setup: iBook SE/Airport/Dave, ABS, Win98 PC and Linux Samba machine. Can see them all just fine.
The patch is primarily intended to solve a file copy problem with 9.1.
details in our FAQAn answer and a workaround
March 14, 2001 -- Carl Ketterling of Thursby Software has responded to our reports of problems with DAVE on AirPort networks. First, he points out that NAT in the AirPort Base Station causes name resolution problems. Thursby also recommends using a fixes IP address in the Mac when using DAVE on an AirPort connection. Ketterling's message:
The only problem DAVE's ever had with AirPort is when trying to resolve names across NAT. From my tests, however, NAT is not used between two clients connected to the same AirPort. And even if it did cause a problem, it wouldn't result in a hung computer at boot. It actually sounds like the name resolution isn't working properly over that configuration.
We have confirmed that NAT is not used between wireless connections to the AirPort Base Station. Therefore, using Windows and Macintosh both connected wireless will be no different than using both connected via Ethernet when using DAVE or any other network application.
When using NAT on an AirPort, there are browsing problems with DAVE that can be worked around. I believe you have details on your site about this, and I know we have Airport special report.[Search for AirPort.]
As always, we'd like any customer who's having problems with DAVE to contact us so we can help resolve the issues.
Director Customer Services
Thursby's FAQ has this to say about about using DAVE over an AirPort connection:
DAVE can work with AirPort if you turn the AirPort Base Station into a simple router and avoid using Network Address Translation (NAT). Configure the Macintosh with a fixed IP address. Configure the AirPort Base Station with a fixed IP address and to "Distribute a range of IP addresses" which includes the IP address being used by the Macintosh. All IP addresses must be in the same subnet as the rest of your LAN. (Note: Setting the Base Station to have a fixed IP address is not absolutely necessary).
For more on configuring AirPort in cross-platform networks, see our page.
TIP: DAVE performance
A reader report
May 29, 2001
David Ezzy reported that of a performance problem using Thursby System's DAVE without a hub:
I have a PC running Windows 2000 with a SMC EZ 10/100 Ethernet card and a Apple G4-466 linked with a crossover cat5 Ethernet cable and am using Thursby's Dave. All works fine, except the file transfer speeds from the Mac to the PC are painfully slow whereas, the transfers from PC to Mac are fast.
I have disabled all anti virus software. I have checked the network with "WhatRoute 1.7" diagnosis software and everything seems fine with the network.
May 30, 2001
I wonder if the reader is using the DAVE browser or a mounted volume on the desktop. I find it's much faster to transfer files using the DAVE browser.
May 31, 2001
Gregory Smith wrote to say that he found that file copying in DAVE was faster using the DAVE browser than using a mounted share on the desktop. I am writing to say that my experience is exactly the opposite.
I have found that when copying extremely large files (in the multimegabyte range), the DAVE browser can be twice as slow as mounting the share on the desktop. The machine I was using is a G4/450, DAVE 2.5.1, Mac OS 9.1.
June 11, 2001
I too have seen this problem. I use DAVE 2.5.1 on an iMac 400 DV connected to a Windows Workgroup. File transfer to the PC network is really slow. I haven't tried it the other way around, though.
June 13, 2001 -- Nicholas Lucia sent us a report of this performance problem:
We ran into the DAVE performance issues also. We were testing multiple products for a large Macintosh group inside a major corporation. We evaluated DAVE, ExtremeZ-IP and MacServer IP (NT SFM was out because it was NT 4.x and IP is the only allowed protocol). In all cases, the copy process to the server was at normal speed and a copy from the server would go slowly (16K increments every 20 seconds). Changing the workstation duplex to full fixed copy performance completely for all products. When we talked to the Thursby people about this, they had no answers.
Lucia also has sent this performance tip:
If you have a large amount of Mac users accessing the same share, make sure that all DAVE clients have "Disable Desktop Database" checked in the Chooser setup (this affects any access that puts the DAVE icon on the Desktop). After ~12 users, new users would not be able to log on via 2.5.3 because of some inconsistency in the desktop database. This required that I delete the desktop database from each directory on the server (even automated through AppleScript, this took a LOOOOOONNNNGGGG time). The better choice is to let each workstation "cache" it's database instead of writing it to the server.
July 3, 2001
Chris Backert wondered if DAVE can work with the Windows 2000 Active Directory:
I currently work in an office with a Windows 2000 environment that is in the process of implementing Active Directory. At the time we are using DAVE software to allow our Mac users to be compatible with our network, but with the pending switch to active directory we may have to find a new solution. According to Thursby.com "Currently, DAVE 2.5.2 has not been tested with and does not support Active Directory or Distributed File System access. This issue is being looked into for possible resolution in a future release of DAVE." Any suggestions?
Several other readers did have some suggestions:
July 6, 2001
It is important to know what function Active Directory will be deployed.
Active Directory is used as a name for a lot of different technologies. One of the most important is USER Managment, another is the NETWORK Managment. All these parts are no "compatible" with their NT counterparts, thus DAVE can not do it. You would need a real Active Directory client for MacOS9/X, that I guess would be difficult to implement.
So they are out of luck if they don't use an NT Server as a kind of bridge to the Mac, NT, and Windows 95/98 world.
PS: For user management exist other better solutions (LDAP Servers like that from iPlanet which you can use in Mac OS X).
July 6, 2001
I have successfully used Dave to login to a Windows network running Active Directory, and in to the W2K Server itself. The W2K server was NOT running Active Directory in native mode. This means it is able to be backwards compatible with Windows NT Domain controllers (it also appears itself when in this mode as both a PDC and Active Directory controller).
I would NOT recommend running Active Directory in native mode as you then lose this backwards compatibility (this would also make it unable to talk to other systems like SAMBA).
I have not tried using Dave myself with DFS (Distributed File System).
However as a general comment, I would have thought that if a Win 8 client can access the server then Dave should be able to as well (since Win 8 also does not truly support Active Directory or DFS either).
As a general comment, Active Directory is a good idea (in that a directory of any description is a good idea). However, as usual Microsoft have made a very poor implementation of a good idea (at least for this their first version, maybe by version 3 it will be usable). Furthermore, Microsoft have yet again hijacked standards intended for other purposes (e.g. DNS) and mutated them for their own purposes.
One consequence of the above is that you cannot rename a DNS domain name if it is being used for Active Directory (as well as Internet) purposes (which is the recommended choice by Microsoft). You must also make sure not to use someone else's legitimate DNS Domain name (easy enough to do if you choose a fictitious root domain, but what about the future? Several new root level domains have just been created after all).
To rename a domain you have to create the new one, move the directory objects to the new domain and then delete the old one. This of course in typical Microsoft manner is nowhere near as simple as it sounds. What's more this is potentially a much more common situation than you may think, for example what if a company changes its name, or merges with another company?
PS. As you and others will be aware, Windows still uses three letter file extensions to determine what type of a file a document is (e.g. '.doc' is a Word file). Did you however know that Microsoft has started to hijack other companies established three letter extensions? For example '.pdf' as everybody (except Microsoft) knows is an Adobe Acrobat PDF (Portable Document File). Microsoft have stolen this to act as their own file type for Package Distribution Files (in W2K). The result is that if you double click on an Adobe PDF file it will no longer have a proper Icon and Windows will not know to open it in Acrobat. One can 'reeducate' W2K (preferably with a baseball bat or other blunt instrument) to associate '.pdf' with Acrobat instead but it should not be necessary to do this.
(For information on node types, see the above.)
July 24, 2001
Gregory Smith found that DAVE was causing some problems with the sleep function of his iBook, and so tried Connectix' DoubleTalk. However, he had a different problem with DoubleTalk:
I currently use DAVE for networking my iBook with our NT network. After disabling all of the DAVE components I found that my system was more stable and sleep worked more reliably. I wanted to try DoubleTalk so borrowed a copy from a friend. (I'm willing to buy my own copy once I see it works to my satisfaction, which it doesn't yet). The problem I'm having is DoubleTalk reverts to a "B" type node when using DHCP. In DAVE I could set it to DHCP and a "H" type node, which apparently our network requires (don't know what all of that means myself). Connectix won't provide support unless you register so they are of no help. Hopefully someone out there has experience with this.
The answer to the DoubleTalk question from Connectix:
July 26, 2001
When you configure DoubleTalk to get its settings using a DHCP server, DoubleTalk will honor whatever NetBIOS settings your DHCP server returns. In Gregory Smith's case, his DHCP server is either instructing DoubleTalk to use broadcast mode (B-node), or is not returning any NetBIOS settings in which case DoubleTalk reverts to B-node. Some DHCP servers, such as hardware routers, cannot be configured to give out NetBIOS settings.
The solution is to configure DoubleTalk manually. Open the DoubleTalk control panel and select "Manually" from the "Configure" pop-up menu. Since the DHCP server is not providing the WINS server's IP address, you will need to get it from your system administrator and enter it into the control panel.
DoubleTalk has extensive online help explaining each field in the control panel in detail, and in most cases the Setup Assistant will guide you through the configuration process. Probably not Gregory's case though, since his DHCP server was not providing the necessary information.
July 31, 2001
Gregory Smith tells us how he finally was able to set DoubleTalk as an H-type NetBIOS node, and compares it to DAVE:
I had to set up DoubleTalk manually with H-type nodes and type in the IP address for the WINS servers. The interesting part is Dave seemed to get this info on it's own (I used Dave to get the IP addresses for use in DoubleTalk). I believe Dave uses DNS to find the WINS servers but that is just my guess (I'm no expert on this stuff). Also DoubleTalk did have a good help system that talks about what the different types of nodes are, I apparently missed it the first time.
This problem is often accompanied by and error message displaying "DXCannontInitCIFD." Suggested fixes are described below.
July 31, 2001
I tried using DAVE 3.0 on my Pismo 400 with OS X 10.0.4. Previously I had used Sharity but I disliked the long restarts/shutdowns attributed to it. I connect to my company's Windows 2000 network.
However, when I try to log on with DAVE (either directly or automatically at startup), I get an error message stating that my Password/User ID is no longer valid. But I know this to not be the case; either a PC box or by using Sharity on my PowerBook accept the same info. Eventually DAVE will "backdoor" to the Explorer window and I can access the servers. But it is never a reliable or reproducible workaround. I certainly don't know what I do to finally access the network.
I tried changing the password on the PC then try the new password with DAVE, but I get the same result.
August 1, 2001
The Log-in error happens to me too. Win2K servers are in use; I downloaded DAVE 3 when it was announced and it is running on 10.0.4
August 1, 2001
I'm having a similar problem with DAVE X to what David Nine describes.
Using the Explorer window to browse the domain I can connect to any visible machine without any problems. But whenever I try to use UNC I get the invalid userid/password message. Even machines that I have browsed to successfully get the invalid message.
Unfortunately most of the shares I want to access (MP3 server, sourcelib, IS documents, etc.) are on hidden shares that can only be reached using UNC. I'm now getting an alert "DXCannotInnitCIFSD" whenever I try to launch DAVE Explorer and the DAVE X control panels won't even drop down from the system preferences. I have only played around with DAVE X for a short time because of these problems. Also, I haven't restarted my TiBook for about a week now, so changing locations and sleeping might have screwed something up.
August 3, 2001
I can verify that this problem is caused by sleeping a PowerBook/iBook without logging out of Dave. The only fix (besides a reboot) is to make sure you use the "Log out..." command in Dave Explorer before sleeping your 'book.
August 6, 2001
I can also confirm the 'DXCannontInitCIFD' error on the launch of Dave for OS X. However, I've found a simple solution: simply rerun the DAVE setup assistant (/Library/Application Support/DAVE Setup Assistant/), leaving all of your settings the same and then relaunch the DAVE Explorer program and everything should work fine. I've been using this technique whenever I get the error for over a week without any complaints
August 6, 2001
This day's update includes a report by Leland Jory, he says he "gets the "DXCannotInnitCIFSD" when he tries to launch DAVE Explorer in the DAVE 3 for OS X", and I've been getting this error too since I installed DAVE. This happens because the cifsd application which queries for SMB shares crashes randomly. You do not have to reboot the computer to fix this, all you need to do is relaunch cifsd. From the command line, type 'sudo open /System/Library/Filesystems/DAVE/cifsd.app' then you can use DAVE Explorer to browse for SMB shares.
August 8, 2001
I have Dave 3 on my OS X 10.0.4 cube at work and home and have the same problem with the DXCannontInitCIFD cannot be initialized after putting the computer to sleep. One reader noted doing a reinstallation of Dave to fix it. I found that if I logged out and back in, it worked fine until I put the computer to sleep again.
October 10, 2001 -- We received several reports that DAVE 3, which runs only on OS X 10.0.4, was also inhibiting the SMB/CIFS Windows file sharing client that is built into Mac OS X 10.1, after users had upgraded from 10.0.4 to 10.1. We asked Thursby Systems if this was true and how one should remove DAVE for OS X 10.0.4. We received this reply:
Yes, this is true. To remove DAVE, run the installer and choose uninstall. We strongly suggest that you reboot the computer BEFORE uninstalling. During the uninstall, you may receive errors that the uninstall was unsuccessful -- this message is incorrect.
If you've deleted the installer, you can download a copy from the following URL:
Thursby Software Systems, Inc.
Paul Lira tried this successfully and reports his experience:
I ran the uninstaller and there was a lengthy hang in the installer application but it then completed. Next, I went to the 'Go menu' and 'Connect to Server', typed in smb://servername/ and I got my login to my NT server and I logged in fine. No restart was even needed after the uninstall.
December 10, 2001
I've had an issue with Dave 3.1 for OS X a couple of times where I all of a sudden cannot connect to any Windows networks. The DAVE Network does not show up in the "Connect to Server" dialog, and I cannot log in from the DAVE Network pref pane. I think I may have found a workaround, however.
First, kill the cifsd process (if it's running). Then, browse to /System/Library/Filesystems/DAVE/ and launch cifsd.app (it's the only item in there). You should now be able to log into the Windows network and access shared resources.
December 18, 2001 -- Thursby Systems reported an "undocumented tip" for DAVE for Mac OS 9 than enables you to make use of shortcut files on mounted Windows servers:
1) Open the File Exchange control panel.
2) Click the "Add " button. The Add Mapping dialog should appear.
3) Enter the three letters LNK in the Extension text bo
4) Click the Select button. The "Select An Application" dialog should appear.
5) Navigate to the DAVE folder found on your System drive (the one that holds the DAVE utility). Open the folder, then open the DAVE application.
6) Click on the File Type: pop-up menu and select "shct".
7) Click the Add button and then quit File Exchange.
Your Macintosh can now handle Windows shortcut files! Shortcut files are like aliases on the Macintosh. You may come across them on a mounted volume, or PC users may e-mail them to you. If you click on one of these files, DAVE will try to figure out where the file is stored, then mount that volume on your desktop and tell the Finder to open the file. A shortcut must be for a file in a shared folder. If it is not, you won't be able to access it from your Mac (and neither will other PC users).
January 21, 2002
Steve Byan thinks DAVE 3.1 has a conflict with Synchronize!a third-party file synchronization program in Mac OS 9.2:
I upgraded to DAVE 3.1 on my PowerBook G3 last December. Our network uses NetApp servers for our SMB shares. DAVE 2.5.1 worked fine for me, but when I upgraded I began to get "-50" errors when attempting to use Synchronize to sync my PowerBook with my SMB share. Finder copies work fine. I've just tried opening a file on the share using BBEdit and got the same -50 error. CodeWarrior also fails to open the file, but does so silently, without any error dialog box.
January 30, 2002
David Bills sent a workaround:
I've had this problem. What happens is that the permissions on the windows volume get set incorrectly. I'm not sure exactly what they are, but you will have problems accessing the files on the windows computer too. I got around it by copying and pasting the affected folders of files under windows and then recycling the originals. I'm guessing that this procedure simply rewrites the permissions on the folder.
January 30, 2002
Meanwhile, David Bills has a problem with this software and DAVE in Mac OS X. He also supplies a workaround:
I'm having a problem with the new beta 4 software. It seems that Synchronize is creating a permissions problem with SMB volumes mounted via DAVE under OS X.
The problem first manifested itself when I saw a -50 error under OS 9.2 when trying to access files with BBedit which had been synched. Then, I started getting crashes under Windows 2000 when trying to access the files.
What happens is that the permissions on the Windows volume get set incorrectly when synching.
I got around my problem by copying and pasting the affected folders under Windows and then recycling the originals. I'm guessing that this procedure simply rewrites the permissions on the folder.
June 14, 2002
The source of the problem turned out to be our Network Appliance servers, which are old enough to be incompatible with NetApps newest releases of its software. Consequently we run them with an old revision (version 5.2.6R2), rather than 6.<something>. DAVE 3.1 did not support these older versions. DAVE 3.1.1 has resolved this problem and works fine with our older NetApp servers, both under OS 9.2 and OS X 10.1.4 and 10.1.5. Apple's build-in SMB network client still fails to work with the older NetApp servers.
report their symptoms to our support departmentMicrosoft Office X copy protection bug -- the cause of a problem with DAVE?
February 15, 2002 -- Alan Griffin reports a problem with Office X applications over a network with DAVE connection:
I have just made the transition to OS X and as I need to connect to an NT network I upgraded from Dave 2.5.2 to Dave 3.1. Imagine my shock when I was unable to open Excel or Word files across the network.
...The workaround is to drag files to your local machine then copy them back when they have been updated, but this is a completely impractical way to work in an environment where you are sharing files all day every day.
We asked Thursby Systems Director Customer Services Carl Ketterling about the problem. He responded:
We've had several reports of this problem -- enough to know that is a serious problem -- but we have other customers using Microsoft Office without problems. We are having a difficult time reproducing this in our office which, as you know, is usually the first step in resolving a this type of problem. We have documented this as a bug, and we hope to have it corrected in our next release. For customers experiencing this problem, we would like them to MacInTouch. As stated above, we do not yet have a solution, but the information may help us track down the problem and will allow us to contact customers once a solution is found.
However, this problem could be related to a Microsoft Office X "security bug," which is a problem with the anti-piracy software in Office X. (See this Network Security Update page report on the issue.) Microsoft has released a OS X FAQ.com as a fix for the bug. (Macintosh writer Bob LeVitus provides some tips on installing the update at let us know.
If you've seen this problem (with DAVE or another network), let us know. Also let us know whether you've installed the Microsoft Network Security Update.
February 20, 2002
Per Thörnblad confirms our theory about the Microsoft Network Security Update fixing this problem:
I had the same problem as Alan Griffin reported about not being able to open Word-files from a Dave-mounted file server. I am using Dave 3.1 and Mac OS X 10.1.2.
After installing the security update for Office X the problem seems to be solved as I now can open Word from my file server.
February 21, 2002
I agree that it does seem like that Office X security patch has cured the problem with not being able to open files on DAVE volumes.
Unfortuantely, Alan Griffin reports that this hasn't fixed the problem:
March 11, 2002
I applied the Office security patch and updated to system 10.1.3 for good measure - made no difference.
I then disabled ports 2222 and 3640 using Norton Personal Firewall - which I read somewhere would defeat the MS copy protection checks - bingo for one glorious afternoon I could open files happily across the network.
The following day I was back to the same error message with Excel files but still able to open Word documents. That's the way it still stands. Makes no sense to me!
If you've seen this problem and have installed the Microsoft Network Security Update for Office, please if it affected the problem.
February 18, 2002 --Greg Newton is having problems using Retrospect to back up Mac files on a Windows NT network using DAVE 3.1:
We have been successfully using Dave 2.x for around 3-4 years now and it has been a great product. We just purchased some new Macs to use on our NT4 server based network and I decided to upgrade to the new 3.1 version to try it out. All systems were go, until I tried to back up the server to my new G4 (running OS 9.2.2) using Retrospect 4.3. I did this regularly using 9.2.2, Retrospect 4.3 and Dave 2.5.x with no problems. Now, using Dave 3.1 I get huge numbers of errors in the Retrospect log (typically a -127 error) and Retrospect gives the warning that the "volume may be corrupt?" which is always reassuring.
Quitting Retrospect and attempting to open a folder on the server that yielded the "-127" error, I find that most if not all my files are apparently missing. The only way to get them back is to log off the NT server and log back on and bingo, all the files are back. Attempting to backup again yields the same problem with the mounted server "forgetting" files which apparently causes Retrospect to generate numerous errors. Has anyone seen this type of error? Again, this never happened when using earlier versions of DAVE.
February 20, 2002
Problem confirmed and is directly related to version 3.1. I reloaded version 2.5.2 and Retrospect works perfectly. I have reported this problem to Thursby and they are taking a look at it.
On a positive note, opening of directories on the NT4 server by a Mac client that contains hundreds or even thousands of files is significantly faster than in version 2.5.2. Will keep you posted on further findings as necessary.
If you've seen these problems, please .
Problem with StuffIt: related to Retrospect issue?
February 25, 2002
Gregory Newton sent a report of problem with StuffIt over a DAVE network.
Testing the latest patch from Thursby for version 3.1, I have identified another issue that may be related to the previous problem with Retrospect.
Running under Dave 3.1 and attempting to use Stuffit 6.5.1 from the contextual menu in the Finder to stuff a file located on the server that will be saved back to the server, I get a file error that states "Your preferred destination folder is currently write protected, Error -61". This error does not occur using Dave 2.5.2. Folders on our server are NOT write protected. Thursby has been advised of this issue and is looking at it.
Note: The patch called let us know should fix this problem.
February 27, 2002
There is a bug in OS X 10.1.3 which causes either a Finder stall (spinning beach ball) or Kernel Panic using DAVE to connect to a Windows network.
If you attempt to connect to a Windows PC using DAVE and click to save the password into the Keychain, after a couple more times of connecting to different PC's you will get either a Finder stall (spinning beach ball) or Kernel Panic. This problem actually occurred in 10.1.2 to a lesser extent, but on my iMac 350 once I upgraded to 10.1.3 the problem became constant. I have tried DAVE with and without the recently released patch - same problem. Not sure if this is a Keychain or a DAVE problem - either way, it caused some serious errors on the Hard Drive which I couldn't fix using fsck - had to re-boot into OS 9 and use Norton.
If you've seen this, please DAVE 3.1p2.
March 1, 2001
I never connected the two symptoms, but CAN confirm that lately whenever I use Dave to connect I get the same "beachball of death" problem, and end up having to reboot the Mac. I can't confirm that it's related to the Keychain (as I've had Dave configured that way for some time now) but I can confirm the same problem using Dave 3.1 and OSX to connect to windows machines.
Until they get it worked out, I've switched over to using "sneakernet" and ZIP discs to get what I need transferred.
April 3, 2002
Phil Noguchi says the problem also occurs with Sharity:
My Dave 3.1 in OS X 10.1.3 had similar symptoms to the spinning ball, where I could not see at all anymore about thirty or so NT servers. I had just recently started to use the Keychain to store logins; when I used the Keychain Access utility, and deleted all files related to NT shares, that sure enough cured the problem.
I could retain Keychain passwords for things like email without problems. This problem with stored Keychain access for servers is not apparently restricted to NT servers. My AppleTalk access to servers also was inhibited. The same symptoms were found in my home network without an NT server, but with Windows 2000 Workgroup sharing. I had deinstalled DAVE, and tried Sharity, which had the same lack of response as DAVE. So at least for me it seems to be a Keychain issue.
April 8, 2002
In regards to the OS X Keychain post you have on your website, I also consistently (every single start-up) have had the same problem and have been unable to find the solution. Thursby has yet to return my emails. This is just to verify this is indeed an issue, and I have seen it occur on my other Mac as well.
April 10, 2002
Peter Gray reports that Thursby Systems told him that the patch which we reported in February should fix the problem. Gray reports:
As far as I can tell it's fixed all the kernel panics. The readme pretty much says Don't Install this Update unless you are having the Kernel Panics. They also said the crashes came mostly from having NetBarrier X installed. Either way it fixed my problems with crashes.
June 18, 2002
Joe Bauder reports that firewalls on running on a PC (specifically, Zone Alarm) can interfere with DAVE:
I installed DAVE 3.1.1 and tried to share a printer and files with my PC under OS X. I had previously been able to connect using OS X's SAMBA networking but this time had an issue with connecting with my PC from the Mac.
I tried fiddling with the PC in a number of ways, trying to set up WINS resolution even though I didn't have a WINS server, trying to get my router to do WINS resolution, etc. I have an ME partition and a Windows 2000 Pro partition and neither worked...
Then it dawned on me: I have Zone Alarm [a firewall product] installed on both ME and Windows 2000 Professional. I looked at Zone Alarm and the "medium" security setting I had set up on both machines specifically said that peer-to-peer or share level networking works fine. I tried setting it to "low" security and it would not work on the ME partition or the Windows 2000 Pro partition. Then I just turned off Zone Alarm and everything else turned right on. File sharing, printer sharing, etc.
I either had to remove Zone Alarm altogether or (and I will probably do the latter) just turn off Zone Alarm on the PC whenever I have a networking issue or find the ports needed to pass through. I actually just looked at the DAVE "compatibility" page and they cleared it up:"DAVE will work with firewall software if the software is configured to allow traffic to and from the ports DAVE uses. DAVE uses ports 137, 138, 139 using TCP and UDP. Please contact Network Ice at http://www.networkice.com, Zone Labs at http://www.zonelabs.com, Open Door Networks, Inc. at http://www.opendoor.com or Symantec at http://www.symantec.com for information on configuring these products."
June 19, 2002
First to a Linux Magazine article with some info.
There are three ports involved in Windows File Sharing (SMB): 137, 138, and 139. [Actually four, 135.] The first two utilize UDP and are used to facilitate browsing in the Network Neighborhood and to exchange datagrams. If they are blocked, a machine will not simply "show up" in Dave or other Windows client's Network Neighborhood. Across the Internet, who cares, right?
The last port, 139, is a TCP port and handles the heavy lifting during file sharing. It is the ONLY port that HAS to be open to access a Windows CIFS server.
However, unlike AppleShare, getting CIFS to work with just one port is a feat of achievement. Since you can't simply "browse" to the computer, you often end up having to monkey with IP hosts files as well as NetBIOS lmhosts files. It isn't pretty and doesn't work the same on all windows clients, much less Dave. Also, since you can't browse a remote computer, you can't find out what share names are...meaning you'd better know what the share name of the folder you want to hit is before hand.
So the sage words of advice: if you are behind a firewall (say like a broadband router) and are running ZoneAlarm on the individual PC on your LAN, you can safely open port 139, as well as 137 and 138, because the WAN-side firewall is going to stop any incoming attack. On the other hand, if the PC you are trying to hit is directly connected to the WAN, close up 137 and 138, force open 139, and read the documentation about how to adjust all those files (hosts, lmhosts--the Dave manual does a pretty good job). Make sure your permissions are adequate, and that security boundaries are set (don't share your Windows folder, for instance!).
Software's Paul Nelson commentJune 21, 2002
Paul W. Nelson
V.P. Engineering, Thursby Software Systems, Inc.
Regarding this by Scott Boone:However, unlike AppleShare, getting CIFS to work with just one port is a feat of achievement. Since you can't simply "browse" to the computer, you often end up having to monkey with IP hosts files as well as NetBIOS lmhosts files. It isn't pretty and doesn't work the same on all windows clients, much less Dave. Also, since you can't browse a remote computer, you can't find out what share names are...meaning you'd better know what the share name of the folder you want to hit is before hand.
The last sentence is quite misleading, since browsing for computers is quite different from browsing the shares that are offered by a computer. In fact the last sentence is just plain wrong. If you know the IP address of any Windows NT 4, Samba or DAVE computer, you can get a list of shares using only port 139 (tcp).
Unfortunately, Microsoft's file sharing implementations many problems related to security, especially denial of service attacks (there are many ways that an evil client can blue-screen any windows server (regardless of how recent or how many patches have been applied). They can even bring down the computer without authenticating. Because of this, most people should never allow access to port 139 from the Internet to ANY Microsoft server. There are a lot of port scanners searching the Internet for unblocked port 139 servers, hoping to take advantage of home users running Windows. Some ISPs won't even route TCP connections to port 139 because of this activity. If you WANT to connect across the Internet to 139 and are having trouble, you might talk to you ISP to see if they are blocking 139.
The best defense for home and small businesses is to use private network numbers, such as 192.168.X.X and a NAT router. These routers are quite popular, easy to configure, and provide very good security.
June 25, 2002 -- Scott Boone disagreed with that Boone's comment on browsing remote PC was misleading. Boone defends his statement:
It also depends on how the user has security set up on the server end. It can be set up so that you won't get a browse list. And I was assuming that the user was already aware of the inherent risks of using SMB sharing. The problems are not necessarily as dire as Paul's comment would suggest, one just needs to know how to set things up and make sure they are up to date with security patches. There are plenty of Google-able sites to help with that. I guess the ultimate lesson here is: only do this if you ABSOLUTELY NEED to, and definitely do your research first.
let us knowMemory leak using DAVE and Mac OS 9.2.2
July 15, 2002
Kathy Devault reports a problem with DAVE 3.1.1 that causes Mac OS 9.2.2 to use all available memory when a server volume is mounted.
I have a brand new G4 OS 9.2.2 running DAVE version 3.1.1. The Mac is connecting to Samba shares on a Solaris machine running Samba Version 2.0.6. File system HFS plus.
When I am connected to a server with approximately 300,000 files on it, the operating system will often begin to grow until all free memory is used up. As soon as I quit a program, the OS takes the memory. With 256 MB, the OS would use up to 231 MB. I just installed another 256 MB, the OS grew to use 430 MB! Needless to say, this crashes my Mac. This only happens when connected to this server.
Other Macs in the group (OS 9.0.1, DAVE 2.5) have no problem connecting to the same server.
The fix: use older verion of DAVE
July 19, 2002
Just to update you on the problem below. We installed DAVE version 2.5 into the Mac, which seems to have solved the problem. So there definitely seems to be a problem with DAVE version 3.1.1 and OS 9.2.2. I've informed Thursby, and they are looking into it also.
If you've seen this problem, please .
November 18, 2002 -- Tomi Siikaluoma is having a problem with DAVE 3.1 login on a network that uses Active Directory:
We are using Mac OS 9.2.2 and DAVE 3.11, our network uses Windows 2000 Server and Workstation and Microsoft Active Directory and LDAP server. Active Directory server is running on native mode.
Some of our users have started having problems logging on network via DAVE. When user tries to login, DAVE returns error message: "The remote server reported an error. Your connection was rejected because of an invalid username or password." User can still login from Windows computers and changing password from Windows does not solve the problem. The problem exist even when user tries to log in using DAVE 2.5.1, so it not related to DAVE 3.1
This problem didn't exist before switching on Windows 2000 and Active Directory last summer. I wonder if anybody else is having same problem? I'm talking with Thursby Support but so far I haven't been able to solve this problem and I seems to be getting more common over time.
November 19, 2002
We are having trouble doing this also. We have been using Connectix DoubleTalk v1.1 and Thursby DAVE 4 to connect to a Win NT server on a Win NT domain. Both of these applications work fine for this configuration. However, the server is being changed to Win2K on a Win2K domain. We have tried both DoubleTalk v1.1 and DAVE 4 to connect to a test volume on another Win2K server on the Win2K domain. All attempts have failed.
The Win2K domain uses Kerberos as a default authentication protocol, but will use NTLMv2 as a fall back. The DAVE 4 documentation states that it can use NTLMv2 to authenticate. After contacting Thursby, they indicated that if the default authentication is Kerberos, DAVE 4 does not know to fall back to NTLMv2. They also indicated that support would be added in a future release of DAVE for Kerberos authentication, but only for OS X.
November 21, 2002
I have personally had no problems using DAVE 3 to login to a Windows 2000 Server running Active Directory. They way I did it was to have the Windows 2000 server configured to run in 'mixed mode'. This means it is backwards compatible with NT domain controllers (which then act as BDCs to the Active Directory server).
I suspect those having problems have chosen to run Active Directory in 'native mode.'
November 22, 2002
Zach Halmstad disagrees with the previous writer about "native mode." (Halmstad also has an older version of DAVE than did the readers of previous reports.)
We have about 300 computers (9.1 to 9.2.2) with DAVE 2.5.2. We have never seen this problem, and our AD servers are all in native mode, and have been for at least a year. As I don't think you can easily go back to mixed mode, I hope this can save someone a headache, unless of course this is specific to later versions of DAVE.
Thursby responds: Native mode is okay; issue with .NET servers and digital signing
November 27, 2002
Thursby Vice President of Engineering Paul Nelson
As one reader has already pointed out, DAVE DOES work with Active Directory, even in "native" mode. If customers are having difficulty getting DAVE to work, they should contact our technical support department. DAVE has been tested against Active Directory systems both on Windows 2000 and .NET servers.
There is one issue with Active Directory that administrators should be aware of especially when using .NET servers. DAVE does not support cryptographically signing each network transaction. Users should make sure that the "Microsoft network server: Digitally sign communications (always)" security policy item is set to "Disabled" when using DAVE. This item can be found under Windows Settings/Security Settings/Local Policies/Security Options.
If this suggestion works for you, please .
Note: the problem has also been reported with .
December 13, 2002
I'm running Mac OS X 10.2. I connect to two servers: one running Win 2000 Server SP3, the other running Linux with Samba 2.2.6. I'm connecting to both of them using DAVE v4. I can copy files to the Win 2000 server just fine. But every now and then I'll have files that I can't copy to the Samba server. It gives me the "The operation cannot be completed because one or more required items cannot be found. (Error code -43)" message. It's not very often. Right now I have a few JPG files on the NT server. These files were created with Photoshop just by using the "Save..." command. I can copy them to my Mac's HFS+ hard drive and back to the Win 2000 machine. But when I try to copy them from either source to the Samba machine, I get the error. Here's the interesting part. If I open them back up in Photoshop and save them as JPGs using the "Save for Web..." command, I have no trouble coping the new files to the Samba server. It seems to me that it has something to do with the resource forks.
September 23, 2005 -- A couple of readers commented on the new " + contact + " the recently released new version of the SMB file and print sharing solution for Mac OS 9 and X.
Jubart Igig is bullish on Thursby Software's DAVE 6.0:
Dave 6 is awesome! We run a multiple Windows 2003 server environment with about 250 Macs and a 100 PCs and it works perfect. That other "fix" from Apple stinks. Now it's time to write a report to corporate to purchase the $17,500 license...
Scott McDonald had problem with Windows 2003 Server SBS:
I upgraded to DAVE 6 from DAVE 5.1 solely so I could upgrade to OS X Tiger. I decided to install DAVE 6 on my Mac (a white iBook 800 MHz) running OS X 10.3.9 first before upgrading to Tiger to see how it worked.
At first, all seemed to go well. I was able to access files on my firm's Windows 2003 Server just as with DAVE 5.1 with no problems. But then my firm upgraded (laterally switched) to Windows 2003 Server SBS (Small Business Server?). The system administrator also implemented passwords (no passwords were required before). I immediately had problems: inability to connect to the server, or connection, but inability to open folders on the server (Finder would appear to lock up or folders would "disappear" from the Finder).
I try turning off WINS support in DAVE to see if that was part of the problem. There was no change. Desperate to get to my files, I uninstalled DAVE 6 using the included uninstaller program, then I reinstalled DAVE 5.1. DAVE 5.1 worked like a charm! No connection problems whatsoever.
But, of course, reverting to DAVE 5.1 torpedos my reason for upgrading in the first place--to be able to upgrade my system to Tiger.
If you've seen this problem or tried DAVE 6
Thursday, December 27, 2007
As we have previously noted, DAVE 6.x and AdMitMac 3.x and earlier are incompatible with Mac OS X 10.5 Leopard. CleanApp of both. J. Thierry reported a problem with the older version of DAVE, and notes that a complete removal was required:
Before upgrade to Leopard : no problem. After upgrading to Leopard, on my MacBook Pro, PC share icon appears in the shared computers of the Mac, but connection always failed whatever I did.
The problem was the older version of application DAVE 6.xx. I removed it using Click here for current MacWindows news, but it was not completely removed.
I performed a complete removal, and bingo, as in a dream, all is OK. The Mac has access to all the Windows shared folders.
(Theirry has not tried the DAVE 7.0 upgrade, which provides Leopard comptibility.)
Thursday, July 3, 2008
Tommy Birchett reports that Leopard's Spotlight can't search mounted SMB/CIFS shares using Thursby's DAVE 7:
Spotlight searching does not work on Thursby's DAVE mounted CIFS volumes with OS X 10.5.x. Steps to Reproduce:
- Install OS X 10.5.x on any hardware
- Install Thursby DAVE 7.x
- Connect to CIFS share (on NetApp) via DAVE.
- Use the Finder/Spotlight to search any mounted DAVE volume--no results displayed.
This problem does not appear in OS X 10.4.x or earlier with any version of DAVE installed. This problem does not occur with AFP Volumes. This problem does not occur when CIFS volumes are mounted via OS X native CIFS.
Thursby recommends filing a bug report with Apple if you are having this problem.
If you've seen this problem
Monday, July 7, 2008
Jim Downward responded to last week's report about Spotlight's inability to search network shares. He sent a Unix shell script that enables spotlight to do this. His report:
If indexing is not occurring, the volume enable indexing bit is not being set. At least in 10.4.x, Spotlight does not automatically search served volumes, which can be dismounted. Not being able to search these volumes was really annoying. After some research, I discovered that to get newly mounted servers to be indexed. I had to force indexing to be turned on every time the server was mounted.
To do this, in Library, I placed a plain text file to enable indexing into the /Library/LaunchDaemons folder.
Call the file this: enableindexing.plist
Type this in the file:
A create the shell script (also a plain text file) called: enableindexing.sh
Place it into the directory: /usr/bin
Type this in the script:
sleep 1 # let things settle down a bit
if mdutil -s "/Volumes/sharedvolume" | grep -q "Indexing Disabled" ; then
mdutil -i on "/Volumes/sharedvolume" >/dev/null
Note, mdutil must be used to enable Spotlight indexing each time any shared volume is mounted.
The enableindexing.sh file must be set to be executable in Terminal (chmod +x /usr/local/bin/enableindexing.sh).
Here is a link to the original information on the subject I found years ago on MacOSXHints.com
The property list file is much easier to work with if you use the PropertyListEditor from Apple which you can find in Apple's Developer Tools package.
The process is pretty solid once set up, but you do need to manually add each network volume you want to index into the list of volumes being scanned on mount by enableindexing.sh.
For those not familiar with the Unix, you can get to the /usr/bin directory from the Finder by opening the Go menu, selecting Go to Folder, and typing /usr/bin in the field.
If you've used this
Wednesday, September 17, 2008
Jonas Lanz in Zürich Switzerland found a solution to making Spotlight search SMB shares. He writes:
I have a similar problem.
- Use OS X 10.4
- Run "Go/Connect to server..."
- Enter smb://<sharedvolume> and klick "Connect"
- The Volume gets mounted and it is visible in spotlight and on the desktop (depending on your settings).
- The mounted volume can be sarched (unindexed, might take several hours))
- Run mdutil -i on "/Volumes/<sharedvolume>" as root
- The mounted Volume gets indexed and a status bar appears by clicking the spotlight icon which indicates the progress (might also take several hours).
- The mounted volume again can be searched by spotlight (now indexed, which is way faster).
With OS X 10.5 you have to run the "mdimport" command [in Terminal] first.
As soon as you run the mdutil command it says that the mounted volume gets indexed but nothing happens at all. Even the unindexed search does no longer work.
Other effect: Spotlight always jumps to the location "Computer" even if you start searching in a mounted volume.
If you've used tried this approach
Click here for current MacWindows news