Re: [Bacula-users] Problems with BaculaSD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matti Jormakka wrote: > That the connection was refused seems significant. At least on a > Centos4 system with a default firewall configured, ports that are > not explicitely permitted are rejected. You don't say what OS you > are run

Re: [Bacula-users] Problems with BaculaSD

Thank you. Those confusing http://... are a result of some "nice" feature of e-mail reading software and not part of the original message.2006/11/6, Arno Lehmann < [EMAIL PROTECTED]>:Hi,On 11/6/2006 8:58 AM, Matti Jormakka wrote:> 2006/11/6, Ger Apeldoorn < [EMAIL PROTECTED]> [EMAIL PROTECTED]>>:>>

Re: [Bacula-users] Problems with BaculaSD

Hi, On 11/6/2006 8:58 AM, Matti Jormakka wrote: > 2006/11/6, Ger Apeldoorn <[EMAIL PROTECTED] > >: > > > I believe it already does connect to router, since > host.mydomain.com is > > resolved as the public IP (given by ISP natura

Re: [Bacula-users] Problems with BaculaSD

You did try if from another host on your network? Yes, with no success. The port forward looks fine to me... You dont need to do anything else to activate it? (just a guess)To me too... The port forwarding should work without any activations. All other port forwardings we have work fine.-- Matti Jo

Re: [Bacula-users] Problems with BaculaSD

> "Telnet localhost 9103" works but "telnet host.mydomain.com 9103" (which is > then correctly resolved as the public IP) doesn't. There seems to be > something wrong with the port forwarding. The port forwarding is set up > for the sd in the following way in the router: > > Source IP/Mask: 0.0.0.

Re: [Bacula-users] Problems with BaculaSD

2006/11/6, Ger Apeldoorn <[EMAIL PROTECTED]>: > I believe it already does connect to router, since host.mydomain.com is> resolved as the public IP (given by ISP naturally) of our router.Ok, I didnt get that.. :) Then you should check for the firewall like Michael proposed. It might also bethat the

Re: [Bacula-users] Problems with BaculaSD

That the connection was refused seems significant.  At least on aCentos4 system with a default firewall configured, ports that are not explicitely permitted are rejected.  You don't say what OS youare running, but you might check if firewall software is runninglocally and open the appropriate ports

Re: [Bacula-users] Problems with BaculaSD

> I believe it already does connect to router, since host.mydomain.com is > resolved as the public IP (given by ISP naturally) of our router. Ok, I didnt get that.. :) Then you should check for the firewall like Michael proposed. It might also be that the daemon is not running on host. You can

Re: [Bacula-users] Problems with BaculaSD

On Mon, 6 Nov 2006, Matti Jormakka wrote: We have configured a Director and a Storage Daemon on a machine called host in our local network. In addition to a local test File Daemon (running on host) we have a File Daemon on a machine outside our local network. We have set up a domain name host

Re: [Bacula-users] Problems with BaculaSD

> Shouldn't you make the FD connect to the router then?? > Port forwarding is something else than a router; the router mimicks the > host that is on the LAN. (for the specified port only) Sorry, that was not very clear, was it?? :) I meant this... Port forwarding is something else than a router;

Re: [Bacula-users] Problems with BaculaSD

Hi Matti, Op maandag 6 november 2006 07:27, schreef Matti Jormakka: > Hello, > > We have configured a Director and a Storage Daemon on a machine called > host in our local network. In addition to a local test File Daemon > (running on host) we have a File Daemon on a machine outside our local > ne

[Bacula-users] Problems with BaculaSD

Hello,We have configured a Director and a Storage Daemon on a machine called host in our local network. In addition to a local test File Daemon (running on host) we have a File Daemon on a machine outside our local network. We have set up a domain name host.domain.com for host that is visible to o