> 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 telnet to the port in question to check if it works; much quicker than
restarting your job every time.
First check it on host itself; like 'telnet localhost 9103'
If this works (you get 'connected to') you know the daemon is listening.
Then try the same from another host on your network. If this works, the
firewall settings are probably not bothering you. <- if you firewall based on
the remote ip address, it will work from here, but not from the outside..
Check that if you have problems.
If that worked, try the same from the system outside your network. If this
does not work; check if the port-forward is set correctly (to the right port
on the right host)
Ger.
"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.0 / 0.0.0.0
Destination IP/Mask: 10.0.0.5 / 255.255.255.255 ( 10.0.0.5 is "host")
Port Start/Port End/Port Map: 9103 / 9103 / 9103
Protocol: TCP
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
