GS108PEv3 and GS105PE work but not reachable

---

rsworden wrote:

 AT&T Pace router -- IQrouter -- GS108PEv3 -- GS105PE - access points

 

Both GS devices are brand new. They work correctly, essentially plug-n-play out of the box. Devices wired to the 108 work fine. The 108 powers the 105 fine. Devices wired to the 105, and WiFi devices on the access points on the 105 work fine.

 

The IP addresses for both devices are visible in the IQrouter's listing but no hostname is associated.

---

This does read like both switches DHCP client are working and get an IP config from the DHCP server on the router. A hostname is not "associated" - a DHCP client does not have to provide a hostname with the request, so the hostname can remain empty. Nothing wrong to that point 

rsworden wrote:

 The 108 can't be pinged, no matter where my Mac is plugged in. "request timeout for icmp_seq" even when plugged directly into it.

 

The 105 can be pinged.

Potentially something wrong or broken on the 108. I would suggest to reset (restet button) and bring it up with jut a Mac or Windows system connected (without any other connection to the router or other systems). More below.

rsworden wrote:

Neither device will provide an admin page at https://ipaddress.

This switch class/models don't support https - use http on port 80. 

rsworden wrote:

I installed the ProSAFE utility in Windows, and it cannot see any switches.

There is a nice Netgear Switch Discovery Tool available for both Windows and macOS - perfectly sufficient for the pure discovery (and much less intrusive than the ProSafe Plus Utility with the network capture driver). 

rsworden wrote:

I plugged my Mac directly into the 108, did factory reset, tried static IP on my mac and tried the default .239 address. Cannot ping or https.

If you expect the router fall-back to it's default IP address, you must run it without any connection ie. to the router with the DHCP server. Disconnect all network cables, just keep a link to one computer (Mac or Win does not matter - except of that we would have the ProSafe Plus Utility available on Windows).

Both Windows and macOS systems will auto-configure ZeroConfig addresses on the network interface if there is no DHCP server resp. no fixed network config. Therefore, you need to manually apply a fixed (or alternate) network config into the 192.168.0.0/24 255.255.255.0 network - just use unique addresses (not .239).  

Now you can try to ping the 192.168.0.239, discover it, or use a Web browser and call http://192.168.0.239/.