FAQ MacServerIP:

• Can I install a newer trial version on the same computer where I have an older one installed?
   
• Mac OS 10.2: Files are displayed ghosted and disappear when I click on them
   
• Mac OS 10.1.x: When trying to copy a folder with multiple files to a MacServerIP volume the Finder fails
   
• Does MacServerIP 8.0 Cluster support Load Balancing?
   
• Some users cannot use the trash can of a volume shared by MacServerIP.  They are asked to delete the file immediately
   
• If a file is already opened by one user, some applications, like Office 2001, of another user fail to open it for read only
   
• File transfer between Macs and Win 2003/XP/2000/NT is up to 5 times faster, but the speed from MacServerIP  to Mac is slower  than a conventional file server, like Services For Macintosh (SFM).
   
• Labels for Folders are not saved:
   
• License code is invalid:
   
• The license code dialog indicates that MacServerIP is running in demo mode, but I have entered a license code:
   
• How to upgrade to a newer version:
   
• Configuring MacServerIP on a cluster:
   
• Either Windows NT/2000's MacFile service or MacServerIP cannot be started:
   
• Volumes shared with MacServerIP aren't listed in the chooser of a particular user:
   
• Files and folders created by users were not shown in the finder:
   
• A user cannot logon, albeit he has entered the correct password:
   
• If a client cannot connect via TCP/IP:
   
• The shared volumes can only be accessed for reading:
   
• A user cannot login to the MacServerIP, although the user account has been created using Windows' User Manager:
   
• A Macintosh client hangs while starting up and displaying the MacServerIP log-on message:
   
• "Error EX ... x:/.../Temporary Items/FileName" and "Error EX ... x:/.../.../FileName"
   
• Ensure that Windows NT/2000's AppleTalk protocol (SFM / Services for Macintosh) has been installed correctly.
   
• If the setup.exe program does not start, then please restart your computer and ensure that no other application is running while using setup.
  
• Booting: "NT Loader not found".
   
• Please always check the Applications Event Log of Windows NT/2000/XP/2003.
  
• How to share hundreds of SFM volumes automatically with MacServerIP
   
• I cannot see the MacServerIP server in the Chooser
  
   
• Can I install a newer trial version on the same computer where I have an older one installed?
  Yes, that’s possible. For this you should install a newer trial version into the same folder where the older version was installed.
   
• Mac OS 10.2: Files are displayed ghosted and disappear when I click on them
  Please upgrade to build number 8.00.02.148 or higher of MacServerIP
   
• Mac OS 10.1.x: When trying to copy a folder with multiple files to a MacServerIP volume the Finder fails
  We are currently working on a fix. Furthermore, Apple solved this Mac OS 10.1.x specific problem with the upgrade of Mac OS 10.2. 
   
• Does MacServerIP 8.0 Cluster support Load Balancing?
  Yes, it does. You have to configure both cluster nodes as active and configure MacServerIP in that way that it will use the virtual IP number of the cluster, then Load Balancing will be used for any connection coming through this virtual IP number. 
   
• Some users cannot use the trash can of a volume shared by MacServerIP.  They are asked to delete the file immediately:
  Please upgrade to build number 8.00.02.147 or higher of MacServerIP
   
• If a file is already opened by one user, some applications, like Office 2001, of another user fail to open it for read only:
  Please upgrade to build number 8.00.02.147 or higher of MacServerIP
   
• File transfer between Macs and Win XP/2000/NT is up to 5 times faster, but the speed from MacServerIP  to Mac is slower  than a conventional file server, like Services For Macintosh.
  The problem of slow speed is caused by the problem of your IP network (between the specific Mac and the Server) and not by MacServerIP.  Please set everything to full duplex (network card of the server, the Mac). Switch auto sensing/negotiation off (network card of the server, the Mac, port of the hub.)
  Some network card drivers on both Windows and Macintosh machines are known to have problems. Ensure that you have installed the latest network card drivers on all machines. If you e.g. have an older Apple, NetGear or Asante driver, make sure that you install the latest updates. Even some of the latest driver can cause performance problems. Like some of the Apple build-in network card drivers, which have problems with auto-negotation. You can download a tool from Apple's Web site for setting these network card to use full-duplex.
  To achieve the best performance you should connect all computers to a switch instead of an hub, because a switch allows to send and receive data at the same time (full duplex). 
   
• Labels for Folders are not saved:
  Please ensure that you have installed build 02.143 or higher.
   
• License code is invalid:
  Please ensure that you have installed the correct version of MacServerIP. If you have the cluster version or an upgrade code of MacServerIP, then please ensure that you have installed build 02.147 or higher of MacServerIP 8.0. License codes for the server version can only be used if you have actually installed the server version.  License codes for the workstation version can only be used if you have actually installed the workstation  version.  License codes for the cluster version can only be used if you have actually installed the cluster version.
  
  
• The license code dialog indicates that MacServerIP is running in demo mode, but I have entered a license code:
  Please ensure that the user who uses the MacServerIP administration client, the system group and the administrator group have full access to the MacServerIP registry key. HKEY_LOCAL_MACHINE/Software/cyan/MacServerIP
  
  
• How to upgrade to a newer version:
  Do not uninstall the old version of MacServerIP. Simply run the installer of the newer version. For downgrading to an older version of MacServerIP, do not uninstall the new version. Simply run the installer of the older version. The configuration information of MacServerIP 6, 7, and 8 is mutually compatible. Enter the upgrade code in the license code dialog. You can order the license code from one of cyan's partners.
  You can try a fully functional version of the latest MacServerIP 8 on both, a PC with an existing MacServerIP installation and on a PC without an existing MacServerIP 6/7 installation for 20 days without a license code. The MacServerIP 7 license code is different from the MacServerIP 8 code.
  
  
• Configuring MacServerIP on a cluster:
  1. Install MacServerIP on each node on the local drive (C:) of each node.
  2. Enter the virtual IP address in the "Protocol" tab of MacServerIP (first check "Advanced Functions" in order to make the tab visible)
  3. Configure MacServerIP as generic service in the cluster software. IMPORTANT: The service name is "AfpServer"
  4. Configure the cluster software in the way that it replicates the registry key "Software\Cyan\MacServerIP" to the second cluster node:
  In the Cluster Administrator, right-click the MacServerIP (AfpServer) resource and click Properties on the shortcut menu. Click the Registry Replication tab. Add a new entry. Enter as registry key: "Software\Cyan\MacServerIP" (without "). Click OK to close the Properties dialog box.
  
  
• Either Windows NT/2000's MacFile service or MacServerIP cannot be started:
  Ensure that both servers use different AFP-server names.
  
  
• Volumes shared with MacServerIP aren't listed in the chooser of a particular user:
  Check with the Windows Explorer or the FileManager if the required access rights (read) of the folder of the volume have been granted for this user.
  
  
• Files and folders created by users were not shown in the finder:
  Probably, the access rights to the parent folder are restricted, so the users could create files/folders, but these users could not be assigned as the owners of the files/folders besides, these files/folders could have no owners at all and were not accessible by anybody, including administrators. Solution: Change the access rights of the parent folder with the Windows explorer and logon with administrator privileges and take ownership of the files and folders created, after that change the access rights of these files/folders.
  
  
• A user cannot logon, albeit he has entered the correct password:
  Ensure that the accounts of the users who are allowed to use the shared volumes of MacServerIP include the privilege "Network Logon", otherwise these users couldn't be authorized.
  
  
• If a client cannot connect via TCP/IP:
  Please ensure that: 1. On the Windows NT/2000/XP system TCP/IP is installed and a correct TCP/IP address and subnet mask have been assigned. 2. That the Macintosh client uses AppleShare 3.7 client software or higher with TCP/IP installed and configured correctly. 3. Ensure that the TCP/IP addresses and subnet masks of the computer on your organization's TCP/IP network have been assigned correctly. See "Ensure that the AppleTalk and TCP/IP are installed correctly" for a brief instruction on how to assign TCP/IP addresses and subnet masks.
  
  
• The shared volumes can only be accessed for reading:
  1. Go to the "Volumes" tab dialog page of the MacServerIP Administrator (AfpAdmin.exe) application and press the "Edit..." button and check if the "Volume is Write Protected" option has been enabled.
  2. Check that the user or the group he belongs to has writing rights for the volume.
  
  
• A user cannot login to the MacServerIP, although the user account has been created using Windows' User Manager:
  If the MacServerIP is configured to use DES-encryption for passwords, MacServerIP must "know" the password of the user account. Please verify the password of the particular user account in the "Passwords" tab dialog of the Administrator application. Please also read "Authorization" in the "Tab Dialog Page: "MacServerIP" topic.
  
  
• A Macintosh client hangs while starting up and displaying the MacServerIP log-on message:
  This problem occurred only once when a Macintosh client tried to reconnect a few remembered volumes during startup: 1st solution: Shutdown MacServerIP, remove the MacServerIP message using the administration application, restart MacServerIP, restart the Macintosh computer; 2nd solution: Shutdown MacServerIP, restart the Macintosh computer, restart MacServerIP. Please, if you experience this problem, send an e-mail to cyan software.
  
  
• "Error EX ... x:/.../Temporary Items/FileName" and "Error EX ... x:/.../.../FileName"
  Please ignore this message. It's not an error. This message is written if a file is created in the "TEMPORARY ITEMS" folder and is removed from this folder immediately after creation. When MacServerIP is trying to access this file and sees that it has already been removed, then MacServerIP is writing this error message. But, actually, no error has happened. In a not yet released version of MacServerIP this error message will not be written anymore.
  
• Ensure that Windows NT/2000's AppleTalk protocol (SFM / Services for Macintosh) has been installed correctly.
   
  
• If the setup.exe program does not start, then please restart your computer and ensure that no other application is running while using setup.
   
  
• Booting: "NT Loader not found": 
  Please remove the diskette from drive A:.
   
  
• Please always check the Applications Event Log of Windows NT/2000/XP.
  
  
• How to share hundreds of SFM volumes automatically with MacServerIP
  Run the "IP-Server Installation Wizard" of MacServerIP:
  1. Open the MacServerIP Administrator
  2. Click on the icon in the upper left corner in order to display the menu
  3. In the menu select "Installation Wizard"
  4. Select one of the 2 options starting with "Copy W2k/NT's MacFile volume information"
  5. Click "Next >"
  6. Then wait some until the server finishes this. If you have x00000 files this can take or 20 minutes or more. You can tell by looking at the processor usage whether this has finished.
  
• I cannot see the MacServerIP server in the Chooser
  1. please make sure that the option "AppleTalk (list server in chooser") is checked.
  2. restart the MacServerIP service (not the NT/W2K Server)
  3. check for network hardware errors. AppleTalk is much more sensitive than TCP/IP. Ff there are problems with cables, AppleTalk often stop functioning while TCP/IP still works. Check whether you can see other AppleTalk resources of the NT/W2k Server with a Mac, like the printers share with Print Services for Macintosh