Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

Can't access my server in my network

Discussion in 'General Wireless Discussion' started by fanch, Nov 30, 2012.

  1. fanch

    fanch New Around Here

    Nov 30, 2012

    I have the following new configuration:
    In my cellar I have a router Netgear WNR3500. To it is connected, a Windows Home Server and another router Netgear R6200. This second router is in the attic and is my main wifi access in the house.
    I can't get access to the Home Server from the second router. It is just not seen when I map the network as seen by the second router. As a result, I cant use the server if I do not connect to the first network.
    Could someone help me out?


  2. jdabbs

    jdabbs Super Moderator

    May 28, 2008
    Probably NAT, or overlapping subnets. On whichever device is not connected to your modem:
    • change the management IP to something unlikely to conflict with other devices ( would be ok with the default settings on both routers)
    • turn off DHCP on that device
    • connect the uplink to a LAN port (not WAN)
    • have devices behind that router obtain a new IP lease, rebooting will usually do it (devices with a static IP may need to be reconfigured)
    This will put your devices on the same network segment so they can communicate with each other.
  3. stevech

    stevech Part of the Furniture

    Mar 13, 2010
    San Diego
    Second router: Don't use the WAN port. Configure it as an Access Point (see FAQ on that there).
  4. sfx2000

    sfx2000 Part of the Furniture

    Aug 11, 2011
    San Diego, CA
    the comment about having multiple DHCP servers is very valid - you might have accidentally created two non-routable subnets...

    If network a is and network b is - devices on both subnets can see the internet, but they won't see each other...

    Ideally, you should only have a single DHCP server - on the primary router - the secondary should not have a DHCP server.

    There's a good how-to on the primary site that deals with the specifics
  5. tipstir

    tipstir Very Senior Member

    Aug 16, 2008
    South Florida
    Second router should have a static IP address and not be using DHCP that features should be disabled along with the NAT, SFI or any firewall on it. Let the main Router do all of that management.

Share This Page