Re: can't connect to remote client

On 9/2/25 12:04, Gary Dale wrote:
> When I run bacula-dir with -d 100 then try the connection to my client 
> using bconsole, I get the output below, which shows that the address 
> translation is working. The fd is running on the client machine and 
> the name and password match. I've listed the server as a director 
> authorized to contact the fd. And yes, I did restart the fd. No, there 
> is no firewall. Yes, I can do things like ping the client workstation.
>
> Connecting to Client <client name>-fd at <client FQDN>:9102
> TheLibrarian-dir: bsockcore.c:357-0 Current <client local IP>:9102 All 
> <client local IP>:9102
> TheLibrarian-dir: bsockcore.c:447-0 Could not connect to server 
> Client: <client name>-fd <client FQDN>:9102. ERR=Connection refused
> TheLibrarian-dir: bsockcore.c:254-0 Unable to connect to Client: 
> <client name>-fd on Transponder.home.rahim-dale.org:9102. 
> ERR=Connection refused
;;;

Does netstat on the client machine show that bacula-fd is actually 
running and listening on the addresses and ports that you think it does?

Does the Director resource Password in bacula-fd.conf on the client 
match the Client resource Password in bacula-dir.conf?

Can you telnet from the machine that bacula-sd is running on to the 
client machine's TCP port 9102?