Hey, > No route to host = firewall?
No. The hosts in question are simply not running, but on the same subnet. That's OK though, because they're workstations whose users are not in today. But that's not the point. The point is that cfrun prints > > cfrun:ls-bs-si2.bs.linet-services.de: Couldn't open a socket > > cfrun:ls-bs-si2.bs.linet-services.de: socket: No route to host three times although the hosts ls-bs-ws3.bs.linet-services.de, ls-bs-ws7.bs.linet-services.de and ls-bs-ws8.bs.linet-services.de are the ones that aren't reachable. The output above is useless. ls-bs-si2.bs.linet-services.de is up and reachable, tested with "cfrun ls-bs-si2.bs.linet-services.de" (in fact, it is the host on which I run "cfrun"). Moritz -- LINET Services GbR Gotenweg 15 Tel.: 0531-280 191 71 38106 Braunschweig Fax.: 0531-280 191 72 http://www.linet-services.de [EMAIL PROTECTED]
pgpYSnBhQC3X1.pgp
Description: PGP signature
_______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine