Ummm!
> > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
> > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
> > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
> > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0
> > >read_socket_with_timeout: timeout read. read error = Connection reset by peer.
> > >session setup failed: code 0
That's Samba doing a broadcast to find a particular machine. I've
noticed that amanda-2.4.2p1 doesn't like broadcasts at all and will fail
dismally even though smbclient will cope. You either need to:
* setup a "wins" server on the samba machine
* setup /etc/smb.conf on the samba machine to point at your "wins"
server
Now, I can't explain this very well but Samba, by default, will lookup
DNS, wins and then broadcast. You use "wins" if you want the SMB
protocol to work across a subnet; because you can't broadcast across a
subnet you need a special server to harvest the other subnet's
information. If your local Samba can't find the machine you want
locally, or via a local wins server, it will start to broadcast.
Eventually one of your wins servers will respond or it will timeout.
I've noticed that Amanda doesn't like this broadcast behaviour at all
and will fail despite the fact that smbclient '\\OTHERMACHINE\Share'
will eventually work.
In my smb.conf I have:
wins server = winsserver.mydomain.com.au
wins support = No
name resolve order = wins bcast host lmhosts
Amongst other things....
DSL
--
There's a sad face in the mirror
And I'm sad to say it's me
Like a ghost up in the attic
Only love can set met free...
