DLink DCS-950G no DHCP lease given

Hello, I just bought an Airport Extreme to replace my Linksys 54g. Anyways somehow the Airport is not giving my DLink DCS-950G ip camera any DHCP lease. I tried using wireless and wired connection. In wireless, I can see in the logs wireless clients the MAC address of the DCS-950g but I cannot see any DHCP lease.
Since it's pretty much simple in the config, I cannot figure out what's wrong.
I have a Thinkpad T60 and i get a lease on this one.
So pretty much my Airport Extreme is useless.
If I cannot find help and/or solution, I will return the unit to BestBuy and get a refund.
PS: my DLink DCS-950G is working perfectly with my Linksys Router, so I cannot believe it's a problem with this unit.
iMac G5 + Thinkpad T60 Mac OS X (10.4.9)

Thanks for the reply, Chris. Often, the equipment doesn't participate in our DNS. Vendor just needs an IP address. May or may not even DHCP to get it. We wish to create the reservation in DHCP, so it doesn't "get stepped on" down the road. And, we wish to document the assignment in DHCP.
Maybe the Prime IP Express team will have some ideas

Similar Messages

DHCP Lease Reservations in Prime IP Express 8.2

How are enterprise customers keeping track of DHCP Lease Reservations in terms of a description for the device for which the reservation has been created?
In an enterprise, healthcare environment, we make reservations for say - medical vendor equipment. Like many organizations, we have long used an access database containing entries with MAC, IP, description of the device, date created, etc.
CNR customers since versions 2.0 through 6.3.3. Presently migrating to Prime IP Express 8.2. We would like to get rid of our access database/tables and rely exclusively upon features/functions in 8.2. As best I can tell, there's no facility to provide a description - in addition to MAC, IP address, lookup key - for a given reservation. Guessing it isn't in the RFCs.
Do other enterprise customers have this requirement? Thoughts on how they're handling it? Maintain separate information sources in addition to DDI system itself?

Thanks for the reply, Chris. Often, the equipment doesn't participate in our DNS. Vendor just needs an IP address. May or may not even DHCP to get it. We wish to create the reservation in DHCP, so it doesn't "get stepped on" down the road. And, we wish to document the assignment in DHCP.
Maybe the Prime IP Express team will have some ideas

MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

First, let me give you some context:
Framework: MDT 2013 with MS SDK 7.1
Task Sequence: Standard Client TS with sysprep and capture.
Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

I have this issue intermittently as well. For us, it coincided with the deployment of IP phones, which meant PoE switches all around. However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
boot.
As this issue has been intermittent, I've backburnered it. When it does happen, I just wait for the lease to arrive then rerun the wizard.
Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on. Basically, what Keith Garner said. They also disabled PortFast awhile back to see if that made any difference, and it did
not.

TS1388 After one or two websites the search "freezes". To rectify this I need to go into "Network" and press "Renew DHCP Lease" on my imac 10.6.8

After one or two websites the search "freezes". To rectify this I need to go into "Network" and press "Renew DHCP Lease" on my imac 10.6.8TS1317 - Mac OS X: Troubleshooting a cable modem, DSL, or LAN Internet connectionAny help?

Check your computers time and date are correct, and updating to your location via Apple's servers.
WiFi, Internet problems, possible solutions

[SOLVED] Hostname not showing in DHCP lease list

This is a brand new installation using the new systemd base.
Installed openbox as window manager and Network Manager.
What did I miss that the hostname of this computer (opus) is not showing up in the DHCP Leases list?
When I connect to the network using Network Manger(DHCP), hostname is not sent to the DHCP server (DNSmasq). It shows up as a "*":
DHCP leases
Hostname    IP-address    MAC-address    Lease expires
*    192.168.10.100    XX:XX:XX:XX:XX:XX Nov 28th, 19:34
*    192.168.10.59    XX:XX:XX:XX:XX:XX Nov 28th, 19:23
alarmpi    192.168.10.69    XX:XX:XX:XX:XX:XX Nov 28th, 16:56
RM696    192.168.10.97    XX:XX:XX:XX:XX:XX Nov 28th, 18:23
(I blanked out the MAC-addresses.)
The first entry is connecting through wireless. The second is wired.
At the command line:
hostname
opus
hostname -f
localhost.localdomain
/etc/hosts:
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost opus
::1 localhost.localdomain localhost opus
# End of file
What file do I need to change and how?
Updated:
1) I created a /etc/dhclient.conf file and added:
send host-name "opus";
request subnet-mask, broadcast-address, time-offset, routers,
domain-search, domain-name, domain-name-servers, host-name;
and rebooted.
This had no effect.
2) Just for kicks, I uninstalled Network Manager and installed Wicd.
This DID send the hostname and it displayed on the DHCP Leases List. But it also had the effect of turning off the WiFi radio.
I did try to turn it back on: Went to the BIOS, made sure it was on (it was). Read some posts about power savings and what to do (tried them, didn't work).
So I uninstalled Wicd, re-installed Network Manager and I am back to where I was.
Last edited by dastagg (2012-11-29 11:15:11)

Sorry, forgot to add this:
https://bbs.archlinux.org/viewtopic.php?id=152376
Follow the instructions on the bottom.

RV180W firmware 1.0.5.4 DHCP lease problem

Yesterday I upgraded my RV180W to firmware 1.0.5.4. Today the only machine that we have with XP can't get a DHCP lease (we have some 20 machines that can that all have W7 o W8.1). Also none of the iPhones nor Androids that connect via wifi get leases either and thus have fallen back to 3G.

Hello,
First of all I want to say that I'm sorry you are experiencing an issue with the device after the firmware upgrade.
Now, we have tested this device with the new firmware on our lab and we are not experiencing the same issue, which leads me to believe this may be an issue with your particular configuration or network topology.
We would love to have the opportunity to troubleshoot this issue on the Small Business Support Center. If you are still under support with the device, give us a call and we will be happy to assist you.
If you are not able to or are out of support, then please provide as much information as possible in regards to your current configuration as well as network topology, maybe a detailed network diagram could be helpful to so that we can have a better idea of that the issue could be.
I hope this was helpful.

My internet keeps going down and when I try to renew the DHCP lease it stops working altogether

Every couple of weeks my internet would go down, I would be surfing the web and suddenly my connection would fail. I would try renewing my DHCP lease and every time I did I would get an IPv4 address of 192.168.0.100. Originally, restarting the router would fix the problem but the past couple of times they needed a technician from the provider to fix it. Even using the Ethernet cable doesn't work either.
is there a reason why this keeps happening and how do I stop it from happening again? Is there anything I can try to fix it on my end?
my computer is a five year old MacBook, running OS X 10.9.4

Having the same problem. Watched 25 minutes of a rental and it stopped with the message"unable to load video"
Using current version IPad mini.
Ios7 is HUGH PIECE OF CRAP!!!!

How do I revoke a DHCP lease in the 10.8.4 server app?

Hello Everyone,
I have some devices (security cameras) that have successfully requested a DHCP lease. Since then I went ahead and manually created a static reservation for them with a MAC hardware address in the DHCP. For whatever reason they are not switching over to the reserved address. The leases were originally for 1 day. It has been 5 days now. After the first day I switched my lease time to 1 hour. I have done everything short of leaving the devices off for 24 hours.
In Lion server, I could revoke the lease via the gui. No such luck now. My call to Applecare resulted in a "there is no way in 10.8.4 to do this". They said it would switch to the new reserved address after the initial lease period timed out, so I'm hoping the representative was wrong twice. They mentioned a complete lease wipe, but couldn't say if this would cause me to lose my list of reserved static addresses, which isn't an option.
It seems crazy that such a basic feature wouldn't make it into this release of the DHCP service. Any help would be greatly appreciated!

Are there any DHCP queries from the cameras? Check the DHCP server log via Console.app or Server.app (or Terminal.app) for details. (I don't know the 10.8 path to the DHCP logs offhand.)
According to a FAQ over at the Vivotek site, the following is the setup sequence for various recent cameras; the boxes start up in the "I don't have an IP address" self-allocated address block oddly enough, and apparently don't ask for a DHCP address? (You may well be aware of all of this, but this is the block that DHCP clients use when they first communicate with DHCP servers.)
If you are using our new product such as IP7138 / IP7139 / FD7131 / VS7100… etc, no matter your network environment is what, you can always find the camera by Installation Wizard II with the IP address 169.254.x.y.
And then, please double click the camera found by Installation Wizard II or directly type the IP address to your Internet Explorer URL box to access your camera (you do not need to change your PC's IP address). After access your camera, please go to "Network" page to configure proper network settings.
See if the devices are available via mDNS, as well; download the Bonjour Browser and have a look around your LAN. (If you're very lucky, the cameras might be visible and chatting on mDNS.)
Might also try resetting one of the cameras back to factory defaults, and seeing if you can get them to re-ask the DHCP server.
(I've had issues with some HP printers and DHCP clients and IP address assignment, but that's fodder for another discussion. And I also wouldn't rule out a rogue DHCP server, either. I've seen all sorts of unexpected stuff connected to networks over the years...)

WLC2504 clients not receiving DHCP leases

I'm stock with a 2504 using version 7.0.220.0 that won't lease out DHCP adresses
Wifi clients are unable to get a DHCP lease from an external DHCP server.
The WLC are handling 3 WLAN, 2 using internal DHCP server, 1 (that wont work) using external DHCP. The external DHCP server, is a router/firewall (out of my reach) that suffered from a power out, a short while ago, ever since the DHCP is not working on that VLAN, if client are getting static ip adresses, everything works fine. If i'm using the same network link, and plug it into a computer, I get a DHCP address.
I've enable DHCP proxy
Debbuging DHCP, using: Debug DHCP packets enable
Gives me this:
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP received op BOOTREQUEST (1) (len 308,vlan 20, port 1, encap 0xec00)
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option len (including the magic cookie) 72
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: message type = DHCP INFORM
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: 12 (len 1) - skipping
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: 55 (len 13) - skipping
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP options end, len 72, actual 64
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->srcPort 68, op: 'BOOTREQUEST')
Thanks

Hi Steen,
When a client is in DHCP REQ state on the controller, the controller drops DHCP inform packets. The client will not go into a RUN state on the controller (this is required for the client to pass traffic) until it receives a DHCP discover packet from the client. DHCP inform packets are forwarded by the controller when DHCP proxy is disabled.
Please check this, if still u r facing issue then provide more info.
Can you please paste a client debug of the client having DHCP issues.
Go to cli of the wlc and run the client debug . Diconnect the client then reconnect and gather the output and post.
Regards

N82 does not correctly process DHCP leases

I have no problem attaching my new N82 to my, and friends, home wireless networks. However, it fails to connect to the Univeristy Campus network giving the error: "Web: No gateway reply!"
This is because the phone doesn't correctly process DHCP leases with the 'network of one'' (2545.255.255.255) subnet mask.
Campus network details:
HP WAP 530 enterprise access point. The DHCP server is an ISC dhcp server giving out ip address in the standard private class C address range (192.168.1.0) with a subnet mask of (255.255.255.255), and a default route of 192.168.1.1.
This works on Windows 2000/XP/Vista and MAC OSX, but many embedded devices will not add the default route as they see it as outside their subnet. Many institutions use 255.255.255.255 to mitigate inter host communication.
This means I cannot use my N82 at work and I'm not happy. Beware, don't assume you can use your Nokia device at work.

If task manager says it's still running, then obviously it hasn't completed, contrary to what you said. Maybe this .exe process isn't written correctly. For example, maybe it is dependent on the current directory it is launched from, and so double-clicking it causes it to be launched from the directory it lives in, but when run from this java app, the working directory is somewhere else.

Continually have to renew DHCP lease

Occasionally my MBP will loose wireless connection. It often happens when my phone accesses the wireless Linksys router.
Every time it happens, I open network preferences, go to Advanced and "Renew DHCP Lease" and it fixes it.
Almost looks like I could use a script or something to make it renew DHCP lease when wireless disconnects.
Any ideas?

BoyHowdyDoo wrote:
Try another router. They are cheap.
I guess they're cheap for most people who are happy overspending for Apple products.
Usually not a problem with your Mac.
None of my other non-Apple devices have any problem connecting.
I really appreciate you being one of the few trying to help. My negative comments come from my frustration at Apple.

Need to renew dhcp lease often

to use the internet (wireless network) i must renew the dhcp lease every time i click a link or open a window. ive reset internet preferences and removed filesharing software. any ideas?

I also have the same problem and it started off small and it took me much trial and error to discover that only by renewing the DHCP lease every time I wanted to open a page could I still surf the net. My internet service provider first suggested that I try rebooting everything and I did -that worked for 5 minutes...then it was back to square one...I spoke with apple they were surprised that it was happening and gave me the option of paying for an over the phone trouble shooting diagnostic explaining that it could be the network card. For some reason last night everything worked perfectly without having to renew the lease.. and then this morning I am once again having to renew with every page. I did try an IP program called IPNETMonitorX but was quickly confused/overwhelmed with tech babble...
Has anyone solved similar issues?

Needing to Renew DHCP Lease every five minutes to stay online

I experienced ALL the networking and DNS problems since my Leopard install, but adding OpenDNS servers to my router cured the problem. For two months, anyway. Now, in the last week, I've got problems again, and now the only thing that cures the suddenly dead network connection is to simply Renew DHCP Lease. Instantly my connection works again. But I'm needing to do this LITERALLY every five or ten minutes. Once I do this, it returns me the same IP address (as my router is set to do so), and all works again. Monitoring outbound network activity, I can see continuous failed requests to resolver1.openDNS.com and resolver2.openDNS.com. Barring waiting until 10.5.2, which we all hope resolves these problems (hur hur), any ideas?

I have had wireless problems intermittently for a year, and seriously for 6 weeks. Apple denied the issue and was no help in spite of many tens of thousands of people on their own discussions complaining. I found a post suggesting a couple of things which fixed the problem. I don't know if both are necessary, but the first by itself does not solve the problem.
Lock the channel of your router to channel 1, apparently Apple and 802.11n don't play well together on higher channels. When this becomes a standard this will be resolved I hope.
Open your network preferences, select 'airport' and advanced. Delete unused networks. Select your network.
Open TCP/IP and write down all the settings, configure iPv4 manually. Enter the settings manually. Turn off IpV6.
Open DNS and write down your DNS server. Delete it and re-enter it manually.
This has worked on 2 macbooks and an iMac for the last 3 weeks with no network drops.
Joe Shea
Philadelphia

DHCP lease for Guest Wireless network

Is there a "rule-of-thumb" for the lease of DHCP on a guest or general use wireless network. The standard user is expected to be relatively transient. Thanks in advance for the comments / help.

I think ther no such rule of thumbs in a wireless network but the networks that incorporate large numbers of mobile devices, such as laptops and wireless telephony devices, should be configured with shorter DHCP lease times (for example, one day) to prevent depletion of DHCP-managed subnet addresses. Mobile devices typically use IP addresses for short increments of time and then might not request a DHCP renewal or new address for a long period of time. Longer lease times will tie up these IP addresses and prevent them from being reassigned even when they are no longer being used.

DHCP Server is not passing out DHCP Leases

I can't seem to figure out why DHCP server is not passing out DHCP lease a client?
Also I can't seem to figure out why NVI0 interface is UP? I have setup another box similarly and NVI0 is down on that and the DHCP server is working fine on that too. Strange!
I am working on CISCO 881 VPN Router...Please have a look at it and let me know. Thanks
Here is the configuration in the box...
sh run
Building configuration...
Current configuration : 6543 bytes
! Last configuration change at 17:09:54 CST Fri Sep 14 2012 by XXXXX
version 15.0
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname XXXXX
boot-start-marker
boot-end-marker
logging buffered 51200 warnings
aaa new-model
aaa authentication login default local
aaa authentication login vpn_xauth_ml_1 local
aaa authentication login sslvpn local
aaa authorization network vpn_group_ml_1 local
aaa session-id common
memory-size iomem 10
clock timezone CSTime -6
clock summer-time CST recurring
crypto pki trustpoint TP-self-signed-3079619067
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3079619067
revocation-check none
rsakeypair TP-self-signed-3079619067
crypto pki certificate chain TP-self-signed-3079619067
certificate self-signed 01
30820252 308201BB A0030201 02020101 300D0609 2A864886 F70D0101 04050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 33303739 36313930 3637301E 170D3132 30393134 31393231
32375A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D33 30373936
31393036 3730819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
8100993C D622004B F3AEA1E5 81106C28 36EC52D0 5435ABC3 8912095F 3641168A
B67D97AF AEB43CF3 00A00EB5 702FA355 9F58EBEF F42294DC 0E32CF40 E17D372A
3BC36401 55EDBA5C 910B7A51 89D709A8 7EAB3FF0 E4C99D34 CBE3F316 069C0E16
BC284055 35E3D762 463DABF6 852C4E7A D2EF45A4 21F08689 4DF17870 9E2A6C27
1BFB0203 010001A3 7A307830 0F060355 1D130101 FF040530 030101FF 30250603
551D1104 1E301C82 1A506F70 6C617276 696C6C65 2E796F75 72646F6D 61696E2E
636F6D30 1F060355 1D230418 30168014 64EA4CAE 2029E4C2 702584C6 B5732464
5C9DA38A 301D0603 551D0E04 16041464 EA4CAE20 29E4C270 2584C6B5 7324645C
9DA38A30 0D06092A 864886F7 0D010104 05000381 81006C27 96E06B83 04DBDA81
EEB0AF35 84ED370E A8C9694E F9B9326D 69CB1043 9C396D7B 760D252F 4881926D
878E434F 9AFC3E6D A5BF43F2 E619D6EC F45C039A 5FFB478F A99F7EE5 274E37D5
11976FDE 823FD1A9 700203E5 67A329B3 F4CF45F0 245757C8 E2349276 B13414D1
017616FA 38A40BA8 42545AC5 C7676D21 29E4F491 CADB
        quit
ip source-route
ip dhcp excluded-address 10.10.10.1
ip dhcp excluded-address 192.168.1.1 192.168.100.101
ip dhcp excluded-address 192.168.1.254
ip dhcp pool ccp-pool
   import all
   network 10.10.10.0 255.255.255.248
   default-router 10.10.10.1
   lease 0 2
ip dhcp pool Internal_Network
   network 192.168.1.0 255.255.255.0
   dns-server 192.168.100.254
   default-router 192.168.1.254
ip cef
ip domain name yourdomain.com
ip name-server 192.168.100.254
no ipv6 cef
license udi pid CISCO881-K9 sn FTX1604828T
username XXXXX privilege 15 secret 5 $1$QEcR$96cmvs/h/.05G6BnorcWG/
username XXXXX secret 5 $1$PQQ1$3.Vin0i/2uZ/KD0xEJ8GC.
crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
crypto isakmp policy 2
encr 3des
hash md5
authentication pre-share
group 2
crypto isakmp client configuration group YYYYYYY
key XXXXX_XXXXX_XXXXX
pool VPN-Pool
acl VPN-Access-List
crypto isakmp profile vpn-isakmp-profile-1
   match identity group YYYYYYY
   client authentication list vpn_xauth_ml_1
   isakmp authorization list vpn_group_ml_1
   client configuration address respond
   virtual-template 2
crypto ipsec transform-set encrypt-method-1 esp-3des esp-sha-hmac
crypto ipsec profile VPN-Profile-1
set transform-set encrypt-method-1
interface FastEthernet0
interface FastEthernet1
interface FastEthernet2
interface FastEthernet3
interface FastEthernet4
description WAN_INTERFACE
ip address 192.168.100.3 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
interface Virtual-Template2 type tunnel
ip unnumbered FastEthernet0
tunnel mode ipsec ipv4
tunnel protection ipsec profile VPN-Profile-1
interface Vlan1
description VLAN1_INTERFACE
ip address 192.168.1.254 255.255.255.0
no ip redirects
no ip unreachables
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
ip local pool VPN-Pool 192.168.1.151 192.168.1.200
ip forward-protocol nd
ip http server
ip http access-class 23
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip nat inside source list 100 interface FastEthernet4 overload
ip nat inside source static tcp 192.168.1.100 21 192.168.100.3 21 extendable
ip nat inside source static tcp 192.168.1.100 80 192.168.100.3 80 extendable
ip route 0.0.0.0 0.0.0.0 192.168.100.254
ip access-list extended VPN-Access-List
permit ip 192.168.1.0 0.0.0.255 any
permit tcp host A.B.C.D host 192.168.1.100 eq ftp
permit tcp host A1.B1.C1.D1 host 192.168.1.100 eq ftp
permit tcp host A2.B2.C2.D2 host 192.168.1.100 eq ftp
permit tcp 192.168.1.0 0.0.0.255 host 192.168.1.100 eq ftp
permit tcp host A3.B3.C3.D3 host 192.168.1.100 eq ftp
permit tcp any host 192.168.1.100 eq XXX
access-list 23 permit 10.10.10.0 0.0.0.7
access-list 23 permit 192.168.1.0 0.0.0.255
access-list 100 permit ip 192.168.1.0 0.0.0.255 any
no cdp run
control-plane
banner exec ^C
% Password expiration warning.
Cisco Configuration Professional (Cisco CP) is installed on this device
and it provides the default username "cisco" for one-time use. If you have
already used the username "cisco" to login to the router and your IOS image
supports the "one-time" user option, then this username has already expired.
You will not be able to login to the router with this username after you exit
this session.
It is strongly suggested that you create a new username with a privilege level
of 15 using the following command.
username <myuser> privilege 15 secret 0 <mypassword>
Replace <myuser> and <mypassword> with the username and password you
want to use.
^C
banner motd ^C XXXXX-XXXXX VPN Router ^C
line con 0
exec-timeout 30 0
logging synchronous
no modem enable
line aux 0
line vty 0 4
access-class 23 in
privilege level 15
password 7 124A50424A5E5550
transport input telnet ssh
scheduler max-task-time 5000
end

Hi Jennifer,
I have gotten it resolved. Per your suggestion, I have turned on debug ip dhcp events and found that POOL EMPTY message. After little research, I found out that I have made a mistake in my excluded-address range.
I have had it as
ip dhcp excluded-address 192.168.1.1 192.168.100.101
It should have been
ip dhcp excluded-address 192.168.1.1 192.168.1.101.
It was a typo.
Thank you for the suggestion.
Srini

DLink DCS-950G no DHCP lease given

Similar Messages

Maybe you are looking for