I have a VB front end application working with a MySQL backend database. The software works GREAT when used with Windows 2000. When using Windows 98, scrolling through records, opening and closing a few forms that opens miscellaneous connections, the application will throw an 10055 - mysql cannot connect to the server error. (10055 is a WinSock's (Microsoft's TCP/IP stack implementation) error code.)
I did some research and found a few things that may help the situtation:
"Some users reported to us there is another solution for Windows 95/98/Me which solved the problem. Windows 95/98/Me allows up to 100 (default value) of concurrent TCP connections. It looks like when the number of connection reaches the limit 10055 error is reported. The solution is to increase the limit of simultaneous connections. You can do it by changing/creating value of the key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections
If you will create the MaxConnections variable key use STRING type for it (early Windows 95 used DWORD probably). Set the value to 300 for example, restart the Windows and check whether 10055 problem disappeared."
So I tried this, and it seemed to get a little further before crashing. Now it gives a "too many connections" error. After reading about the situation, it seems that windows 98 releases the connections 240 seconds later. I ran "netstat -an|more" and found indeed that Windows 98 was still hanging on to the connection to the MySQL server. There were WAY too many and of course that will cause problems if there is a MAX on the number of connections. Windows 2000 does not have this problem. It seems to release the connection almost immediately.
Does anyone know a solution for this problem? Is there a way to lower the connection time out? Is there a winsock replacement?? What about a different network card that might work differently? Any suggestions would be greatly appreciated.1
Aaron
I did some research and found a few things that may help the situtation:
"Some users reported to us there is another solution for Windows 95/98/Me which solved the problem. Windows 95/98/Me allows up to 100 (default value) of concurrent TCP connections. It looks like when the number of connection reaches the limit 10055 error is reported. The solution is to increase the limit of simultaneous connections. You can do it by changing/creating value of the key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections
If you will create the MaxConnections variable key use STRING type for it (early Windows 95 used DWORD probably). Set the value to 300 for example, restart the Windows and check whether 10055 problem disappeared."
So I tried this, and it seemed to get a little further before crashing. Now it gives a "too many connections" error. After reading about the situation, it seems that windows 98 releases the connections 240 seconds later. I ran "netstat -an|more" and found indeed that Windows 98 was still hanging on to the connection to the MySQL server. There were WAY too many and of course that will cause problems if there is a MAX on the number of connections. Windows 2000 does not have this problem. It seems to release the connection almost immediately.
Does anyone know a solution for this problem? Is there a way to lower the connection time out? Is there a winsock replacement?? What about a different network card that might work differently? Any suggestions would be greatly appreciated.1
Aaron
![[ponder]](/data/assets/smilies/ponder.gif "[ponder] [ponder]")
