i have the same problem since last week; the list for "available wireless networks in range" kept being empty; after 3-4 nlites i ended up with a working and a non-working configurations; posting both of the configurations and the difference; Non-Working: Last_Session__2008.05.19_00.04.30_.ini Working: Last_Session__2008.05.19_01.31.34_.ini Difference(removed components in the Non-Working config): ;# Network # Client for Netware Networks Communication tools Comtrol Test Terminal Program Connection Manager FrontPage Extensions H323 MSP Internet Connection Wizard Internet Information Services (IIS) IP Conferencing MSN Explorer Netmeeting Network Diagnostic NWLink IPX/SPX/NetBIOS Protocol Peer-to-Peer Share Creation Wizard Synchronization Manager Vector Graphics Rendering (VML) Web Folders Windows Messenger ;# Services # Alerter Application Layer Gateway Beep Driver Distributed Link Tracking Client Error Reporting Extensible Authentication Protocol Service Fax Service Health Key and Certificate Management Service IMAPI CD-Burning COM Service Indexing Service Messenger Network Access Protection (NAP) Network DDE QoS RSVP Quality of Service (QoS) Remote Registry Removable Storage Route Listening Service RPC Locator Service Advertising Protocol Simple TCP/IP Services System Restore Service Task Scheduler Telnet Uninterruptible Power Supply Volume Shadow Copy Windows Time Wired AutoConfig ONE or more of the above components/services is responsible(there is a dependency); hope someone can pin-point the cause(me just cant invest the time); my guess is, its one of the top components in "Network" section; note: this is an SP3 issue(i read that in SP3 the wireless subsystem has been completely/partialy redone); never had this issue in SP2
