I apologize up front for sending this message to the list. I'm hoping one of the WinSock gurus here may have some thoughts on this strange issue. I use ICS components in my own source code. However, this issue is NOT related to the ICS components.
We have a DataSnap client talking to a DataSnap server via TCP/IP. (Note DataSnap is using Indy, and I'm asking them as well.) For most users, the client can connect to the socket without incident. However, on a given workstation where two Windows profiles can run our software and connect successfully, a third Windows profile gets the error "Invalid argument (#10022 in WSAAsyncSelect)" when trying to connect. Same application, same exact build. The source code is not doing anything specific to the Windows profile. User rights should not be an issue. Just to be sure, we made Domain Users an Administrator on one of the workstations we were testing. This made no difference. My best guess is that there are WinSock related configuration options in HKCU that could be affecting WinSock? My first thought was the MTU, but that is stored in HKLM\System. Has anyone seen something like this before? Where WSAAsyncSelect will fail for one user but not another? Thank you so much for any thoughts you have. -- Jon Robertson Embarcadero Certified Delphi XE Developer Good programming is 40% experience, 30% skill, 20% RTFM, 10% caffeine, and 5% attention to detail. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be