Alas, RASPPTP.SYS on Vista still uses TDI and still fails to (or chooses
not to, who knows, maybe it is a ‘feature’) IoGetRelatedDeviceObject() when
it submits a TDI_SET_EVENT_HANDLER IRP.
But of course, Thomas is 100% right. On Vista, WFP is the way to go…
-dave
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Thomas F. Divine
Sent: Wednesday, November 28, 2007 2:42 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] strange use of TdiTransportAddress by windows vpn
server
Humm…
On Vista and later TDI is deprecated. There are shims that provide some
support for legacy TDI clients. However, TDI is not the mainline path for
filtering above the new Vista TCP/IP implementation.
Use the new Windows Filtering Platform (WFP) instead of TDI filters on Vista
and later platforms.
Good luck,
Thomas F. Divine
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-307213-
xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Wednesday, November 28, 2007 12:06 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] strange use of TdiTransportAddress by windows vpn
server
Hello all,
I have a TDI driver in which I monitor all address and connection
objects. When a VPN server is created in Windows Vista, I can see the
creation of the corresponding TdiTransportAddress for port 1723, but
no TDI_SET_EVENT_HANDLER or TDI_LISTEN requests. How does it manage to
listen for connections?
Thank you!
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer