Host Unable to Ping Outside of LAN

[alexbarrycooper]

Hello, I'm currently having an issue with being able to ping the IP address 8.8.8.8 with my host computer. I am using a 3550 Cisco switch and a 2621xm Cisco router with the Host computer connected to the switch along my router's 0/1 interface connected to the switch my router's 0/0 interface connected into my ISPs modem and the modem is connected to the internet.

[paul driver]

Hello

Not sure I understand - i thought you had access to the router?

if not where are you making the changes i am suggesting?



res
Paul

[alexbarrycooper]

your request, I don't understand how to accomplish it that's my concern. currently I am using a console cable to access my router with putty/terraterm/hyperterm. I am sorry for the confusion.

[paul driver]

Hello

So you are actually on the rtr be it via console connection, thats not a problem.

You should be able to run these commands on the rtr even when accessed  via the console cable.

sh ip int brief
sh ip route
sh arp
sh ip nat translations

res
Paul

[alexbarrycooper]

Router#sh ip int brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 10.0.0.208 YES DHCP up up
FastEthernet0/1 192.168.0.200 YES manual up down
Router#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/24 is subnetted, 1 subnets
C 10.0.0.0 is directly connected, FastEthernet0/0
Router#sh arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.0.0.1 0 1086.8c39.f1ab ARPA FastEthernet0/0
Internet 10.0.0.208 - 000f.34c0.1980 ARPA FastEthernet0/0
Router#sh ip nat translations

[paul driver]

Hello

okay ,

1) ip route 0.0.0.0 0.0.0.0 fa0/0 10.0.0.1
2) you fa0/1 physically interface is up but logically its down, so it seems like your switch or your host on that switch isnt bringing up the other side

Can you post the config of the switch please
How is the host obtaining ip addressing-- statically I guess?

res

Paul

[alexbarrycooper]

No, the host is getting its IP dynamically.

Building configuration...

Current configuration : 3307 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Switch
!
!
ip subnet-zero
ip routing
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
!
!
interface FastEthernet0/1
no ip address
!
interface FastEthernet0/2
no ip address
!
interface FastEthernet0/3
no ip address
!
interface FastEthernet0/4
no ip address
!
interface FastEthernet0/5
no ip address
!
interface FastEthernet0/6
no ip address
!
interface FastEthernet0/7
no ip address
!
interface FastEthernet0/8
no ip address
!
interface FastEthernet0/9
no ip address
!
interface FastEthernet0/10
no ip address
!
interface FastEthernet0/11
no ip address
!
interface FastEthernet0/12
no ip address
!
interface FastEthernet0/13
no ip address
!
interface FastEthernet0/14
no ip address
!
interface FastEthernet0/15
no ip address
!
interface FastEthernet0/16
no ip address
!
interface FastEthernet0/17
no ip address
!
interface FastEthernet0/18
no ip address
!
interface FastEthernet0/19
no ip address
!
interface FastEthernet0/20
no ip address
!
interface FastEthernet0/21
no ip address
!
interface FastEthernet0/22
no ip address
!
interface FastEthernet0/23
no ip address
!
interface FastEthernet0/24
no ip address
!
interface FastEthernet0/25
no ip address
!
interface FastEthernet0/26
no ip address
!
interface FastEthernet0/27
no ip address
!
interface FastEthernet0/28
no ip address
!
interface FastEthernet0/29
no ip address
!
interface FastEthernet0/30
no ip address
!
interface FastEthernet0/31
no ip address
!
interface FastEthernet0/32
switchport access vlan 2
no ip address
!
interface FastEthernet0/33
switchport access vlan 2
no ip address
!
interface FastEthernet0/34
switchport access vlan 2
no ip address
!
interface FastEthernet0/35
switchport access vlan 2
no ip address
!
interface FastEthernet0/36
switchport access vlan 2
no ip address
!
interface FastEthernet0/37
switchport access vlan 3
no ip address
!
interface FastEthernet0/38
switchport access vlan 3
no ip address
!
interface FastEthernet0/39
switchport access vlan 3
no ip address
!
interface FastEthernet0/40
switchport access vlan 3
no ip address
!
interface FastEthernet0/41
switchport access vlan 4
no ip address
!
interface FastEthernet0/42
switchport access vlan 4
no ip address
!
interface FastEthernet0/43
switchport access vlan 4
no ip address
!
interface FastEthernet0/44
switchport access vlan 4
no ip address
!
interface FastEthernet0/45
switchport access vlan 5
no ip address
!
interface FastEthernet0/46
switchport access vlan 5
no ip address
!
interface FastEthernet0/47
switchport access vlan 5
no ip address
!
interface FastEthernet0/48
switchport access vlan 5
no ip address
!
interface GigabitEthernet0/1
no ip address
!
interface GigabitEthernet0/2
no ip address
!
interface Vlan1
ip address 169.172.10.10 255.255.0.0
!
interface Vlan2
ip address 192.168.0.206 255.255.255.0
!
interface Vlan3
ip address 192.168.1.106 255.255.255.0
!
interface Vlan4
ip address 192.168.2.106 255.255.255.0
!
interface Vlan5
ip address 192.168.30.206 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.0.200
ip route 0.0.0.0 0.0.0.0 192.168.30.200
ip http server
!
!
!
line con 0
line vty 5 15
!
end

[paul driver]

Hello

1) Is the router connected to an access port in vlan 2 - if it isn't then it should be?

2)Whats the reason you have two default  static routes on the switch - the only default should be pointing to routers inside address. which is 192.168.0.200

3) Where is dhcp being sourced from for all these vlans,I don't see it on the rtr or switch?

4) do you require all these vlans, if you you'll need to add them you your NAT access list and also
apply static routes on the rtr and them point towards your switch

example:
rtr
ip route 192.168.30.0 255.255.255.0 fa0/1 192.168.0.206 ( for vlan30)

res
Paul

[alexbarrycooper]

Alright, the router is connect into the switch under 0/34.

I have two default routes because I have two routers, this configuration is for my Microsoft Private Cloud Lab. One router is for vlan 0002 (the router we are configuring) and another is for vlan 0005. I figured if I could get the first router configured correctly then I could get the second one done on my own.

I don't think I understand Question 3

Yes I do, my budget was tight. The lab requests that you have multiple switches, but to me it looked like they only did that to break up the broadcast domains, so I got only one switch and two routers and created the vlans to breakup the broadcast domains logically.

I know it must look pretty nuts, but I believe that it would work. If I can get it to work.

please note, i originally had this configuration working at a point-and-time, but due to some configurations that locked me out of my routers I was forced to start from scratch.

[alexbarrycooper]

Also, I do not want vlan 1, vlan 0003 and vlan 0004 to be using the routers. I want them to remain isolated from all other lans.

[paul driver]

Hello

I have two default routes because I have two routers, this configuration is for my Microsoft Private Cloud Lab. One router is for vlan 0002 (the router we are configuring) and another is for vlan 0005.

Well this wont work has you will be blackholing half of you traffic as the rtr wouldn't know which default to choose to route to networks it doesn't know about.

1) As the switch is performing the routing , leave the default static towards the internet and remove the other default.

2) check the cabling for the attached rtr to port

3) make sure your hosts on vlan 2 receive the correct  addressing ( subnet mask /default gateway - this can be 192.168.0.200

conf t
no ip route 0.0.0.0 0.0.0.0 192.168.0.200
no ip route 0.0.0.0 0.0.0.0 192.168.30.200

ip route 0.0.0.0 0.0.0.0 vlan 2 192.168.0.200

int fa0/34
switchport host

sh ip int brief | in up

res
Paul

[alexbarrycooper]

Switch#show ip interface brief | in up
Vlan1 169.172.10.10 YES manual up down
Vlan2 192.168.0.206 YES manual up up
Vlan3 192.168.1.106 YES manual up up
Vlan4 192.168.2.106 YES manual up up
Vlan5 192.168.30.206 YES manual up up
FastEthernet0/32 unassigned YES unset up up
FastEthernet0/33 unassigned YES unset up up
FastEthernet0/34 unassigned YES unset up up
FastEthernet0/36 unassigned YES unset up up
FastEthernet0/37 unassigned YES unset up up
FastEthernet0/40 unassigned YES unset up up
FastEthernet0/44 unassigned YES unset up up
FastEthernet0/47 unassigned YES unset up up
FastEthernet0/48 unassigned YES unset up up

and I have done the ip route configuration as you recommended

[paul driver]

Hello

Okay go back to the router and see if you can now ping the internet sourced from fa0/1
That fa0/1 needs to be in a up/up state, if it isnt then you need to check why is isn't

If it works then your nat will be working for that vlan2

One more thing - on the dhcp server have you made exclusions for the L3 address of the rtr and the switch?

res
Paul.

[alexbarrycooper]

Troubling, I no longer can ping 8.8.8.8 with the router. I am still able to ping the ISP modem though.

And yes, I have excluded those adresses

[paul driver]

Hello

Well thats not good, however all the work we have being doing shouldnt have stopped you from accessing the internet from the router.

can you post the following from the rtr just to make sure no typos have been made:

sh ip route static
sh ip int brief

res
Paul

[alexbarrycooper]

Router#sh ip route static

Router#show ip int brie
Router#show ip int brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 10.0.0.208 YES DHCP up up
FastEthernet0/1 192.168.0.200 YES manual up down

i never set the new ip route "ip route 0.0.0.0 0.0.0.0 fa0/0 10.0.0.1"

i just did add it and now we can ping the outside.