WSAIoctl fails on Windows Server 2003

Question

0.00/5 (No votes)

See more:

Win2003

, +

Hello,

after wasting nearly two days by searching for a solution I try my luck here.

I am using the sniffer from A Little Sniffer that Uses WSA Sockets (Windows Sockets)[^].

My problem is that the call in WSAIoctl returns WSAEINVAL (10022) under Windows Server 2003 (NOT R2!!!), SP2 (the problem occures in both x64 and x86). I did not modify the code from the sample in the link above.

This all works well on Win7, Win Server 2008, Win Server 2003 R2 (yes, here it works!), Win2K. (I didn't have the opportunity to test XP yet)

So now, what is wrong with Win2K3 Server that WSAIoctl does not work? Anyone knowing this problem?

TIA
Hannes

Posted 5-Jun-11 23:28pm

hans083

Updated 5-Jun-11 23:53pm

v2

Add a Solution

2 solutions

Solution 2

after keeping searching and testing it seems that Win2K3 is not the problem. Either MS Network Monitor, also Wireshark do not work in any way with this hardware.

Posted 7-Jun-11 23:40pm

hans083

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

barneyman · Accepted Answer · 2011-06-06T02:21:00

Solution 1

the docs say Setting this IOCTL requires Administrator privilege on the local computer[^]

It may be that the network card you have doesn't support promiscuous mode - either way, have you established it is possible on that server with something like MS's Network Monitor?[^]

Posted 6-Jun-11 2:21am

barneyman