Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Cisco > Point to Point Connection Issues

Reply
Thread Tools

Point to Point Connection Issues

 
 
chsmith700@gmail.com
Guest
Posts: n/a
 
      10-15-2008
On Oct 15, 8:14*am, Trendkill <(E-Mail Removed)> wrote:
> On Oct 15, 9:09*am, Matthew Melbourne <(E-Mail Removed)>
> wrote:
>
>
>
>
>
> > In article
> > <(E-Mail Removed)>,
> > * *<(E-Mail Removed)> wrote:

>
> > > Hello,
> > > I am having a problem with a T1 Point to Point between two stores in
> > > two different cities. I have the connection from Royse City to Terrell
> > > working, but am unable to get from Terrell to Royse City. I am sure
> > > its something really stupid I am over looking. Here are my configs.

>
> > As others have said, your routing looks fine between the sites. However,
> > for the remote network 192.168.10.0/24 network to 'piggy back' off the
> > D107P router for Internet access, then there needs to be a static route on
> > the D-Link D107P router pointing to the remote network 192.168.10.0/24 via
> > 192.168.0.200.

>
> > Cheers,

>
> > Matt

>
> > --
> > Matthew Melbourne

>
> Well he also needs that route for the boxes on 192.168.0.0 to get to
> 10.0, because they most likely use 0.1 as their gateway, and not the
> Cisco router. *So even LAN to LAN would be broke without the route
> (although technically only broken one way).- Hide quoted text -
>
> - Show quoted text -


So in the Royse City, I need to first route 192.168.0.200 first, then
attempt to route 192.168.0.1 cause that is the direct flow? Then in
Dlink I need to have a route back to the .200 so that it can get back?
A dummy proof would def help..

Should I do a route on royse city cisco like so?

192.168.0.200 255.255.255.0 10.100.254.1
0.0.0.0.0 0.0.0.0 192.168.0.1

then in the Dlink assign a route back to 192.168.0.200
 
Reply With Quote
 
 
 
 
chsmith700@gmail.com
Guest
Posts: n/a
 
      10-15-2008
On Oct 15, 8:21*am, (E-Mail Removed) wrote:
> On Oct 15, 8:14*am, Trendkill <(E-Mail Removed)> wrote:
>
>
>
> > On Oct 15, 9:09*am, Matthew Melbourne <(E-Mail Removed)>
> > wrote:

>
> > > In article
> > > <(E-Mail Removed)>,
> > > * *<(E-Mail Removed)> wrote:

>
> > > > Hello,
> > > > I am having a problem with a T1 Point to Point between two stores in
> > > > two different cities. I have the connection from Royse City to Terrell
> > > > working, but am unable to get from Terrell to Royse City. I am sure
> > > > its something really stupid I am over looking. Here are my configs.

>
> > > As others have said, your routing looks fine between the sites. However,
> > > for the remote network 192.168.10.0/24 network to 'piggy back' off the
> > > D107P router for Internet access, then there needs to be a static route on
> > > the D-Link D107P router pointing to the remote network 192.168.10.0/24 via
> > > 192.168.0.200.

>
> > > Cheers,

>
> > > Matt

>
> > > --
> > > Matthew Melbourne

>
> > Well he also needs that route for the boxes on 192.168.0.0 to get to
> > 10.0, because they most likely use 0.1 as their gateway, and not the
> > Cisco router. *So even LAN to LAN would be broke without the route
> > (although technically only broken one way).- Hide quoted text -

>
> > - Show quoted text -

>
> So in the Royse City, I need to first route 192.168.0.200 first, then
> attempt to route 192.168.0.1 cause that is the direct flow? Then in
> Dlink I need to have a route back to the .200 so that it can get back?
> A dummy proof would def help..
>
> Should I do a route on royse city cisco like so?
>
> 192.168.0.200 255.255.255.0 10.100.254.1
> 0.0.0.0.0 0.0.0.0 192.168.0.1
>
> then in the Dlink assign a route back to 192.168.0.200


Correction, I mean the Terrell..to route to Royse City...or will it
see 192.168.0.1 without correctly first routing the cisco
 
Reply With Quote
 
 
 
 
Trendkill
Guest
Posts: n/a
 
      10-15-2008
On Oct 15, 9:21*am, (E-Mail Removed) wrote:
> On Oct 15, 8:14*am, Trendkill <(E-Mail Removed)> wrote:
>
>
>
> > On Oct 15, 9:09*am, Matthew Melbourne <(E-Mail Removed)>
> > wrote:

>
> > > In article
> > > <(E-Mail Removed)>,
> > > * *<(E-Mail Removed)> wrote:

>
> > > > Hello,
> > > > I am having a problem with a T1 Point to Point between two stores in
> > > > two different cities. I have the connection from Royse City to Terrell
> > > > working, but am unable to get from Terrell to Royse City. I am sure
> > > > its something really stupid I am over looking. Here are my configs.

>
> > > As others have said, your routing looks fine between the sites. However,
> > > for the remote network 192.168.10.0/24 network to 'piggy back' off the
> > > D107P router for Internet access, then there needs to be a static route on
> > > the D-Link D107P router pointing to the remote network 192.168.10.0/24 via
> > > 192.168.0.200.

>
> > > Cheers,

>
> > > Matt

>
> > > --
> > > Matthew Melbourne

>
> > Well he also needs that route for the boxes on 192.168.0.0 to get to
> > 10.0, because they most likely use 0.1 as their gateway, and not the
> > Cisco router. *So even LAN to LAN would be broke without the route
> > (although technically only broken one way).- Hide quoted text -

>
> > - Show quoted text -

>
> So in the Royse City, I need to first route 192.168.0.200 first, then
> attempt to route 192.168.0.1 cause that is the direct flow? Then in
> Dlink I need to have a route back to the .200 so that it can get back?
> A dummy proof would def help..
>
> Should I do a route on royse city cisco like so?
>
> 192.168.0.200 255.255.255.0 10.100.254.1
> 0.0.0.0.0 0.0.0.0 192.168.0.1
>
> then in the Dlink assign a route back to 192.168.0.200


Dlink - only knows about 192.168.0.0 and nothing else. Needs a route
that points to 192.168.10.0 via 192.168.0.200

Local Cisco - Only knows about 192.168.0.0 and the Serial link. Needs
a default route pointing to the DLINK, and a route to the far LAN
segment via the far side serial interface.

Remote Cisco - Only knows about 192.168.10.0 and the Serial Link.
Needs a single default route to the serial on the other router. This
will cover traffic to the internet and traffic to 192.168.0.0 since a
default route is all traffic.

This what you were looking for?
 
Reply With Quote
 
chsmith700@gmail.com
Guest
Posts: n/a
 
      10-15-2008
On Oct 15, 8:23*am, Trendkill <(E-Mail Removed)> wrote:
> On Oct 15, 9:21*am, (E-Mail Removed) wrote:
>
>
>
>
>
> > On Oct 15, 8:14*am, Trendkill <(E-Mail Removed)> wrote:

>
> > > On Oct 15, 9:09*am, Matthew Melbourne <(E-Mail Removed)>
> > > wrote:

>
> > > > In article
> > > > <(E-Mail Removed)>,
> > > > * *<(E-Mail Removed)> wrote:

>
> > > > > Hello,
> > > > > I am having a problem with a T1 Point to Point between two stores in
> > > > > two different cities. I have the connection from Royse City to Terrell
> > > > > working, but am unable to get from Terrell to Royse City. I am sure
> > > > > its something really stupid I am over looking. Here are my configs.

>
> > > > As others have said, your routing looks fine between the sites. However,
> > > > for the remote network 192.168.10.0/24 network to 'piggy back' off the
> > > > D107P router for Internet access, then there needs to be a static route on
> > > > the D-Link D107P router pointing to the remote network 192.168.10.0/24 via
> > > > 192.168.0.200.

>
> > > > Cheers,

>
> > > > Matt

>
> > > > --
> > > > Matthew Melbourne

>
> > > Well he also needs that route for the boxes on 192.168.0.0 to get to
> > > 10.0, because they most likely use 0.1 as their gateway, and not the
> > > Cisco router. *So even LAN to LAN would be broke without the route
> > > (although technically only broken one way).- Hide quoted text -

>
> > > - Show quoted text -

>
> > So in the Royse City, I need to first route 192.168.0.200 first, then
> > attempt to route 192.168.0.1 cause that is the direct flow? Then in
> > Dlink I need to have a route back to the .200 so that it can get back?
> > A dummy proof would def help..

>
> > Should I do a route on royse city cisco like so?

>
> > 192.168.0.200 255.255.255.0 10.100.254.1
> > 0.0.0.0.0 0.0.0.0 192.168.0.1

>
> > then in the Dlink assign a route back to 192.168.0.200

>
> Dlink - only knows about 192.168.0.0 and nothing else. *Needs a route
> that points to 192.168.10.0 via 192.168.0.200
>
> Local Cisco - Only knows about 192.168.0.0 and the Serial link. *Needs
> a default route pointing to the DLINK, and a route to the far LAN
> segment via the far side serial interface.
>
> Remote Cisco - Only knows about 192.168.10.0 and the Serial Link.
> Needs a single default route to the serial on the other router. *This
> will cover traffic to the internet and traffic to 192.168.0.0 since a
> default route is all traffic.
>
> This what you were looking for?- Hide quoted text -
>
> - Show quoted text -


I must be retarded, is it possible to configure each router here to
make it work? And give me the exact configurations yall are looking
like it needs to be? Ive tried but its apparent I am doing something
wrong. I have the DLINK routing in, I can get from Terrell all the way
to Royse City DLINK, but nothing after that.
 
Reply With Quote
 
Trendkill
Guest
Posts: n/a
 
      10-15-2008
On Oct 15, 10:12*am, (E-Mail Removed) wrote:
> On Oct 15, 8:23*am, Trendkill <(E-Mail Removed)> wrote:
>
>
>
> > On Oct 15, 9:21*am, (E-Mail Removed) wrote:

>
> > > On Oct 15, 8:14*am, Trendkill <(E-Mail Removed)> wrote:

>
> > > > On Oct 15, 9:09*am, Matthew Melbourne <(E-Mail Removed)>
> > > > wrote:

>
> > > > > In article
> > > > > <(E-Mail Removed)>,
> > > > > * *<(E-Mail Removed)> wrote:

>
> > > > > > Hello,
> > > > > > I am having a problem with a T1 Point to Point between two stores in
> > > > > > two different cities. I have the connection from Royse City to Terrell
> > > > > > working, but am unable to get from Terrell to Royse City. I am sure
> > > > > > its something really stupid I am over looking. Here are my configs.

>
> > > > > As others have said, your routing looks fine between the sites. However,
> > > > > for the remote network 192.168.10.0/24 network to 'piggy back' off the
> > > > > D107P router for Internet access, then there needs to be a static route on
> > > > > the D-Link D107P router pointing to the remote network 192.168.10..0/24 via
> > > > > 192.168.0.200.

>
> > > > > Cheers,

>
> > > > > Matt

>
> > > > > --
> > > > > Matthew Melbourne

>
> > > > Well he also needs that route for the boxes on 192.168.0.0 to get to
> > > > 10.0, because they most likely use 0.1 as their gateway, and not the
> > > > Cisco router. *So even LAN to LAN would be broke without the route
> > > > (although technically only broken one way).- Hide quoted text -

>
> > > > - Show quoted text -

>
> > > So in the Royse City, I need to first route 192.168.0.200 first, then
> > > attempt to route 192.168.0.1 cause that is the direct flow? Then in
> > > Dlink I need to have a route back to the .200 so that it can get back?
> > > A dummy proof would def help..

>
> > > Should I do a route on royse city cisco like so?

>
> > > 192.168.0.200 255.255.255.0 10.100.254.1
> > > 0.0.0.0.0 0.0.0.0 192.168.0.1

>
> > > then in the Dlink assign a route back to 192.168.0.200

>
> > Dlink - only knows about 192.168.0.0 and nothing else. *Needs a route
> > that points to 192.168.10.0 via 192.168.0.200

>
> > Local Cisco - Only knows about 192.168.0.0 and the Serial link. *Needs
> > a default route pointing to the DLINK, and a route to the far LAN
> > segment via the far side serial interface.

>
> > Remote Cisco - Only knows about 192.168.10.0 and the Serial Link.
> > Needs a single default route to the serial on the other router. *This
> > will cover traffic to the internet and traffic to 192.168.0.0 since a
> > default route is all traffic.

>
> > This what you were looking for?- Hide quoted text -

>
> > - Show quoted text -

>
> I must be retarded, is it possible to configure each router here to
> make it work? And give me the exact configurations yall are looking
> like it needs to be? Ive tried but its apparent I am doing something
> wrong. I have the DLINK routing in, I can get from Terrell all the way
> to Royse City DLINK, but nothing after that.


Did you add the route to 192.168.10.0 255.255.255.0 via 192.168.0.200
to the DLINK GUI? The cisco configs look fine, your only gap was on
the dlink itself.
 
Reply With Quote
 
chsmith700@gmail.com
Guest
Posts: n/a
 
      10-15-2008
On Oct 15, 9:24*am, Trendkill <(E-Mail Removed)> wrote:
> On Oct 15, 10:12*am, (E-Mail Removed) wrote:
>
>
>
> > On Oct 15, 8:23*am, Trendkill <(E-Mail Removed)> wrote:

>
> > > On Oct 15, 9:21*am, (E-Mail Removed) wrote:

>
> > > > On Oct 15, 8:14*am, Trendkill <(E-Mail Removed)> wrote:

>
> > > > > On Oct 15, 9:09*am, Matthew Melbourne <(E-Mail Removed)>
> > > > > wrote:

>
> > > > > > In article
> > > > > > <(E-Mail Removed)>,
> > > > > > * *<(E-Mail Removed)> wrote:

>
> > > > > > > Hello,
> > > > > > > I am having a problem with a T1 Point to Point between two stores in
> > > > > > > two different cities. I have the connection from Royse City to Terrell
> > > > > > > working, but am unable to get from Terrell to Royse City. I am sure
> > > > > > > its something really stupid I am over looking. Here are my configs.

>
> > > > > > As others have said, your routing looks fine between the sites. However,
> > > > > > for the remote network 192.168.10.0/24 network to 'piggy back' off the
> > > > > > D107P router for Internet access, then there needs to be a static route on
> > > > > > the D-Link D107P router pointing to the remote network 192.168.10.0/24 via
> > > > > > 192.168.0.200.

>
> > > > > > Cheers,

>
> > > > > > Matt

>
> > > > > > --
> > > > > > Matthew Melbourne

>
> > > > > Well he also needs that route for the boxes on 192.168.0.0 to get to
> > > > > 10.0, because they most likely use 0.1 as their gateway, and not the
> > > > > Cisco router. *So even LAN to LAN would be broke without the route
> > > > > (although technically only broken one way).- Hide quoted text -

>
> > > > > - Show quoted text -

>
> > > > So in the Royse City, I need to first route 192.168.0.200 first, then
> > > > attempt to route 192.168.0.1 cause that is the direct flow? Then in
> > > > Dlink I need to have a route back to the .200 so that it can get back?
> > > > A dummy proof would def help..

>
> > > > Should I do a route on royse city cisco like so?

>
> > > > 192.168.0.200 255.255.255.0 10.100.254.1
> > > > 0.0.0.0.0 0.0.0.0 192.168.0.1

>
> > > > then in the Dlink assign a route back to 192.168.0.200

>
> > > Dlink - only knows about 192.168.0.0 and nothing else. *Needs a route
> > > that points to 192.168.10.0 via 192.168.0.200

>
> > > Local Cisco - Only knows about 192.168.0.0 and the Serial link. *Needs
> > > a default route pointing to the DLINK, and a route to the far LAN
> > > segment via the far side serial interface.

>
> > > Remote Cisco - Only knows about 192.168.10.0 and the Serial Link.
> > > Needs a single default route to the serial on the other router. *This
> > > will cover traffic to the internet and traffic to 192.168.0.0 since a
> > > default route is all traffic.

>
> > > This what you were looking for?- Hide quoted text -

>
> > > - Show quoted text -

>
> > I must be retarded, is it possible to configure each router here to
> > make it work? And give me the exact configurations yall are looking
> > like it needs to be? Ive tried but its apparent I am doing something
> > wrong. I have the DLINK routing in, I can get from Terrell all the way
> > to Royse City DLINK, but nothing after that.

>
> Did you add the route to 192.168.10.0 255.255.255.0 via 192.168.0.200
> to the DLINK GUI? *The cisco configs look fine, your only gap was on
> the dlink itself.


Alright, got the two talking to each other, pings are going thru both
ways, tracerts going thru, but cant access any files on the other LAN
from each location.
 
Reply With Quote
 
Trendkill
Guest
Posts: n/a
 
      10-15-2008
On Oct 15, 12:31*pm, (E-Mail Removed) wrote:
> On Oct 15, 9:24*am, Trendkill <(E-Mail Removed)> wrote:
>
>
>
> > On Oct 15, 10:12*am, (E-Mail Removed) wrote:

>
> > > On Oct 15, 8:23*am, Trendkill <(E-Mail Removed)> wrote:

>
> > > > On Oct 15, 9:21*am, (E-Mail Removed) wrote:

>
> > > > > On Oct 15, 8:14*am, Trendkill <(E-Mail Removed)> wrote:

>
> > > > > > On Oct 15, 9:09*am, Matthew Melbourne <(E-Mail Removed)>
> > > > > > wrote:

>
> > > > > > > In article
> > > > > > > <(E-Mail Removed)>,
> > > > > > > * *<(E-Mail Removed)> wrote:

>
> > > > > > > > Hello,
> > > > > > > > I am having a problem with a T1 Point to Point between two stores in
> > > > > > > > two different cities. I have the connection from Royse City to Terrell
> > > > > > > > working, but am unable to get from Terrell to Royse City. I am sure
> > > > > > > > its something really stupid I am over looking. Here are my configs.

>
> > > > > > > As others have said, your routing looks fine between the sites. However,
> > > > > > > for the remote network 192.168.10.0/24 network to 'piggy back' off the
> > > > > > > D107P router for Internet access, then there needs to be a static route on
> > > > > > > the D-Link D107P router pointing to the remote network 192.168.10.0/24 via
> > > > > > > 192.168.0.200.

>
> > > > > > > Cheers,

>
> > > > > > > Matt

>
> > > > > > > --
> > > > > > > Matthew Melbourne

>
> > > > > > Well he also needs that route for the boxes on 192.168.0.0 to get to
> > > > > > 10.0, because they most likely use 0.1 as their gateway, and not the
> > > > > > Cisco router. *So even LAN to LAN would be broke without the route
> > > > > > (although technically only broken one way).- Hide quoted text -

>
> > > > > > - Show quoted text -

>
> > > > > So in the Royse City, I need to first route 192.168.0.200 first, then
> > > > > attempt to route 192.168.0.1 cause that is the direct flow? Then in
> > > > > Dlink I need to have a route back to the .200 so that it can get back?
> > > > > A dummy proof would def help..

>
> > > > > Should I do a route on royse city cisco like so?

>
> > > > > 192.168.0.200 255.255.255.0 10.100.254.1
> > > > > 0.0.0.0.0 0.0.0.0 192.168.0.1

>
> > > > > then in the Dlink assign a route back to 192.168.0.200

>
> > > > Dlink - only knows about 192.168.0.0 and nothing else. *Needs a route
> > > > that points to 192.168.10.0 via 192.168.0.200

>
> > > > Local Cisco - Only knows about 192.168.0.0 and the Serial link. *Needs
> > > > a default route pointing to the DLINK, and a route to the far LAN
> > > > segment via the far side serial interface.

>
> > > > Remote Cisco - Only knows about 192.168.10.0 and the Serial Link.
> > > > Needs a single default route to the serial on the other router. *This
> > > > will cover traffic to the internet and traffic to 192.168.0.0 since a
> > > > default route is all traffic.

>
> > > > This what you were looking for?- Hide quoted text -

>
> > > > - Show quoted text -

>
> > > I must be retarded, is it possible to configure each router here to
> > > make it work? And give me the exact configurations yall are looking
> > > like it needs to be? Ive tried but its apparent I am doing something
> > > wrong. I have the DLINK routing in, I can get from Terrell all the way
> > > to Royse City DLINK, but nothing after that.

>
> > Did you add the route to 192.168.10.0 255.255.255.0 via 192.168.0.200
> > to the DLINK GUI? *The cisco configs look fine, your only gap was on
> > the dlink itself.

>
> Alright, got the two talking to each other, pings are going thru both
> ways, tracerts going thru, but cant access any files on the other LAN
> from each location.


Have you tried \\servername or \\ip address. Either way, you are most
likely beyond a network issue and into a workgroup or domain issue
since you now have multiple networks.
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Share-Point-2010 ,Share-Point -2010 Training , Share-point-2010Hyderabad , Share-point-2010 Institute Saraswati lakki ASP .Net 0 01-06-2012 06:39 AM
IP Route Tables - Point to Point Connection - Only Routing 1 way SallyBridges Cisco 3 12-06-2007 06:06 PM
using L2 connection as Point-To-Point rsurf Cisco 0 07-13-2007 08:07 PM
E1 Controller Point to POint connection Gary Cisco 5 08-08-2006 09:16 AM
Scenario 5: IS-IS routing on Frame Relay Multi-point and Point-to-Point David Sudjiman Cisco 0 06-08-2006 09:11 AM



Advertisments