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.
My WAN IP address is 72.X.X.X and the public IP addresses provided by the ISP is 200.X.X.X subnetMy secondary ISP WAN IP is 33.X.X.X and the public IP addresses are in the same subnetThere is a web server in the DMZ, which does not work when I set th...
Hello again,What worked in test environment failed in liveThe FTD is in production but I am unable to access LAN devices from the DMZ network. Can someone guide me in the right direction please, this is a bit urgent The DMZ interface is in switch mod...
Hello all,None of the zones are able to resolve DNS. I can ping 8.8.8.8 from LAN and DMZ but cannot ping google.com. The DNS policy under policies > DNS is defaultDNS server group under Objects > Object Management has all the ISP provided DNS servers...
Hello all,I have setup my FTD to be managed by the FMC. When I tried to access the CLI through COM port, the password isnt accepted.Do the CLI access gets disabled if the FTD is managed by the FMC?
Hello all,I am configuring an SPF port (1/9) on Cisco 3105 as the LAN interface which connects to the Nexus 5000.The IP on 3105 interface is 192.168.255.209/30 and the IP on Nexus interface is 192.168.255.210/30.Both ports are up and online but I am ...
Hello @Karsten Iwen The ISP is routing the 200 subnet to the firewall. I ti was working on the ASA but not in FTDI added "arp permit-nonconnected" but that didnt help
@Marius Gunnerud The migration ignored a few NAT rules and that caused the issue. I did thorough check between the ASA and the FTD and found the missing NAT rules. Added them to the FTD and name resolution started working.
The test I conducted today1. The DMZ interface IP on the FTD is 10.11.11.1/24 and a computer in the zone is 10.11.11.2/24. I ran nslookup google.com 8.8.8.8 and got a reply2. The LAN interface IP on the FTD is 10.10.10.9/30 and the nexus switch is di...
