Hello again,
I ran into another slight problem that has been discussed on the list
earlier... This one is about an error message that smbclient backup
produces on a couple of XP machines: "Call timed out: server did not
respond after 20000 milliseconds ..." Specifically, two locally
connected XP workstations produce this error repeatedly.
The response earlier was that using antivirus SW may cause very long
response times which trigger this hard-coded timeout of smbclient,
making the backup fail.
So, I was just wondering, are there any new ways around this issue?
I fooled around with smbclient's source code and recompiled it with a
threshold 10 times longer but still one of the machines on the local
network gives this error. (Or more precisely, reports that the server
did not respond after 200000 milliseconds.) The machine has an antivirus
suite installed, but so do all the other ones.
I was also able to "fix" this by installing Cygwin/rsyncd on the
misbehaving workstation, but I'd rather use the smbclient option, since
file sharing doesn't require any software installation on the clients.
Regards,
Marko Tukiainen
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
