mimi hath wroth:
Yet another way. Right click on the "My Computah" on the desktop. Select Properties -> Hardware -> Device Manager -> etc. I think you're working under the "advanced" tab.
Fastest way: Start -> Run -> cmd devmgmt.msc
Extra credit: To go directly to various control panel and admin appletes, first make a list with: Start -> Run -> cmd cd \\windows\\system32 (or winnt for w2K) dir *.msc You can kinda guess what they do by decoding the file names. For example, gpedit.msc is the Group Policy Editor.
That will not work. The "properties" for your unspecified wireless device is usually a rather extensive list. There are several places where it lists the wireless channel. One is for ad-hoc networking only and will change the channel. The other is for infrstructure type networking and will change as soon as you connect to an access point. I guess(tm) that the setting is there for a starting channel when the client scans for a suitable access point to connect. In infrastructure mode, the channel is controlled by the access point, not the client.
You're mixing two questions here. Encryption has nothing to do with channel. You can mangle the encryption any way you want, and you still be able to connect. That's because the access point controls the channel, not the client computah. If you tweak the registry or device properties to claim that the client is on channel 1, but the access point is on channel 11, you're going to end up on channel 11 (in infrastructure mode). Ad-hoc is a different story.
No clue why you can't connect (or what you're trying to accomplish). Since you're into tweaking, it's likely that you have changed something that shouldn't have been changed. Hard to tell from here, especially since you didn't disclose what device you're tweaking. In another part of this thread, you seem to have solve the encryption key problem, so I guess it's fixed.
Incidentally, if you're a masochist, try enabling the Windoze Wireless diagnostic output using: netsh ras set tracing * en net stop wzcsvc net start wzcsvc Look for log files in: c:\\windoze\\tracing\\ directory. There's quite a bit of output, but something should show up in wzctrace.log.
I usually save a trace file collection for a normal connection. Then, when something goes awry, I can compare it with the current version.