How to access router with DHCP server disabled?


Recommended Posts

I daisy chained two routers by enabling RIP on the first router and disable DHCP server on the second rounter while giving it a LAN ip outside of first router's DHCP pool.

However, after I disabled 2nd router's DHCP server, I don't know how to get back to its login page again. I tried connecting to the LAN ip I gave to the 2nd router, but I hit a dead end with no page found.

Both routers are Netgear. One is RP614, the other one is MR814.

Any help is appreciated :cool:

Huh? If your putting the 2nd router on the first routers network "while giving it a LAN ip outside of first router's DHCP pool. " Why would you turn on RIP? Did you turn on RIP on the first router? What routing information do you think you need to pass between these 2 routers that seem to be on the same network segment?

Reset the router to factory defaults if your having an issue connecting to its interface. What IP address did your machine have when you tried to connect to the 2nd routers interface? Where they even on the same segment?

Curious what IP address did you put on the 2nd routers WAN interface.. I would assume since you felt you needed Routing Information to be passed between these routers -- you would be routing.. and therefore one network connected to the WAN port, another on the LANs

Disconnect the 2nd router from everything but your machine.. then put your machine on the same segment as the routers LAN IP you gave.. try to connect to it then.

Dude are you wanting to route between segments on your network -- or are you just tying to create a access point out of your MR814? You do not need to turn on RIP for that.. and are you plugging the 2nd router into the first using one of its LAN ports..

Here is a guide on using a wireless router as an access point;

http://www.dslwebserver.com/main/wireless-...cess-point.html

BudMan thx for the feedback. I already did what they said in the guide and the network was running fine. The only problem was that I couldn't access the 2nd router's login page. Later I found that I didn't assign an ip to the 2nd router in the same range as the rest of my network. The mistake I made was my network was running on 192.168.0.x, and I set the 2nd router to be 192.168.1.1, which is outside .0.x. After I fixed the ip to 192.168.0.254, I am able to login to the 2nd router.

Thanks again.

So you did just want an access point ;) I couldn't figure why in the world you would turn on RIP -- when you said you put the second routers IP into your orig address space??

Glad you got it working.

  iczman said:

I do have RIP enabled on my 1st router. I don't have to do that for my configuration to work?

NO -- where did you get the idea that you need RIP??

The Routing Information Protocol, or RIP

RIP sends routing-update messages at regular intervals and when the network topology changes. When a router receives a routing update that includes changes to an entry, it updates its routing table to reflect the new route. http://www.cisco.com/univercd/cc/td/doc/ci...ito_doc/rip.htm

http://en.wikipedia.org/wiki/Routing_Information_Protocol

RIP is used to dynamically adapt to changes in network connections, you have 1 segment.. what routing info do you think you need to update. you only have 1 route.. ie your first router.. You don't even have any other routers on the network? You have an access point, and hosts. Who exactly do you think your sending Routing Updates too?

Even if you were using your 2nd router as a true router, and had a different segment.. RIP would not be needed.. since you would not be changing routes on the fly or adding new networks -- would you?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • This was cool back in the day when done properly - loved having icons of specific devices.
    • Microsoft quietly burying a massive Windows 7 hardware driver feature as Windows 11 kills it by Sayan Sen Last month Microsoft announced a big update for Windows hardware drivers. The company declared that it was killing Windows Device metadata and the Windows Metadata and Internet Services (WMIS). For those wondering what it is, device metadata, as the name suggests, is the collection of additional, user-facing information that an original equipment manufacturer (OEM) provides about a hardware device. The feature was introduced with Windows 7 and can include stuff like icons, logos, descriptive texts, among other things, that help the Windows UI display details about such devices in places like Task Manager or Device Manager. This was a huge deal back in the day when Windows 7 debuted. The company called the feature "Device Stage" and Microsoft described it as a "new visual interface" that essentially worked like a "multi-function version of Autoplay where it displays all the applications, services, and information related to your device." It is often considered synonymous with the Windows "Devices and Printers" Control Panel applet. Neowin did an in-depth overview of the feature when it first launched which you can find in its dedicated article here. The Windows OS was able to obtain the device experience metadata from the WMIS, but now that the feature is being deprecated, Microsoft has begun removing information about Device Stage from its official support documents. Neowin noticed while browsing that a support article regarding automatic Windows hardware drivers was updated for Windows 11 and 10 sometime last year after the release of Windows 11 24H2. Previously, this article was geared for Windows 7 and was much longer. It also contained information about Device Stage, which, as mentioned above, was a headlining feature on Windows 7. In the said article, the section "If Windows can't find information about your device in Device Stage" has been deleted. You can find the archived version of the support page here. Aside from shortening the amount of information on the page, Microsoft has also added some more details on it. The company has now tried to define what the Microsoft Basic Display Adapter is, how updating drivers through Device Manager works, as well as a thorough and detailed troubleshooting section for common hardware driver errors on Windows, including one for USB-C. You can find all the new details on the updated support page here on Microsoft's website.
    • Sounds creepy to say the least. Don't need nor want AI having access to my history. They're claiming it to be an "offline" model now, but how can we guarantee they don't go behind our backs and change that?
    • Exactly! Without those fundamentals you've mentioned, Democracy is literally just Demonstration of Crazy, nothing to be proud of in such system.
    • Still I see almost no ads in mobile Edge unlike Chrome. So their browser is much better at blocking ads than Chrome and it is a fact. It even blocks ads on YouTube and you can add simple custom block filters. Also, Edge still support manifest v2 on desktop, so I'll look for another browser when I start seeing ads again.
  • Recent Achievements

    • First Post
      viraltui earned a badge
      First Post
    • Reacting Well
      viraltui earned a badge
      Reacting Well
    • Week One Done
      LunaFerret earned a badge
      Week One Done
    • Week One Done
      Ricky Chan earned a badge
      Week One Done
    • Week One Done
      maimutza earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      481
    2. 2
      +FloatingFatMan
      264
    3. 3
      snowy owl
      238
    4. 4
      ATLien_0
      234
    5. 5
      Edouard
      176
  • Tell a friend

    Love Neowin? Tell a friend!