ETCPad "WiFi Connection Failure"

Sounds like it might be a IP address problem...

Have you tried connecting your ETCPad with a dynamic IP generated by the DHCP?

Check all of your devices and subnet masking, make sure each device can talk to each other.

(If any of those things confused you, watch this and then check again.)

I switched it to DHCP, instead of static IP, but it's still not working. All other devices on the network seem to be working normally. I still cannot get the ETCPad to connect to the network.

What network settings did your IT team give you?

Are you working with a wireless router or a wireless access point?

When you switch your ETCpad to DHCP, what address does it receive?

What is the IP/Subenet mask of your console you'll eventually want to connect to?

Static IP settings from IT are as follows:
IP - 172.16.23.51      Subnet Mask -  255.255.255.0 (Prefix length - 24)     Gateway - 172.16.23.1         DNS - 172.16.23.1

We are working with a wireless access point.

When I switch it to DHCP, the ETCPad displays "WiFi Connection Error"

IP and subnet of the console are 172.16.23.5 and 255.255.255.0, respectively.

Does the WiFi Connection Error  message have any additional information associated with it? (e.g.: "This network doesn't have internet access" or similar)

Do you know if your IT department has a DHCP service running on the network? Also, have they enabled any filtering or authentication catches (like a terms of service page that you have to agree to when connecting)?

There is no additional information with the WiFi Connection Error message. I don't know about the DHCP service, but I can say with some degree of certainty that there is no ToS/sign-in page, at least none that has appeared on any other devices.

Quick update to let everyone know that the problem has been solved. As it turns out, even with the static IP settings, the trick was to turn on DHCP service from the primary console. Interestingly enough, that one little checkbox also solved another problem we'd been having in which OSC wouldn't work through the Wi-Fi.