Tom Newton wrote, sometime around 03/08/06 15:19: > On Thu, 2006-08-03 at 15:11 +0100, Russell Howe wrote: >> It said the fd closed the connection - anything in the FD's logs (on the >> Windows box) explaining why? > > Where might I find such a log?
Hmmm.. I thought it kept one, although I fail to see where now that I'm actually logged into one of our Windows boxes. Is there anything which looks promising on the right click menu for the filedaemon's tray icon? I'd run tcpdump on the intermediary firewall and see if you spot the TCP connection being closed - that will at least potentially help you to debug this.. Also, look at "netstat -ano" output and match the pid of bacula-fd.exe (get it from Task Manager - you'll have to add in the "PID" column using 'View' -> 'Columns' or somesuch) to see which ports it is listening on. Once you know the port numbers, you should be able to telnet to them from the director and the fd and get a connection (along with warning messages from the fd about weird connections :) -- Russell Howe [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
