Most users set up WAFS quickly and easily using the installation wizard. Below are common issues encountered when setting up WAFS, and recommended solutions.
The Agent cannot connect to the Vault. Make sure the Vault service is running, and that it is using a port that allows TCP/IP traffic between the two computers. By default, the Vault uses TCP/IP port number 80, but that port may already be used on the computer (e.g., by IIS), or may be blocked by a firewall. You can change the port number and allow access in the firewall. There are also issues specific to XP firewalls and Microsoft ISA.
WAFS cannot create a backup Job because of the Access Control Lists (ACLs) of files in the selected folder. The Agent works as a SYSTEM process, so it must have full control over all the files in order to access them. You must ensure that the SYSTEM account (a predefined "user" on every Windows computer) has full-control over every file and folder. You can let it add SYSTEM or you can add SYSTEM to every file/folder yourself, using Windows Explorer. You can also use Microsoft's cacls.exe or Xcacls.exe utility to display or modify ACLs of files.
Some third-party applications may need adjusting. Old versions of StorageExec, QuotaAdvisor, PowerQuest, UltraBac, DoubleTake, and UnDelete may cause performance issues.
If you are using a cloned virtual machine, make sure that you have changed the Computer name and SSID. They must be unique across the network.
For more information about special configurations, considerations for use with other applications, and connection problems, refer to Technical Notes.