WRV200 Static routing question

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by ErnieD, Jun 7, 2010.

  1. ErnieD

    ErnieD Guest

    Hello All,

    Newbie here on the board could use your help!

    I have walked into a new job where the business has 4 sites each connected via VPN over these WRV200 units (from what I have read and researched here apparently I am in for a challenge!). Anyways, there are 3 remote sites and 1 central office, all the devices are in gateway mode and use static IPs, all are on various fw versions (I am going to be updating all shortly to v1.0.39) to hopefully gain some consistency and remedy the netbios sharing problems we are seeing. My primary concern right now is that none of the remote sites can see each other or share data however all can see the central office. I figured I could just go into the routers and set up static routes to each remote location but I am not able to do so...I keep getting a "gateway address is IP conflict" error message? What am I doing wrong? Here's some info:

    Central Office =
    Remote A =
    Remote B =
    Remote C =

    All can ping the Central office
    None of the remotes can ping each other
    When I tracert a remote office from another I get directed out the internet GW (which of course fails)
    When I try to add a static route for the remotes in any of the routers I am not allowed...so how should I edit the routing table to keep subnet traffic local???? Do I need a dedicated router at each site? I was hoping to stay away from this option as (of course) $$ is tight!

    Thanks in advance and sorry if this is a stupid question...been some time since I was responsible for a network and coming into one that is half-a$$ed is even worse!

  2. DocLarge

    DocLarge Super Moderator Staff Member Member

    It sounds like you have a "hub-and-spoke" configuration. Have you tried putting static routes for each remote office on the central router? Also, try enabling "RIP" on each router as well because it sounds like a routing protocol isn't enabled, thus "disallowing" the separate networks to see each other.

    I'm a little rusty but this is what it appears to be at first glance (give it a shot).

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice