[don't treat below as gospel - I haven't flocked in a while so some things may have
changed or I may have mis-spelled things]
There a few subtle things that can stop flocking working:
* set FLOCK_TO and FLOCK_FROM at both ends for a 2 way flock
* HOSTALLOW values may need to be changed to include these other machines
* If you have security enabled - then this might need to be made more flexible
to include other authentication mechanisms
* Machines in other pool may be of a different ARCH or OpSys
* Your jobs may be setup to use a shared filestore (NFS for instance) which
isn't available from the other pool.
You can use
condor_config_val -pool NODE_NAME -name NODE_NAME val
where val is one of
hostallow_write, hostallow_read, flock_to, flock_from
to see what values are set for the different machines
But the more usual culprits are firewalls.
Are there any firewalls between the pools? (or is one pool behind a NAT)
Remember that for jobs to flock, every submit node needs to be able to talk to every execute node
and vice versa over the fixed ports and upper port range, all over both tcp and udp.
If that is not the case, you'll have to relax the firewalls or use GCB.
for more info on firewalls in a Condor Pool