Toad World® Forums

Toad floods Windows 2008 with failed logins

I have a SQL Server 2008 Enterprise R2 installation, and a client accesses it using TOAD for SQL Server across a VPN. All he has to do is load his copy of TOAD while on the VPN (doesn’t even have to connect to my database server), and my SQL Server box is immediately flooded (seen via the Security Event Log) with failed NTLM lgoin attempts from the computer that is running TOAD, all on different ports, which continues once a second until TOAD exits. I have seen nothing on the net that relates to this yet. TOAD has been uninstalled and re-installed, so a virus is doubtful, and it definitely occurs when TOAD starts, and stops when TOAD exits.

Has anyone seen a problem like this, or can anyone give me a place to look to rectify this situation? I know I can use another query analyzer instead of TOAD, but the point here is to use TOAD without having these issues with security on my SQL Server box.

Thanks,
Brian

Hi Brain,

can you please let me know if you have turned on this option:
Tools>Options>Database>General>Pool service status in connection list

Yes, the user on my system who is using TOAD does have the Pool Service Status in the connection list on. I assume turning it off may result in these bad logins stopping?

Thanks,
Brian

Can you please turn it off and let us know if it helped?

Valentin, I know I had this issue several week ago !!!

In my case it was suspected that a malware was the culprit, which was found with
Avast Pro boot level virus scan, but not found with Windows running.

However, now I have my doubts.

Please advise the setting recommendation to prevent this from happening.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image002.jpeg

Valentin, I know I had this issue several week ago !!!

In my case it was suspected that a malware was the culprit, which was found with
Avast Pro boot level virus scan, but not found with Windows running.

However, now I have my doubts.

Please advise the setting recommendation to prevent this from happening.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image003.png

Valentin, I know I had this issue several week ago !!!

In my case it was suspected that a malware was the culprit, which was found with
Avast Pro boot level virus scan, but not found with Windows running.

However, now I have my doubts.

Please advise the setting recommendation to prevent this from happening.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image001.gif

Valentine,
We turned off the Pool Service Status on TOAD, and the login failure flood immediately stopped. My client could still used TOAD to connect to SS, so no skin off his nose if this is turned off, but now I do not get any spurious attempts to connect to my SQL Server while his TOAD is running. I hope this helps the other person on this thread who had a similar problem. My problem was resolved by turning OFF this option: Tools>Options>Database>General>Pool service status

Thanks for your assistance, much appreciated.
Brian

Brian, thanks for the update… Who Knew !!!

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image001.gif

Brian, thanks for the update… Who Knew !!!

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image002.jpeg