ION Networking nightmare.

My first guess based upon it working with the aRFR and not with the PC Client is the PC Client is having issues with it's local firewall. If it is Windows 7 you may need to add a rule to allow EOS.exe through the firewall, run as administrator, or some combination thereof to get the client to work.

The other option may be the router is blocking the UDP traffic. A simpler topology would be to not use the WAN port at all, set either the router or the Ion, but NOT both, as the DHCP server. Change your subnet accordingly.

My first guess based upon it working with the aRFR and not with the PC Client is the PC Client is having issues with it's local firewall. If it is Windows 7 you may need to add a rule to allow EOS.exe through the firewall, run as administrator, or some combination thereof to get the client to work.

The other option may be the router is blocking the UDP traffic. A simpler topology would be to not use the WAN port at all, set either the router or the Ion, but NOT both, as the DHCP server. Change your subnet accordingly.

What we do at our school is the Ion is in the LAN Port setup as the DHCP. 

DHCP on the router is disabled and router set to just be an access point and thats it. We don't change router ip or anything.

When connecting to the console via irfr in our case. When we connect to the router on our IOS device we assign the device the ip address of 10.101.100.101+ and subnet as 255.255.0.0 this allows the ios device find the console. For every other user we use the same ip address but just change the last number to .102 and so on. 

Shorrock

I have run into this kind of situation before, especially with Android devices.  Here is how I have set up my AP.  All lan point DHCP server disabled on everything but the Ion.  This will allow hardline devices to receive IP's when hardline into the network.

Wan DHCP Server enabled on AP only and only on the WAN side(this is an advance setting on the AP.  Set the DHCP range on the Wan to 10.101.xxx.xxx.  As long as the client device can connect to the AP and receive an IP address from that device you should be good to go. 

P-

Thanks everyone.  What router model numbers are you using?  I'm starting to wonder if there's a problem with the way the NetGear works.

Thanks!

I just wanted to clear up some things from this thread on the setup of aRFR and iRFR.

There are two ways that we recommend here from the factory. We chose these two set-ups because they are relatively easy to do, and they also require less configuration on the router. These are to 1) connect the console/network to the WAN/Internet port on the router and 2) use the router as a Wireless Access Point (WAP).  There certainly are other methods to configure this system -- this is what we presently recommend.

Both of these methods require you to turn the DHCP server on the console. You can find this setting by exiting to the shell (Browser -> Exit), then choosing Settings. Finally, go to the network tab. There should be a section listing the Address Service or DHCP Service. This section should list a first address, number of addresses, and default gateway. The console defaults should be adequate. If you don't see these options, scroll further down in the shell to make sure you are looking at the right section. Press Accept, then allow the console to reboot.

Console Connected via WAN/Internet Port on Router

After turning on the DHCP server, connect the console's Ethernet port (or a port from your lighting network's switch) into the router's WAN (or Internet) port. 

Reboot the wireless router so that it obtains an address on its WAN port from the console.

By default, most routers will have a DHCP server enabled for their local ports. Keep this enabled. Any wireless device that connects will automatically obtain an IP address from the router, and information that is bound for the console will get passed through to the WAN port (on to the lighting network or direct to the console).

Finally, connect the aRFR/iRFR to the WAP. You should be able to continue by connecting or configuring the app to connect to the console (as outlined in the wiki article here: aRFR | iRFR).

Router configured as Wireless Access Point (WAP)

After turning on the DHCP server at the console, configure the router as a WAP using the router's configuration interface (usually a webpage). Configuring the router as a WAP eliminates most variables. Many of these have it as a quick setup option.

Once configured as a WAP, connect the console (or a port from your lighting network's switch) to the router via the WAN port (or Internet port).

Finally, connect the aRFR/iRFR to the WAP. The phone should obtain an IP address through the console. You should be able to continue by connecting or configuring the app to connect to the console (as outlined in the wiki article here: aRFR | iRFR)