The Authentication failure is due to Backup Exec on the PC. Do me a favor and thank them very much! *grumble*. They basically hacked together a backup exec client for the mac. There isn’t any “user” name used to authenticate to a mac. However, there is a password. What is not documented well, is the password of the ACCOUNT you use to log INTO Backupexec is the password used to try to authenticate to the box. NOT the password used under the machine viewing section. So, what ever password is used to get to the BackupExec Console on your PC, is the password you need to assign to the backupexec clients configuration.
On a similar note, you will notice the BackupExec client for mac installs a startup item in /System/Library/StartupItems/. This is NOT the right place to have it run. If you boot your server in “Safe” mode, the backup exec client will STILL load. I recommend to move it from /System/Library/StartupItems/ to /Library/StartupItems/. Makes things easier to troubleshoot if you encounter problems.
FYI, be aware of the following issues with BackupExec:
1. Does not copy resource forks well. (intermittently looses the resource forks)
2. Does not capture ANY ACL information.
3. Does not capture user/owner information on files
4. Strips off meta-data related to the file (aka spotlight information, embedded icons).
I found out the hard way this issue removed any relationship to the parent file, and had to recreate every link to the graphic files. Quark files were considered unknown files since Quark doesn’t even have a .suffix to their files. Be warned.
.
.
Comments are closed