We have a set of servers communication on a domain using WCF with net.tcp binding. Everything works well, everybody can play together. However, if I start a VPN connection on a client machine even though the connection to the remote WCF service
does not use VPN (Use default gateway or remote network is unchecked), and the IP address I'm connecting to does not exist on the WCF server (it is on the local machine only), the mere fact that VPN is running prevents the WCF client from making the connection
to the remote machine. We get a message saying something to the effect of "the remote logon faiiled" and "the server has rejected the client credentials". Presumably VPN is screwing up the client credentials somehow, but ...
We cannot always guarantee that our customers will never have VPN running! In fact, I need VPN to connect to our bug tracking system. It seems like there should be some way to use WCF with net.tcp binding and yet allow a completely unrelated
VPN connection to be made.
Any ideas would be greatly appreciated!
View Complete Post