I have a home network that is ad-hoc based with no router. It has worked great with windows XP for years, but with Windows 7, it will not auto connect to it, will not auto server it on startup, and will not even give the option to set it to automatically log on. It refuses to remember the Wep code either. How can I set it to(or force if there is no built in option)windows to not only autoconnect to my network but to remember the Wep settings. It does not use WPA currently. Also, how can I make windows automatically SERVE the ad-hoc network on log-in instead of manually typing it in. Even if I tell the network manager to save the network, I have to delete that network and re-make it just to be able to serve it again next log in. this problem was in vista the the one month I used it before moving back to XP.

Really? Nobody?

Due to security, WEP is not going to be very effective on Windows 7. Can you use WPA instead?

The windows XP machine could not connect to Windows 7 created Ad-Hoc with WPA.

Does Windows at least see the network when you connect?

I am having the same problem. Yes, it sees the AD-HOC, you can connect to it... its just like the gentleman above said, you cant AUTO CONNECT to it from a windows 7 box, nor will the windows 7 box thats hosting the process will allow you to AUTO START the ad-hoc.

I have found that you also can't use "netsh wlan connect" to manually force an adhoc network connection. If you could do that, you could set up Task Scheduler to periodically issue this command and give the illusion of autoconnect."netsh wlan disconnect" *does* work. "connect" doesn't.Others have reported that this did work under Windows Vista, at least with auto-connect turned off in the profile.Has Microsoft given up on support for ad-hoc networking in Windows 7? Or do we have to wait a year for a service pack to fix this?

I am guessing that, unfortunately, this behavior is By Design. There is an error code specifically for this condition: WLAN_REASON_CODE_INVALID_ADHOC_CONNECTION_MODE Automatic connection cannot be set for an ad hoc network. You will get this error if you manually edit an ad-hoc connectionprofile to change it from manual to automatic and then attempt to load it with "netsh wlan add profile filename=<filename>".

hi all, i found a way to auto connect (via cmd) to adhoc networks in windows 7 * create a profile like you do for a hotspot * after that -> * start cmd. enter netsh goto wlan * export profile "yourcreatedprofile" * edit the exported profile in notepad.exe * replace * <connectionType>ESS</connectionType> * with * <connectionType>IBSS</connectionType> * * back in netsh type -> * add profile "yourcreatedprofile" * connect "yourcreatedprofile" * voila now you can use the commandline to connect like in Vista have fun inteks

wow inteks! i think only MS guys did understand you.. Can you pls write this like step-by-step for us, non-experts :) i really stuck in firts command line... i guess its not real command line because its not accepted in my cmd... one more time... pls describe it step by step, this problem gonna make me crash my laptop and bac to Vista :S