Windows 2000 DDK or Windows 2003 DDK

I'm testing NDIS driver that is built with Windows 2K DDK and Windows 2003 DDK as well on Windows 2003 host. I'm not recving any packets from the application layer on the host I'm testing. If I use same Driver on Windows 2000 host, I recv packets from application layer. Any clue?

 

It's a bit unclear. It sounds like your driver isn't receiving
outbound/send packets. But on second read, it sounds like you might be
having problems with loopback packets. What kind of NDIS driver are you
writing? IM or miniport?

Depending on your answer(s) I might have some idea of what's going on.

Bryan S. Burgin


This posting is provided "AS IS" with no warranties, and confers no rights.

 

and...

Bryan S. Burgin


This posting is provided "AS IS" with no warranties, and confers no rights.

 

I've NDIS 4.0 Intermediate Filter driver that is developed for Windows 2000 using Windows 2000 DDK.

Now I'm testing that driver on Windows 2003 host.

1. I compiled the Driver with Windows 2000 DDK and installed it on Windows 2003 host. Installation is smooth except the warning message saying the driver is not certified/designed for Windows 2003.

a) From a client machine, if i do telnet <win2k3 test machine><port>, then i see one TCP connection in SYN_RCVD State on win2k3 machine.
b) From win2k3 machine, if i do telnet <some other machine><port>, then i see one TCP connection in SYN_SENT state on Win2k3 machine.

The response from protocol module is getting dropped. I'm hitting breakpoints on incoming packets but not on outgoing packets. TCP sending packet out but my driver isn't recving the packets.

Thanks for the earlier reply. I appreciate your time. Now, i'm compiling the driver with Win2k3 DDK though the documentation says to compile with earlier (i.e. Win2K) version to work on both Win2K and Win2K3.

Any help is appreciated.

Thanks,
GSN

 

I would suggest making the stack as simple as possible -- just TCPIP, your
IM and the real adapter miniport (take out QoS/PSched, etc). Later, once
you have things going, start adding in the default stack. That will start
testing other areas of you driver -- like handling checksum offloading,
packet flags, etc.

You might also run "netstat -s" to see if it reports is (and why) packets
are discarded before it reaches (or should reach) the application header.
I'll guess, it's malformed header, bad checksum, bad address, etc.

Bryan S. Burgin


This posting is provided "AS IS" with no warranties, and confers no rights.

 

Thanks very much. I found the issue. I really appreciate your time. There were two issues. One is checksum error and other is ip routes on the system. The API "DeleteIpForward" didn't delete the route to Loopback Adapter.

I've two routes with same Network and MASK

one forward the packets to Loopback Adapter ... METRIC is 2 (low
I couldn't delete this route. Even when I attempted to delete that entry, I got a reply as "the specified route doesn't exist". If I type "route PRINT", it prints that route.

other to eth Adapter ... METRIC is 20 (high
I found workaround for this. I reduced the METRIC for this route to 1