I find that I am getting this error since I am using the netTCPBinding.
I don't get this exception when the client and server are on the same machine, but when they are on different machines, this exception occurs.
If I set the identity on the end point as mentioned in the article:
it is working fine.
So my question is , should the service end point always have an identity when using netTcpBinging?
I tried setting Security.Mode = None and still I got this identity exception.
is there any way through which I can ask the service to ignore the SSPI details and accept client request?
View Complete Post