FIX: TOS Bits Cannot Be Set for Unconnected Sockets (196358)
The information in this article applies to:
- Microsoft Platform Software Development Kit (SDK) 1.0, when used with:
- the operating system: Microsoft Windows NT
This article was previously published under Q196358 SYMPTOMS
Type-of-Service (TOS) bits on the header portion of IP packets cannot be
set for unconnected User Datagram Protocol (UDP) sockets. Unconnected UDP
sockets are Windows sockets of type SOCK_DGRAM in the address family
AF_INET which do not use the connect/WSAConnect API to establish a default
destination address for the send/WSASend and recv/WSARecv API calls.
RESOLUTION
To specify TOS values for UDP sockets, use connected UDP sockets or apply
the fix provided in the MORE INFORMATION section of this article. To use
connected UDP sockets, use the Winsock connect/WSAConnect API call where
the operation performed by connect establishes a default destination
address that can be used on subsequent send/WSASend and recv/WSARecv calls.
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 4.0 and
Windows NT 4.0 with Service Packs 1, 2, and 3. This problem was corrected
in Microsoft Windows NT 4.0 Service Pack 4. To obtain the latest Windows NT
4.0 service pack, please see the following article in the Microsoft
Knowledge Base.
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Modification Type: | Minor | Last Reviewed: | 7/11/2005 |
---|
Keywords: | kbBug kbfix kbIP kbOSWinNT400sp4fix kbWinsock KB196358 |
---|
|