Well, that can be a little confusing, so I plan ahead, in fact, the server tells you that you are not authorized, usually for this you would add something like below to the proxy generated by you
svc.ClientCredentials.Windows.AllowedImpersonationLevel = System.Security.Principal.TokenImpersonationLevel.Impersonation;
where svc is your generated proxy. I also saw this on an incorrectly configured IIS endpoint, where the virtual folder does not allow anonymous dialing (although you say that you cannot access the service configuration so that this does not help). hope this helps
edit added more information
Depending on your security, it may turn out that a setting similar to the one below may be more useful.
svc.ClientCredentials.Windows.AllowedImpersonationLevel = System.Security.Principal.TokenImpersonationLevel.Anonymous;
Edit 2 The above config shows that the wsHttpBinding you are using has Windows installed as clientCredentialtype for transport security and user authentication, which means that you will send NTLM authentication credentials through the current user credentials (since negotiateServiceCredentials is true) confirmed Do you, that the user is logged in, has the rights to the service?
source share