Roland Roberts wrote:
> tcpdump is doing something weird; it won't show me the traffic for some
> reason (tcpdump -vv -n dst host 192.168.3.3 and src host 192.168.3.3);
> yet the client is clearly getting some message.
If the client and the director are on the same machine, you may need
to specify
On 03/29/2010 02:01 PM, Hugh Brown wrote:
> Roland Roberts wrote:
>
>> Okay, so it didn't work, no big deal, the server was past due to be
>> upgraded. So I upgraded to Fedora 12 on the server and picked up the
>> 3.0.3 bacula server. But since this upgrade, the 3.0.3 server can't
>> talk to
Hi Roland,
This is a small check list you can do following Hugh comment.
Assume the client passwd matches the director's passwd.
On backup server
1. do a status client=ClientName from bconsole, (send the result from
that)
2. if 1 does not work, do a ping to Client IP
3. do a nmap -PO clientI
Roland Roberts wrote:
> Okay, so it didn't work, no big deal, the server was past due to be
> upgraded. So I upgraded to Fedora 12 on the server and picked up the
> 3.0.3 bacula server. But since this upgrade, the 3.0.3 server can't
> talk to the 3.0.3 client. But it does talk to a 2.4.4 client
On 03/27/2010 08:41 AM, Julian Golderer wrote:
> Am Samstag 27 März 2010 02:57:17 schrieb Roland Roberts:
>
>> Any suggestions on what's happening here?
>>
> Maybe some problems with Fedora Firewall or SELinux?
> Does the fd listen to any interfaces?
> Does the fd just listen to IPv6 or I
Am Samstag 27 März 2010 02:57:17 schrieb Roland Roberts:
> Any suggestions on what's happening here?
Maybe some problems with Fedora Firewall or SELinux?
Does the fd listen to any interfaces?
Does the fd just listen to IPv6 or IPv4?
Nameresolution or DNS problems?
Julian
