wireless clients dropping off network when no traffic is passed

Unanswered Question
Oct 9th, 2008

Hi all, I have a setup whereas I have multiple workgroup bridges with a small switch connected to the ap with 3 pc's on each, these wgb's then associate to an access point. It seems that the connection does not stay alive between them unless we ping the wgb's.

Is there a reason and fix for this?

cheers

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
amritpatek Wed, 10/15/2008 - 06:02

The access point to which a workgroup bridge associates can treat the workgroup bridge as an infrastructure device or as a simple client device. By default, access points and bridges treat workgroup bridges as client devices.

You can configure access points and bridges to treat workgroup bridges not as client devices but as infrastructure devices, like access points or bridges. Treating a workgroup bridge as an infrastructure device means that the access point reliably delivers multicast packets, including Address Resolution Protocol (ARP) packets, to the workgroup bridge. You use the infrastructure-client configuration interface command to configure access points and bridges to treat workgroup bridges as infrastructure devices.

wesleyterry Mon, 01/19/2009 - 16:16

Is the AP controller based, or autonomous?

If autonomous you can just ignore this post....

If LWAPP, What is the value of your "session timeout" for the WLAN?

I had this problem with some thin clients doing RDP sessions, if the screen was idle, no packets were sent and therefor the connection went idle...

I know we now have a simple network monitor watching these clients (so they ping regularly), but I think the Session Timeout variable was partially to blame.

If there is any corelation between the session timeout length and the time it takes your clients to drop, then I'd say they are related.... But I may be confusing this with a different problem...

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode