It looks like your problem may be the firewall route. 1, not to an address on the route itself. we are facinf and issue with ping from access to core core management vlan 98 192. I have the switch plugged into one of the interfaces on the. Cisco access switche...
HOME / The core switch cannot ping the firewall - Estlas Command & Optical Systems
The response traffic will not go via the firewall and will go directly via the switch. This leads to an asymetric routing issue and the firewall will likely drop traffic as it does not see the TCP responses.
Can ping from firewall to hosts, but not hosts to firewall I am setting up a new fortigate 200F and have run into some problems. I can ping from the firewall to any of the hosts inside my LAN, but the hosts
So your pings from the switch should go into the firewall. I would expect the firewall has a 10.1.2.1 interface for the PCs to use as their gateway and that both are setup thus.
With what you have described, I don''t think you have enough data to make a determination. Why is their core a stack of three switches? How does everything connect back to the core? My initial impression
Hi Folks, Interesting issue I am troubleshooting. Back story: Layer 3 Core switch with single fiber trunk ports heading out to multiple Layer 2 access/idf switches. Hosts connected to
Has anyone seen a scenario where and edge switch can reach its core (default gateway) but cannot ping the PC connected locally to that switch. While core switch can ping this PC but edge
You probably need to setup your switch IP as a trusted host on the Forti. No idea why a setting having to do with user authentication would prevent the firewall from responding to ping but there you have it.
I connected a Cisco C3650 switch (port 0/1) to a firewall LAN interface (ip: 192.168.19.2), which is also the default gateway of the switch. Here is the partial config of the switch: (a complete
"access-group MY-INSIDE-ACL in interface inside" Also, does your switch have IP Routing enabled? If the ping is getting to the firewall and you have a good access-list (running packet tracer
These switches are stacked. Everything is working fine. However, a strange issue is being faced i.e. switch is unable to ping its local SVI. The protocol and line protocol of SVI is UP. and
We are in the process of replacing a switch and I am configuring/testing it. For some reason I am unable to get internet to the switch or ping the firewall from the switch. We are using a
I can ping both x440 from the core and the core from them. I also can ping switch 4 from switch 11 but not the other way around. I also can''t ping from or to the pcs. Nor from the same switch
Can you ping your defaut gateway? Sounds like either your default route to the firewall is not correct or being overridden by a more specific route. I would mirror a port on the core grab some packet captures.
I have set up a core stack of 3750 switches (3750e, 3750g, and 3750v1 w/PoE) that seems to be running solid. I connected 2 gigabit trunks from the core to a Front of House switch
I have a frustrating issue where I cannot ping a device located in another subnet (vlan82) from my source subnet (vlan10). Here are the particulars: IP Routing is enabled on core, I can ping
HI, we had a network management machine which we removed long time ago and now i have added another machine which is windows, with same IP but it cannot connect to other switched
This switch connects to an ASA 5505, which has a VPN to three locations: My US data center, my UK data center, and our internet cloud security provider (Zscaler). The strangest issue is happening:
In a nut shell, why can I ping a device at a school on the core switch but not on the switch the device is plugged into or anywhere else in our school district?
Can you temporarily create an SVI for that vlan on the core switch with the IP you are assigning to the firewall interface and test ping from clients. If that works I think that points to
Dear All, I have Core Switch 4506 and i have 2 vlan : vlan 2 : 192.168.1.2 255.255.255.0 vlan 10 : 192.168.10.2 255.255.255.0 and no switchport uplink to firewall router 192.168.100.1 My
I suspect this is a simple routing problem - either the firewall doesn''t have a route back, or the server vlan has an SVI when it does not need one if you expect it to go via the firewall.
You can''t ping the L2-SW1 from the firewall; The config on both L2 switches is the same apart from the below which is in the config for the switch i cant connect to via its public ip address;
172.16.32.1 is the gateway for your subnet but probably isn''t the ip address your core is attempting to ping from. I''m guessing your core switch is attempting to ping from a subnet not allowed across the
I am able to ping between VLANs and my Cisco phones get the IP they''re supposed to get and the pass-through is also working properly and receiving the correct IP. The core switch goes
You are telling the firewall how to get to that network, and the address of the next hop for the network cannot be on the network itself because the firewall doesn''t know how to get to the network where
There is no communication with the device until you ping it from the core switch. My theory is that the core switch is not sending an arp packet in response to an inbound syn packet