Conduit unreachable 192.168.2.1
- This topic has 3 replies, 2 voices, and was last updated 7 years ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: AEP Model › Conduit unreachable 192.168.2.1
Hi. I have a conduit mounted on the roof on the mast, there is no way I can get to it, only to the Ethernet cable that comes down to the Ethernet switch.
For some reason I can’t reach the gateway. I plugged in my laptop, didn’t get an IP, and wasn’t able to ping or open 192.168.2.1. Laptop is set to automatic IP.
The gateway has a static IP assigned. 192.168.1.28
DHCP is disabled.
Everything was working great until today.
Hi Pascal
If the Conduit IP Address is static at 192.168.1.28 and DHCP is off,
I would recommend that you statically configure the IP Address on your
laptop NIC card to 192.168.1.111 and see if you can web into it at
192.168.1.28 or Ping it.
If it is not responding, is it possible it lost power?
Do you run a power cable up the mast to power it?
-Best Regards
Hello Steve. I just tried this on the indoor model and this trick worked. Let’s hope the same works on the other one too, I will check soon. The other gateway receives power over Ethernet btw.
Thanks!
Hi Steve. Your suggestion totally helped. We were dealing with an unrelated network issue that triggered everything and which has now been fixed.
Not knowing how to get access to the gateway once a static IP was assigned was however a problem which you solved.
The gateway had a static IP of 192.168.1.28 with DHCP turned off.
On my laptop that I connected with the gateway I manually configured the Ethernet like this:
IP: 192.168.1.111
Net Mask: 255.255.255.0
I was then able to access the web interface at 192.168.1.28 and make changes.
Everything is back to normal now, thanks again!