Greetings. I have created a C# software application which communicates wirelessly (using a virtual Wifi access point running from my laptop) with some hardware I have built. When operating properly, the C# application continuously sends time-critical (every 200 milliseconds) "keep-alive" polling messages to the hardware using the TCP/IP protocol and it (the hardware) acknowledges the receipt of these keep-alive messages. The problem that I have is that this communication works perfectly on one laptop and only works momentarily on another identical laptop - keep-alive messages only work for about 2 seconds before the connection to the hardware is lost. The hardware on the laptops are the same so it is most probably a software setting issue. I suspect that there are some processes that take priority over the TCP/IP connection when running my C# application on the second laptop (the one which doesn't work). The base priority for my C# application's TCP/IP thread is set to Realtime. Any good pointers will be highly appreciated. Thanks

Hi, Based on my knowledge, the issue is related to software development and advanced TCP/IP configuration, Therefore, it is recommended to post the thread in MSDN related forums. Hope this helps. Jeremy Wu TechNet Community Support