![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Dear Sir/Mam,
I have written a server code using the Windows Socket API's. Wherein I have created the socket and bound it to a particular IP address and port number. Later I have made the socket in non-blocking mode by using the proper socket option ( i.e. SO_RCVTIMEO). After which with the use of recv() I am trying to get into the receive mode. Here as the receive time out is being used the socket should come out of the block mode after the time out value. But this is not happening here, instead the socket is always in the blocking mode. I am facing this kind of an issue only on few of the VISTA systems. Whereas on few other VISTA systems it is working fine (means we are ableto switch between block and non-block modes). But there is no problem on any of the XP systems. If I use the Ioctl() function then socket come out from blocking mode in VISTA or XP but if I use the setsocketoption then socket is getting block only on some VISTA system. Could you please provide me with information related to this and help in deriving a proper conclusion. Thanks in advance, |