It does seem to me that this is a Windows security issue. When run from SSMS all is okay so it would have the security context of the user who is logged in. When run through SQL Agent Job it will be the security context of the SQL Agent Service Account. Not my forte, but I would be looking at Windows Event logs first. I would also be asking questions about proxy rules to our infrastructure guys in case the call can't get through.