Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Static Routes

Status
Not open for further replies.

CaptHarrased

Technical User
Jul 7, 2003
26
GB
Good Idea Baddos,

Ok,here we go,

The job is designing a way to install 805's to bridge or route in such a way that engineers with no cisco or routing knowledge can install them (UK wide!)

Standard scenario is main site with 1600 configured by third party supplier(no access to router or config!) This may or may not run nat depending on area. The 1600 supplies connectivity to the outside. The 805's supply connectivity to the remote site only via a dedicated line. OK there is no problem with a bridged scenario that works fine. The problem arises when you route because all the remote clients have the 805 at the main site as their default gateway (using 2000 with rdp client or terminal server thin clients) so internet and email only possable when connecting via the thin sessions. Got round this by setting up static routes on the servers and clients but this overly complicates matters. Now i am surmising that this can be got round by specifying the static routes required in the routers but am not sure if you can or how to do it. The problem is most of the sites are non nat with no available addresses as previously bridges were used with standard internal addresses at the remote end.

What i need is a config file that an any engineer can edit the ip addresses on and blow to the router via console. This i have other than the static route part. The only way i know how to do it is to put the routes on the remote stations and the connecting servers. Plus i do get the feeling that my config has a few things missing even though it works! By the way if I'am coming across like a drowning man its because i am!

enable
config t
hostname Branch
enable secret xxxx
no ip source-route

ip routing
ip classless
ip subnet-zero

interface ethernet 0
no shutdown
ip address 192.168.2.254 255.255.255.0
exit

interface serial 0
ip address 100.0.0.2 255.255.255.0
no shutdown
exit

no router rip
ip route 0.0.0.0 0.0.0.0 serial 0

line console 0
password xxxx
login
line vty 0 4
password xxxx
login
exit
exit
copy run start

reload
**********************************************************

enable
config t
hostname Main
enable secret xxxx
no ip source-route

ip routing
ip classless
ip subnet-zero


interface ethernet 0
no shutdown
ip address 192.168.1.253 255.255.255.0
exit

interface serial 0
ip address 100.0.0.1 255.255.255.0
no shutdown
exit

no router rip
ip route 0.0.0.0 0.0.0.0 serial 0

line console 0
password xxxx
login
line vty 0 4
password xxxx
login
exit
exit
copy run start

reload

*********************************************************

Any advice will be much appreciated but please be aware Ive not got much hands on!! so be gentle!!!!!!!


 
Ok... Let me get this straight.

Does your network look something like this?
INET
|
1600 (managed by ISP)
|-----|------| Corporate subnet
| |
805 805
| |
|----|RN |-----|RN (Remote subnet)

Your servers on your corporate subnet have static routes to the two remote subnets (through the two 805's) and a default route to the 1600?
 
Baddos,

Internet
|
|
1600
|
|
/ Main Site-------- -------|
non nat |
|
|
805main
|
|x21 line
|
|
|
805remote

We used to use 1600's for the remote site so addressing wasnt a problem as we used the aui with a transciever so its the same broadcast domain(think thats right, correct me if its not!) but with the 805's there is no aui only rj45 for console & ethernet plus the new serial connector. If thats not enough info i can email you a proper diag.
Thanks for taking the time Baddos i appreciate it!!!


 
OK... What is the reachablility problem? Can you supply subnet numbers and hosts in each subnets to show who can't talk to who.

-Bad Dos
 
Basically i cant get remote end to connect to anything on the main site. I did have it working but could not get internet access through the 1600. So after fiddling for a few days I now have no connectivity to the 1600 side at all. Before i had it as long as i put a static route in the servers at the main site and on the workstations at the remote end. Now i am unable to ping past the ethernet ports on either router. I think basically i have shafted the configs on both routers! The work pillock springs to mind!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top