Wireless Access

 View Only
  • 1.  WL400 Goes "Off-Line" for no apparent reason?

    Posted May 12, 2003 04:34 PM
    We've had a WL400 as part of our Wireless AP's.. along with other. Seems like out of nowhere it goes "offline" as shown on the AP Manager display. Re-powering the unit seems to clear it ... but only 'for a while'. Then it goes offline again. The indicator lamps look 'normal' during this operation--just cant communicate when it's offline.

    Why? I dont know?
    It is up-to-date on firmware 2.5.3 with the 2.5.1 AP Manager. The Clients are using WL100's with the most current CPQ drivers--W2K all around.

    The AP's are dedicated IP's connected via switches to Linksys BEFSX41 VPN Router. Client machines are DHCP fed via the router's DHCP server--AP range are not served.

    Any thoughts would be appreciated.

    Chet.


  • 2.  RE: WL400 Goes "Off-Line" for no apparent reason?

    Posted May 13, 2003 02:29 AM
    Mmmm... not an easy one :
    Could be that your AP disconnects because it is perturbated by another AP, which echoes around and have your machines considering connection not valid anymore. Could be also configuration problem, like for XP, when you use WEP encryption, connection is stopped after a while (because machines have an idle timeout set). Check this encryption prob, try also to Uncheck the 'Closed Wireless Network' option...
    It works on many networks, the prob you describe is not harware one, must be a config prob...
    hth
    J


  • 3.  RE: WL400 Goes "Off-Line" for no apparent reason?

    Posted May 13, 2003 11:44 AM
    Not sure what 'Closed Wireless Network' means here? -- remember full W2K environment only. I'm having no issues with Netgear and Linksys WAP's only the WL400---again, it just goes offline...signal's still there.. the AP Manager just shows the WL400 and its IP go to 'off line' status. If I 'repower' the unit... it comes back for a few minutes.

    I've also tried changing channels, re-setting up WEP64, changing the authentication on the cards from OPEN to SHAREDKEY...??? It's just baffling.

    I agree it is probably NOT the HW... but what's the fix?

    Baffling!