Got an interesting problem. I have a new Win 10 PC, an industrial small form factor PC. 2 Ethernet ports, I have both configured for static IP addresses. One is (going from memory right now) 192.168.0.1, the other is 192.168.0.2. I have two external pieces of equipment, also with static IP addresses, 192.168.0.20 and 192.168.0.40. I have my own application that communicates with the two peripherals, and both peripherals have their own factory utilities, so I have something I can test with. The deal is: After resetting or powering up the PC, communication will fail the first time. I have to retry. Once communication is established, I can close and open applications all day long and not have a connection failure. As soon as I cycle power to the PC or restart it, the connections will fail the first time and need a retry. I thought it might be my application missing something, but the same thing happens with the utilities that come with the peripherals. I'm suspecting there is some sort of "wake" function for the LANs that I'm missing. This PC is the first time I've used Win10, but not the first time I've used this brand of PC. Does Win 10 have any sort of power-saving that I need to work around? I have turned off all firewalls thinking it might be blocking something. After power cycle or restart I can ping the IP addresses of the peripherals and get a response, but if I try to connect they will fail...just the first time. Any ideas? I'm not some networking genius, so you'll have to type slowly. Thanks.