<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>simple point to point 1841 to 1841 through a T1 in Cisco</title>
<link>http://www.dslreports.com/forum/r22635272</link>
<description></description>
<language>en</language>
<pubDate>Thu, 03 Dec 2009 07:27:42 EDT</pubDate>
<lastBuildDate>Thu, 03 Dec 2009 07:27:42 EDT</lastBuildDate>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22711138</link>
<description><![CDATA[<A HREF="/useremail/u/712841"><b>carp</b></A> : <br>That makes no sense to me.  With NAT removed from the configs you posted I'm not seeing anything jump out at me as to why you are having an issue unless it's something outside of these two routers assuming the current config of the routers is correct based on the rest of the corporate network.<br><br>Are you sure the mask you used for 131.107 on the corp router is correct?  Based on the mask you used you are telling the router that all of 131.107.x.x is the same segment.  No other segments handled by other routers.  I see you have 131.107.15.5 as the IP address on the router at corp but you also have a helper of 131.107.1.14 on the remote.  Are 131.107.15 and 131.107.1 really separate IP segments.  If so, there is work to do on the corporate side of your network.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22711138</guid>
<pubDate>Wed, 15 Jul 2009 10:44:03 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22701426</link>
<description><![CDATA[<A HREF="/useremail/u/1655147"><b>Necrofuzzy</b></A> : We turned off the nat on the remote side. Dont know why we had it on in the first place. From corp we can ping the router and a machine connected to the router via switch, But from the remote machine we cannot ping or communicate with the network that is connected to the router on corporate side, even though they have the same settings. i.e <br>next hop for the remote router is 10.10.52.1(interna)<br>and a route from 131.107.15.5(the corp router) for a network here at corp is 131.107.0.0 255.255.0.0 has been added.<br><br>and here on the corp side the next hop is 10.10.52.2(internal)<br>and a route from  192.168.200.1(remote router)<br>and that route = <br>192.168.200.0 255.255.255.0  to 131.107.15.5]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22701426</guid>
<pubDate>Mon, 13 Jul 2009 16:49:13 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22680725</link>
<description><![CDATA[<A HREF="/useremail/u/1655147"><b>Necrofuzzy</b></A> : Well like i said we really are new to this. And why would we not want the connection to be permanent. Its a direct T1, doesnt go through the internet. Its purpose is to have the remote office connect to our servers and log into our domain. <br>Should we not make it permanent? If not, please tell why?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22680725</guid>
<pubDate>Thu, 09 Jul 2009 14:32:52 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22678372</link>
<description><![CDATA[<A HREF="/useremail/u/676954"><b>aryoba</b></A> : 1. Is there a reason why the remote office router does NAT?<br><br>2. Why do you want route on corp router to reach remote office to be permanent?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22678372</guid>
<pubDate>Thu, 09 Jul 2009 09:25:17 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22678315</link>
<description><![CDATA[<A HREF="/useremail/u/1655147"><b>Necrofuzzy</b></A> : I posted my configurations. Is there no hope for us? We are getting desperate as the deadline grows near. If there is anything we can provide other than this that will help identify what we are doing wrong. Just ask.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22678315</guid>
<pubDate>Thu, 09 Jul 2009 09:19:27 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22660542</link>
<description><![CDATA[<A HREF="/useremail/u/1655147"><b>Necrofuzzy</b></A> : here is my configuration files, as we have yet to get this right<br><br>REMOTE SIDE<br>------------------------------------<br>Current configuration : 3330 bytes<br>!<br>! Last configuration change at 09:12:30 PCTime Mon Jul 6 2009 by buddha<br>! NVRAM config last updated at 14:24:17 PCTime Wed Jul 1 2009 by buddha<br>!<br>version 12.4<br>no service pad<br>service tcp-keepalives-in<br>service tcp-keepalives-out<br>service timestamps debug datetime msec localtime show-timezone<br>service timestamps log datetime msec localtime show-timezone<br>service password-encryption<br>service sequence-numbers<br>!<br>hostname ema2gsv<br>!<br>boot-start-marker<br>boot-end-marker<br>!<br>security authentication failure rate 3 log<br>security passwords min-length 6<br>logging buffered 51200 debugging<br>logging console critical<br>enable secret 5 $1$DH.o$FTjatYmUUyVIDUIPeLvBE/<br>!<br>no aaa new-model<br>!<br>resource policy<br>!<br>clock timezone PCTime -6<br>clock summer-time PCTime date Apr 6 2003 2:00 Oct 26 2003 2:00<br>mmi polling-interval 60<br>no mmi auto-configure<br>no mmi pvc<br>mmi snmp-timeout 180<br>ip subnet-zero<br>no ip source-route<br>ip cef<br>!<br>!<br>ip tcp synwait-time 10<br>!<br>!<br>no ip bootp server<br>ip domain name mcc<br>!<br>username buddha privilege 15 secret 5 $1$lI7B$3ndLe94EF02YErpwx5sM4/<br>!<br>!<br>!<br>interface FastEthernet0/0<br> description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-FE 0$$ES_LAN$$FW_INSIDE$<br> ip address 192.168.200.1 255.255.255.0<br> ip helper-address 131.107.1.14<br> no ip redirects<br> no ip unreachables<br> no ip proxy-arp<br> ip nat inside<br> ip route-cache flow<br> duplex auto<br> speed auto<br> no mop enabled<br>!<br>interface FastEthernet0/1<br> no ip address<br> no ip redirects<br> no ip unreachables<br> no ip proxy-arp<br> ip route-cache flow<br> shutdown<br> duplex auto<br> speed auto<br> no mop enabled<br>!<br>interface Serial0/0/0<br> description $ES_WAN$$FW_OUTSIDE$<br> ip address 10.10.52.2 255.255.255.252<br> no ip redirects<br> no ip unreachables<br> no ip proxy-arp<br> ip nat outside<br> ip route-cache flow<br>!<br>ip classless<br>ip route 0.0.0.0 0.0.0.0 10.10.52.1 permanent<br>!<br>ip http server<br>ip http authentication local<br>ip http timeout-policy idle 60 life 86400 requests 10000<br>ip nat inside source list 1 interface Serial0/0/0 overload<br>!<br>logging trap debugging<br>access-list 1 remark INSIDE_IF=FastEthernet0/0<br>access-list 1 remark SDM_ACL Category=2<br>access-list 1 permit 192.168.200.0 0.0.0.255<br>no cdp run<br>!<br>control-plane<br>!<br>banner exec ^C<br>% Password expiration warning.<br>-----------------------------------------------------------------------<br> <br>Cisco Router and Security Device Manager (SDM) is installed on this device and <br>it provides the default username "cisco" for  one-time use. If you have already <br>used the username "cisco" to login to the router and your IOS image supports the <br>"one-time" user option, then this username has already expired. You will not be <br>able to login to the router with this username after you exit this session.<br> <br>It is strongly suggested that you create a new username with a privilege level <br>of 15 using the following command.<br> <br>username  privilege 15 secret 0 <br> <br>Replace  and  with the username and password you want to <br>use.<br> <br>-----------------------------------------------------------------------<br>^C<br>banner login ^CAuthorized access only!<br> Disconnect IMMEDIATELY if you are not an authorized user!^C<br>!<br>line con 0<br> login local<br> transport output telnet<br>line aux 0<br> login local<br> transport output telnet<br>line vty 0 4<br> privilege level 15<br> login local<br> transport input telnet<br>line vty 5 15<br> privilege level 15<br> login local<br> transport input telnet<br>!<br>scheduler allocate 4000 1000<br>end<br><br>CORP SIDE<br>----------------------------------------------------------<br>Current configuration : 1980 bytes<br>!<br>version 12.4<br>service timestamps debug datetime msec<br>service timestamps log datetime msec<br>no service password-encryption<br>!<br>hostname gsv@ema<br>!<br>boot-start-marker<br>boot-end-marker<br>!<br>logging buffered 51200 warnings<br>!<br>no aaa new-model<br>!<br>resource policy<br>!<br>mmi polling-interval 60<br>no mmi auto-configure<br>no mmi pvc<br>mmi snmp-timeout 180<br>ip subnet-zero<br>ip cef<br>!<br>!<br>!<br>!<br>ip domain name mcc<br>!<br>username buddha privilege 15 secret 5 $1$l9TE$dGB/kZA79E7NgqLZyxmtR1<br>!<br>!<br>!<br>interface FastEthernet0/0<br> description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-FE 0$$ES_LAN$<br> ip address 131.107.15.5 255.255.0.0<br> duplex auto<br> speed auto<br>!<br>interface FastEthernet0/1<br> no ip address<br> shutdown<br> duplex auto<br> speed auto<br>!<br>interface Serial0/0/0<br> ip address 10.10.52.1 255.255.255.252<br> service-module t1 clock source internal<br>!<br>ip classless<br>ip route 192.168.200.0 255.255.255.0 10.10.52.2 permanent<br>!<br>ip http server<br>ip http authentication local<br>ip http timeout-policy idle 60 life 86400 requests 10000<br>!<br>!<br>control-plane<br>!<br>banner login ^C<br>-----------------------------------------------------------------------<br>Cisco Router and Security Device Manager (SDM) is installed on this device. <br>This feature requires the one-time use of the username "cisco" <br>with the password "cisco". The default username and password have a privilege level of 15.<br><br>Please change these publicly known initial credentials using SDM or the IOS CLI. <br>Here are the Cisco IOS commands.<br><br>username   privilege 15 secret 0 <br>no username cisco<br><br>Replace  and  with the username and password you want to use. <br><br>For more information about SDM please follow the instructions in the QUICK START <br>GUIDE for your router or go to &raquo;<A HREF="http://www.cisco.com/go/sdm" >www.cisco.com/go/sdm</A> <br>-----------------------------------------------------------------------<br>^C<br>!<br>line con 0<br> login local<br>line aux 0<br>line vty 0 4<br> privilege level 15<br> login local<br> transport input telnet<br>line vty 5 15<br> privilege level 15<br> login local<br> transport input telnet<br>!<br>end<br><br>like i said we are complete noobs at this. Hope you can help us with this.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22660542</guid>
<pubDate>Mon, 06 Jul 2009 11:08:35 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22640136</link>
<description><![CDATA[<A HREF="/useremail/u/712841"><b>carp</b></A> : remote site router should have statement:<br><br>ip route 0.0.0.0 0.0.0.0 10.10.52.1<br><br>corp:<br><br>ip route 192.168.200.0 255.255.255.0(or your actual mask) 10.10.52.2<br><br>make sure the other devices on 131.107.1.5 have the correct default gateway or the default gateway they point to has correct routing for the rest of the network.<br><br>or post your router configurations.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22640136</guid>
<pubDate>Wed, 01 Jul 2009 14:34:12 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22639783</link>
<description><![CDATA[<A HREF="/useremail/u/1120065"><b>rsaturns</b></A> : I would suspect routing. Does the Corporate site network know how to route back to the 192.168.200 network? You can ping the 131.107.15.5 because that router knows about the 192.168.200 network because I assume you assigned it a static route. <br><br>You would need to tell the router in the 131.107.x.x how to route back to the 192.168.200 network.<br><small>--<br>&raquo;<A HREF="http://vinfotech.blogspot.com" >vinfotech.blogspot.com</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22639783</guid>
<pubDate>Wed, 01 Jul 2009 13:27:51 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22639198</link>
<description><![CDATA[<A HREF="/useremail/u/1655147"><b>Necrofuzzy</b></A> : Ok here is the problem we are having now.<br><br>pc with static ip of 192.168.200.20 is connected to:<br><br>router remote side<br>----------------------<br>Remote site fastethernet ip = 192.168.200.1<br>remote site serialT1 ip = 10.10.52.2<br><br>corporate site serialT1 = 10.10.52.1<br>corporate site fastethernet ip = 131.107.15.5<br><br>that is plugged into our main network wich is 131.107.x.x<br><br>our dhcp server is 131.107.1.14<br>our domain server is 131.107.1.5<br><br>from remote site we can ping the 131.107.15.5 but not the rest of the network.<br><br>??? any ideas why?<br>  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22639198</guid>
<pubDate>Wed, 01 Jul 2009 11:37:41 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22635743</link>
<description><![CDATA[<A HREF="/useremail/u/1120065"><b>rsaturns</b></A> : Edited above post should be address not interface.<br><small>--<br>&raquo;<A HREF="http://vinfotech.blogspot.com" >vinfotech.blogspot.com</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22635743</guid>
<pubDate>Tue, 30 Jun 2009 16:41:23 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22635724</link>
<description><![CDATA[<A HREF="/useremail/u/1655147"><b>Necrofuzzy</b></A> : What is an ip helper interface? Is it something we can do with sdm, (sad) thats what were trying to set it up with. Were noobs .  :huh:]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22635724</guid>
<pubDate>Tue, 30 Jun 2009 16:38:57 EDT</pubDate>
</item>

<item>
<title>Re: simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22635582</link>
<description><![CDATA[<A HREF="/useremail/u/1120065"><b>rsaturns</b></A> : Basically you need to take the following steps.<br><br>Setup the serial interface on each 1841. If this is a true private point to point you can use whatever IP address you want highly recommend a /30 as to save address space.<br><br>Once you can ping across the T1 you&#146;ll need to make sure that the network on the Corp side of the link is aware of the network on the far side aka a route either statically assigned or using some sort of dynamic routing protocol.<br><br>Next setup your Fast Ethernet interface on the remote site with the network subnet of your choosing make sure again from Corp you can reach that side of the far router.<br><br>Setup an IP helper *address* on that fast Ethernet interface and point it to your DHCP server back at Corp.<br><br>Make sure Corp has a scope for this remote network.<br><br>That&#146;s the process in a nutshell with a lot of detail omitted.<br><br>Edited to say ip helper address not interface.<br><br><small>--<br>&raquo;<A HREF="http://vinfotech.blogspot.com" >vinfotech.blogspot.com</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22635582</guid>
<pubDate>Tue, 30 Jun 2009 16:12:34 EDT</pubDate>
</item>

<item>
<title>simple point to point 1841 to 1841 through a T1</title>
<link>http://www.dslreports.com/forum/remark,22635272</link>
<description><![CDATA[<A HREF="/useremail/u/1655147"><b>Necrofuzzy</b></A> : Hello me and my coworkers are very new to this, but here is our situation.<br><br>We have a T1 line running from our current office to a remote site. We have 2 1841 cisco routers to connect to each side.<br>We use a NT domain and assign ip addresses dynamically, on the office side. We would like to assign the addresses from the same dhcp server to the remote site. But first we need specific instructions on how to set up both  routers. We have tried using sdm express but havent had much luck. <br>  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22635272</guid>
<pubDate>Tue, 30 Jun 2009 15:12:43 EDT</pubDate>
</item>

</channel>
</rss>
