Argh..I think I discovered the problem. Our LANDesk core is publically resolvable but not accessible. It appears that because our core resolves from the outside world BrokerConfig.exe that it assumes it can connect to it. If I modify the hosts file and put a bogus IP in for our LANDesk core then I am able to pull policy or send inventory scans via the LANDesk Gateway from outside our network
1 of 1 people found this helpful
The problem you will have is when the client come back into the corporate network, you will not be able to resolve the core and have issues. I would look at why you have a DNS record that resolves the core publicly outside. If it is not necessary, I would remove it. You may also try http://www.droppedpackets.org/technology/mg/ldms-auto-gateway/
I can remove the public DNS record for the core server but I just wanted to make sure that's what was causing the issue. At least, it seems like that's what's happening.