Does anyone know what would cause the wireless to stop working? I had to power down the device to get the wirless to work again.

Thanks!!!

can you state when does this occur?
and what do you see in the logs?

It has only happened once unfortunately. When I checked the logs the time it had begun had already scrolled off. I did not save the logs either.

I do remember that no wireless connections were shown.

Kbr.. quick question.. are you using WPA, and do you have the ZA100 set to AES/TKIP, Auto or what?... I found that if its set to Auto, wierd connection problems seem to happen...I found it helped if you locked it to TKIP (if you have a device that doesnt support AES) in range of the network..
Otherwise iv seen my Za100 get deaf for no apparant reason and it really doesnt show in the logs....

Hope that helps some

Thanks for answering. WPA and I already had it set to TKIP (after more or less having the same experiences that you did) and not auto.

I suspect there may be a software bug that shuts down or corrupts the wireless. Perhaps the wireless devices are not being recognized.

I do have the wired and wireless networks bridged and the wired network was fine.

The next time it happens I intend to get out netstumbler and see if it is actually broadcasting.

Happened to me *again* today with the beta firmware... Basically the remote device loses its connection till i reboot the Za100 *and* sometimes the device, but usually just the ZA100 will do it... Seems to happen after 7 days of light wireless use for me.. How about you KBR...
I too have the wired and wireless networks bridged

quote:

Originally posted by bugeek:
Happened to me *again* today with the beta firmware... Basically the remote device loses its connection till i reboot the Za100 *and* sometimes the device, but usually just the ZA100 will do it... Seems to happen after 7 days of light wireless use for me.. How about you KBR...
I too have the wired and wireless networks bridged

I have not had a repeat of this problem. I am currently running 7.0.47x firmware. It appears pretty stable.

quote:

Originally posted by KBR:

quote:

Originally posted by bugeek:
Happened to me *again* today with the beta firmware... Basically the remote device loses its connection till i reboot the Za100 *and* sometimes the device, but usually just the ZA100 will do it... Seems to happen after 7 days of light wireless use for me.. How about you KBR...
I too have the wired and wireless networks bridged

I have not had a repeat of this problem. I am currently running 7.0.47x firmware. It appears pretty stable.

It just happened again. The Z100G had been operating for more than 2 weeks since the last reboot. Rebooting the computer did not help. There was nothing in the event log to show taht anything was wrong and the wireless computers seemed to be receiving their keys. However they were not recognized as even being attached to the Z100G - not even shown on the list of network devices.

The wireless computers do not appear to be getting an IP address. Since the network connection problem happened after the computer got its IP address, it does not appear to be a DHCP problem.

Funny im seeing the same thing..
Im curious.. what chipset is in the devices affected when it acts up (that you know of)
Two weeks seems to be the magic mark now..

All laptops are Dells, and the one that was on-line when this happened has a Broadcom wireless card and is running Vista Business. The other newer laptops probably have a Broadcom wireless card as well and are running XP (Pro & home). A really old Laptop (XP) has a Linksys PC card, but has not been on line when this happened.

A repeating time limit suggests a few things. Some kind of check that shuts off the wireless when a limit is reached or a memory leak.

The last time this happened a Laptop with XP was on-line and was affected the same way the Vista computer was. So it does not seem to be OS related.

Ding Ding
I just had it happen to me.. did the log appear something like this?
23045 17Sep2007 21:47:00 WLAN client: 00:13:02:84:BC:D2, received group key (TKIP) from wlan network
23044 17Sep2007 21:47:00 WLAN client: 00:13:02:84:BC:D2, associated to wlan network
23043 17Sep2007 21:46:01 WLAN client: 00:13:02:84:BC:D2, received group key (TKIP) from wlan network
23042 17Sep2007 21:46:01 WLAN client: 00:13:02:84:BC:D2, authorized to wlan network using WPA2 (TKIP)
23041 17Sep2007 21:46:01 WLAN client: 00:13:02:84:BC:D2, associated to wlan network
23040 17Sep2007 21:44:54 WLAN client: 00:13:02:84:bc:d2, disconnected from wlan network. Initiator: client. Reason: Unspecified
23039 17Sep2007 21:44:54 WLAN client: 00:13:02:84:BC:D2, associated to wlan network
23038 17Sep2007 21:43:47 WLAN client: 00:13:02:84:bc:d2, disconnected from wlan network. Initiator: client. Reason: Unspecified
23037 17Sep2007 21:43:47 WLAN client: 00:13:02:84:BC:D2, associated to wlan network
23036 17Sep2007 21:41:36 WLAN client: 00:13:02:84:bc:d2, disconnected from wlan network. Initiator: AP. Reason: 4-Way Handshake timeout
23035 17Sep2007 21:41:36 WLAN client: 00:13:02:84:BC:D2, authentication timed out (4-way) on wlan network
23034 17Sep2007 21:41:33 WLAN client: 00:13:02:84:BC:D2, associated to wlan network
23033 17Sep2007 21:41:03 User admin logged in (Source IP: 192.168.10.127)
23032 17Sep2007 21:40:25 WLAN client: 00:13:02:84:bc:d2, disconnected from wlan network. Initiator: AP. Reason: 4-Way Handshake timeout
23031 17Sep2007 21:40:25 WLAN client: 00:13:02:84:BC:D2, authentication timed out (4-way) on wlan network
23030 17Sep2007 21:40:24 UDP 90.101.202.24 [Policy rule] 30565 70.19.249.73 (ZoneAlarm Z100G) 1026
23029 17Sep2007 21:40:21 WLAN client: 00:13:02:84:BC:D2, associated to wlan network
23028 17Sep2007 21:40:17 WLAN client: 00:13:02:84:bc:d2, disconnected from wlan network. Initiator: AP. Reason: 4-Way Handshake timeout
23027 17Sep2007 21:40:16 WLAN client: 00:13:02:84:BC:D2, authentication timed out (4-way) on wlan network
23026 17Sep2007 21:40:13 WLAN client: 00:13:02:84:BC:D2, associated to wlan network
23025 17Sep2007 21:40:08 WLAN client: 00:13:02:84:BC:D2, deauthorized from wlan network
23024 17Sep2007 21:40:08 WLAN client: 00:13:02:84:bc:d2, disconnected from wlan network. Initiator: client. Reason: Unspecified
23023 17Sep2007 21:40:00 WLAN client: 00:13:02:84:BC:D2, received group key (TKIP) from wlan network
23022 17Sep2007 21:39:58 WLAN client: 00:13:02:84:BC:D2, authorized to wlan network using WPA2 (TKIP)
23021 17Sep2007 21:39:58 WLAN client: 00:13:02:84:BC:D2, associated to wlan network
23020 17Sep2007 21:39:43 WLAN client: 00:13:02:84:bc:d2, disconnected from wlan network. Initiator: AP. Reason: 4-Way Handshake timeout
23019 17Sep2007 21:39:43 WLAN client: 00:13:02:84:BC:D2, authentication timed out (4-way) on wlan network
23018 17Sep2007 21:39:40 WLAN client: 00:13:02:84:BC:D2, associated to wlan network
23017 17Sep2007 21:39:11 WLAN client: 00:13:02:84:BC:D2, received group key (TKIP) from wlan network
23016 17Sep2007 21:32:25 NTP updated time by 1 seconds
23015 17Sep2007 21:30:05 WLAN client: 00:13:02:84:BC:D2, received group key (TKIP) from wlan network
23014 17Sep2007 21:30:05 WLAN client: 00:13:02:84:BC:D2, authorized to wlan network using WPA2 (TKIP)
23013 17Sep2007 21:30:05 WLAN client: 00:13:02:84:BC:D2, associated to wlan network

It may have looked like that during a previous event, but with the latest event the event log did not seem out of the ordinary. The wireless PC was not listed though which was about the only thing that was out of the ordinary.

Heh KBR. dont know what to tell you but I do think theres something not quite right with the wireless.. Its been a bit of a "problem area" for me.. Forcing TKIP helped a lot but iv still had some problems keeping a connection, or losing the connection and not being able to get it back, but usually its with intel chipsets that don't like to play well....

quote:

Originally posted by bugeek:
Happened to me *again* today with the beta firmware... Basically the remote device loses its connection till i reboot the Za100 *and* sometimes the device, but usually just the ZA100 will do it... Seems to happen after 7 days of light wireless use for me.. How about you KBR...
I too have the wired and wireless networks bridged

How do you bridge the wired and wireless networks? I can't figure out how to get the wireless users to access the WAN port (Internet). I was also wondering why I can't put the wireless on the same subnet as the LAN IP. It won't let me do that and says the "address range overlaps" or something.

Thanks in advance for your help.