I have joined my domain but now it takes forever to "run the startup script". Like 5 or 6 minutes.-techidave
Here it only takes a few seconds to run it, the tooltip shows up after the login screen, however it looks like you're using the 'classic' login screen and not the newer XP Welcome type - something that I ought to of thought of but didn't
So a bit more testing.-4wd
When Joined to a domain XP & Vista always use the "Classic" logon GINA (Graphical Identification & Network Authorization) interface, The psudo Home Screen styled Other User option for domain members is new for 7. <-Completely off topic, but I thought I'd mention it.)
Does 5 or 6 minutes sound about right for the WiFi card init? I'm wondering if the script is waiting for the program to return. If the ping is every 5 sec, can you (just as a test value) add a sending ping X message to the prog so it's "pulse" can be checked?
EDIT: Just tried again with classic logon and it works OK here. The logon prompt shows up immediately with tooltip showing up a few seconds later, both when there is and isn't a connection. The NetCheck.exe should return immediately, (well, it does from a normal CLI), I wonder if it's possible to try running with the RunAs command, (sorry, no experience with that - perhaps SJ can help)?-4wd
This is one of those points where things get fuzzy. Disconnected is easy, and fully connected is easy, however, partially connected (like the not entirely initialized WiFi card) is a bitch. This is where socket behavior goes completely to shit without extreemly robust error checking. If the (above mentioned) ping X message test only counts to 1 in the 5 min script run time ... That would be a WSACleanup(...) on isle 5 after a partially fragged socket mess.
I don't suppose anyone could tell me how to set up a simple Domain that I could try and replicate this with, (I can set up another laptop as a Domain Controller under XP Pro)?-4wd
Active Directory Domain Controller requires Windows server (2k, 2k3, 2k8). But it's the media/network connection's behavior that's the issue, not the logon behavior.
Now if you put the wrong WEP key in your WiFi card and let it partially connect, DHCP should fail leaving you with an APIPA address and roughly the state you need to test with/for/on.
Caveat: Currently it doesn't reinitialise itself to display on the logon screen if the current user logs off - that's about it. I'm still looking at fixing this by calling it again, (probably needs higher privileges so it can display on the logon screen again).-4wd
Running it on logoff isn't really the issue, because the WiFi card stays on. The trick is to get it to run on wakeup from sleep/hibernation when the connection has dropped because the WiFi card was napping.