This is really interesting as I've never encountered it before (from other hosting providers)
Basically, the problem is now solved by changing the identity (impersonation) element in Web.Config file.
My understanding is by default (not specifying in the Web.Config), impersonation is set to...