When trying to connect to a server and the password is incorrect. Toad-SS and
Toad-ss-Beta gets stuck and Cancel will not work.
Toad should know right away whether the password is correct. Please adjust the
timeout value on the connection .. Additionally the cancel does not seem to
actually do anything…
No graphic provided, for this is easily reproduced.
Hmm… It seems I cannot reproduce it. Are you using SQL Server
authentication? For me, both ToadSS and MSMS react approximately the same way
– error message displays after less than one second. Is your connection
slow? What is the time span if you try to switch from or to this connection?
Hmm… It seems I cannot reproduce it. Are you using SQL Server
authentication? For me, both ToadSS and MSMS react approximately the same way
– error message displays after less than one second. Is your connection
slow? What is the time span if you try to switch from or to this connection?
Well, let me get the mud from the Hogpin off my face… Yes, it works well,
when there is a clear shot to the server. But It fails when the VPN connection
has been torque(d) and no-one let Father Time (AKA Elvis) know that the Secure
VPN (RSA Key) connection had been WACKED.
You should be able to immolate it if the TCP/IP is just plain wrong…. In
this example I have changed the last two digits of the address to .13 where it
would have worked if it was .21.
Sooo, you have a choice to consider…
Is this a bug or Fast Felix Fumbling his Fat Fingers like Elmer Fudd, which
would allow you to Please Deep-Six this issue…. But before you do so,
try a Wacked TCP/IP address and see if you like the NO-Cancel à Cancel
button… I believe is time out around 60 seconds…. (see Below)
Well, let me get the mud from the Hogpin off my face… Yes, it works well,
when there is a clear shot to the server. But It fails when the VPN connection
has been torque(d) and no-one let Father Time (AKA Elvis) know that the Secure
VPN (RSA Key) connection had been WACKED.
You should be able to immolate it if the TCP/IP is just plain wrong…. In
this example I have changed the last two digits of the address to .13 where it
would have worked if it was .21.
Sooo, you have a choice to consider…
Is this a bug or Fast Felix Fumbling his Fat Fingers like Elmer Fudd, which
would allow you to Please Deep-Six this issue…. But before you do so,
try a Wacked TCP/IP address and see if you like the NO-Cancel à Cancel
button… I believe is time out around 60 seconds…. (see Below)
Well, let me get the mud from the Hogpin off my face… Yes, it works well,
when there is a clear shot to the server. But It fails when the VPN connection
has been torque(d) and no-one let Father Time (AKA Elvis) know that the Secure
VPN (RSA Key) connection had been WACKED.
You should be able to immolate it if the TCP/IP is just plain wrong…. In
this example I have changed the last two digits of the address to .13 where it
would have worked if it was .21.
Sooo, you have a choice to consider…
Is this a bug or Fast Felix Fumbling his Fat Fingers like Elmer Fudd, which
would allow you to Please Deep-Six this issue…. But before you do so,
try a Wacked TCP/IP address and see if you like the NO-Cancel à Cancel
button… I believe is time out around 60 seconds…. (see Below)
Well, let me get the mud from the Hogpin off my face… Yes, it works well,
when there is a clear shot to the server. But It fails when the VPN connection
has been torque(d) and no-one let Father Time (AKA Elvis) know that the Secure
VPN (RSA Key) connection had been WACKED.
You should be able to immolate it if the TCP/IP is just plain wrong…. In
this example I have changed the last two digits of the address to .13 where it
would have worked if it was .21.
Sooo, you have a choice to consider…
Is this a bug or Fast Felix Fumbling his Fat Fingers like Elmer Fudd, which
would allow you to Please Deep-Six this issue…. But before you do so,
try a Wacked TCP/IP address and see if you like the NO-Cancel à Cancel
button… I believe is time out around 60 seconds…. (see Below)
Well, let me get the mud from the Hogpin off my face… Yes, it works well,
when there is a clear shot to the server. But It fails when the VPN connection
has been torque(d) and no-one let Father Time (AKA Elvis) know that the Secure
VPN (RSA Key) connection had been WACKED.
You should be able to immolate it if the TCP/IP is just plain wrong…. In
this example I have changed the last two digits of the address to .13 where it
would have worked if it was .21.
Sooo, you have a choice to consider..
Is this a bug or Fast Felix Fumbling his Fat Fingers like Elmer Fudd, which
would allow you to Please Deep-Six this issue…. But before you do so,
try a Wacked TCP/IP address and see if you like the NO-Cancel à Cancel
button… I believe is time out around 60 seconds…. (see Below)