So, how can I get this ephemeral port? When is it created?
Because in TdiDispatchCreate I got the IP Address (when EaName = TdiTransportAddress). But for ports (when EaName = TdiConnectionContext) DDK says that EaValue contains client-supplied handle, opaque to the transport driver, what is this handle.
Where is the port ? Where can I get it (in which TdiDispatchXXX) ?
TIA
Abhijit
wrote in message news:xxxxx@ntdev…
Yes. If you used winsock, and have written a client side code for client-server communication. You would recollect that the client does not specify the local port and tcpip assigns an ephimeral port for it. This is what you are seeing.
-Srin.
----------------------------------------------------------------------------
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Abhijit
Sent: Wednesday, March 24, 2004 9:24 PM
To: Windows System Software Devs Interest List
Subject: [spam] [ntdev] TA_ADDRESS in TDIDispatchCreate of TDI filter driver
In a TDI filter driver, the “Address” field of the Address Object (TA_ADDRESS), is
showing some strange value.
I have done the following:
In a TDI Filter driver’s TDIDispatchCreate, I get the pointer to TA_ADDRESS
object. The AddressType = TDI_ADDRESS_TYPE_IP, but the Address mostly contains
0s. What is this address ? Is it the IP address ?
TIA
Abhijit.
—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@nai.com
To unsubscribe send a blank email to xxxxx@lists.osr.com