Re: [Bacula-users] Unable to Connect fo File daemon. ERR:No Route to host

2007-04-23 Thread Mike Vasquez
I can pint the client and the client can ping the host. I can even telnet into the client and the client can telnet into the host on port 9102 The machines are on the same network. Mike Ralf Winkler wrote: > > A error like this happen normally if the directory can not resolve the > name > of

Re: [Bacula-users] Unable to Connect fo File daemon. ERR:No Route to host

2007-04-23 Thread Keith Gunderson
A little bit more detail, if you need it. See if iptables is blocking the port, after your host configs are done. You may want to do a quick test on the director and storage host. (Save the settings, stop iptables, test bacula, start iptables, then configure iptables correctly.) I won't make

Re: [Bacula-users] Unable to Connect fo File daemon. ERR:No Route to host

2007-04-22 Thread Ralf Winkler
A error like this happen normally if the directory can not resolve the name of the client. Make sure you have a valid route to the client. Do you use subnetting? Can you ping the client from the director computer? Ralf On 4/21/07, Mike Vasquez <[EMAIL PROTECTED]> wrote: This is happened to

[Bacula-users] Unable to Connect fo File daemon. ERR:No Route to host

2007-04-22 Thread Mike Vasquez
This is happened to two new machines running CentOS 4.4. In the logs it says SD termination status: Waiting on FD Here is my settings on one of them. Client { Name = hl72 Address = 192.168.1.3 FDPort = 9102 Catalog = MyCatalog Password = "bacula" #