> thanks for the reply, seems to be the latter as I can easily connect
> to the smb host with other windows and mac machines.

> As I mentioned
> in the original post, I tried running the command via terminal and got the
> same error; I doubt its a credentials problem since I get a completely
> different error when I deliberately enter incorrect creds (LOGON FAILURE).
> Running from the command line with logging turned up doesn't reveal much
> more info. Looks like windows is closing the connection right after
> authentication. Lastly I am able to access other smb shares on *nix based
> hosts from BackupPC just not this Win2K3 box.

There are plenty of things that can be interfering post connection --
anything from third-party firewalls to anti-virus software, to not setting
up the shares properly to setting up a share on a path where the user
doesn't have access.  You probably don't have much choice but poking
through these possibilities, I'd be inclined to start by seeing if the
same user has access to the path at all (locally.)

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/