Ah - not quite what I meant.
1 - Don't bother trying to go to https://patchemea.landesk.com/ - that's not really a browseable site, never has been :).
2 - I was talking about Proxy / Firewall's specifically. You see, it's not "normal browsing", but may depend on user-context (depending on your proxy/firewall) of "who it is" that's trying to browse.
A scheduled patch content update for instance will by default run as the Core's Local System - and your proxy may not like that (or it may have been changed to "not like that"). This is why I said to have a look on Proxy (more likely) and Firewalls (less likely) to see if there's any entries in the logs there of the Core being blocked.
We've seen it a few times that Proxy's caused that problem because they were a bit user-sensitive, and people needed to grant "the Core Server" as opposed to specific users access to the www in the Proxy. There's no general rules here though, as the rules by which this applies change based on what Proxy you use - product A is quite different to Product B - it is its own field.
Hope that clarifies.
Paul Hoffmann
LANDesk EMEA Technical Lead.
error1.JPG
(59.4 K)
