Re: Help with simple point-to-point setup, pls

On Apr 5, 4:43 am, "Ken" <kri...@xxxxxxxxxxx> wrote:
Hello,

I'm trying to set up a point to point connection over T-1 with the
goal that computers at the main office can access computers at the
remote office and vice versa. Also, computers at the remote office
will access the internet through the gateway of 192.168.12.1 at the
main office. On each side of the point-to-point circuit are Cisco
routers with default HDLC settings.

So far, from either network, I am able to ping to the far side of the
router on the other side but nowhere past that.

For example, from 192.168.15.20, I can reach 192.168.12.2 but not
192.168.12.1 (a sonicwall connected to the ISP's router).

Do you have any pointers for me? Following are the essential router
config as well as the results of a "sho ip route" on each router.

! *****************************
! ** For this router, FA 0/0 connects
! ** to the network of the main office lan.
! ** S 0/0/0 connects to a Point-to-point t-1
! ** connection (i.e Remote-Rtr)
! *****************************
hostname Main-Rtr
!
!
!
interface FastEthernet0/0
ip address 192.168.12.2 255.255.255.0
speed auto
full-duplex
no mop enabled
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
ip address 192.168.13.1 255.255.255.0
!
router ospf 1
log-adjacency-changes
network 192.168.0.0 0.0.255.255 area 1
!
ip classless
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0
!
no ip http server
!
!
control-plane
! ****************************
! ** end Main-Rtr
! ****************************

======================================
****************************
**** Remote-Rtr results for "sho ip route"
****************************

C 192.168.12.0/24 is directly connected, FastEthernet0/0
C 192.168.13.0/24 is directly connected, Serial0/0/0
O 192.168.15.0/24 [110/65] via 192.168.13.2, 00:44:25, Serial0/0/0
S* 0.0.0.0/0 is directly connected, FastEthernet0/0

======================================

! *****************************
! ** For this router, FA 0/0 connects
! ** to the network of the remote office lan.
! ** S 0/0/0 connects to a Point-to-point t-1
! ** connection (i.e Main-Rtr)
! *****************************
hostname Remote-Rtr
!
!
!
interface FastEthernet0/0
ip address 192.168.15.2 255.255.255.0
speed auto
full-duplex
no mop enabled
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
ip address 192.168.13.2 255.255.255.0
!
router ospf 1
log-adjacency-changes
network 192.168.0.0 0.0.255.255 area 1
!
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0/0/0
!
ip http server
!
dialer-list 1 protocol ip permit
!
control-plane

! ****************************
! ** end Remote-Rtr
! ****************************

=========================
****************************
** Remote-Rtr results for "sho ip route"
****************************

O 192.168.12.0/24 [110/65] via 192.168.13.1, 00:43:08, Serial0/0/0
C 192.168.13.0/24 is directly connected, Serial0/0/0
C 192.168.15.0/24 is directly connected, FastEthernet0/0
S* 0.0.0.0/0 is directly connected, Serial0/0/0

Hi,
Why are you using OSPF?
As I have undertood, you have two different local networks connected
to two different routers, and one of them is connected to the
internet.
All the routing you need is the following:
1. On the remote router:
ip route 0.0.0.0 0.0.0.0 Serial0
ip classless

2. On the main router:
ip route 192.168.15.0 255.255.255.0 Serial0
ip route 0.0.0.0 0.0.0.0 FastEthernet0

This is the clear way to do it. But if just wanna get it to work, you
can just do the following command on the main router:
ip route 0.0.0.0 0.0.0.0 FastEthernet0 150
This way you will give the default route an Administrative Distance
that is higher than the OSPF. I believe what happening with your pings
is that the reply sent from the main LAN to the remote LAN are using
the default route and loosing the way back to the remote router
because the default route has an AD that is lower than OSPF.
Please let me know how it goes.


Mohammed
http://www.RouterGeek.net

.

Relevant Pages

  • Re: Session terminated
    ... There is not as far as I know a site available to facilitate the connection, but you can still do it with an IP address. ... The IP Address is your PC, the Gateway is your router. ... All of the docs I have specifically state that XP Pro and XP home can use remote assistance. ... This link states that the Home versions and Pro versions cannot use RA between them, which means you can only have home assisting home, or pro to pro. ...
    (microsoft.public.windows.mediacenter)
  • RE: Requesting data from Microsoft Exchange Server.
    ... Exchange server settings page, please ensure input the correct server name ... connection failed. ... All of the remotes use the same model router with the same settings ... The router at the remote site was originally set at MTU 1500 ...
    (microsoft.public.exchange2000.clients)
  • Re: Port is not working, Now what?
    ... All RDC, by default, listens on port 3389. ... That is done in the router.. ... So what if ya got several remote systems that want to use RDC to remotely ... your dial up connection at your home is a major bottleneck. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop Web connection setup question
    ... The most severe problems arise from router preventing ... As for the web bas remote service i was under the impression that you ... > Make sure you test this over your local LAN from another PC first. ... >> is how do you setup Remote Desktop web connection? ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Urgent! New router and big disaster
    ... by CEICW for any type of connection other than full time broadband was ... exists - is completely transparent to the SBS. ... "local router with an IP address" is the setup that matches her network. ... between the server and my cable modem. ...
    (microsoft.public.windows.server.sbs)