04-17-2016 08:30 AM - edited 03-08-2019 05:23 AM
Hello Everyone -
I have 2 issues here which I'm hoping is an easy fix and I'm simply overlooking the basics.
Issue #1 - Cannot ping from switch1 to router1 and vice-versa.
Issue #2 - Cannot gain internet access from PC connected to switch1. (They can ping each other)
I've attached both running configs for the switch1 and router1 and also the topology from packet tracer. If someone could please take a quick look and let me know what I'm doing wrong here I would greatly appreciate it.
If other pertinent information is needed please let me know.
Thanks so much for assisting!
Solved! Go to Solution.
04-17-2016 09:26 AM
Hi,
Are you trying to use sw1 as a layer-2 switch only? if that is the case than you don't need 192.168.2.0/30 segment (between sw1 and r1). All you need is a default-gateway that point to 10.1.1.1
ip default-gateway 10.1.1.1
and this ip should be applied to interface fa0/1 on r1.
now you should be able to ping from PC to its gateway which is 10.1.1.1 (r1)
you should also be able to ping from sw1 to r1 and vice versa.
does it work?
04-17-2016 09:26 AM
Hi,
Are you trying to use sw1 as a layer-2 switch only? if that is the case than you don't need 192.168.2.0/30 segment (between sw1 and r1). All you need is a default-gateway that point to 10.1.1.1
ip default-gateway 10.1.1.1
and this ip should be applied to interface fa0/1 on r1.
now you should be able to ping from PC to its gateway which is 10.1.1.1 (r1)
you should also be able to ping from sw1 to r1 and vice versa.
does it work?
04-17-2016 09:32 AM
Also on sw1 you have this:
interface FastEthernet0/48 description TO SW1
Do you mean r1? because you are on sw1
Also it says 0/48 but the diagram shows fa0/24
So, which is correct?
04-17-2016 09:43 AM
Sorry - Int fa0/24 on packet tracer is the same as fa0/48 on my live switch. Yes, I meant R1 on the description of fa0/48 - It's changed.
04-17-2016 02:01 PM
Ok. Good to know the PC connectivity to r1 is working. The next part you need to work on is the connectivity between r1 and the Internet router before NAT.
Looking at your diagram there is subnet between r1 and the Internet router (192.168.1.0/24) and the IP on r1 is 192.168.1.2/24 using DHCP right? and the Internet router is 192.168.1.1/24 right?
if this assumption is correct do the following:
remove these 2 commands:
ip default-gateway 192.168.1.1
ip route 0.0.0.0 0.0.0.0 192.168.1.1 254
04-17-2016 03:52 PM
My internet router is 192.168.1.1 /24, correct. Also, my internet router (ASUS) is giving R1 a 'static' IP so when I configure fa0/0 to DHCP - 192.168.1.8 is assigned.
I've removed R1's default-gateway, however when I remove route 0.0.0.0 0.0.0.0 192.168.1.1 254 it gives me a 'No matching route to delete'. Funny thing is, if I remove route 0.0.0.0 0.0.0.0 192.168.1.1, I will still have a default route, but the admin distance will be 254. Wonder if it is a bug in the OS?
04-17-2016 06:26 PM
Are you able to ping the Internet router IP (192.168.1.1) from r1?
04-17-2016 06:29 PM
04-17-2016 06:40 PM
Ok. Now if you put a static route on the Internet router for the 10.1.1.0/24 address you should be able to ping the internet router from your PC and the vice versa.
ip route 10.1.1.0 255.255.255.0 192.168.1.8 (r1 ip)
04-17-2016 06:51 PM
Can't add the route with 192.168.1.8 but I can add it with .1
04-19-2016 07:56 AM
Awesome, so now I am able to ping from my PC, which is connected to fa0/1 to google.com but it still won't let me load up a webpage.
Any ideas?
04-17-2016 10:27 AM
I'm just trying to use SW1 as a layer 2 switch and grant my PC internet access through it.
I've removed the /30 from fa0/1 on R1 and changed the default gateway on SW1 to 10.1.1.1 yet I still cannot ping from R1 to SW1 and vice versa.
I can ping from PC1 to SW1 and vice-versa, but cannot ping from R1 to PC1. PC1 also does not have internet access.
** EDIT **
Got it - Set the IP address for fa0/1 on R1 to 10.1.1.1 /24 and set the default gateway of R1 to 10.1.1.1 and I am now able to ping PC1 from R1 and vice-versa.
Now to get PC1 connected to the internet. I would guess it's a NAT issue?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide