A network trace between your IP address and the TCPIP stack is an excellent place to start. Looking at the packet trace will tell you whic h end of the connection is causing the delay.
It could be delays caused by conflicts between the TCPIP algorithms for Nagle and Delayed Acks (which can be intermitten based on the packets tha t need transmitting). Been there, debugged that. It could also be a problem on the PC if Windows is doing paging. Been there too. Brian Nielsen On Tue, 25 Aug 2009 12:32:22 -0700, Schuh, Richard <rsc...@visa.com> wrot e: >We notice fairly frequent occurrences of a momentary hang condition. We see the x-clock in the lower left corner of the terminal emulator screen. These can last any where from a couple to 30 or more seconds. I have been unsuccessful tying this to any messages in the TCPIP console log. How do I find out what is happening, whether it is a TCP/IP problem or one elsewhere in the network? > >* Surely there are numbers in the monitor data that will help, but which ones? I am at a loss. >* Are there any traces that I should run? Seems doubtful - how do you trace a non-event? > > >Regards, >Richard Schuh > > > >
