Everything didnt work. now I install the Serve new and keep my config files.
I will tell the result soon to you. Via telnet it was posible to get on the
comp. now I changed the name from backuupsrv to backup.
Oliver Knittel wrote:
>
> Hello Together,
>
> I get the folloing message when I ask
Oliver Knittel wrote:
> Hello Together,
>
> I get the folloing message when I ask for the Status of Storage File
>
> Fatal error: bsock.c:135 Unable to connect to Storage daemon on
> backupsrv.ke-si.intern:9103. ERR=Connection refused
>
> DNS is correct Sever Name is checkt many times FQN is in
> -Original Message-
> From: Oliver Knittel [mailto:o...@systemhaus-kec.de]
> Sent: 07 December 2009 14:34
> To: bacula-users@lists.sourceforge.net
> Subject: [Bacula-users] Bacula Problem Storage File
>
>
> Hello Together,
>
> I get the folloing message when I ask for the Status of St
Since telnet is refused, too, odds are that either there is a firewall
involved, or the FQDN resolves to the wrong host.
BTW, telnet failing is no longer always a reliable indicator of whether the
firewall is configured correctly, since many firewalls have different rules on
a per-application b
On Mon, Dec 07, 2009 at 06:33:59AM -0800, Oliver Knittel wrote:
>
> Hello Together,
>
> I get the folloing message when I ask for the Status of Storage File
>
> Fatal error: bsock.c:135 Unable to connect to Storage daemon on
> backupsrv.ke-si.intern:9103. ERR=Connection refused
>
> DNS is corre
On Mon, Dec 7, 2009 at 9:56 AM, John Drescher wrote:
>> I get the folloing message when I ask for the Status of Storage File
>>
>> Fatal error: bsock.c:135 Unable to connect to Storage daemon on
>> backupsrv.ke-si.intern:9103. ERR=Connection refused
>>
>> DNS is correct Sever Name is checkt many t
> I get the folloing message when I ask for the Status of Storage File
>
> Fatal error: bsock.c:135 Unable to connect to Storage daemon on
> backupsrv.ke-si.intern:9103. ERR=Connection refused
>
> DNS is correct Sever Name is checkt many times FQN is in hosts too. Password
> is proofed.
>
> When I