Business Community > Controllers > OC300 unavailable after changing IP address
< Controllers

OC300 unavailable after changing IP address

OC300 unavailable after changing IP address

OC300 unavailable after changing IP address
OC300 unavailable after changing IP address
Ayer
Model: OC300  
Hardware Version:
Firmware Version: 1.29.7

I'm adding a subnet to my system to hold all the network hardware (router, switches, APs, Omada Controller).

When I changed the controller's IP address, I forgot that I have a DHCP reservation for it, and instead, I changed it on the device.

After rebooting, the controller is offline. I get a timeout error when browsing to any of the IP addresses (the old IP address, the new IP address, or the fallback IP address).

I have used the recovery mode to install the same firmware.

 

Is a factory reset my only option? I don't want to do this as I don't have a recent configuration backup.

 

Thanks for your assistance!

  0      
 
  0      
 
#1
Options
4 Reply
Re:OC300 unavailable after changing IP address
Hace 15 horas

Hi @Wayne110,

 

If you have physical access, you should be able to directly attach a host to the controller to access it.  Just manually set the hosts interface to a unique address in the same subnet that the controller is using.

  0  
  0  
#2
Options
Re:OC300 unavailable after changing IP address
Hace 9 horas

  @D-C 

I should be able to, but I can't. When connecting directly to Port 2 on the OC300, I cannot reach it at the old address, the new address, or the fallback address.

I've tried using NMAP to see if I can find it, but it doesn't show up.

 

Since the router is being controlled by the OC300, I can't log into that either.

  0  
  0  
#3
Options
Re:OC300 unavailable after changing IP address
Hace 9 horas

@Wayne110, you may need to unplug the cable from port 1 and power cycle it to force it to start up with the fallback IP. 

  0  
  0  
#4
Options
Re:OC300 unavailable after changing IP address
Hace 8 horas - last edited Hace 8 horas

  @Wayne110 

 

I have never tried this but I read on the internet (the link appears below) that you might be able to determine the controller's IP address by connecting a PC directly to the controller and running Wireshark.  Filter the arp packets and they may give you a clue.  It's odd that neither the old nor the new IP addresses respond.  It almost sounds like a typo error when you entered the new address.

 

Link:  support dot.wheatstone dot com/portal/en/kb/articles/using-wireshark-to-find-an-unknown-ip-address

 

 

 

1x ER7406 1x OC300 4x SG2008 1x EAP610 3x EAP650-Desktop 1x EAP772-Outdoor
  0  
  0  
#5
Options

Information

Helpful: 0

Views: 63

Replies: 4

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.