for my wireless connection, if I want to make Windows "repair" it, I need these services :
: works if set to "manual", however it is always started as soon as network is running so I personally set it to "automatic"
: I just discovered about this one today. If it is not running, Windows cannot even disable the adapter. If set to "manual" but is not running, Windows don't start it so it fails. I used to set it to "manual", however I remember I always seen this service running. Should be started by Windows at boot. Now will set this one to "automatic"
network location awareness (NLA)
: the same as cryptographic service except it is not adapter disabling that fails, but the the IP acquisition step. repair process hangs.
: again the same except it is final registration step that fails. displays a message box "failed at DNS register". and DNS client
nearly the same, it fails just before, at releasing the previous DNS set.
as you can see, crypto, NLA, DNS and DHCP are called at different steps of the repair process. I think these services might be crucial for wired connections too. Also, I've already constated removing too many network-related components can lead to serious issues, like impossibility to accept incoming connection requests (server-oriented apps).
about my config : manually set adresses, no DHCP server on the network, do not use the Windows wireless assistant, no WEP or WPA
This post has been edited by OuTmAn: 19 January 2009 - 11:15 AM