FAQS

01 / Known ADmitMac Issue: Cannot log in after upgrading to Mavericks

ADmitMac v7 is not supported on OS X 10.9, Mavericks. In order to prevent any problems, you should uninstall ADmitMac before upgrading. The "Uninstall ADmitMac.app" can be found in the /Library/Application Support/ADmitMac folder.

If you have already upgraded to Mavericks, the incompatibility can cause a situation preventing you from logging in to any account. To remedy this situation, please follow these steps:

NOTE: If you do not feel comfortable performing these steps, please contact our Support Specialists for further help.

  • Restart the computer holding down the Command+S keys. This will start the system up in Single User mode.
  • At the prompt type the following commands:
  • /sbin/fsck -fy {hit the return key}
    /sbin/mount -uw / {return}

    cd /Library/Filesystems/DAVE/ {return}

    mv cifsd.app cifsd-disabled.app {return}

    exit {return}

This last line allows the boot to continue, and you should then be able to log in to a local administrator account and run the uninstaller. If you have trouble with the commands, or if they do not allow you to log in to a local account, please contact our Support Specialists for assistance.

02 / Do ADmitMac and DAVE support .lnk (shortcut) files?

Our products support '.lnk' files in most cases.

If the link is a link to a file in the same share, double clicking the link will open the file.

If the link is a link in a different share, double clicking the link will cause the share to be mounted, and the file to be opened.

Not all targets of link files will be accessible to the Mac. For example, a link may refer to a file that is not in a shared folder. In this case, opening the link on a Macintosh will result in an error dialog:

"This is not a network shortcut. It can only be opened on the machine it was created on."

03 / Do ADmitMac and DAVE work with Network Appliance Filer?

ADmitMac and DAVE have been tested and found to work properly with Network Appliance Filer v5.3 and above. We do provide support for the latest public release of DAVE and ADmitMac when used with the latest supported versions of Network Appliance Filer.

04 / "There is a problem making the remote connection because of an invalid username or password."

Here are the steps that should resolve the matter:

  • Delete the printer icon from your desktop
  • Go into your Hard Drive -> System Folder -> Preferences folder and delete "DAVE DT Print Preferences"
  • Reboot the computer
  • On startup, go under the Apple menu and select "DAVE".
  • Once this window opens, click on "Access" in the menu bar at the top, and choose "logon" (this is the most important part, you must login this way instead of via the chooser to fix the problem).
  • Here you will login to the domain using your domain username and password
  • Once you have logged on in this manner, go into the chooser and recreate the printer as before (you should not get prompted to login again when you select the server via the chooser).

05 / The file "FILENAME" in the desktop printer "PRINTERNAME" will be moved to the desktop because it is not a print file.

We are looking into this issue for possible resolution in a future release of DAVE. It seems that the Windows postscript print driver does not format the postscript file correctly for the Macintosh to read. The Macintosh will recognize that the file is a postscript file, but because of the formatting, it will not recognize it as a print file.
Please try the following steps:

  • On the Windows machine, go to Start-Settings-Printers
  • Delete the printer
  • Close the printer control panel and open the Network Neighborhood
  • Double click on the name of the Macintosh sharing the printer
  • Double click on the name of the printer
  • Windows must set up the printer now. Click Yes.
  • Click Next
  • Configure the printer as a Apple LaserWriter and click Next
  • Name the printer and click Next
  • Click Finish and check for test page

"06 / "\\<COMPUTERNAME> is not accessible. You might not have permission to use this network resource. Contact the administration of the service to find out if you have access permission. The network path was not found."

This message could also read:

"\\<COMPUTERNAME> is not accessible.
The device does not exist on the network"

Try disabling any firewall software on the Macintosh to see if this makes a difference. If you are using Mac OS X, disable the built in firewall service. Many firewalls by default block the ports that DAVE uses for communication. The ports DAVE uses are ports 137,138,139, and 445 using both TCP and UDP.

Try changing the name of the Macintosh. A computer name can be up to 15 alphanumeric characters and cannot contain any illegal characters (eg. an apostrophe). It must be unique on the network.

If this does not work, stop DAVE Sharing, remove the shares, add them back in, and start the DAVE Sharing service again. Make sure that none of the share names are longer than 12 characters or have any illegal characters in the name.

07 / "DAVE failed to mount "SHARE". Please correct the following error and try again. Invalid Argument".

This is usually caused by a memory allocation problem on the windows computer, where the machine does not have enough resources or memory available to respond to a connection request by the Macintosh. If more than one machine is connecting to the windows computer, it may not have enough resources available to allow one more machine to connect. You can resolve this issue by increasing the IRPStackSize value in the registry. You can find instructions on how to do this in Microsoft Knowledge Base Article - 177078. Below is the link to Microsoft's article on this issue:

http://support.microsoft.com/default.aspx?scid=kb;en-us;177078

Another possible solution would be to increase the amount of ram on the Windows computer. Finally, In rare cases we have found that some older antivirus software may also cause this to occur. A quick way to test this would be it disable the antivirus software and see if the problem goes away. If this does resolve the problem, you may want to see if there is an update to your antivirus software.

08 / Unexpected error [57}

To update ADmitMac to the latest version, you must run the installer while logged in to a local admin account. If you run the installer while logged in to a domain account, the installation might fail or cause damage to your domain account.

If you have already run the installer while logged in to a domain account, please log in with a local admin account and run the installer again. If the Setup Assistant runs automatically after the installer quits, please click through it - confirming settings - until it completes.

09 / "The operation could not be completed because you do not have enough access privileges."

There are three possible causes for this.

  • If you are using a network home folder, make sure that your domain account has not met the disk quota available to you. There is a known issue where if your home folder grows in size and nears, or has reached, the amount of hard disk space alloted to your domain account, you will not receive a disk quota warning. Instead, once the disk quota is met, you will no longer be able to save files to your home folder.
  • If your home folder was recently moved to a different location, make sure that your domain account is the owner of your home directory.
  • If you are using a local home folder, and login to different domains, make sure that the username for your domain account is not identical on more than one domain. The name of your home folder will be the same as the username you use to login to the domain. The first time you login to your domain, your domain account for that domain will be the owner of the home folder. If you login to another domain using the same username, ADmitMac will try to use the home folder from the previous login.
  • Because the accounts are different, the new domain account will not be the owner of the home folder and will not have the necessary permissions for it. However, this new domain account will not be the owner of this home folder.

10 / Why does it say "Connection Failed" when I click the server in the Sidebar?

In Mac OS X v10.5 (Leopard), Apple made some significant changes to the Mac OS Finder and the Sidebar, and these changes persist in Mac OS X v10.6 (Snow Leopard). You will not be able to access Windows servers through the sidebar, but will be able to access the volumes once you have mounted them using either the ADmitMac Browser, or by entering the path into the Server Address field in "Go - Connect to Server". We have been made to understand that it is a bug in the Finder that keeps network volumes from working properly in the Sidebar, and that Apple is working to resolve it.

In the Finder Preferences (General), make sure that "Connected Servers" is checked. Also in the Finder Preferences (Sidebar), make sure that "Computer" is selected.

Once a volume is mounted, you can access by opening from the Desktop, or by selecting "Computer" in the sidebar, then the mounted volume.

11 / Can I use DAVE or ADmitMac to access files I stored on my server with Apple's built-in SMB or vice versa?

There should be no problem accessing files copied using one method and accessed using another as long as the file does not store important information in the resource fork.

However, if the file being accessed does store important information in the resource fork, you may have trouble using the file with DAVE/ADmitMac if it was copied there using Apple's SMB. Likewise, Apple's s SMB cannot read the resource fork data of a file copied using DAVE/ADmitMac. DAVE and ADmitMac store the resource fork data on the server using the same specifications as Microsoft's own Services for Macintosh (SFM). However, Apple's SMB stores the resource fork information on the server in a more UNIX-like format which does not conform to Microsoft's SFM.

What this means is that if you copy a file with a resource fork to a server with DAVE/ADmitMac, you may only be able to access that file with DAVE/ADmitMac. If you copy a file with a resource fork with Apple's SMB you may only be able to access that file with Apple's SMB.

If you are trying to migrate from Apple's SMB to using DAVE or ADmitMac, we have created a script that can convert the resource forks of files copied using Apple's SMB into the format that DAVE and ADmitMac uses. Here is the link to a page with more information as well as a link to download it:

http://www.thursby.com/converter

12 / Can a Macintosh running DAVE communicate with a Microsoft Windows XP computer running the built in firewall service?

DAVE will communicate through firewall software if the software is configured to allow traffic to and from the ports DAVE uses. DAVE uses ports 137, 138, 139 and 445 using TCP and UDP. Another solution is to allow all TCP/IP traffic from a particular IP address (in this case the IP address of the Macintosh) to go through the firewall.

Here are links to pages on Microsoft's website with information on configuring the built in firewall for Windows XP:

If you are using Windows XP SP 1:
How to turn on or turn off the Internet firewall in Windows XP
http://support.microsoft.com/kb/283673

How to manually open ports in Internet Connection Firewall in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308127

If you are using Windows XP SP 2:
Description of the Windows Firewall feature in Windows XP Service Pack 2
http://support.microsoft.com/kb/843090

13 / Will DAVE or ADmitMac work where Samba is the WINS server?

Unfortunately, DAVE or ADmitMac will not work where Samba is the WINS server. Our engineers have determined that this is due to a problem with Samba's implementation of WINS. This issue does not occur using Microsoft's implementation of WINS. Our engineers have reported this bug to Samba as Bug ID 476.

Some options are:

  • Configure DAVE or ADmitMac to use a different WINS server (a Windows computer running WINS).
  • Disable WINS. This may allow you to browse machines in the same subnet. Machines outside the subnet require that you connect manually by IP address or DNS name.

14 / Is it possible to mount hidden shares from a DAVE equipped Macintosh?

Yes. If would like to access a hidden share, you must mount it manually. You can do that either in the "Connect to Server" window, or using the DAVE browser.

To use the "Connect to Server" window:

  • Select Go/Connect to Server...
  • In the Address field, enter the Server and the Share Name (ex. C$) using URL format. For example: cifs://SERVER/C$
  • 3. Connect (or press Enter).

To use the DAVE Browser:

  • Go to the hard drive /Applications folder and open the DAVE Browser application.
  • In the Address field, enter the Server and the Share Name (ex. C$) using URL format. For example: cifs://SERVER/C$
  • Connect (or press Enter).

15 / How do I change the DAVE license code?

If you have evaluated DAVE and have purchased a new license, you do not need to reinstall -- you can simply change the license code (key) in the software you're evaluating.

To change your license code, open your System Preferences and choose DAVE Network. Click the lock and authenticate to enable the preference pane. Click "Change License...", enter the new license code and click OK.

16 / Installing the trial version of ADmitMac or DAVE

After downloading the disk image, please be sure to read the included "Read Me" file as it contains important information about ADmitMac or DAVE.

17 / How do I remove the trial version of ADmitMac or DAVE?

If you choose not to purchase ADmitMac, you should remove the software. To remove ADmitMac, use the following uninstall utility:
/Library/Application Support/ADmitMac/Uninstall ADmitMac

If you choose not to purchase DAVE, you should remove the software. To remove DAVE, use the following uninstall utility:
/Library/Application Support/DAVE/Uninstall DAVE

18 / How do I change the ADmitMac license code?

If you have evaluated ADmitMac and have purchased a new license, you do not need to reinstall -- you can simply change the license code (key) in the software you're evaluating.

To change the license code in Mac OS X 10.6 and later:

  • Open the Directory Utility, located in the /System/Library/CoreServices folder.
  • In the Services tab, double-click ADmitMac in the list to open the ADmitMac Configuration tool (you will need to enter administrator credentials). The ADmitMac window will display.
  • In the Domain Configuration tab, click the Change License button and enter the new license information.
  • Click Done.

To change the license code in Mac OS X 10.5, Leopard:

  • Open the Utilities folder (from within the Applications folder) and double-click Directory Utility.
  • In the Services tab, double-click ADmitMac in the list to open the ADmitMac Configuration tool (you will need to enter administrator credentials). The ADmitMac window will display.
  • In the Domain Setup tab, click the Change License button and enter the new license information.
  • Click Done.