I have seen this question on this board several times but have not seen a resolution. I am testing an application with about 300 virtual users using IE 5.5. This should results in around 1200 concurrent connections. However, I receive the Winsock 10060 after 1 minute and 20 seconds consistantly. I have modified my number of connections for each controller and agent machine to the 65000 setting. I have also set the TcpNumConnections in the registery for each machine at 16000. Has anyone who has experienced this issue found a solution to their problem? Please help!
I had this problem and is caused by a redirection to some site in the internet (I'm testing on the intranet). Verify if there is a redirection, in this case modify the socks configuration in the in EditProfile\Replay\Internet\Hosts tab, in the Standardhost field put the IP address of the redirection and put the your socks configuration in the socks field, don't forget the ports.
Hope this helps.
[This message has been edited by sqainfo (edited 06-27-2001).]
The times I've seen winsock errors have been when the web server has been overwhelmed in some manner.
I ran into this problem testing a web server based on NT4/IIS4. When the server was upgraded to Windows 2K/IIS5, the winsock errors disappeared. I normally saw winsock errors either when I slammed the server with a high number of initial requests or when the test ramped up to very high levels of traffic.
What kind of server are you testing? Is your content static or are you pull content from a database/include files?
Are you starting off with a small number of users and ramping up or are you hitting the server with 300 users right off the bat?
I also had the same sort of message and that too was caused by the server.
Ramped up the memory on the server and things were better.
The trouble is, I think it is quite confusing getting winsock errors, especially when you are testing Linux servers which obviously don't use winsock. Because of this, I was initially under the impression that the cause was down to the SP agent machines, and it also doesn't help that there doesn't seem to be many resources giving a detailed explanation of winsock errors.