Article ID: 890856 - Last Review: October 26, 2006 - Revision: 1.5 A program that uses raw sockets may not see incoming UDP packets in Windows 2000
On This PageSYMPTOMSIn Microsoft Windows 2000, when you run a program that uses raw sockets, and the raw sockets use the WSAIoctl function with the SIO_RCVALL flag, the program does not see an incoming User Datagram Protocol (UDP) packet. The application sees only the outgoing Internet Control Message Protocol (ICMP) packet. This problem occurs even though the UDP packet is set to an unbound port. For example, this problem occurs when your program uses the Rcvall code sample that is included in the Windows 2000 software development kit (SDK). Programs that are affected may include a call that is similar to the following: WSAIoctl(
Socket, SIO_RCVALL, &Option, sizeof(Option), NULL, 0,
&Length, NULL, NULL
);
CAUSEThis problem occurs because the TCP/IP stack lacks the code that is required to handle this scenario correctly. RESOLUTIONHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesNo prerequisites are required.Restart requirementYou must restart your computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Version Size File name ----------------------------------------------------- 19-Jun-2003 19:05 5.0.2195.6687 120,240 Afd.sys 19-Jun-2003 19:05 5.0.2195.6602 108,816 Msafd.dll 08-Dec-2004 04:08 5.0.2195.7008 319,792 Tcpip.sys 19-Jun-2003 19:05 5.0.2195.6655 16,240 Tdi.sys 19-Jun-2003 19:05 5.0.2195.6601 17,680 Wshtcpip.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor additional information about the new file naming schema for Microsoft Windows software update packages, click the following article number to view the article in the Microsoft Knowledge Base: 816915
(http://support.microsoft.com/kb/816915/
)
New file naming schema for Microsoft Windows software update packages For additional information about the terminology that is used in this article, click the following article number to view the article in the Microsoft Knowledge Base:824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates | Other Resources Other Support Sites
CommunityArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top