FD SOLUCIONESOPTICAL CONNECTIONS Share a Connection Schedule
HOME / The core switch cannot ping the PCs connected to the access switch

The core switch cannot ping the PCs connected to the access switch

Fibre interconnection and data room reference Published 08 Nov 2025

Use this reference to prepare product questions for FD SOLUCIONES. Check interfaces, capacity, protection and installation requirements against the current product documentation.

The issue is likely due to VLAN misconfiguration, missing default gateway on the access switch, or incorrect port tagging on the PC-facing ports. Common Causes1.

VLA

N and Trunk Configuration Ensure that the uplink between the core and access switch is configured as a trunk and that the VLANs for the PCs are allowed on the trunk. If the access switch ports connected to PCs are in access mode, they should be assigned to the correct VLAN and not tagged unless the PC NIC is configured for VLAN tagging. 2.

Default Gateway on Access Switch If the access switch is a Layer 2 device, it needs a default gateway pointing to the core switch SVI for inter-VLAN routing. Without this, the access switch cannot forward traffic from its VLANs to the core switch. Use the command ip default-gateway [core SVI IP] on the access switch.

3. Layer 3 Routing If the access switch is Layer 3, ensure IP routing is enabled and that the switch has routes to the core switch and other VLANs. The core switch should also have routes to the access switch VLANs.

4.

AC

Ls and Firewall Rules Check for ACLs applied inbound or outbound on the VLANs.

An AC

L blocking traffic from the access VLAN to the core switch can prevent pings even if routing is correct. 5.

ARP and MA

C Table Issues Sometimes clearing the ARP table on the core switch and the access switch can resolve connectivity issues if stale entries exist.

Recommended Troubleshooting Steps

Verify VLA

N membership on the access switch ports connected to PCs. Ensure they are in the correct VLAN and untagged. Confirm the trunk configuration between core and access switch allows all necessary VLANs.

Check the default gateway on the access switch if it is Layer 2. If the access switch is Layer 3, ensure IP routing is enabled and proper routes exist. Test connectivity from the access switch to the core switch using ping from the switch itself.

Review AC

Ls on both core and access switches to ensure ICMP traffic is permitted.

Clear ARP and MA

C tables if necessary and retest connectivity. By systematically checking VLANs, trunking, default gateways, routing, and ACLs, you can identify why the core switch cannot ping PCs connected to the access switch and restore proper communication.

The core switch cannot ping the PCs connected to the access switch - FD SOLUCIONES OPTICAL SYSTEMS [PDF]

The core switch cannot ping the PCs connected to the access switch
Core to access switch ping working and access to core is not pinging

Look for me Access switch do not aware the IP coming from Core switch to reach back. so make sure Access switch aware routing setup correctly using ip route command.

A device can be pinged from core switch ( router) but not the switch it

This is likely related to how the vlans are setup with the gateways on the core switch, and the vlan where the mgmt interface is on the edge switch where the device is connected.

Ping Issues on Client and Access Switch

The only difference I see on the core switch is that there is an ACL that permits access from the VLAN we''re trying to ping from, but it''s set to ''ip access-group OUT'' and not ''IN'' as with

I can''t ping to the switch before I ping the core!

If you can reach it from there then it''s probably a firewall/access control issue. If you can''t reach it even from its LAN then it''s possible that the management IP settings on the switch are

Cant ping pc connected to switch

You have the Control and Default overlapping on ports, but as B-rad said, PC ports should be untagged unless you''re configuring tagging on the NICs. That''s an unnecessary step and

A Switch Cannot Be Pinged by a Directly Connected Device

If the switch is directly connected to a PC, apply the traffic policy in the inbound and outbound directions of the interface connected to the PC. If the switch is directly

Unable to ping switch : r/Cisco

If it''s not, then unless the switch has a way to route inter-VLAN traffic, you''re not going to be able to ping it. As a test, I would connect a computer to a free switchport (assign VLAN 1 to that access switch

Troubleshooting VLANs & Trunks

So far we checked VLAN issues on a single switch. When everything checks out with your VLANs and the traffic has to pass one or more switches then you might want to check the trunks.

Cisco Switch Can''t Ping Attached Device

The switch is just another host on a different VLAN. The VLANs are like yards separated by fences. You need a gate (router) to get from one to the other. If you add a VLAN 2 SVI on the

Internet not reaching Core/Access Switch

Router has internet but Core Switch not picking, what i''m i missing? Router and Switch can ping each other Router Configs Router#sh run Building configuration Current configuration :

Crackhead/pass.txt at master · moimikey/Crackhead · GitHub

How to create a web form cracker in under 15 minutes. - moimikey/Crackhead

A device can be pinged from core switch ( router) but not the switch it

I have found that if I do a ping sweep of the whole school IP range for these devices, I do not ret a response from a device. If I ping from the CLI of the connected switch it also fails. If I ping

Can ping a PC from the Switches, but not from my PC

I can ping the TN from all three switches, even the 3560G where my notebook is connected to The VLANs are distributed over the switches using VTP from the core switch All

Cannot ping management interfaces of the new Cisco switches

Hi Friends, My task was to add new switches to the existing environment. So, the Setup is as below. So, i have these 5 new switches which i need to connect to the core Sw. I created all the

switching

Weird thing I encountered is I cannot ping the A5500 (172.16.1.1) when I disconnected port from both switch but work normally when connected. But A3100 is same still cant ping either way.

Solved: unable to access switch management IP, need to ping it first

The odd thing is, after sometime (maybe when the arp age out or mac-address timed out) i can not access the switch remotely or ping it from my workstation. I need to logged in on the core

Solved: Can''t ping host from switch

I configured another interface for that and I connected the new host. These 2 hosts, same VLAN, can ping each other with no problem. 1° problem: from inside the switch I can''t

Re: Pinging of VLANS (Core and Access Switch)

3. However, when I test from a laptop connected to an access switch (set to access mode for VLAN 10), the laptop can only ping its own gateway, and can''t reach other VLANs. For the setup:

Related Video Reference

This video was associated with the source search result. Verify technical details against current product documentation and project requirements.

Technical note

This reference is intended for preliminary fiber and communications infrastructure research. Optical interface, fiber type, port or core capacity, electrical input and output, enclosure protection, cooling, installation limits and applicable standards must be verified for the specific project.

More Optical Connection References

Bring the Connection Schedule into Focus

Send your panel schedule, optical interfaces, patching requirements and quantities by email or WhatsApp.

Discuss the Connection Scope