Re: Routing across internal subnets

We have a gre tunnel between this main site and the remote sites on our Cisco
routers in order to connect the separate subnets for the smaller remote
locations. Individual VPN's from each PC are not really feasible, and the
sites do not have a servers set up to do VPN's just the routers that do the
tunnel.

Our end goal is the following (for one location):

Remote Site - Cisco Router - Cisco Tunnel Endpoint (Remote) -
192.168.20.0 - 192.168.20.1 - 192.168.100.2 -

Cisco Tunnel Endpoint (Main Office) -Cisco Router - SBS Server (External
Nic) -
192.168.100.1 - 10.10.10.1 - 10.10.10.2 -

SBS Server (Internal Subnet)
192.168.0.0

In essence, that the external 192.168.20.0 subnet can communicate with the
192.168.0.0 Subnet.

Are thoughts are that we may need a 3rd NIC to do a static route (although
current configured static routes do not work), a Vlan in the 192.168.0.0
subnet on the Cisco Router, or possibly ISA.

Thanks again in advance.





"Larry Struckmeyer" wrote:

Hi James:

Other than not being able to ping the internal nic from the router, are you
having any other problems? Can you explain your desired end goal?

Larry

"James Brubaker" <James Brubaker@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:37DFBF55-63F9-455E-ACCC-AC9510F75728@xxxxxxxxxxxxxxxx
Here is my configuration, any help is greatly apreciated!!
SBS2003, Two NICS, Inside Private NIC is 192.168.0.1, Outside is
10.10.10.2.

Connected to a Cisco Router With Static IP of 10.10.10.1, Which is
connected
directly to the Internet via static IP.

SBS2003 is DHCP server for Internal Network (192.168.0.0) side, no
problems
with
Internet Access, no problems with VPN to SBS.

From the Cisco router (with the 10.10.10.1 address), we are unable to ping
the 192.168.0.0 side of the SBS2003. We have the router and the server
configured with RIP version 2, and the SBS2003 shows up on the router in
the
IP Route as connected.

In the SBS2003, A route to the Cisco router shows up when we do a 'show
neighbors' in RRAS.

We have tried to accomplish this by adding static routes on the SBS2003 in
RRAS using
route -p add 192.168.0.0 mask 255.255.255.0 10.10.10.1
route -p add 192.168.0.0 mask 255.255.255.0 10.10.10.2
route -p add 10.10.10.1 mask 255.255.255.0 192.168.0.0
route -p add 10.10.10.2 mask 255.255.255.0 192.168.0.0
but to no avail!!!

Any suggestions or help would be appreciated. We do not have ISA server
installed on the SBS2003 at this point.

Thanks in advance!



.

Relevant Pages

  • Re: 2 NIC SBS2003R2 LAN/WAN Firewall Router Connection Failure
    ... I changed the SBS external IP settings as you suggest. ... Clients and the SBS Server can reach the router. ... may be there are some rule deny the access from some IP addresses or subnet. ... |> Two Nics, a static IP address, ISA, router ...
    (microsoft.public.windows.server.sbs)
  • Re: Routing and RRAS Problem - Pleasehelp
    ... Traffic from your "internal" subnet can get ... out to the Internet by default routing, but the return traffic will fail. ... You need to add an extra route to the Linksys router so that it knows how to ...
    (microsoft.public.windows.server.networking)
  • Re: Running out of IP addresses
    ... In fact it is pretty hard to find a hardware LAN router these days. ... I think it worth planning a second subnet at this stage as I can see the existing scope running out, even with a 'full range' on the current subnet. ... I understand that I will need to introduce a DHCP server on the second subnet. ...
    (microsoft.public.windows.server.networking)
  • Re: ntpq no longer working -
    ... what it shows the router is addressing 70.41.189.188 at wildblue, ... Where I've used the term "gateway", throughout this email, I'm ... Internet Port ... The subnet mask is used against the IP address to determine what else is ...
    (Fedora)
  • Re: How to enable communication between Two different lans (subnets)/ domains 2003 server based? Ass
    ... You need a route on the Internet ... to forward traffic for the new subnet to the internal router. ... and get it working properly on its own subnet using its own DNS ...
    (microsoft.public.windows.server.networking)
Loading