About HopelessATvlans

HopelessATvlans · 11-01-2022

Hi all,So long time reader first time poster. I have inherited a bit of a mess and mish mash of a network. My main issue is that I can not ping a subnet (VLAN300) 192.168.0.0/23 from the server stack 172.25.1.0 (VLAN200) however I can ping fine the o...

HopelessATvlans · 11-01-2022

Hi George, They run a mix of Server 2016 & 19. All firewalls are off internally in windows and AV is defender.

HopelessATvlans · 11-01-2022

from 192.168.1.97 to 172.25.1.15

HopelessATvlans · 11-01-2022

Trace from 192 to 172 DCover a maximum of 30 hops:1 1 ms 8 ms 3 ms 192.168.1.2542 1 ms 2 ms 2 ms swndc01.domain.local [172.25.1.15]Trace complete.Trace fails other way. 192.168.1.254 is the core stack I sh run above

HopelessATvlans · 11-01-2022

I would agree with you however all devices can access the internet fine and 192 subnet can ping and connect to the 172 subnet fine. the fact that works proves two way as the eho needs a reply, I just dont know why its one way.

HopelessATvlans · 11-01-2022

Hi! Thanks for your reply! The GW for both subnets are 172.25.1.253I do think the Access Control is done on the fortinet especially with the rule that is set. I am ware of setting up the SVI as its a 24h business and I dont want to make live changes ...

Member Since	‎11-01-2022 03:07 AM
Date Last Visited	‎11-02-2022 12:52 AM
Posts	6

User Statistics

User Activity

Inherited VLAN mess - one way ping

Re: Inherited VLAN mess - one way ping

Re: Inherited VLAN mess - one way ping

Re: Inherited VLAN mess - one way ping

Re: Inherited VLAN mess - one way ping

Re: Inherited VLAN mess - one way ping