Internet access issues between the IAP-103 & FVS336Gv2

First - a couple of questions 1 - how is the Aruba connected to the FVS and does it get it's address using DHCP? 2 - what DHCP lease duration are you running? 3 - are there any other devices in the network that do not connect via the Aruba - are these devices affected when the WiFi fails - if there are none, it might be worth the effort to temporarily connect a laptop directly to the FVS for troubleshooting purposes. If devices directly attached to the FVS do not lose their connection along with the wireless ones, that would suggest that the FVS is not the source of the problem. At a glance, the symptoms suggest that there is an intermittent connectivity issue between the FVS and the Aruba, or that either the FVS or the Aruba may be locking up, which is what led to my suggestion of connecting a device directly to the FVS. What's puzzling me is ... 1 - and I recognize this may simply be how the device reports the symptoms - is that in my experience failure of the DHCP server or loss of connectivity to it, should not prevent a wireless client from associating with an access point (AP) (or joining a WiFi network), they should associate with the AP but not get an ip address, which typically results in an APIPA address (169.254.x.x) 2 - if you can't join the network how can you tell what ip address the Aruba has, and if it is set for DHCP and unable to access the FVS, why is it not reporting an APIPA address?

For the Question:
1. the AP is connected the following way, As well the AP has a static IP address and the static IP is tagged under Vlan 1
AP > JGS516PE > FVS (AP is getting PoE from the JGS)

2. DHCP Lease time
Vlan 1 - 72hours (non guest office use only
Vlan 2 - 1hr guest WiFi
Vlan 3 - 1hr guest Wifi / Demo phone

3. when this happens all wired connections have no issue including the AP, I can still see and access AP from the wired side and WiFi side if on a client that already connected. As well any pre authorized and WiFi users with a current DHCP lease have no issues

Other questions:
1.A computer or a phone will not fully connect when this issues happens. But on the APs GUI I can see units connecting the AP. They will not get any kind of IP address and on the APs GUI it will be listed as 0.0.0.0

2. Aruba is assigned a static IP address

As well with firmware Version 4.3.1-18, the FVS has become VERY sluggish when navigating between menus.

also not to air out any dirty laundry, I need to kind of find an answer quickly. As my return period is coming up quickly, and either need to keep this unit or send it back.

This thread might be related.

http://forum1.netgear.com/showthread.php?t=90972

Nhellie26 wrote:
This thread might be related. http://forum1.netgear.com/showthread.php?t=90972

This is very related, I did infact try this from the link above and solved my issue. But sadly I lose the functionality of VLan which the routed stated it did, and I have to have this function to stay PCI compliance. So sadly I am going to have to return this product.

Have you called support and reported this? If this is a bug Netgear should do something about it. :rolleyes: