I have an R6300 that I need to do a full reset on.
By full, I mean not just usernames and passwords (which has already been done), but settings as well. The regular full reset doesn't turn back on DHCP. Without the DHCP, it appears I cannot connect to the router itself. Tried both secure and unsecure HTTP protocols at 192.168.1.1 from multiple systems on my network, and it would not connect, wired or wireless.
DHCP is being done by my server, so I'd turned it off on the router.
How can I get the DHCP turned back on so I can change the remaining settings?
30 seconds on the reset while it's on, and with it off, hold the reset while turning it on.
Neither of these restores DHCP. I am still receiving DHCP from my server, not the router, on my wireless devices, and I cannot get the login page from the router itself, either from a wired connection or wireless.
My OP stated the same issues. I don't even have a method of finding out what firmware version is currently installed so I can try a newer version to see if that would work. But it's likely the firmware update would fail as well as there's no login page available.
Neither of these restores DHCP. I am still receiving DHCP from my server, not the router, on my wireless devices
Talk of your own server suggests that you have an atypical setup. You may have to delve a bit deeper into that.
The router is just a part of the network. It has to fit in with other stuff.
It might help if you provided more detail about your own network.
For example, what is your server and what modem/gateway sits in front of your router.
.... and I cannot get the login page from the router itself, either from a wired connection or wireless.
That is another clue suggesting that other things are getting in the way. That can be a sign that something else is trying to be a router alongside your R6300.
Be warned that the your decade old R6300 is pretty basic and ageing. Maybe you have bolted on stuff that it doesn't understand.
You started off asking about a "full reset". That is what people have tried to answer. My guess is that this is the least of your problems.
My network consists of a Netgear CM2000 cable modem followed by a TP-Link firewall router, to a Server 2012 box to the LAN. Typically the server provides DHCP. The R6300 is intended as a WAP only, on my network, hence disabling its DHCP.
Because I temporarily needed a plain router, the R6300 was removed from the main network and connected directly to the CM2000. The CM2000 is a single port cable modem, so a router is needed to provide IP addresses to anything connected to it if more than one item.
so, just CM2000 -> R6300 -> PC. With the full reset, there is still no DHCP.
While the R6300 may be old, it shouldn't be unable to turn DHCP back on once it's been turned off.
so, just CM2000 -> R6300 -> PC. With the full reset, there is still no DHCP.
We are beginning to see the full picture.
Are you resetting and restarting everything in the required order? This is important because the devices in the network take their cues from devices that are already there.
You can't just turn things on and off in a random order.
Be sure to restart your network in this sequence:
Turn off and unplug modem.
Turn off router and computers.
Plug in and turn on modem. Wait 2 minutes for it to connect.
Turn on the router and wait 2 minutes for it to connect.
Turn on computers and rest of network.
You may have done this already, but again this bit of detail isn't in your earlier messages.
While the R6300 may be old, it shouldn't be unable to turn DHCP back on once it's been turned off.
I threw that in because I suspected that something else might be involved. I was right. This was your first mention of the TP-Link firewall router and Server 2012 box.
