On Mon, 13 Jun 2005 17:31:47 +0100, G <(E-Mail Removed)> wrote:
>>>I have a 3com Wireless ADSL router (this one:
>>>http://www.3com.com/prod/en_UK_EMEA/...=3CRWDR100A-72)
>I've been using the US Robotics (USR) WiFi card admin tool, on which the
>'Site Survey' screen shows (I think) available networks across all
>channels. So I think the other networks probably *are* new, though I'm
>not sure if this is relevant.
The "site survey" tools for the access point and the clients are quite
different. The way infrastructure mode works is that the access point
sits on a fixed channel number. The client radio scans all the
channels looking for a matching SSID. When it finds the SSID, it
stays on that channel. The access point "site survey" is only
interested in other access points on the same channel it's sitting
upon.
>I don't think the problem is with the browser caching the router's admin
>screens
It's been a problem for me on several occasions. Best not to make
assumptions and just clear the browser cache and see what happens.
> -- the first thing I know of the channel switching back to 6 is
>when I see it listed that way on the Site Survey screen of the US
>Robotics tool.
I'm guessing that's the site survey tool in the wireless client
(laptop). It takes quite a while to "expire" the connection in such
tools. I'm not familiar with the SMC incantation, but the Dlink and
Linksys flavors will list an access point long after it has moved to a
different channel, or you've driven out of range. Methinks it best
that you fire up Netstumbler on either the laptop or on a different
machine. It will show instantly if there is any connection or status
change. If this is too much trouble, then just change the SSID at the
same time you change channel and tell the SMC client to go hunting for
the new SSID. That should take care of any persistance.
>Also, I can switch the router to any channel I like if
>the wireless feature is disabled, and it keeps showing that way on the
>admin screens. However, as soon as I re-enable wireless, it flips back to 6.
I'll stand on my guess(tm) that it's browser cacheing. That's exactly
what my stupid BEFW11S4v4 was doing before I put the browser settings
back to normal. The screens for wireless enabled and disabled are
probably diffrent. When you switch back and forth, the browser
displays the cached version instead of getting a fresh copy.
>As to the exact nature of the connection error -- I'll see if I can get
>an error message out of it when I'm back home tonight, but in general I
>see my network listed, click on it and click 'Connect'... and nothing
>happens. It says 'Connecting...' for a few seconds, then gives up and
>starts 'Scanning...' again. The basic problem is that I can't get a
>connection at all -- I get the Windows network connection icon at the
>right of the taskbar with a red X on it.
The big X usually means that it's disabled. Right click and select
"enable". Of course, it's probably not something that simple.
There's probably a connection "profile" in the SMC client that's setup
to autologon to your access point. Probably, some of the settings
have changed. If there's such an animal, try deleting and recreating
the connection parameters. If you can "see" the access point with the
SMC client utility, then you should be able to connect. Also, try it
without encryption to simplify testing. Then turn the encryption back
on again.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558