Hello.
For any possible future reference: the part about the wildcard may be
correct or may be nonsense, but what actually solved the problem was
adding the “domain” entry in /etc/resolv.conf.
Sincerely,
Maxim
2012/2/1 haruspex :
> Hello.
>
> Thank you, you saved me from going insane.
ect even from localhost. Either I
missed a firewall/antivirus setting somewhere, or the rsyncd doesn't
like Windows 7 (and it is even 32-bit).
Sincerely,
Maxim
2012/1/31 Les Mikesell :
> On Tue, Jan 31, 2012 at 11:25 AM, haruspex
> wrote:
>> Hello.
>>
>> Name resolu
checked?..
Sincerely,
Maxim
2012/1/31 Les Mikesell :
> On Tue, Jan 31, 2012 at 9:59 AM, haruspex wrote:
>>
>> “rsync target::” works just fine:
>> vm-backuppc# /usr/local/bin/rsync 192.168.0.118::
>> docs Documents and Settings
>> dDrive En
em
is somewhere with how BackupPC handles the sockets or nearby, judging
by results of “grep -r "inet connect" *”...
Sincerely,
Maxim
2012/1/31 Les Mikesell :
> On Tue, Jan 31, 2012 at 9:29 AM, haruspex wrote:
>>
>> I have installed BackupPC 3.2.1 on a FreeBSD server to back s
into something similar a little while ago.
>
> --
> /Sorin
>
>
> -Original Message-
> From: haruspex [mailto:princeps.candi...@gmail.com]
> Sent: den 31 januari 2012 16:29
> To: backuppc-users@lists.sourceforge.net
> Subject: [BackupPC-users] Bizarre connection failu
Hello.
I have installed BackupPC 3.2.1 on a FreeBSD server to back several
Windows workstations up. The Xfer method is rsyncd. Some of them
workstations work fine, but three display strange behaviour:
1) One gives “inet connect: Connection refused” though “telnet
873” from the very same FreeBSD
