Hello all,

 

For a number of years I have run a small home network of windows machines.  I recently decided to move my computing to Linux.  I now have two machines running Fedora 8.  The first machine assumed the role of my windows server using samba.  The second machine is to be my system archiving unit and I am initially trying to get BackupPC to maintain an archive of the windows shares on the first Linux box.

 

I ultimately want to run ‘rsync’ as my transfer method, but was advised to use ‘smb’ when starting out since it would be simpler to set up.  I am still quite a novice at Linux but this undertaking is quickly educating me.

 

I have ssh running and can log into the other Linux machine and perform CLI operations in both directions.  I have set up ssl and can connect from either machine to the other using https://’hostname’/ getting the default Apache html page.  On the archiving unit, I can use https://’hostname’/BackupPC/ to open the BackupPC GUI.  I cannot bring up the BackupPC GUI from the windows server machine but get a 403 screen – access not authorized.

 

BackupPC is running and trying to perform the defined schedule but consistently fails with the message “tree connect failed: NT_STATUS_BAD_NETWORK_NAME”.

 

Since the problem appears to be with BackupPC getting a valid connection to the shares, I manually connected via smbclient:

 

[ken@archiver ~]$ smbclient '\\winserver\share#1' -U ‘uid’

Password:

Domain=[winserver] OS=[Unix] Server=[Samba 3.0.32-0.fc8]

smb: \> ls

 .                                                               D            0 Mon Oct  6 09:02:18 2008

 ..                                                              D            0 Sun Oct  5 22:11:07 2008

 lost+found                                            D            0 Mon Mar 31 12:45:23 2008

                    >>>>> files deleted for brevity <<<<<

 Linux Firewalls Using iptables.doc   A  252416 Sun Oct  5 19:09:10 2008

 

        55384 blocks of size 1048576. 46808 blocks available

smb: \>

 

I am using a ‘per PC’ setup file for the windows server defining all machine specific directives leaving config.pl to define only the common settings.  In the $host file, I have tried various forms of how I specified the shares:  ‘\\servername\sharename’, ‘//servername/sharename’, ‘sharename’, etc.  All get the same result.

 

All machines on the network are running with static IP addresses and nmblookup consistently finds them all by either hostname or IP address.

 

Any comment or suggestion would be appreciated.  -- ken