Releasing WLAN DHCP Lease

I'm using a 100Mbps Airport Extreme on my Verizon FiOS connection. I need to swap it out for another router to debug a problem. Verizon FiOS requires that the current router physically release its DHCP lease before it will hand out another one to the replacement router. Powering down and swapping the routers isn't enough.
Does anyone know how I can do a WLAN DHCP "release" on an Airport Extreme. I can't find any way to do that with the AirPort Utility.
Thanks!

I guess you haven't set any reservations on your AEBS, so you could try setting the DHCP Lease Time down to 1 minute and turn off the connected machines.

Similar Messages

  • 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

  • Self-assigned IP after trying to renew DHCP lease for former network

    Hi all,
    MacBook Pro 15" purchased in Februrary 2008, currently running 10.5.5, up-to-date with patches as of yesterday, 10/20/2008.
    For a few weeks now, I've been consistently unable to connect to wireless networks (secured or unsecured, public or private) after changing networks (i.e. going from home to a coffee shop).
    I have control over my home network router, and its logs show that upon connecting to the network, OS X tries to renew a DHCP lease for the previous network it was on. Upon receiving the "bad network" DHCP reply, instead of releasing the lease and obtaining a new one, the AirPort interface is immediately assigned an IPV4LL address (from 169.254.0.0/16) and no combination of changing network settings, changing AirPort settings, or rebooting will eliminate the old DHCP lease.
    The end result is that my MBP is entirely nonfunctional on some wireless networks that other clients (both Windows and Mac) seem to have no trouble accessing. The problem is quite annoying because I can't connect to access points that (previously) worked fine and whose configurations haven't changed.
    In any case where this problem occurs, an old DHCP lease for a different network (10.0.0.0/8 when trying to get on 192.168.0.0/24 or vice versa) is present, so I strongly suspect a DHCP problem. In all cases, I have perfect connectivity to the access point itself, so problems with the wireless connection parameters (including encryption), or those troublesome problems with 802.11b/g/n interoperation seem highly unlikely.
    One of two things would help me:
    1) Please tell me how to clear the DHCP lease cache. Deleting files from /var/db/dhcpclient/leases does nothing (they appear again upon reboot, identical save for timestamps even after changing network environments, so the cache must be read at boot time and written at shutdown). Selecting "Renew DHCP lease" from the "TCP/IP" tab in the advanced network settings merely attempts to renew the existing lease (for an invalid IP address); it does not appear to release invalid leases.
    2) If this is really how the DHCP client is behaving, change the DHCP client so that upon receiving the "Bad network" response, it releases (or simply abandons) the lease and obtains a new one, rather than immediately assigning an IPV4LL address to the AirPort interface.
    Additionally, is there any documentation on the Apple DHCP client? Under Linux, I could alter dhcpcd parameters to diagnose things like this. I could find no documentation about the Apple DHCP client outside of Mac Help, which wasn't really any help in this case.
    Finally, I do not suspect that this is an instance of the problem discussed in http://discussions.apple.com/thread.jspa?threadID=1352518&tstart=0 as my connection is rock-solid if it can get an IP address when it connects. I've never even seen it hiccup.
    Thanks,
    Matt Z.

    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

  • Releasing unused DHCP IP addresses in OSX Server 10.4

    In OSX Server 10.4.11 is there any way to release unused DHCP client addresses in the Server Admin app? We have 73 clients showing (and only 30 on the network) because various computers have been added to the network and removed/reinstalled at various times, and that means we're running out of available addresses in our little chunk of the subnet.
    We've previously set a longish lease time on DHCP addresses because we've had problems in the past with sleeping Macs being woken up and having clashing IPs with other Macs that have had that IP reassigned to them, but it means that we do have a long list of unused DHCP clients.
    Does Server 10.5/10.6 allow the release of DHCP addresses from the admin app (oh, for a right-click delete!), or is that just not possible in the DHCP protocol (NB I'm trying to release unused IP addresses, not asking live clients to rescind their IP address).

    It's not legal within the DHCP protocol - as far as the server is concerned, that IP address has been handed to the client and should be reserved for that client until the lease expires. The server has no way of knowing whether the client is still using the address.
    You may be able to break the rules, though - the server stores the DHCP leases in /var/db/dhcpd_leases, so you should be able to stop the DHCP server, edit the file to remove the unnecessary leases, then start the server back up. No guarantees, tho'.

  • Cisco 867VAE drops connection on DHCP lease timeout

    Hey!
    We have a very annoying problem on our hands. I'm no IOS expert, but I make do.
    We've got a Telia DSL connection that has a 20 minute DHCP lease timer. Every 20 minutes when it shakes hand again, the connection drops for about 5 seconds. This because the Cisco thinks that administratively shutting down the interface is a good idea....
    How do I stop this behavior? I've tried manually setting <ip dhcp client lease 1 0 0> (for 1 day lease) but it completely disregards that.
    Best would obviously be to stop it shutting down the interface every time, but worst case scenario I'll take a solution with a longer DHCP lease since the address rarely changes.
    <snip from log>
    *Aug  1 01:44:43.514 PCTime: %DHCP-6-ADDRESS_ASSIGN: Interface ATM0.1 assigned DHCP address 81.230.xxx.xx, mask 255.255.255.0, hostname elsa
    *Aug  1 02:04:48.498 PCTime: %DHCP-5-RESTART: Interface ATM0.1 is being restarted by DHCP
    *Aug  1 02:04:56.106 PCTime: %DHCP-6-ADDRESS_ASSIGN: Interface ATM0.1 assigned DHCP address 81.230.xxx.xx, mask 255.255.255.0, hostname elsa
    *Aug  1 02:25:01.050 PCTime: %DHCP-5-RESTART: Interface ATM0.1 is being restarted by DHCP
    </snip>
    It's running firmware c860vae-ipbasek9-mz.153-2
    I'm attaching the current running-config as well.
    Thank you in advance!
    Best Regards
    Daniel

    I'm sorry for not reporting in. The case is closed at Cisco and they simply couldn't do anything. The router does, according to the debug logs, send dhcp renew requests, but the ISP doesn't reply to them. If they get lost on the way, or if there's an incompatability with the ISP, I dunno. I heavily doubt it, since Telia (Swedish ISP) used Cisco gear for pretty much everything.
    Also, Telia will not reply to anything like this, since they don't support equipment they don't supply.
    So I'm completely at a loss, and will remain there until I stumble across something.
    I've received an 887M router though, which I'm gonna test. But I'm currently stuck with the fact that it's not supported anymore, and therefor I can't seem to download new IOS software (it uses a very old one).
    This is the last reply I got before they closed my case:
    *Aug 27 14:56:15.751 PCTime: DHCP Ack Message
    *Aug 27 14:56:15.751 PCTime: DHCP: Lease Seconds: 1200
    *Aug 27 14:56:15.751 PCTime: DHCP: Server ID Option: 213.66.241.86
    *Aug 27 14:56:18.751 PCTime: DHCPD: IP address change on interface ATM0.1
    *Aug 27 14:56:18.751 PCTime: DHCPD: IP address change on interface ATM0.1
    *Aug 27 14:56:18.751 PCTime: DHCP: Releasing ipl options:
    *Aug 27 14:56:18.751 PCTime: DHCP: Applying DHCP options:
    *Aug 27 14:56:18.751 PCTime:   Setting default_gateway to 81.230.121.65
    *Aug 27 14:56:18.751 PCTime:   Adding default route 81.230.121.65
    *Aug 27 14:56:19.751 PCTime:   Adding route to DHCP server 213.66.241.86 via ATM0.1 81.230.121.65
    *Aug 27 14:56:19.751 PCTime:   Adding DNS server address 195.67.199.39
    *Aug 27 14:56:19.751 PCTime:   Adding DNS server address 195.67.199.40
    *Aug 27 14:56:19.751 PCTime: DHCP: Sending notification of ASSIGNMENT:
    *Aug 27 14:56:19.751 PCTime:   Address 81.230.121.83 mask 255.255.255.192
    *Aug 27 14:56:19.751 PCTime: DHCP Client Pooling: ***Allocated IP address: 81.230.121.83
    *Aug 27 14:56:19.803 PCTime: Allocated IP address = 81.230.121.83  255.255.255.192
    *Aug 27 14:56:19.803 PCTime: %DHCP-6-ADDRESS_ASSIGN: Interface ATM0.1 assigned DHCP address 81.230.121.83, mask 255.255.255.192, hostname elsa
    *Aug 27 14:56:25.751 PCTime: DHCP: Client socket is closed
    *Aug 27 15:06:18.759 PCTime: DHCP: Client socket is opened
    *Aug 27 15:06:19.759 PCTime: DHCP: QScan: Bound..T1 fired..Renewing
    *Aug 27 15:06:19.759 PCTime: DHCP: SRequest attempt # 1 for entry:
    *Aug 27 15:06:19.759 PCTime: Temp IP addr: 81.230.121.83  for peer on Interface: ATM0.1
    *Aug 27 15:06:19.759 PCTime: Temp  sub net mask: 255.255.255.192
    *Aug 27 15:06:19.759 PCTime:    DHCP Lease server: 213.66.241.86, state: 7 Renewing
    *Aug 27 15:06:19.759 PCTime:    DHCP transaction id: 914
    *Aug 27 15:06:19.759 PCTime:    Lease: 1200 secs,  Renewal: 600 secs,  Rebind: 1050 secs
    *Aug 27 15:06:19.759 PCTime: Temp default-gateway addr: 81.230.121.65
    *Aug 27 15:06:19.759 PCTime:    Next timer fires after: 00:03:46
    *Aug 27 15:06:19.759 PCTime:    Retry count: 1   Client-ID: cisco-d48c.b524.7b17-AT0.1
    *Aug 27 15:06:19.759 PCTime:    Client-ID hex dump: 636973636F2D643438632E623532342E
    *Aug 27 15:06:19.759 PCTime:                        376231372D4154302E31
    *Aug 27 15:06:19.759 PCTime:    Hostname: elsa
    *Aug 27 15:06:19.759 PCTime: DHCP: SRequest - ciaddr: 81.230.121.83
    *Aug 27 15:06:19.759 PCTime: DHCP: SRequest: 293 bytes
    *Aug 27 15:06:19.759 PCTime: DHCP: SRequest: 293 bytes
    *Aug 27 15:06:30.759 PCTime: DHCP: Client socket is closed
    *Aug 27 15:10:04.759 PCTime: DHCP: Client socket is opened
    *Aug 27 15:10:05.759 PCTime: DHCP: QScan: Renewal..Retrying
    *Aug 27 15:10:05.759 PCTime: DHCP: SRequest attempt # 2 for entry:
    *Aug 27 15:10:05.759 PCTime: Temp IP addr: 81.230.121.83  for peer on Interface: ATM0.1
    *Aug 27 15:10:05.759 PCTime: Temp  sub net mask: 255.255.255.192
    *Aug 27 15:10:05.759 PCTime:    DHCP Lease server: 213.66.241.86, state: 7 Renewing
    *Aug 27 15:10:05.759 PCTime:    DHCP transaction id: 914
    *Aug 27 15:10:05.759 PCTime:    Lease: 1200 secs,  Renewal: 600 secs,  Rebind: 1050 secs
    *Aug 27 15:10:05.759 PCTime: Temp default-gateway addr: 81.230.121.65
    *Aug 27 15:10:05.759 PCTime:    Next timer fires after: 00:01:53
    *Aug 27 15:10:05.759 PCTime:    Retry count: 2   Client-ID: cisco-d48c.b524.7b17-AT0.1
    *Aug 27 15:10:05.759 PCTime:    Client-ID hex dump: 636973636F2D643438632E623532342E
    *Aug 27 15:10:05.759 PCTime:                        376231372D4154302E31
    *Aug 27 15:10:05.759 PCTime:    Hostname: elsa
    *Aug 27 15:10:05.759 PCTime: DHCP: SRequest - ciaddr: 81.230.121.83
    *Aug 27 15:10:05.759 PCTime: DHCP: SRequest: 293 bytes
    *Aug 27 15:10:05.759 PCTime: DHCP: SRequest: 293 bytes
    *Aug 27 15:10:16.759 PCTime: DHCP: Client socket is closed
    *Aug 27 15:11:57.759 PCTime: DHCP: Client socket is opened
    *Aug 27 15:11:58.759 PCTime: DHCP: QScan: Renewal..Retrying
    *Aug 27 15:11:58.759 PCTime: DHCP: SRequest attempt # 3 for entry:
    As pointed to you in my previous mails  renews/packets are being sent and as router is not getting back any reply, lease is timing out and that’s  the reason why the interface is getting flapped. You need to find with ISP  why the renews and rebind packets are not responded to by Providers DHCP server.
    Hope this clarifies your query.
    Thanks and regards,
    Lijesh

  • [Q]: Static DHCP Lease with the WRT54GL...

    Hello,
    I have replaced my old D-LINK router with a WRT54GL wireless router.
    On the old router I could configure static DHCP entries, providing the same IP address to specific MAC addresses (from my different devices at home), and still continue to receive all other settings via DHCP (Like DNS servers that my ISP changes from time to time).
    Using static IP addresses is not an option due that the ISP I'm connected changes the DNS settings frequently and my computers can't connect to the internet. Setting the WRT54GL router as DNS server on my computers is also not practical.
    On the WRT54GL I could not find how to create static (or permanent) DHCP leases.  Is this possible?.. is this in the wish list for future releases of the firmware?
    Thanks in advance.

    Thanks for the quick response.
    I was surprised that this (and maybe other) Linksys routers does not provide this simple feature.
    All DHCP servers I know provide this feature and most of the unmanaged routers that provide DHCP services have this feature. 
    --- Ricky.

  • EA3500 issue, possibily with DHCP lease renewal

    I have a new EA3500 router that's working great for a variety of devices* except a Windows7 laptop.  24 hours after establishing a connection, the laptop loses connectivity and it's very difficult to re-establish a connection.  Usually I have to reboot the router, but 24 hours later the problem returns and Windows is unable to connect. 
    My router settings include DHCP client lease time set to 1440 minutes (24 hours), so I thought the problem might have something to do with DHCP lease renewal.  To test this theory, on Saturday night I did ipconfig/release and ipconfig/renew and established connectivity from the laptop.
    Sunday morning I spoke with Linksys support and changed several settings per their recommendation:
    Network mode mixed (I had it on N-only for some reason)
    Assigned different SSIDs to the 2.4GHz band and 5 GHz band
    2.4 GHz band channel is 20MHz only, using channel 9
    5 GHz band channel is 40 MHz only, using channel 161
    I also power cycled the router. 
    Everything worked fine until Sunday night, 24 hours after the release/renew, when I lost connectivity.  I am not sure what to try next and whether the problem lies with the router or the laptop. 
    * other devices include Macbook, 3 iPhones, iPad, 2 Kindles, printer, DVD player

    If you are only having this problem with the laptop then there is a possibility that the problem might really be with the laptop. What you can do on the router though is to add the laptop on DHCP reservation. In that way, even if the router’s DHCP Lease time will stop, the laptop will still be connected since the laptop will now have a fix ip address.

  • Cisco Phone 7937 DHCP lease issue

    Hi ,
    We have configured DHCP lease id 8 day. But Cisco Conferance Phone 7937 is taking DHCP lease for only 1 day. Can any one know the reason

    Firmware 1.4(5) is available for the 7937. The release notes don't mention your problem, but there are other DHCP fixes in the firmware.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7937g/firmware/english/1_4_5/release_notes/7937_rn_145.pdf
    I haven't seen anything like this with our 7937s. Have you Wiresharked the phone, to be 100% sure what the phone is getting via DHCP is what you think it should be getting?
    GTG
    Please rate all helpful posts.

  • WRV210 DHCP Lease Renewal

    I have been having intermitent connectivity issues with all devices on my network, and I have noticed that the DHCP leases are not renewing on the router.  The only solution I have right now is to reboot the router every day.  Has anyone had this issue, or have any ideas about fixes other than assigning static IP addresses for everything?
    Thanks,
    Mike

    When you noticed that the DHCP lease has not renewed, if you go to a client machine and do a release/renew will it get an IP address then? Check and see if you are on the latest firmware version for your router. If you are having to reboot the router just to have DHCP broadcast acknowledged then you may want to go ahead and give your SBSC a call and open up a case with them.
    You can find your SBSC here.

  • DHCP Lease Break

    I am constantly changing routers and testing my connection. I really want to have a way to get verizon to break my lease without having to go through the call center. Is there a way to do this from my phone or internet somehow?(I can use my phone to access internet)

    I just have to send a giant THANK YOU for this post!  I've been "fighting" with Verizon tech support & reading hour upon hour of documents to get my VPN to work with Verizon's FiOS Westell 9100EM.  I had tried the "bridge" technique along the way & couldn't make it work.  But, somewhere in the back of my head remember reading "FiOS does not need a modem". 
    I used this post to see how to release my DHCP and plugged my trusty old Netgear router directly into the "wall" and everything WORKS!  The wireless speed is much less than FiOS, but I can go back to earning a living from home, so I can deal with that.
    BTW, I did plug Verizon's Westell into a LAN on my Netgear & get wireless speeds a bit better than the Netgear alone. THANK YOU, THANK YOU, THANK YOU, THANK YOU!!!

  • WRT320N static DHCP leases

    hi,
    i have a wrt320n. it runs fine, but i'm in need of static DHCP leases.
    the reason is simple: if one uses static port forwards for applications that doesn't support upnp, and the client gets a different ip than what's specified for the port forwards, it all gets messed up.
    i couldn't find any reference for this feature neither in the manual nor in the router web interface, so i guess it's not possible ATM.
    could you please add support for this (quite basic) feature?
    thanks in advance.
    Solved!
    Go to Solution.

    Well i think the feature which you are trying to look under the linksys router its not possible. I think you need to wait until linksys release the new firmware along with the DHCP Leases.

  • WRT150N DHCP Lease Renewal Lockup

    I have a WRT150N that uses both wireless and wired clients. It is connected to a Roadrunner cable modem that renews DHCP ever 24 hours (approximately at 0545). If one of the clients is in use at that time the WRT150N locks up and will not respond to any of the clients. I have to unplug the WRT150N to restart it. I had a WRT54G previously and this never happened. I've uploaded the newest firmware to no avail and I can't afford having to do a hard restart 3 or 4 times a week. Is there a solution or would it be better to deep 6 this router and go back to what works.

    When you noticed that the DHCP lease has not renewed, if you go to a client machine and do a release/renew will it get an IP address then? Check and see if you are on the latest firmware version for your router. If you are having to reboot the router just to have DHCP broadcast acknowledged then you may want to go ahead and give your SBSC a call and open up a case with them.
    You can find your SBSC here.

  • 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

Maybe you are looking for