I am opening a small branch office in another state and the equipment we purchased is as follows:
ASA5505
3560G.
We'll use a site to site vpn but just in case there's connectivity issues I'd like to use the ASA as DHCP. So far I have a scope defined in the ASA and if I plug a laptop directly in I get an applicable IP address. I trunked the port on the switch that goes to the ASA but not the one on the ASA itself (license restriction) The VLAN that I'm using for my PC's has an ip helper address that is assigned to the inside IP of the ASA.
I am facing an issue with setting up dhcp server on a 3750G-24PS-S,IOS : c3560-ipbasek9-mz.122-58.SE.bin,the switch configuration is below,interface Vlan100 description ***Data Segment*** ip address 192.168.102.1 255.255.255.0 no shut!ip dhcp excluded-address 198.168.102.1 198.168.102.10! ,ip dhcp pool datalan network 198.168.102.0 255.255.255.0 default-router 198.168.102.1 dns-server 192.168.40.11,!,interface GigabitEthernet0/1 switchport access vlan 100 switchport mode access spanning-tree portfast.
I'm using an ASA5505 with dhcpd.but i want to assign a specific IP address from the configured dhcp range to a specific PC.Is it possible to bind a specific ip to this particular PC's MAC address.
Not sure if this is a problem with the switch or the wireless AP connected to the switch, but I have a couple of 3560's, one is a 3560G and the other is a 3560, both have phones and wireless ap's connected to them. The ap's on both of these switches continue to loose there ip address and thus disconnect from the controller. This happens about once a week, but the odd thing is that the phones never loose there ip address. All of my other 3560s and 3560g's that have AP's and phones connected are working fine.
Our company is planning to buy one of cisco ASA 55xx series.But there is still one question left about DHCP pool limitations.Here I found some information about licensing for DHCP on ASA 5505: [URL]In other words, we don't have any information about ASA 5510, which contains DCHP pool licensing.
I found a tricky task for our ASA 5505 firewall. I am not able to go internet when using DHCP but I can access by using fixed IP address in client PC.Same IP, Same Mask, Same DNS, Same Gateway. All the same but no hope. Any configuration i missed in firewall?
I've got a Catalyst 3560G, and I want to reset the current index for a DHCP pool. I could remove the leases given for that pool, but I couldn't find this option.
I have a ASA 5505 that I have been using for a while, but a new ISP is trying to configure my service so that the outside interface has to be configured as DHCP to receive a reserved IP address, and then they will route a separate, non-contiguous block of addresses to that address.
Essentially, they have a DHCP reservation for 1.2.3.4 for my ASA, and then they have 10.2.3.16/28 as a separate block routed to me.
Obviously, I can do my static NAT translations using outside as the address, but I cannot get the separate block of addresses to route through the ASA. Is there a way to do this and get them to work? My ASA is running 7.2(2)
I want to configure multiple DHCP configuration on ASA 5505. I tried to create sub interface for different IP Pool but it was not configure on ASA 5505. is it possible to create subinterface on ASA 5505?
ASA 5505 IOS version: 8.3(1) License: Security Plus
So here's what I think I should do to give email access only to a segment of addresses of my inside network.
1) Create a network object for 62 machines that will represent my dhcp clients.I plan to use 192.168.0.65-192.168.0.126. So I will use address 192.168.0.64 with netmask 255.255.255.192. Then set DHCP server to service this address range.
2) Create an ACL which will Permit Any to use tcp port 110 (pop3) to get to the outside. Which leads me to question #1:
How do I permit the source "Any" to communicate with "Any Less Secure Networks" like the implicit rule that gets zapped once I create new ACL? Is "Any Less Secure Network" implied by the "Any" destination?
3) Create an ACL which will Deny my DHCP range to talk to the outside.
4) Create an ACL which will Permit Any to talk to Any Less Secure Network(essentially recreating the implicit Permit ACL that got zapped).
I am used to setting up access-lists on outside interfaces with ip addresses that are static. I have recently been given a site that is using a dyndns.org client for name to ip address resolution on an outside interface that is dhcp assigned. I created an access-list to open up ports 41794 and 41795 to an engineering application but everytime I try to connect from the outside I get a syn timeout. The application works when inside the lan. Basically I want to allow outside connections from anywhere on the outside to go to ports 41794 and 41795. I am running a Cisco ASA 5505 on version 7.2(4) Below is my conifg. what I may have misconfigured?
: Saved:ASA Version 7.2(4)!names!interface Vlan1 nameif inside security-level 100 ip address 172.31.2.1 255.255.255.0!interface Vlan2 nameif outside security-level 0 ip address dhcp setroute!interface Ethernet0/0 switchport access vlan 2!interface
I have configured DHCP snooping on a WS-3560G-48PS running IOS 12.2(58)SE2 ipservicesk9 variant.When I enable DHCP snooping clients don't get IP addresses, when DHCP snooping is disabled, everything works fine.I have set up a SPAN port and run a capture (attached) on the traffic. Wireshark notes the Seconds elapsed field appeared to be encoded in little-endian but only on some packets. Apart from that, I can see nothing wrong with the DHCP Offer responses from my DHCP server.Attachment config.txt contains the interesting parts of the configuration. Please note g0/32 has been set to ARP inspection trust as without working DHCP snooping it would require a static bind.Is there any way of figuring out which option can't be parsed? Is there a way to force forwarding of unparsable DHCP packets while still running DHCP snooping?
We've just started with the ASA 5505. We do run a DHCP server on the inside interface, so it is in the same VLAN 1 as all of the clients. However, we cannot get it to work.We can't use DHCP Relay, as the ASA 5505 only allows to relay to DHCP servers in a different subnet.Or do we have to move the DHCP server to a different subnet. If so, how would we configure that scenario?
I am having a very strange issue with connecting new machines to reach the internet.We have a ASA 5505 which the previous tech configured the DHCP pool to 192.168.1.60 - 192.168.1.110
We ended up reaching our limit which I changed it to: 192.168.1.60 - 192.168.187
Then next day when I arrived to work, our DC was hung from windows updates. Once we got everything back up, every computer currently on the network can reach the internet/VPN tunnels etc. So (continuing with my day) I created a new server in a VM (Hyper-V)I can ping everything internally (even the router) 192.168.1.1, but I cannot resolve DNS. I have configured a static IP, tried Dynamic IP.I have looked for any ACL indicating to block outside the range of the old DHCP pool but no luck.On my local maching I can ping the DNS addresses, but just not on the new server.
My ASA 5505 has stopped giving out DHCP address to my machines.Everything was working fine and nothing has changed in the network. I've reloaded the firewall and clear all DHCP on the firewall I've even re-entered the cmd on the ASA.
I'm able to staticlly assigned address to the clients and all is way. When I do a DHCP debug on the ASA I don't see any events relating to the DHCP service apart from checking for lease expiry.
I've also tried to plug a machine straight into the ASA and no result. I finally did a packet capture and I am seeing the client machine sending out a DHCP discover packet and nothing else is responding.
My ASA config is:
dhcpd address 192.168.3.10-192.168.3.33 inside dhcpd dns 8.8.4.4 interface inside dhcpd option 3 ip 192.168.3.1 interface inside dhcpd enable inside
Cisco ASA 5505 Security Plus 1 link with PPOE dialup for internet access
desirable situation: Primary link with a PPOE dialup Secondary Link with DHCP address Asignment
Problem: i want to configure Dual ISP Failover modus, but the problem exist when i configure the ip sla syntax it looks good in the running config. but after a reload the secondary line becomes primary
It looks like the ppoe client authentication is busy when the ip sla tracking mechanism becomes active. can i tweak the settings that the ip sla tracking mechanism starts later?
What i the correct config for Dual ISP setup with primary PPOE and secondary DHCP
Since two weeks I have a problem with the VLANs who I started to configure. I hope together we find the way.I have 5 VLANS configured in a CISCO 3560G switch. In my windows server 2003 I configured DHCP scope for each VLAN.One of the requirement to connect vlans each other is to put the IP of each vlan as gateway in the clients.So, how can I do to access to internet?. The ip of my Firewall are in one of the VLAN´s.When the configuration of the LAN only had one DHCP scope the gateway was the ip of my firewall. But now i don´t know how to configure the DHCP server, or the firewall, or the switch, or all of them To get access to internet.
I have an ASA 5505 configured to get a DHCP'd IP address from the ISP on it's outside interface. The problem I am seeing is when the ISP renews their IP address, the ASA 5505 is still holding on to the old IP address information. I have to either manually renew the IP or reload the ASA. I have the potential of rolling out hundreds of these devices and I would not like my customers to have to reboot their ASA everytime the ISP's DHCP lease experies. I am using an easy vpn autoconnecting to an ASA 5520. Static IP's are not an option on the outside interface of the ASA 5505's.
I've got a 5505 and I'm getting a DHCP address from a cable modem. How can I show the DNS that the ASA is getting? show int vlan 2 is only givving me the IP and net mask.
We recently upgraded our 5505s to 8.2(5) 26 and noticed that each will crash after a cerntain amount of time. Some crash every 30 minutes other will crash every 4 to 8 hrs. The only difference would be the user's home ISP and/or home router, if they have one. They are configured with a dynamic dhcp IP address for the outside interface and the crash files starts with the following:When we downgrade back to 8.2(5) 13 the problem goes away. Any known bugs for this version? I haven't been able to find anything yet. We do have one 5505 that does not have this issues. The only thing that may be different is that it was never at 8.2(5) 13. We had downgrade it from a 8.3 version.
I'm running a 5505 with DHCP on the outside interface. All 5505 are connecting to 5545.Can I configure the ASA for a site to site to automactically discover the the peer address and automatically establish a connection with 5545?In other words can I configure all settings for the site to site except the peer address. Once connected on network and get outside DHCP, can it also put that address is the peer section of site to site?
I've been running a cisco asa 5505 for quite some time and it has been running fine, now all of a sudden it starts to renew it's outside dhcp adress like every 2 hours. I dont think it's the ISP since I have another device connected also using dhcp to the same ISP and it doesnt renew itself, it's just the ASA. Rebooting it, makes it pick up an adress straight away. The interface seems to be up, the GUI just reports "no ip adress" and then the ASA get's a new IP after about 10-15 min without one. Pressing the renew IP adress button in the GUI throws an error.
I've been having this issue for about 3 months now, off and on, never seemed to be predictable but started happening more and more, which prompted me to look into it.
Currently, the DSL Modem is configured in bridge mode with the ASA handling PPPoE. The WAN address is being assigned via DHCP. The ASA is running 8.2(1). The WAN interface will drop it's DHCP lease and will not renew it without power cycling the DSL modem. I did a little bit of googling and found mention of setting "dhcp-client client-id interface outside", specifically this was an issue pre 7.2(22), but doesn't seem to affect my situation. Originally, I had the MTU on the outside interface configured as 1500, changing it to 1492 has not resolved my issue either.
I've enabled PPPoE and DHCPC debugging and posted the results below when the event occurs, I'm thinking this is moreso a PPPoE issue than it is a DHCP/DHCP Lease issue as I am not seeing any debug messages from DHCPC.
i have ASA 5505 and have a ADSL modem (hwich has DHCP enabled) 192.168.1.X/24....i have static ip as well which is 34.X.X.X. i want to use ASA as a firewall and want to make site to site VPN..i tried to google it but i cant find any config.i have 4 swicth port in the ADSL modem so shd i connect my ASA with building switch but then it will have DHCP enabled if i disable DHCP on ADSL router then how will my ASA communicate.
I have an ASA 5505 with software version 8.2(1). It is making DHCP requests for IPSec clients that connect to the ASA. The DHCP requests packets the ASA makes have an extra '00' appended to the hostname field, and the length field is the size of the hostname + 1. The DHCP server is Microsoft Server 2003 and this causes the hostname to be registered with an unknown character which appears as []hostname. Then when server 2003 tries to update the DNS record, it fails because of the invalid character in the hostname. Is there anyway to have the ASA have the correct length for the hostname field in the DHCP packet, or a workaround that will solve this problem?
I need to configure public and private wireless access using an ASA 5505 and an Aironet AIR-AP1041N-A-K9. I need to be able to do this via ASDM and http if at all possible. I simply do not have the time to learn hundreds of lines of arcane CLI code. The Aironet connects to the ASA successfully, and receives an IP. I can then connect to the AP wirelessly, but do not receive an IP. I have setup a second SSIDVLAN on the AP, and can't connect to it at all.
We want that inside host should get ip from subnet 192.168.10.0 /24. This ip pool is configured in DHCP server (ip 172.16.10.1) which is connected to ASA2. There is no routing issue as we are able to ping DHCP srever 172.16.10.1 from ASA1. to do config needed on ASA1 and ASA2 , so that host connected to ASA1 inside interface can get ip from DHCP srever. We have configured 192.168.10.1 /24 to ASA1 inside interface which will be gateway to inside host of ASA1.