Windows Embedded Standard 7 TCP/IP Services not completely started before user application loads RRS feed

  • Question

  • WES7 is set to autologon a user and launch a startup batch that launches my application.  My application, through a series of LEDs, notifies the user when the system is initialized and ready to go.  What I've noticed is that even though the system is "up and running" TCP/IP services are not initialized yet.  For example, RDP Server won't respond as well as ICMP/ping and FTP services.  Sometime later, maybe 20-30 seconds Windows TCP/IP services come alive and everything is okay.  Once other thing to note is that I am using BIT Locker and when I turn it off, TCP/IP services, a majority of the time, are alive immediately at or around autologon.  My guess is that there is some contention when Windows is logging and starting services and the behavior for which services are started when is not always deterministic.  Is there a way to guarantee TCP/IP services starting before other services?  I’ve messed around with several services in service manager but none seemed to fix the problem.  One other item to note.  I was able to issue a ping as my first command in my startup script to a fixed IP which appears to force TCP/IP services to initialize.  The problem with this “hack” is that I don't know any host IP addresses until my system has fully started.  Plugging in the loopback address in the script or my own external IP did not work.



    Thursday, January 29, 2015 5:39 PM

All replies