Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello Experts ,
I have some strange behavior on FTD as below :
I have nat statement from inside to dmz1 :nat (inside,dmz1) source static obj_10.1.1.11 obj_192.168.2.28and with packet tracer i can confirm traffic sourced from 192.168.2.138 to 192.16...
Hello Expert ,
As per my understanding the FlexConnect with central auth and local switch , will keep the clients "thats already authenticated" connected , however i had the situation where already authenticated users were disconnected from AP when A...
Hello Experts ,
I have a critical application traffic which passing though my Cisco ISR 4321 and i noticed that some packets being dropped as Taildrop ,
Please find below output from packet-trace debug :
sh platform packet-trace summary | i Gi0/0/...
Hello Experts ,
Am trying to configure nat on newly installed fiber connection at GigabitEthernet0 , how ever am getting below error :
(config)#ip nat inside source list 103 interface GigabitEthernet0.10 overload%NAT is not supported on GigabitEther...
Hello Experts ,
I have a weird issue with my ASA , i configured two connection profiles X and Y , both have exact same config , the only difference is the name , when trying to connect to profile X anyconnect will work , however when trying to conne...
The idea of this nat is to forward dmz subnet clients to inside server 192.168.2.28 , so the traffic direction will be from dmz to inside ,
Can you please double check both packet-tracer and check why first one is working fine and the second does not...
Hello MHM,
Please check the nat again :
nat (inside,dmz1) source static obj_10.1.1.11 obj_192.168.2.28
Inside subnet is 10.1.1.0/24 and dmz subnet is 192.168.2.0/24, what is wrong in such nat??
Make sense as logs from WLC ,
But does not make sense the client disconnected from AP , i have to enable AP debugs based on your suggestions during the issue to check what's happening as WLC logs are not that helpful ,
