[twsocket] OT: Microsoft network sniffers
Never noticed them before, but Microsoft has two network traffic monitoring or sniffer tools. The older one is Microsoft Network Monitor 3.4 for XP and later, and Microsoft Message Analyzer 1.0 for Windows 7 and later, both free from the download center. Has anyone tried either? I note that Nirsoft 'Who is connected sniffer' supports WinPcap and both the Microsoft tools, so presumably there is a published interface for them to allow application control. Has anyone tried the Microsoft sniffers? Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] OT: Microsoft network sniffers
I have long ago when I needed to look at traffic, both work for the job. Thanks, Matt -Original Message- From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of Angus Robertson - Magenta Systems Ltd Sent: Tuesday, March 11, 2014 11:21 AM To: twsocket@lists.elists.org Subject: [twsocket] OT: Microsoft network sniffers Never noticed them before, but Microsoft has two network traffic monitoring or sniffer tools. The older one is Microsoft Network Monitor 3.4 for XP and later, and Microsoft Message Analyzer 1.0 for Windows 7 and later, both free from the download center. Has anyone tried either? I note that Nirsoft 'Who is connected sniffer' supports WinPcap and both the Microsoft tools, so presumably there is a published interface for them to allow application control. Has anyone tried the Microsoft sniffers? Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TWsocketServer and ENQ ascii char
I use the tcp-ip to connect medical devices via the standard protocol ASTM . ASTM is the name of a standardization organization which probably - among other things - publish the protocol you are using. Is any reference document describing the protocol available? In ASTM to establish communication with the instrument, we must respond to Ascii character ENQ received by an ACK. However, it seems from what you have told me that TWsocketserver does not consume the ENQ. Is there a way to solve this problem? Are you writing a client program or a server program? A client program will connect (that is initiate the connect) while a server program will passively wait for connection. For a client, you should a a TWSocket component. For a server, you should use a TWSocketServer, but each connected client is handled by a TWSocket component. Whatever TWSocket you have, you should turn off line mode (this is off by default anyway). This way, you get an OnDatavailable as soon as the remote part is sending the ENQ. You then call Receive to get hand on the received characters and you can use Send to send the ACK. This is much the same as when using RS232 (I know you use it). The only serious difference is that data is sent by packet. That means you may receive a lot of characters at a time, usually a complete message. -- francois.pie...@overbyte.be Embarcadero MVP http://www.overbyte.be http://francois-piette.blogspot.com -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
