In this situation, my application can connect to the MSSQL server in one of two ways; via a direct TCP/IP connection (WAN) (IP's filtered using RRAS in 2003 Server) or via a VPN connection.
The application will first try to open the connection using the WAN connection string and if it can't, then it tries using the VPN connection string.
My issue is, I set the connection timeout to 5 seconds for the first attempt but it's taking way longer than that to return an exception. The order in which I attempt to open the connection doesn't really matter.
I have looked at the ConnectionTimeout property after changing the connection string and it does indeed show 5 seconds. It appears that the connection timeout value is being ignored.
Everything works but the long delay, for VPN users, is just annoying.
Has anyone had this issue?