ScoobyJawa

Hi all

I've got a lab which I want to give access to the internet.

I've got a 2600 hooked up to my sky router and gaining an IP address (192.168.0.5) via DHCP (allocated from my sky router). This can ping 192.168.0.1 which is the sky router itself, the 90.x.x.x address the router has in isp land and all the way out to the internet. So jobs a good un!

Also I have this router connected up to a second router, running eigrp to publish available networks on each router. The second router can ping the 192.168.0.5 address on the port on the first 2600, but it can't ping 192.168.0.1 or anything out in internet land.

Its doing my head in - anyone got any ideas why? It sees the 192.168.0.0 network eigrp publishes via the link to the other router and can ping that network address on the other routers port but no further?!!?

Thanks

hodgy0_2

firstly I would diasable eigrp (dynamic) routing and use static routing to get it working

what icmp message to you get back "reqeust timed out" or "host not found"

does the sky router have a route back to the 2nd 2600

also to get replys back from the internet your natting has to be correct too

hodgy0_2

also have you got a copy of Cisco Config Maker

a GUI program (made by Cisco) that allows you to design a network by drag and dropping cisco routers and switches ion a visio type page, it will then generate the config file -- quite good for small networks

ScoobyJawa

Scratch that - Windows Firewall blocking ping reply

Still looking at the other bits!

hux309

Try asking here.

Sky User - The unofficial support forum for everything Sky!

But be warned many have tried and failed to manage it, sky routers are very restrictive.

hodgy0_2

well i would have suggested the windows firewall (honest guv) -- but from your post it looked like you were using the routers to test connectivity

ScoobyJawa

Cracked it

Added correct PAT config to the 2600 connected to the Sky Router and a static route (gateway of last resort) on the other one - jobs a good un!

Now to nail it down with access-lists - bet I break it lol - its all good learning curves!

hodgy0_2

nice one

access list get processed as soon as you press return

so a good tip, if you are accessing the router remotly is, before you edit the access list, set the router to reboot in say 1hr, that way if you "lock" yourself out by incorrectly applying an access list, the router will reboot to the original config in the time you specified and you will be able to reconnect

when all is working you can just cancel the reboot command

ScoobyJawa

Ah - yeah I remember them teaching us that on the CCNA course - defo a useful trick

hodgy0_2

ringing a datacentre half way round the world and asking the on-call technician to goto location 5b, rack 02076 and recycle asset no xyz

means you only make that mistake once

ScoobyJawa

whoops