NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PharmlyDoc
Jan 02, 2021Tutor
Connecting to GS728TPv2 home network with CAX80 and EAX80?
I just setup the GS728TPv2 in my basement. It's on the opposite side of where my Netgear CAX80 cable modem/WiFi-6 router is located so I ran a cat8 cable to it. I have smart phones and tablets throug...
- Jan 05, 2021
Something very basic must be wrong between the GS switch and the CAX router. Either a basic Ethernet link issue, poor wiring, poor cabling, or ports configured to another purpose.
What happens when connecting the Mac USB-Ethernet port to the port/cable/link intended for the switch connection - locally on the CAX, remote near to the switch?
PharmlyDoc
Jan 04, 2021Tutor
Thank you for responding. I reset the switch to factory defaults. The firmware is uptodate. I set the IP address to static as 192.168.1.189 , the subnet mask as 255.255.255.0 . But what about the default gateway? Right now the default gateway is 192.168.1.1 ,which is the IP for my CAX80. Is this correct?
I am able to access the user interface of the switch if I (1) connect my laptop directly to the switch, (2) turn off the laptop's WiFi, and (3) set the IP address of the lan port for laptop to the 192.168.1.xxx range . Once I change the lan port on the laptop back to configure IPv4 using DHCP the connection to the switch GUI is lost. I am also unable to access the internet on my laptop when connected to the switch via an ethernet cable. Do I need to configure the routing settings for the switch?
I also went into the Nighthawk interface for the CAX80 and reserved 192.168.1.189 for the corresponding MAC address of the switch, but that doesn't seem to have helped.
Here are the ping results after setting the configuration of my laptop's IPv4 back to DHCP:
Computer ~ % ping 192.168.1.189 PING 192.168.1.189 (192.168.1.189): 56 data bytes ping: sendto: No route to host ping: sendto: No route to host Request timeout for icmp_seq 0 ping: sendto: No route to host ^C --- 192.168.1.189 ping statistics --- 15 packets transmitted, 0 packets received, 100.0% packet loss
CAX80 CableModem/Router_ReserveIPGS728TPv2_RoutingGS728TPv2_IP_Configuration
schumaku
Jan 04, 2021Guru - Experienced User
PharmlyDoc wrote:Here are the ping results after setting the configuration of my laptop's IPv4 back to DHCP:
Computer ~ % ping 192.168.1.189 PING 192.168.1.189 (192.168.1.189): 56 data bytes ping: sendto: No route to host ping: sendto: No route to host Request timeout for icmp_seq 0 ping: sendto: No route to host ^C --- 192.168.1.189 ping statistics --- 15 packets transmitted, 0 packets received, 100.0% packet loss
This looks wrong to me. If the switch would not be reachable on the LAN, the response would simply timeout, but not result in a "no route to host" message. "No route to host" says this: When the destination of the ICMP message is not on the local direct connected subnet, it will be forwarded to the system default gateway to handle it. If there is no default gateway, or the gateway has no information in its routing table to forward the packets, you will see "no route to host".
- PharmlyDocJan 05, 2021Tutor
I think I inserted the wrong terminal code for pinging the switch.
Please see inserted images which are screenshots from my Macbook Air (MBA) connected via ethernet cable to the switch. The first screenshot is of sending a ping to the switch's IP address when the ethernet cable is hooked up and when the WiFi adaptor is turned on - in which case the WiFi normally takes precedence. Ping-to-switch_with_WiFi_on
As expected, the ping does not work when the MBA is connected to the switch via ethernet cable with the WiFi turned off, and with the LAN port IP is set to DHCP. (self-assigned IP address is 169.254.222.54) MBA ping to switch fails with this MBA network/IP configuration
Setting the IP configuration on the MBA from DHCP to "Manually" - I chose "192.168.1.251" , results in the MBA be able to ping the switch (MBA is directly connected to switch via ethernet cable). MBA ping to switch successful when manually setting the MBA's IP address to a value in the 192.168.1.xxx range
My question now is how do I get my internet signal to pass through the switch and to computers connected to the switch? – What should the configuration be for the routing tab in the GS728TPv2 GUI?
Also, how should I configure the switch settings so that I can access it's GUI from my laptop connected via WiFi to my CAX80 or EAX80? If that makes sense.
Thank you.
- schumakuJan 05, 2021Guru - Experienced User
Something very basic must be wrong between the GS switch and the CAX router. Either a basic Ethernet link issue, poor wiring, poor cabling, or ports configured to another purpose.
What happens when connecting the Mac USB-Ethernet port to the port/cable/link intended for the switch connection - locally on the CAX, remote near to the switch?
- PharmlyDocJan 05, 2021Tutor
I don't believe the port on the CAX80 (that connects to the switch via a CAT8 cable) is the issue. Reason being is because right now I am on my Macbook Pro which is wirelessly connected to the EAX80 (with my network devices setup as illustrated in my initial post), and I ran an app called LanScan. Upon starting the scan, all the devices on the network populate on the list almost immediately except the switch. But - after about 1 minute the IP address and correct MAC address for the switch populate on the list as well.
In other words, the LanScan app running on my MBP is able to pickup the switch, although with a delay, in which my MBP is wirelessly connected to my wifi-extender --> extender wirelessly connected to CAX80 --> CAX80 connected via cat8 cable to switch.
So why is it that the user interface for the CAX80 does not have the switch listed as a connected device? This makes me think I don't have the routing settings correctly configured in the switch's GUI?
And check this out, I went into the terminal on my MBP, still connected via WiFi, and pinged 192.168.1.189, and the switch pinged back 64 bytes and then the request timed out for 73 pings, then 64 bytes for pings 74-76, then timed out for pings 77-156...
Around ping 157 I typed 192.168.1.189 into my webbrowser on my MBP, and the pings were successful for a bit longer - I then had to allow my browser to trust the address...request timed out from pings 170 - 226...after trusting the Netgear certificate I refreshed the webbrowser around ping 258 and then the pings are successful off and on. The login screen for the switch user interface never populated in the webbrowser.
I terminated the terminal request after ping 405. Please see the attached pdf file.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!