Solved: Hey @Rokas Daunoras '

Rokas Daunoras · ‎02-13-2017

Hello Cisco Community,

I'm having problem with tagging

these ports are untagged but i need ip address like 10.100.50.1 or 10.100.70.1 tagged

it's should be like this,

1 - 8 untagged 50,70 tagged

9 - 16 untagged 1,70 tagged

17-24 untagged 1,50 tagged

Also pinging problem

Why computers from different networks can't communicate?

i add both switch & router config in txt file.

Regards

azibnaseem · ‎02-20-2017

Hey [@badaro292@gmail.com]

I have created a lab in GNS. I have attached screen shots & configuration of both Router & Switch for your review. Please make a mirrored configuration on your both Router & Switch.

Moreover, As your traffic is nated toward internet that's why, any is included in the access-list & this access-list is used for nating not applied on any router interfaces.

From your switch configuration, ip routing & ip subnet zero commands are still there. Please remove these commands & also remove IP address from router FastEthernet 0/1 & create sub-interface as I have created in Router configuration.

Regards'

View solution in original post

Mark Malone · ‎02-13-2017

Hi

the first thing I see is the default gateway is missing on the switch ? return traffic wont know how to get back , you need a default gateway to the router , try that see if it fixes the issue

Rokas Daunoras · ‎02-13-2017

Hey,

You mean like this?

!
ip default-gateway 10.100.100.2
ip classless
ip http server
!

But then i need to add ip route?

Mark Malone · ‎02-13-2017

Hi

yes a default-gateway , no route the switch is layer 2(trunking) so it only needs a default gateway, routes go on devices which are layer 3 or act as layer 3 , layer 2 devices just get a default gateway

your passwords are visible in the files you uploaded too

Rokas Daunoras · ‎02-15-2017

Hey,

Switch now have default gateway 10.100.100.2

But still computers can't communicate what could be the problem?

Passwords doesn't matter since these devices are off production they are just for me to understand.

Mark Malone · ‎02-15-2017

Ok cool

switch is layer 2 , so remove this ....ip routing

and there is no requirement for the vlan interfaces except for mgmt. reasons on a layer 2 switch

remove the ip routing and see if you can ping between the sub interfaces

ping 10.100.50.1 source 10.100.70.1

Rokas Daunoras · ‎02-17-2017

Hey,

Ip routing is off on switch

Sub interfaces ping in text file it is successful.

Regards

azibnaseem · ‎02-15-2017

Hey [@badaro292@gmail.com] '

First of all remove the command ip routing with the command no ip routing.

Please post the output of command,

sh vlan brief

Regards'

Rokas Daunoras · ‎02-17-2017

Hey azibnaseem

Ip routing is removed on switch

Regards

azibnaseem · ‎02-17-2017

Hey [@badaro292@gmail.com]

Please share the client computers IP Addresses & also mention on which ports are these clients connected.

Regards'

Rokas Daunoras · ‎02-17-2017

Hey azibnaseem

IP address and subnet mask of each PC

1. 10.100.100.2 255.255.255.0

2. 10.100.50.3 255.255.255.0

3. 10.100.70.4 255.255.255.0

1. 10.100.100.2 connected to Port 5

2. 10.100.50.3 connected to Port 15

3. 10.100.70.4 connected to port 20

azibnaseem · ‎02-17-2017

Hey [@badaro292@gmail.com] '

Please confirm, are you just facing ping problem from client PC to client PC.

Regards'

Rokas Daunoras · ‎02-17-2017

Hey azibnaseem

Yes pinging from PC to other PC getting timeout.

Regards

azibnaseem · ‎02-17-2017

Hey [@badaro292@gmail.com]

I have attached the topology screen shot. Please review & confirm that is this a same topology your are going to configure?

Regards'

Rokas Daunoras · ‎02-17-2017

Hey azibnaseem

Yeah just different ports

Regards

(Help) Tagging Switch Ports & Pinging problem