Connection Problems Using Standard Security

I have an app that queries the same SQL Server, instance and database. In one execution of the app, it makes multiple queries against the database in two different runs, each run being approx. 10 seconds apart. The app app does remote logins to the SQL Server using Standard Security. Each run makes twenty (20) connection attempts and all connection attempts between the two runs are using the same SQL account/password€¦(when successful) there is a .5 second delay between each attempt. So, here is a visual description:

Run 1
- connection attempt 1 (.5 sec delay), account1/password
- .
- .
- .
- connection attempt 20, account1/password

(10 second delay)

Run 2
- connection attempt 1 (.5 sec delay) , account1/password
- .
- .
- .
- connection attempt 20, account1/password


The problem I€™m seeing is: All connection attempts in Run 1 are successful in connecting to the SQL Server. All connection attempts in Run 2 are UNSUCCESFFUL when connecting to SQL Server (error message is €œSQL Server cannot be found or Access Denied€?). Remember, ALL connection attempts are using the same SQL account and password.

As an added note: When I switched from using SQL Standard Security to Windows Security, ALL connection attempts in each Run was successful.

Does see anything wrong with this? Is Standard SQL Security limited in the number of simultaneous connections or in some other kind of way?