Unable to get ip address from DHCP server for Aironet 1130AG Access Point

I have a network in which DHCP server is enabled. I have read the installation guide also there it is mentioned that 1130G Access point will not have any staic ip assigned to it.So it will automatically get the ip from the DHCP server from the network. I have connected that from the network but it is unable to get the ip address from the same. The same thing i have configured in the netgear it is coming fine. I have seen the sonic wall and used the IPSU tool also from checking the ip address from Mac Address but i am not able to get the same. Please provide me some tips to check where i am wrong in configuration because the first web page also not coming because of the ip address.

narendra,
I would suggest that the AP be connected to a laptop or desktop pc that would run a local dhcp server with a small scope setup...plenty of free ones on the web(this pc would obviously not be connected to your currnet network). This way you can watch the dhcp server hand the AP it's address (this can take a few minutes). Once you have the address use it to access the GUI and give the AP a static address (I find it good pratice to give all my autonomous AP's static addresses for ease of troubleshooting)...Hope that helps.

Similar Messages

Unable to get IP address from DHCP

hi all,
I have a AP1131 which cannot get IP from DHCP server. I have tried to configure static IP address and controller IP by lwapp command and the AP can successfully joined the controller. However, after I changed it to DHCP in WLC, it cannot get IP address and all lwapp config is gone. It cannot join the controller anymore only after I reset it and configure a static IP for it. The following error message appears after I changed it to DHCP in the WLC:
*Mar 7 08:44:36.511: RESETTING THE STATIC IP ADDRESS: LWAPP goes back to discovery
%WIDS-6-DISABLED: IDS Signature is removed and disabled.
%LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
%LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
%LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
%LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
%LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
%LWAPP-3-CLIENTERRORLOG: Config Command: error verifying sequence number
Any expert has some idea on it?
Thanks.

Is that AP on the same subnet as the other AP's? The thing is, when you configure the AP with static information, you say the AP is able to join the WLC. This means that there is no issue with the AP. Now when you set the AP to use DHCP and not static, the AP does not obtain a DHCP address? Is that correct? If you have more than one AP on the same switch and on the same vlan, and only one has an issue, then maybe reset that AP to default and see if that fixes it. I'm also assuming that the vlan is being forwarded and you have enough dhcp address in the scope.

Unable to get IP address from DHCP since upgrading

Hi all,
I upgraded my machine to Mountain Lion last night. Ever since then I have been unable to get any IP information using DHCP. Each time I hit Renew Lease within the Network control panel I just get back a self assigned IP address. If I look in the system logs I see the following generated each time my machine tries to look for the DHCP server:
Jul 26 01:32:27 Lightning.local configd[22]: bootp_session: bind port 68 failed, No route to host
Jul 26 01:32:27 Lightning.local configd[22]: bootp_client_open_socket: S_get_bootp_socket() failed, No route to host
Jul 26 01:32:27 Lightning.local configd[22]: bootp_client_bind_socket_to_if(en1, 6): session socket isn't open
Jul 26 01:32:27 Lightning.local configd[22]: bootp_session_transmit: neither bpf nor socket send available
Jul 26 01:32:27 Lightning.local configd[22]: bootp_client_bind_socket_to_if(en1, 0): session socket isn't open
Jul 26 01:32:28 Lightning.local configd[22]: bootp_session_delayed_close(): socket is already closed
I've tried rebooting, clearing the PRAM, deleting Prefs, etc, but nothing seems to have worked.
Anyone any ideas what is going on or what else to try? It used to work perfectly before I upgraded.
Thanks

I am also having this problem since I upgraded to Mountain Lion. I did an upgrade from Lion, not a clean install. I had done a clean install of Lion though. In my case, the network connection is working most of the time, but it is droping one a day. Deactivating the Ethernet and the Wi-Fi adapters and reactivating them does not help.
Here is my what I am getting in the console when I have lost internet connection and I try to renew the DHCP lease:
2012-08-30 6:13:59.158 PM configd[17]: bootp_session: bind port 68 failed, No route to host
2012-08-30 6:13:59.158 PM configd[17]: bootp_client_open_socket: S_get_bootp_socket() failed, No route to host
2012-08-30 6:13:59.158 PM configd[17]: bootp_client_enable_receive(en0): failed
2012-08-30 6:14:00.158 PM configd[17]: bootp_session_delayed_close(): socket is already closed
And I get a self assigned IP.
I hope Apple will have a fix for this soon!
Cheers!
JF

IPad wont get IP address from DHCP Server

I have an enterprise WPA2 PEAP MSCHAPv2 wireless network. It allows access via 802.1x authentication using Radius (MS IAS Server) with certificates. I can join the network, enter credentials (that I can see work) and get the certificate. The problem is that I don't get an IP address. I get a 169. APIPA address. I tried to use a static IP address and that doesn't work either. I have connected various laptops, iPhones even a Dell Streak to this wireless network without issue. My iPad won't get an IP at all. There are plenty of addresses in the pool.
The setup is a 3COM WX3008 wireless LAN controller and 9552 access points.
Any ideas? I went through the articles on wireless settings and none of them help at all. I guess my next step is to wipe the iPad.
Like I said... EVERYTHING else works, every other device we try is surfing just not the iPad.

I see what you are trying to say but in this case its just not true. There is a problem with the iPad. Moving away from the most secure wireless technology or changing my "router" isn't a reasonable solution. We are using a current production model enterprise wireless LAN controller with lightweight access points. Its running its latest code. Its not the Free After Rebate model from the local B&M.
Again, when everything BUT the iPad works (iPod/iPhone/laptops of varying OS & vendor are all good) its not the routers fault. While downgrading my network may work it is not a reasonable solution to a problem with only the iPad.
Of course I don't like hearing it. I am here to hopefully find someone else with the same issue or get some tips that lead to a solution so the next google searcher will land on a solution.

AP gets always a new IP address from DHCP server

Hello,
When an access points doesn't find a controller it gets always a new IP address from DHCP server.
Does anyone know, why?
thanks

Hi,
From what I know this is to do with DHCP option 60 and 43.Normally when APs request for IP address, DHCP Server also returns the management IP Address of WLC if the VCI matches.
If the VCI sent by the AP does not match with the one configured under DHCP for that particulart AP type, the DHCP will never return the WLC IP and hence AP can not find the controller.And the AP keeps sending DHCP Req and sometimes end up getting two IP addresses!
So may be you can check VCI on DHCP server for that AP model.
Let me know.
Cheers

DHCP client fails to get an valid IP address from DHCP server. windows 8.1

I have a win 8.1 Pro 64 bit pc in my office .I'm trying to connect it to my wireless cisco router with either wireless or hardwired connection but I get an error in the event viewer with discription DHCP error 1007. and Ip address showing
169.254.93.17 but our dhcp range is 192.168.1.x
Log Name: Microsoft-Windows-Dhcp-
Source: Microsoft-Windows-Dhcp-Client
Date: 23/Jun/2014 12:03:21 PM
Event ID: 1001
Task Category: Address Configuration State Event
Level: Error
Keywords: (1)
User: LOCAL SERVICE
Computer: sanddeplap.vts.com
Description:
Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0xF4B7E22D8721. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its
own from the network address (DHCP) server.
Event Xml:
<Event xmlns="http://schemas.">
<System>
<Provider Name="Microsoft-Windows-Dhcp-
<EventID>1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>75</Opcode>
<Keywords>0x4000000000000001</
<TimeCreated SystemTime="2014-06-23T08:03:
<EventRecordID>363</
<Correlation />
<Execution ProcessID="988" ThreadID="7932" />
<Channel>Microsoft-Windows-
<Computer>sanddeplap.vts.com</
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="HWLength">6</Data>
<Data Name="HWAddress">F4B7E22D8721<
<Data Name="StatusCode">121</Data>
</EventData>
</Event>
I tried to track issue with microsoft network monitor I'm attaching the capture file also please help me to sort out this issue
capture report https://onedrive.live.com/redir?resid=AFE3D0245A92F6F8%21183

The issue is that your machine is not being assigned an IP address / was unable to reach the DHCP server to receive one. The 169.254.x.x IP your machine is showing isn't assigned from DHCP, it's assigned by the local machine and is referred to as an APIPA
address.
So something is preventing your machine from reaching your DHCP server, which could one of a number of things. In the first instance I'd suggest having a look at
http://epan36.blogspot.co.uk/2012/09/eventid-1001-dhcp-your-computer-was-not.html which lists several of things that could cause this error and things you can try in order to resolve it.
If none of those work, can you confirm whether you have any other machines connecting via the same method on the network, which might indicate whether this is an issue at the machine end or somewhere between the machine and DHCP server?

APs unable to receive IP address from DHCP (core 6500 series switch)

Dear Friends,
a week ago I had stable wireless network APs were getting IPS from 6500 series switch (DHCP) but unfortunately some WISM got rebooted and now APs are unable to receive IP address from Core 6500 DHCP, to cater this issue I have another DHCP server configured on windows 2008 i created another subnet and and put APs in that vlan now all APs are are successfully receiving IPS from windows DHCP server I don't know why APs are not able to receive IPs from core 6500 series DHCP.
please advice
Thanks
Faysal

Thanks george for stepping up here is DHCP config
ip dhcp excluded-address 10.10.30.1 10.10.30.20
ip dhcp excluded-address 10.10.8.1 10.10.8.10
ip dhcp excluded-address 192.168.10.1 192.168.10.5
ip dhcp excluded-address 10.9.20.1 10.9.20.30
ip dhcp pool vlan_30
network 10.10.30.0 255.255.254.0
default-router 10.10.30.1
option 60 ascii """"""""""""""""""""""""CiscoAPc1250""""""""""""""""""""""""
option 43 hex f110.0a0a.1e0b.0a0a.1e0d.0a0a.1e0f.0a0a.1e11
dns-server 10.10.2.11
lease infinite
ip dhcp pool WiSM1_SP
network 192.168.10.0 255.255.255.248
default-router 192.168.10.1

DHCP Server Assignment - Aironet 1130AG

I am attempting to configure a Cisco Aironet 1130AG to use a Windows Server 2003 DHCP server for assigning addresses to clients connecting to the access point. Does anyone know how to set this option? I cannot find it anywhere.
Any help will be greatly appreciated.

I'm having more or less the same problem but mine is even more low level than this. I have three 1130ag's that were setup in as PEEP authentication. The PEEP was proving to be a problem for whatever reason and we decided to go with WEP authentication and have the 1130's be regular old APs. Well apparently they can't or won't do that. I set one up as a standalone AP and it actually worked for about three weeks giving out DHCP addys to laptops then one day decided it wouldn't anymore. So I reset it using the MODE button and put the same information back into the device. Now it will allow clients to connect but never gives them a DHCP addy. We don't have and never had a Cisco Wireless controller and these have been working as PEEP WAPs for well at least a year or so. Why won't they simply give out DHCP to the clients?

AVAYA IP Phones unable to get an IP address from DHCP server.

I installed new SRW208P switch and I mada an uplink connection with SRW 2024 switch (using GE port).
when I am trying to connect AVAYA IP Phone to the SRW208P port, the set trying to get an IP address from the DHCP server and failed to get it.
some times after 10 minutes, it get the IP address, but all the machines (PCs) connected to the same switch (SRW208P) hange.
Note: the PCs an IP Phones are connected with separate UTP cables to the access switch.
Is there any suggestions to solve this issue, please.
Regards,

The issue is that your machine is not being assigned an IP address / was unable to reach the DHCP server to receive one. The 169.254.x.x IP your machine is showing isn't assigned from DHCP, it's assigned by the local machine and is referred to as an APIPA
address.
So something is preventing your machine from reaching your DHCP server, which could one of a number of things. In the first instance I'd suggest having a look at
http://epan36.blogspot.co.uk/2012/09/eventid-1001-dhcp-your-computer-was-not.html which lists several of things that could cause this error and things you can try in order to resolve it.
If none of those work, can you confirm whether you have any other machines connecting via the same method on the network, which might indicate whether this is an issue at the machine end or somewhere between the machine and DHCP server?

Trouble getting IP address from DHCP-enabled router

I've recently set up a LinkSys WRT54G wired/wireless router on a home network that has a wired Windows XP machine and a wireless PowerBook with AirPort.
The WRT54G assigns network addresses using DHCP. The PowerBook is able to find the wireless network established by the WRT54G, but doesn't get an IP address from it.
The router seems to be behaving correctly, so I'm guessing there's a problem in the PowerBook setup somewhere. Any ideas?

Double-check your AirPort's settings:
System Preferences > Network > Show > Network Port Configurations
- Verify that an AirPort option exists. If it does not, click "New" to create one. (Note: If you are unable to create an AirPort configuration, the AirPort card in your computer either doesn't exist or it is not recognized.)
- Verify that AirPort is "On" (checked)
- Verify that AirPort is at the top of the list. If it isn't, you can drag it to the top.
Systems Preferences > Network > Show > AirPort
AirPort tab
- By default, join: Automatic
TCP/IP tab
- Configure IPv4: Using DHCP
- Configure IPv6: Automatically or Off
Proxies tab
- Configure Proxies: Manually
- Select a proxy server to configure: <All proxies should be unchecked unless you specifically require a proxy for Internet access.>
- Exclude simple hostnames (unchecked)
- Bypass proxy settings for these Hosts & Domains: <leave blank>
- Use Passive FTP Mode (PASV) (checked)

I get no ack from dhcp server when using a fresh install of archlinux

Here is the dhcpcd -d eth1 log output
eth1: using hwaddr 00:a5:5d:03:25:b0
dhcpcd[1028]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd[1028]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd[1028]: eth1: broadcasting for a lease
dhcpcd[1028]: eth1: sending DISCOVER (xid 0xef2c208), next in 3.76 seconds
dhcpcd[1028]: eth1: offered 146.66.2XX.YY from 146.66.2AA.ABC
dhcpcd[1028]: eth1: sending REQUEST (xid 0xef2c208), next in 4.35 seconds
dhcpcd[1028]: eth1: sending REQUEST (xid 0xef2c208), next in 7.94 seconds
dhcpcd[1028]: eth1: sending REQUEST (xid 0xef2c208), next in 15.13 seconds
dhcpcd[1028]: eth1: sending REQUEST (xid 0xef2c208), next in 32.22 seconds
but when I connect the same port, eth1, to a router, and the router to the "internet connection", the router gets an ip and dhcpcd -d eth1 gets a 192.168 address and is all fine.
Weird isnt it?
What could this be?
Last edited by antonikus (2012-11-12 08:39:09)

Hi,
sadly not able to really help you, but It seems that I'm having the same problem.
I'm running an up to date arch install (with testing enabled) and for some strange reason one of the dhcp servers I use does not ever return any packets at all to me.
Openwrt on my home network works like a charm, but here in the office I do not get an ip (or any reply at all sadly) from our dhcp server. I don't know what server we're running though ...
kind regards

Linksys X3000 - get internal IP from DHCP server

Hi,
I have Linksys X3000 router. I would like to use it as a wireless AP. I have disabled the NAT and the DHCP, but is it possible to set the routers ip from an other DHCP server. When I set up the router it always asks for it's own IP address.
The other server is connected on one of the LAN sockets. The WAN socket is not used. Thank you for the reply.
András

The router (X3000) uses a static IP address. Even if you disable its DHCP server and NAT, you will still have to assign it a Local IP address. The computers/devices that are connected to the X3000 will get their IP addresses from the main router's DHCP server but the X3000 will have to use a static IP address that you will assign to it. If the main router's IP address is 192.168.1.1, give the X3000 and IP address of 192.168.1.x.
This article for Cascading routers may help. Check the steps for cascading routers via LAN to LAN.

Router connected to cable modem by Ethernet port cannot get IP address from DHCP.

I have an ethernet cable on Fa0/0 connecting my 1841 router to my cable modem. The issue is that the router cannot obtain an IP address via DHCP when I have the "ACL-OUTSIDE-IN" ACL applied inbound on the Fa0/0 interface. I tried to allow all BOOTP and BOOTPS traffic in my ACL, but still no luck. I really don't want to run the router without a simple ACL firewall and connect it to the internet. When I take off the ACL off of Fa0/0, the router is able to get an IP address via DHCP.
Router#sh run
Building configuration...
Current configuration : 10736 bytes
! Last configuration change at 18:14:42 MST Fri Nov 16 2012 by matt.chan
version 12.4
service nagle
service timestamps debug datetime msec localtime show-timezone year
service timestamps log datetime msec localtime show-timezone year
service password-encryption
hostname Router
boot-start-marker
boot system flash:c1841-advipservicesk9-mz.124-25f.bin
boot-end-marker
logging count
logging userinfo
logging buffered 1048576 informational
enable secret 5 <removed>
aaa new-model
aaa authentication login AUTH-LOCAL local-case
aaa session-id unique
memory-size iomem 25
clock timezone MST -7
ip cef
ip nbar pdlm flash:directconnect.pdlm
ip nbar pdlm flash:citrix.pdlm
ip nbar pdlm flash:bittorrent.pdlm
ip nbar custom steam destination udp range 27000 27030
ip nbar custom rdp destination tcp range 3389 3391 55402
ip domain lookup source-interface FastEthernet0/0
ip name-server 8.8.8.8
ip inspect name fa0/0_inspect_ou icmp router-traffic timeout 10
ip inspect name fa0/0_inspect_ou ftp timeout 300
ip inspect name fa0/0_inspect_ou udp router-traffic timeout 120
ip inspect name fa0/0_inspect_ou tcp router-traffic timeout 300
login block-for 60 attempts 4 within 60
login quiet-mode access-class ACL-ACCESS-QUIET
password encryption aes
crypto pki trustpoint TP-self-signed-1755372391
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-1755372391
revocation-check none
rsakeypair TP-self-signed-1755372391
crypto pki certificate chain TP-self-signed-1755372391
certificate self-signed 01
3082023F 308201A8 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 31373535 33373233 3931301E 170D3132 31313137 30313130
35325A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D31 37353533
37323339 3130819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
8100D53F 9EB5B123 3103A4D5 82E786F7 F91C2DE5 9E409A22 80AF78F6 812F624A
89FE9103 73C4AAAB 13FF880D F628607D 6888AC49 18BEDD77 778F0DB1 F9A796E9
E92717CD 6DD19450 5066620A 91278C33 E38349EA 92B8C671 80761609 0AC46E6F
2C8C6BCF ABC7E1F7 A64BD28C C85477FE B23F8A7C 555ECDF9 CE461B8D 6C017370
0ED70203 010001A3 67306530 0F060355 1D130101 FF040530 030101FF 30120603
551D1104 0B300982 074E5543 4C455553 301F0603 551D2304 18301680 146CA2E0
936C651F E2ED4DCD D7025FF3 2AB029E0 95301D06 03551D0E 04160414 6CA2E093
6C651FE2 ED4DCDD7 025FF32A B029E095 300D0609 2A864886 F70D0101 04050003
8181004A AFA4D07C 1424DE0E EF3F17F2 BB1EA63B CB17C13D 1AEA31A1 BAB6AF77
DB6EA8A2 2117DCD1 5530A18C 3618D568 CC7EF520 E039ACBD DA906352 BB7E51BD
0954490C B2AB30C2 FBBE4738 C214BE1C CB63FFEA BAFC46E0 3DC419EE 714B9ABD
144A21E3 3E54C103 FF47FAF1 412FE5C4 59ACD1FE FD72356B C8DC04C3 E2EDF275 45954C
quit
username <removed secret 5 <removed>
ip ssh maxstartups 10
ip ssh time-out 60
ip ssh authentication-retries 2
ip ssh port 2226 rotary 1
ip ssh version 2
class-map match-all Zuri-YouTube-Class
match access-group name NAT-Pool-Zuri-WLAN
match protocol http host "*youtube.com*"
policy-map PMAP-QOS-VTI-IN
description QOS FOR TU0
class class-default
shape peak 1512000
policy-map PMAP-QOS-VTI-OUT
description QOS FOR TU0
class class-default
shape peak 512000
crypto isakmp policy 1
encr aes 256
authentication pre-share
group 5
lifetime 43200
crypto isakmp key 6 <removed> address <removed>
crypto isakmp invalid-spi-recovery
crypto isakmp keepalive 10 5 periodic
crypto ipsec transform-set EDGE-TS ah-sha-hmac esp-aes 256
crypto ipsec profile EDGE
set security-association lifetime kilobytes 256000
set transform-set EDGE-TS
set pfs group5
interface Loopback0
no ip address
interface Tunnel0
description "VTI Link"
bandwidth 4000
ip address 172.20.0.2 255.255.255.0
ip mtu 1400
ip nbar protocol-discovery
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1360
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 7 12090011003E5A0C0F186E752220211B4A
keepalive 10 5
tunnel source FastEthernet0/0
tunnel destination <removed>
tunnel mode ipsec ipv4
tunnel path-mtu-discovery
tunnel protection ipsec profile EDGE
service-policy output PMAP-QOS-VTI-OUT
hold-queue 75 out
interface FastEthernet0/0
description "Link to ISP"
bandwidth 4000
ip address dhcp
ip access-group ACL-OUTSIDE-IN in
no ip proxy-arp
ip nbar protocol-discovery
ip nat outside
ip inspect fa0/0_inspect_ou out
ip virtual-reassembly
ip ospf cost 1
duplex auto
speed auto
no keepalive
no cdp enable
interface FastEthernet0/1
description "Link to LAN"
ip address 172.16.0.1 255.255.255.248
ip access-group ACL-INSIDE-IN in
no ip proxy-arp
ip nbar protocol-discovery
ip nat inside
ip virtual-reassembly
ip ospf cost 1
ip ospf priority 255
duplex auto
speed auto
no keepalive
router ospf 1
log-adjacency-changes
redistribute static subnets
passive-interface default
no passive-interface Tunnel0
network 172.20.0.0 0.0.0.3 area 0
ip forward-protocol nd
ip route 10.0.0.0 255.0.0.0 Null0 name "Class A Private"
ip route 172.16.0.0 255.240.0.0 Null0 name "Class B Private"
ip route 172.17.0.0 255.255.0.0 FastEthernet0/1 172.16.0.2 name "Home WLAN"
ip route 172.19.73.31 255.255.255.255 Null0
ip route 172.27.0.0 255.255.0.0 Tunnel0 172.20.0.1 name "IPsec GRE Tunnel"
ip route 192.168.0.0 255.255.0.0 Null0 name "Class C Private"
ip route 192.168.0.0 255.255.255.0 Tunnel0 172.20.0.1 name "VLAN 70"
ip route 192.168.100.1 255.255.255.255 FastEthernet0/0 70.162.0.1 permanent name "CABLE MODEM MANAGEMENT"
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0 dhcp 253
ip dns server
no ip http server
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip nat translation tcp-timeout 300
ip nat translation udp-timeout 120
ip nat translation max-entries 2048
ip nat inside source list ACL-NAT-172.16.0.0/29 interface FastEthernet0/0 overload
ip nat inside source list ACL-NAT-MANAGEMENT interface FastEthernet0/0 overload
ip nat inside source static tcp 172.16.0.4 22 interface FastEthernet0/0 2227
ip nat inside source static tcp 172.16.0.5 3389 interface FastEthernet0/0 3391
ip nat inside source static tcp 172.16.0.3 3389 interface FastEthernet0/0 3390
ip nat inside source static tcp 172.16.0.4 80 interface FastEthernet0/0 8084
ip access-list standard ACL-ACCESS-QUIET
permit 216.161.180.16
permit 172.16.0.0 0.1.255.255
permit 172.27.0.0 0.0.127.255
permit 172.20.0.0 0.0.0.3
ip access-list standard ACL-NAT-172.16.0.0/29
permit 172.16.0.0 0.0.0.7
ip access-list standard ACL-NAT-172.17.0.0/24
permit 172.17.0.0 0.0.0.255
ip access-list standard ACL-NAT-172.17.1.0/24
permit 172.17.1.0 0.0.0.255
ip access-list standard ACL-SNMP
permit 172.16.0.4
ip access-list extended ACL-CRY-MAP
ip access-list extended ACL-INSIDE-IN
deny   ip host 172.16.0.2 172.27.0.0 0.0.127.255
deny   ip host 172.16.0.2 172.20.0.0 0.0.0.3
permit ip 172.17.0.0 0.0.0.255 any
permit ip 172.16.0.0 0.0.0.7 any
permit ip 172.17.1.0 0.0.0.255 any
ip access-list extended ACL-NAT-MANAGEMENT
permit tcp host 172.27.10.11 eq 3389 host 72.166.77.196
ip access-list extended ACL-OUTSIDE-IN
deny   ip 10.0.0.0 0.255.255.255 any
deny   ip 172.16.0.0 0.15.255.255 any
deny   ip 192.168.0.0 0.0.255.255 any
permit tcp any any range 3390 3391
permit udp any any eq bootpc
permit udp any any eq bootps
permit tcp any any range 2226 2228
permit tcp any any range 8081 8084
permit icmp any any echo
permit icmp any any net-unreachable
permit icmp any any host-unreachable
permit icmp any any port-unreachable
permit icmp any any parameter-problem
permit icmp any any packet-too-big
permit icmp any any administratively-prohibited
permit icmp any any source-quench
permit icmp any any ttl-exceeded
deny   icmp any any
deny   ip any any
ip access-list log-update threshold 10
logging history informational
logging trap debugging
logging 172.17.228.17
logging 172.17.228.10
control-plane
line con 0
exec-timeout 15 0
privilege level 15
logging synchronous
login authentication AUTH-LOCAL
line aux 0
login authentication AUTH-LOCAL
line vty 0 4
exec-timeout 60 0
privilege level 15
logging synchronous
login authentication AUTH-LOCAL
rotary 1
transport input ssh
scheduler allocate 20000 1000
ntp clock-period 17178311
ntp source FastEthernet0/0
ntp server 148.167.132.201
end

Hi Matt,
Try adding below line
ip access-list extended ACL-OUTSIDE-IN
permit udp any eq bootpc any eq bootps
Regards
Najaf
Please rate when applicable or helpful !!!

Phones not getting IP address via DHCP server on same VLAN

Hello....we have a new series of Cisco SF-200s and one new Cisco SF-300. All switches are operating in layer 2 mode currently. Let's say for all intents and purposes, all ports are in VLAN1....pretty much default setup. There is a fiber backbone between uplink ports...and it is working correctly it appears.
There is a DHCP server allocating addresses 192.168.0.60 thru 192.168.0.79. Subnet mask is 255.255.255.0.
PCs and laptops successfully receive an IP address and can access things.....such as surfing the internet. Tested that from multiple switches....all seems to work just fine.
However, it seems that some newly purchased phones (Digium models) simply will not acquire an IP address like the PCs and laptops do.
Pretty broad question....but just wondering.
Thanks!

Hi Greg,
Might be interesting to goto the following sections of the GUI disable the discovery protocols;
1. Administration>Discovery -LLDP >properties
2. Administration>Discovery -CDP >Management interface
3 Smartports >Properties > Admministrative Auto Smartports is disabled.
the switches are real smart and may pre-empt what you are trying to achieve.
regards dave

Wireless Router 877W users cannot get ip address from DHCP

Users can connect to wireless but they cant get ip address what can be the problem ?
Thanks
no aaa new-model
resource policy
ip subnet-zero
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 10.10.10.1
ip dhcp excluded-address 192.168.239.1 192.168.239.50
ip dhcp pool users
   network 192.168.239.0 255.255.255.0
   default-router 192.168.239.1
   dns-server 4.2.2.2
bridge irb
interface ATM0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
interface ATM0.1 point-to-point
no snmp trap link-status
pvc 8/35
pppoe-client dial-pool-number 1
interface FastEthernet0
interface FastEthernet1
interface FastEthernet2
interface FastEthernet3
interface Dot11Radio0
no ip address
encryption vlan 1 key 1 size 40bit 0 1234567890 transmit-key
encryption vlan 1 mode wep mandatory
ssid wirele
    vlan 1
    authentication open
    guest-mode
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
channel 2437
station-role root
interface Dot11Radio0.1
encapsulation dot1Q 1 native
no snmp trap link-status
no cdp enable
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Vlan1
description $ETH-SW-LAUNCH$$INTF-INFO-HWIC 4ESW$
ip address 192.168.239.1 255.255.255.0
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
bridge-group 1
bridge-group 1 spanning-disabled
interface Dialer1
ip address negotiated
ip nat outside
ip virtual-reassembly
encapsulation ppp
ip tcp adjust-mss 1452
dialer pool 1
no cdp enable
ppp authentication pap callin
ppp pap sent-username xxxx password xxx
crypto map MerkezVPN
interface Dialer0
no ip address
interface BVI1
no ip address
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1

go into config t and add "bridge 1 route ip" and see what you get....

Unable to get ip address from DHCP server for Aironet 1130AG Access Point

Similar Messages

Maybe you are looking for