Re: [Bacula-users] WinXP Bacula client problem

2006-07-31 Thread Brandon King
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Thanks for the suggestion. TcpView is a nice way of viewing connections, but as I found out, won't tell you if tcp-filtering is turned on, which was my problem! It's now working again after I added port 9102 to tcp-filtering exceptions as well

Re: [Bacula-users] WinXP Bacula client problem

2006-07-31 Thread Georger Araujo
Get TCPView from http://www.sysinternals.com/Utilities/TcpView.html and check if bacula-fd.exe is really listening on port 9102. It definitely could be a firewall issue. Double-check exceptions, both in programs and ports, and make sure the client (IP and port) is correctly configured on both sides

Re: [Bacula-users] WinXP Bacula client problem

2006-07-31 Thread Brandon King
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I forgot to mention I am using bacula 1.38.11 with win32 client 1.38.10. Also, the error message I get when doing 'status client' from the bconsole, I get: Connecting to Client burner-fd at xxx.xxx.xxx.xxx:9102 Failed to connect to Client burner-f

[Bacula-users] WinXP Bacula client problem

2006-07-31 Thread Brandon King
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I've got bacula setup and running on a Linux server and I've been trying to setup up clients. So, far I've tried three WinXP machines. Two of them worked just fine, but one of them I am having trouble with. For some reason bacula-fd.exe serv