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.

Similar Messages

  • DHCP lease issue for PPPoA sessions when using external DHCP server

    We used to use the Cisco 7206VXR's DHCP server to hand out leases, and when we lost several hundred customers on a link, the router was able to get them up and connected with an IP address within minutes.
    We switched over to using an external DHCP server so we could have more control over some extended DHCP options, as well as to aggregate all our DHCP traffic. Now, if we lose 100 DSL customers all at once, it takes 90 minutes for them to come up again. They come in a few at at time, until all 100 are back.
    We see waves of RADIUS auth's in our RADIUS log (RADIUS has always been handled externally, so nothing changed there), and continuous streams of DHCP requests come in and DHCP offers go out. What seems to be happening is that a whole bunch of modems auth with RADIUS, request IP addresses, but for whatever reason, timeout when they don't all get their lease, drop the connection, and retry the whole process all over again. We purchased a dedicated DHCP server, thinking that was the bottleneck, but performance is about identical.
    Here's our config:
    interface Virtual-Template1
    ip unnumbered Loopback11
    ip helper-address a.b.c.d
    peer default ip address dhcp
    ppp authentication pap
    ppp ipcp dns a.b.c.d e.f.g.h
    ppp ipcp unique-address
    My questions are:
    - is there any performance issue with using an external DHCP server and PPPoA
    - is there anything in our config that would cause such delays
    Frank

    GP:
    No, the DHCP server is not across a WAN link; there is only a 10/100 switch in between the router and the DHCP server. There are no dropped packets on the interface.
    I ended up opening a case with TAC about this issue. While I had the helper address configured in the template, TAC recommeneded that I specify the actual DHCP server with the command "ip dhcp-server x.x.x.x". This eliminates the DHCPBROADCAST (which I've verified). Perhaps the DHCP relay portion of the Cisco router is performed serially, instead of in parallel. By that, I mean, the next DHCPBROADCAST won't go out until there is the response for the first DHCPBROADCAST.
    I'll know in a few days when we test again.
    Frank

  • WLC 5508 Internal DHCP server issues

    Hi,
    I am hoping to get your feedback around the dhcp issues I am facing with Two Centrally Switched Wireless LANs. I have tried to explain the setup and the problems below and would appreciate it if anyone can suggest a solution for the problems I am facing:
    The setup is as follows:
    - I have a WLC 5508 which has been configured with 4 SSIDs, out of which 2 are using Central Authentication and Switching.
    - I have an LWAP connected to the WLC in HREAP mode.
    - WLC is configured as the DHCP server for clients connecting to the SSID 'Guest'. For the rest, I am using external dhcp server.
    - Only one scope for Guest Interface is setup on the WLC. 
    Problems:
    1. As far as I know, for WLC to act as internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to SSID 'Internet' are
    unable to get an ip address from the external dhcp server, if dhcp proxy is enabled on the WLC. If i disable the proxy, it all works fine.
    2. DHCP does not release the ip addresses assigned to clients even after they are logged out.
    3. If a machine which was earlier connected to 'Guest' SSID connects to the 'Internet' SSID, it requests the same ip it was assigned by the WLC which it was assigned under 'Guest', but gets tagged with the Vlan configured on the management interface.  
    ************Output from the Controller********************
    (Cisco Controller) >show sysinfo
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller
    Product Version.................................. 7.0.116.0
    Bootloader Version............................... 1.0.1
    Field Recovery Image Version..................... 6.0.182.0
    Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
    Build Type....................................... DATA + WPS + LDPE
    (Cisco Controller) >show interface summary
    Interface Name                   Port Vlan Id  IP Address         Type        Ap Mgr        Gu                                                                            
    est
    guest                                        1    301      10.255.255.30    Dynamic   No              No                                                                            
    management                          1    100      172.17.1.30        Static          Yes            No                                                          
    service-port                              N/A  N/A      192.168.0.1       Static         No               No                                                                            
    virtual                                        N/A   N/A      10.0.0.1              Static         No               No                                                                            
    (Cisco Controller) >show wlan summary
    Number of WLANs.................................. 4
    WLAN ID  WLAN Profile Name / SSID               Status    Interface Name
    1        LAN                                    Enabled   management
    2        Internet                               Enabled   management
    3        Managment Assets          Enabled   management
    4        Guest                                  Enabled   guest
    (Cisco Controller) >show dhcp detailed guest
    Scope: guest
    Enabled.......................................... Yes
    Lease Time....................................... 86400 (1 day )
    Pool Start....................................... 10.255.255.31
    Pool End......................................... 10.255.255.254
    Network.......................................... 10.255.255.0
    Netmask.......................................... 255.255.255.0
    Default Routers.................................. 10.255.255.1  0.0.0.0  0.0.0.0
    DNS Domain.......................................
    DNS.............................................. 8.8.8.8  8.8.4.4  0.0.0.0
    Netbios Name Servers............................. 0.0.0.0  0.0.0.0  0.0.0.0
    (Cisco Controller) >show interface detailed management
    Interface Name................................... management
    MAC Address...................................... e8:b7:48:9b:84:20
    IP Address....................................... 172.17.1.30
    IP Netmask....................................... 255.255.255.0
    IP Gateway....................................... 172.17.1.1
    External NAT IP State............................ Disabled
    External NAT IP Address.......................... 0.0.0.0
    VLAN............................................. 100
    Quarantine-vlan.................................. 0
    Active Physical Port............................. 1
    Primary Physical Port............................ 1
    Backup Physical Port............................. Unconfigured
    Primary DHCP Server.............................. 172.30.50.1
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... Yes
    Guest Interface.................................. No
    L2 Multicast..................................... Enabled
    (Cisco Controller) >show interface detailed guest
    Interface Name................................... guest
    MAC Address...................................... e8:b7:48:9b:84:24
    IP Address....................................... 10.255.255.30
    IP Netmask....................................... 255.255.255.0
    IP Gateway....................................... 10.255.255.1
    External NAT IP State............................ Disabled
    External NAT IP Address.......................... 0.0.0.0
    VLAN............................................. 301
    Quarantine-vlan.................................. 0
    Active Physical Port............................. 1
    Primary Physical Port............................ 1
    Backup Physical Port............................. Unconfigured
    Primary DHCP Server.............................. Unconfigured
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... No
    Guest Interface.................................. No
    L2 Multicast..................................... Enabled
    (Cisco Controller) >show dhcp leases
           MAC                IP         Lease Time Remaining
    00:21:6a:9c:03:04    10.255.255.46    23 hours 52 minutes 42 seconds        <<<<<<< lease remains even when the client is disconnected.
    *********Example of Client connected to the right Vlan with an ip address from the incorrect interface. *************
    (Cisco Controller) >show client detail 00:21:6a:9c:03:04
    Client MAC Address............................... 00:21:6a:9c:03:04
    Client Username ................................. N/A
    AP MAC Address................................... a0:cf:5b:00:49:c0
    AP Name.......................................... mel
    Client State..................................... Associated
    Client NAC OOB State............................. Access
    Wireless LAN Id.................................. 2                 <<<<<<<<   'Internet' SSID
    BSSID............................................ a0:cf:5b:00:49:ce
    Connected For ................................... 319 secs
    Channel.......................................... 36
    IP Address....................................... 10.255.255.46      <<<<<<< IP address assigned from the 'Guest' Interface or dhcp scope on the WLC
    Association Id................................... 1
    Authentication Algorithm......................... Open System
    Reason Code...................................... 1
    Status Code...................................... 0
    Session Timeout.................................. 1800
    Client CCX version............................... 4
    Client E2E version............................... 1
    QoS Level........................................ Silver
    802.1P Priority Tag.............................. disabled
    WMM Support...................................... Enabled
    Power Save....................................... OFF
    Mobility State................................... Local
    Mobility Move Count.............................. 0
    Security Policy Completed........................ Yes
    Policy Manager State............................. RUN
    Policy Manager Rule Created...................... Yes
    ACL Name......................................... none
    ACL Applied Status............................... Unavailable
    Policy Type...................................... N/A
    Encryption Cipher................................ None
    Management Frame Protection...................... No
    EAP Type......................................... Unknown
    H-REAP Data Switching............................ Central       <<<<<<<<<
    H-REAP Authentication............................ Central       <<<<<<<<<<
    Interface........................................ management
    VLAN............................................. 100           <<<<<<<<<<< right Vlan
    Quarantine VLAN.................................. 0
    Access VLAN...................................... 100

    Hi All,
    I have a similar issue where Wireless clients are not receiving automatic addressing from an internal DHCP server. I have multiple interfaces configured on the WLC which are connected to separate VLANS. The manually specified DHCP primary server entry is the same on all interfaces. Some clients are able to authenticate and receive automatic IP configuration but some clients are failing the address assignment process. I have checked connectivity between the WLC and DHCP server, this is confirmed as working. When I carry out a "debug dhcp packet enable", I get the following outputs which seems as if the DHCP discover request from the client is skipped. Your thoughts and inputs on this are appreciated.
    DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: message type = DHCP DISCOVER
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 116 (len 1) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 61 (len 7) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: requested ip = 169.254.223.5
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 12 (len 13) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: vendor class id = MSFT 5.0 (len 8)
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 55 (len 11) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 43 (len 2) - skipping
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP options end, len 76, actual 68
    *DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP Forwarding DHCP packet (332 octets) packet DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
    Thanks,
    Raj Sandhu

  • Cisco WLC DHCP upgrade issues

    Hi,
    I've discovered an issue with our WLC 4400 series controllers when we do firmware upgrades (recently moved to 6.0.199) it seems to reset the dhcp server on the controller but the Access points still retain their old IP until the lease runs out (48hrs). This means that any AP's requesting a new lease often get an IP conflict for the first 48hrs after the upgrade and we experienced areas where AP's wouldnt connect.
    Is this a common issue and is there anyway to get the AP's to request a new address from the controller?
    thanks,
    Matt

    Hi Matt,
    When you do a WLC upgrade, a WLC reboot is required, this results in the DHCP lease table getting restarted as well.
    Solution:
    1-Setup an external DHCP Server to overcome this.
    2- Restart the access points, so they request a new IP address.
    This is mentioned on WLC release notes 6.0.199.0 that you are running, it is for clients, for the rule still applies:
    Link
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn6_0_199.html#wp581125
    Internal DHCP Server
    When clients use the controller's internal DHCP server, IP addresses are  not preserved across reboots. As a result, multiple clients can be  assigned the same IP address. To resolve any IP address conflicts,  clients must release their existing IP address and request a new one.
    The same also applies on newer releases such as 6.0.199.4 and 7.0.
    Have a good day.
    Serge

  • 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

  • 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.

  • 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.

  • 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?

  • Cisco SPA502 G - DHCP & Call problem

        Good day.
         I have many cisco spa 502G phone in my network which working correctly. But one phone doesn't working via DHCP. If I using static IP, I can ping phone, or login in on web-interface, but when i was trying upgrade firmware through Firmware Updater, I see error - upgrade failed, No Response From Spa. Phone firmware version is 7.4.3a .
         End the most important problem is that phone can't work correctly with my asterisk-server. If i receive call from anybody, i can do this only system keys nearly phone-screen. I can't call from this telephone ((
    Please, community help, and sorry for my english

    Hello Sergey,
    To wich firmware do you want to upgrade? For some firmwares you have to do this in steps, you can not go directly to 7.5.4 form the frimware that you are using.
    When you put the phone back to DHCP can it be that the phone tries to get an ip adres that is allready in use. Chek the DHCP pool etc to check the leases. At our office some phones say that they are initializing network for a long time and when we check the problem is that the phone wants to get an ip adres that is allready in use.
    You can check your other phones web ui to see if an duplicated ip adres is causing the problem that you can not use the phone with DHCP.
    Kind Regards
    Richard

  • DHCP Renew Issue with Road Runner

    I have had Road Runner for 6 weeks, the first four weeks everything was running smoothly. However, for the last two weeks the connection has been sporadic and I am constantly losing my connection.
    My computer is connected directly to the modem with an ethernet cable; there is no router, there are no other computers. I'm simply trying to stay online with my little computer.
    My network settings are for built-in ethernet, using DHCP, with the addresses provided by my ISP (Road Runner) and I've added two DNS server addresses for Road Runner (because several other discussions, posts, etc. recommended using those to help stay connected). I've tried turning my IPv6 off, I've tried manually configuring my DHCP connection, I've scoured the internet for help. All to no avail. Most topics deal with networking with PC's or airports and I have neither attached to this computer. I've created new locations to try and "erase" any default settings and I've kicked the modem a few times (accidentally I assure you ).
    From what I can tell, (keep in mind I sell trees and know nothing about this) the DHCP lease does not renew when it's supposed to. I am disconnected every half hour or so, or I have to press "renew" to be able to stay online (highly annoying).
    When I first subscribed to Road Runner the connection was fine and I was able to stay online indefinitely. Two weeks ago that changed, even though I did nothing (intentionally) to change network settings. This means I downloaded nothing that would affect my network configuration, I didn't poke around in network configurations, I did not change any settings. I've spoken with their online "tech" support four times. I've spoken to three people on the phone and I've had a tech come out to replace my modem and ethernet cable. When the problem persisted I contacted them again and was told the problem was with Apple <gasp>.
    I believe I need help in finding a way to have my mac recognize changes in DHCP and to renew the lease automatically, for all I know it could be that the moon isn't aligned with Saturn <shrug>...preferably in vernacular I can understand. Thank you in advance for any help!
    Lori

    Hi Lori,
    You're not really in the right forum for your problem (this area is for Apple-server) but I'll give it a go...
    First, short explanation on DHCP. This process is pretty straightforward for the client's function so I'm suspicious of the "blame the mac" conclusion from Road Runner (although does not exclude possibility). When the mac starts up, it issues a 'Discovery' broadcast, looking for a DHCP server. The server responds with an 'Offer' of an IP address. The client then responds with a 'Request' to the server for the same IP address and the server then sends an 'Acknowledgement' that it may use this address, along with other information including the 'Lease Time' - how long the client may continue to use that info.
    The lease time is important. After 50% of this time has gone, the client will attempt to renew it from the same server by issuing another Request and awaiting another Acknowledgement. Should there be no Acknowledgement, the client will continue to issue Requests up until the expiry of the original lease time at which point it will drop all the info which it received from the server and then issue another Offer broadcast, looking for a new server (which may or may not be available).
    So, first thing, lets see what lease time you are getting from Road Runner and see if this corresponds with the 30 minutes you seem to get from a session...
    Ensure you have a cable connection to your router, restart computer. In Applications-> Utilities, start up Terminal. Enter the following line, ending with normal 'return' key (new line)...
    ipconfig getpacket en0
    That's a zero at the end.
    Look for the line similar to this, "lease_time (uint32): 0x1bd8", and post back the string of chars you get at the end of your line (corresponding to the "0x1bd8" part). Quit the Terminal utility.
    Can you also confirm what computer model you use, and the system version?
    -david
        Server 10.4.8

  • E3000 DHCP server issues?

    I recently purchased an E3000 and immediately upgraded to the latest firmware version,1.0.03 build 2 Sep 7, 2010 . I've noticed a few issues with the DHCP server.
    First, some entries appear to drop out of the DHCP client table before their DHCP lease expires. This has happened with several Windows 7 clients and with a pair of Linksys WRT54GS routers that obtain their IP addresses from the DHCP server in the E3000.
    Second, I have two Netgear GS108Tv2 switches attached to the E3000. When these switches are running firmware version 5.0.0.8 they can obtain IP addresses from the E3000, but I can't access them using a web server. When these switches are running firmware version 5.0.1.11 they fail to obtain IP addresses from the E3000. I suspect the DHCP client in these two devices has a problem and I have reported this behavior to Netgear, but I believe the DHCP server in the E3000 may also be part of the problem. Why? Because I connected the switches to one of the WRT54GS routers mentioned above and they were able to obtain IP addresses from the DHCP server in the WRT54GS, which is a model 7.0 running firmware versionv7.50.8 build 001, Oct. 5, 2009  .
    Finally, a question regarding DHCP reservations with the E3000. When creating a DHCP reservation, does the assigned IP address have to come from the scope of addresses assigned to the DHCP server? For example, I have configured the start IP address for the DHCP server in the E3000 to be 192.168.1.64 and the maximum number of users to be 64. However, I have created reservations for IP addresses 192.168.1.10 and 192.168.1.20 for the two WRT54GS routers mentioned above. I have also created a reservation for two clients within the assigned range as well. All assignments appear to be working correctly, but I would like to confirm that both approaches are kosher.
    Thanks in advance.

    On 04/27/2011, I opened a case with LinkSys/Cisco support concerning lost DHCP Client Table entries on both my new E3000 V1.0 router (running firmware upgrade 1.0.4) and it's WRT54G V8.0 predecessor.  After several days of using WireShark capture traces, I was able to determine the entries were being dropped when an application on one of my four WinXP/SP3 systems sends a "DHCP Inform" packet to the router.  The E3000 (and WRT54G V8.0) responds with correct IP Lease information but deletes the client's entry from it's DHCP Client Table in the process.  My problem was supposedly referred to the support team in Irvine, CA about a week ago, after I discovered what was causing the table drop, but I have not heard from the Irvine team yet.  I will follow up on Monday for a status update. 
    Oddly enough, the "triggering application" is MicroSoft's AutoUpdate process.  Once I configured MS AutoUpdate from "Check but do not download updates" to "Turn Off Automatic Updates", the AutoUpdate process ceased generating "DHCP Inform" packets and my system has not been deleted from the router's DHCP Client Table since then.  I have a total of four WinXP/SP3 systems behind the E3000, one is direct connected to an Ethernet port on the router and the other three are connected to the EG008W switch which is connected to a port on the E3000.  One of those three systems is occasionally connected wirelessly to the E3000 for long periods with no connection problems.  My NVidia nForce 730i tower is one of the systems on the EG008W switch and is the one that was being dropped from the DHCP Client Table (whether it was on the switch or direct connected to the E3000).  The system that is always direct connected to the E3000 is an identical NVidia nForce 730i tower and has never been dropped from the DHCP Client Table.
    Please note that the client that was being dropped from the router's DHCP Client Table did NOT lose access to the Internet.  Repeated checks using Command Prompt "ipconfig /all" indicated the client still had it's IP Address lease.  Issuing a "ipconfig /renew" command resulted in the client being shown in the router's DHCP Client Table until the next "DHCP Inform" packet was sent and responded to by the E3000 (and WRT54G) router.
    Concerning switch connection issues with the E3000 and some newer WRT54G wireless routers, I had a similar issue in March 2011 with a LinkSys SD2005 Gb switch newly connected to a WRT54G V8 and later my new E3000 wireless routers.  The SD2005 had no issues connecting to an older WRT54G V6 router.  A call to the Support line transferred me to the Cisco Engineering support team which confirmed connection compatibility issues with older switches and new LinkSys Wireless routers due to firmware changes in switch connection support.  I replaced my SD2005 with an EG008W Gb switch and have no problems with it on either the E3000 or the WRT54G V8 backup router.
    Concerning the randomly assigned dynamic IP addresses from the E3000, from my perspective this appears to have started after the WRT54G V8.0 Wireless-G router firmware.  Not only does the E3000 definitely prefer the upper 10 IP addresses of the dynamic range but it ignores a client's request to renew a previously assigned IP address during the client's "half-life" IP Lease renewal process and usually assigns a different IP address.  This may part of undocumented identity protection policies.  I have chosen to use the E3000's DHCP Reservation function for my home based systems, both wired and wireless.  I do not use the DHCP reservation function for the new E3000 "Guest" wireless network.  Please note my use of DHCP reservation went into effect about halfway through my DHCP Client Table diagnosis process and had no affect on the issue except that I had reliable client IP addresses to use in ShareWare capture filters.
    I apologize for the long dissertation, but after 40+ years in various mainframe/open-system positions, I have a well known penchant for documenting problems for future reference.

  • Cisco Phone Control and Presence 8.6.1.1185 with IBM Lotus Notes 8.5.2 (Integrated Sametime Client 8.0.2) - No presence status visible

    Hi community,
    I am trying to integrate Cisco Unified Presence 8.6.1.10000-34 with IBM Lotus Notes 8.5.2 with the integrated Sametime Client version 8.0.2 via the Cisco Plugins 8.6.1.1185.
    Phone control is working fine, whereas the presence status is not shown (= no handset symbol next to the Sametime user). When I look in the preferences of the plugin, I can see that the plugin has connected successfully to the CUCM (8.6.2.20000-2),whereas the connection to the CUPS has not been established.
    The user id as well as the password are all the same on all systems. Here is a description of what I have configured via the ciscocfg.exe tool:
    Feature Control:
    - Enable Phone Status -> checked
    - Enable Dial Using Cisco IP Communicator -> unchecked (not required)
    - Enable Control Desk Phone -> checked
    - Default Mode -> Control Desk Phone
    Control Desk Phone Settings:
    - Voicemail Pilot Number -> left blank (no voicemail)
    - Cisco Unified Communications Manager
         - Servers -> IP address of CUCM
         - Read Only -> unchecked
         - Use as Default CUCM -> checked
         - Synchronize Credentials -> checked
              - Use Sametime Credentials -> checked
    Use Secure Connection: -> not required
    LDAP Phone Attributes: -> not required
    Phone Status Settings:
    - Cisco Unified Presence Servers -> IP address of CUPS
    - Read Only -> unchecked
    - Synchronize Credentials -> checked
         - Use Sametime Credentials -> checked
    - Sametime User ID Mapping
         - Use Business Card Attribute -> MailAddress
         - Remove Domain -> checked
    - Display Off-Hook Status Only -> unchecked
    At the moment I don't see an error in the configuration, but maybe I am wrong. Could anyone please tell me what the error could be?
    Thanks a lot in advance!
    Kind regards,
    Igor

    Hi all,
    here are some additions to my above post:
    Servers and clients used:
    1x CUCM 8.6.2.20000-2
    1x CUPS 8.6.1.10000-34
    1x IBM Lotus Domino Messaging Express Server 8.5.2
    1x Sametime Entry Server 8.5.2 (on top of the Domino server)
    2x IBM Lotus Notes 8.5.2 with integrated Sametime 8.0.2
    2x Cisco Phone Control and Presence with Lotus Sametime (PCAP) 8.6.1.1185
    2x Cisco Unified Personal Communicator 8.5.5.19839
    Setup:
    - CUCM, CUPS and CUPC are working fine, i.e. Desk Phone control via CUPC, as well as availability and presence status are working without issues
    - IBM Lotus Domino server is the LDAP Directory, the Sametime Entry Server is installed on top of the Domino server and uses the Domino Directory
    - User ID and password on CUCM/CUPS match the ShortName field and password in Domino
    - The PCAP plug-in has been manually deployed to both Notes clients with the following configuration:
         - Enable Phone Status -> active
         - Desk Phone Control -> active
         - no credential synchronization for CUCM and CUPS, i.e. every user must fill the user details himself
         - Sametime User ID Mapping is implemented via the LDAP Attribute uid (which is equal to the user id in CUCM)
         - LDAP configuration filled in with details of the Domino server
    Phone Control is working fine, also the connection to the LDAP server (Domino) is fine. However, when I type in the credentials for the CUPS server login, I can see (in Troubleshooting pane) that the user (pparker) is connected to the CUPS server for a short period of time and then gets disconnected. After that no connection is possible to the CUPS server, i.e. status is always disconnected.
    I have collected the Tomcat (EPASSoap00010.log and security00010.log) logs via RTMT and compared them to the logs from the PCAP plugin. The relevant time period is from 15:14 to 15:17. In the Tomcat logs I can see that the authentication is successful (see attached files), however in the log of PCAP plugin I can see the following messages:
    2012/02/03 15:14:35.281 WARNUNG Credential is rejected. Nothing to retry ::class.method=com.cisco.sametime.phonestatus.cup.CUPPresenceWatcher.answerChallenge() ::thread=CT_CALLBACK.1 ::loggername=com.cisco.sametime.phonestatus.cup
    2012/02/03 15:14:35.281 WARNUNG #### Connection rejected presence server ::class.method=com.cisco.sametime.phonestatus.cup.CUPPresenceWatcher.onPresenceServerConnectionRejected() ::thread=CT_CALLBACK.1 ::loggername=com.cisco.sametime.phonestatus.cup
    2012/02/03 15:14:35.281 WARNUNG Credential is rejected. Nothing to retry ::class.method=com.cisco.sametime.phonestatus.cup.CUPPresenceWatcher.answerChallenge() ::thread=CT_CALLBACK.2 ::loggername=com.cisco.sametime.phonestatus.cup
    2012/02/03 15:14:35.281 WARNUNG #### Connection rejected presence server ::class.method=com.cisco.sametime.phonestatus.cup.CUPPresenceWatcher.onPresenceServerConnectionRejected() ::thread=CT_CALLBACK.2 ::loggername=com.cisco.sametime.phonestatus.cup
    I don't understand why the connection is rejected although the Sametime Internal ID and CUPS User ID match. Does anyone know what the issue could be?
    All posts are very much appreciated!
    Thanks a lot in advance!
    Kind regards,
    Igor

  • Internet DHCP/DNS issues with WRT1900ac

    I've had a WRT1900ac now for about 2 weeks and the problems seem to be escalating.  Need help.  And yes, I've already read dozens of threads about these issues and nothing seems to be working.
    Most of the problems seem to be centered around this DHCP/DNS issue that so many have been reporting.
    First, the symptoms:
    Galaxy S4 phones when connected via wifi have some apps that don't update (facebook and google play)
    Some computers (both Win 7) will connect to the network just fine, both wired and wireless - but won't be able to get to the internet
    I've spent the last 2-3 days of my life reading forums and trying all sorts of things to get this to work properly (like my old router) and I'm still stuck.  Some things I've tried:
    Firmware is up-to-date (latest version: 1.1.8.164461)
    Manually assigned static DNS in router config settings (connectivity -> local network) to various combinations including the router address, 8.8.8.8, 8.8.4.4, 75.75.75.75, 75.75.76.76 (I have comcast), OpenDNS addresses, etc.  I read that the router address is not needed, so I stopped including it.
    I manually assigned IPs and DNS on the Galaxy S4 phones and that seemed to work... but also seems unnecessary.
    I've reserved DHCP addresses on the computers in question, that didn't seem to work, I also manually set DNS on one of the comupters (can't on the other... long story/not my computer) and that worked for a while and then stopped working.
    The only way to get one of the computers on the internet now is to turn on the guest network (even though the computer is hard wired to the router), connect, and then the wired network works.  No clue why this is, but my guess is that it needs the guest network for DNS, then it fails back over to the wired network.  Once that happens, I can actually turn off the wifi on the computer and everything works great... until I reboot.  Key point: I can't change any settings on that box other than entering in SSID/passphrase info for the wireless connection.  I can connect to the regular (non-Guest) wifi just fine - I just can't ever get to the internet.
    I've tried massaging DHCP settings on the router until I'm blue in the face - Static DNS, reserving DHCP addresses, hell I even put one of the computers in the DMZ to see if that would work and it still can't connect to the internet (it's worth noting that with my old router, Linksys WRT310N, the setup was literally plug-and-play - no hassle with any of this).
    I've tried countless router reboots, factory resets, turning off my modem and router for 2+ minutes, and nothing is working.
    I even read somewhere that if you modify your DHCP settings at all that the WRT1900ac stops doing DNS properly and breaks, so I even tried several "hard" factory resets and used all the default DHCP/DNS settings.  And it worked... for a few hours.
    Seriously, I'm at my wit's end.  I'm out a lot of money on this thing and it's been one headache after another.  Please help.

    I think for most people its a bad idea to hold out that hope, lol. It seems like a great piece of hardware but if you really need a router and don't want to have to 'play' with it, its probably not a good choice. I have an EA6900 that I am very happy with but it has the same restrictions as far as DNS and I really hate the idea that I am forced to use the smartwifi portal. I would really like for them to give me a choice of the old gui or the new one and let ME decide. Lots of routers to choose from out there now and new ones seem to be coming out all the time so do some reading and see if something suits you better. Good luck!

  • 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.

  • Cisco 2960x - auto qos voip cisco-phone on access ports

    After configuring "auto qos voip cisco-phone" on a stack of 2960x switches, we later noticed that after a power cycle (config was saved first) it went missing when doing a "show run" from the interface configs, on one of the switches (g1/0/1-48 had it applied, then after power cycle it didn't show).  However, doing a "show auto qos interface" shows it is still applied to all interfaces g10/1-48. 
    I try to do "auto qos voip cisco-phone" again on g1/0/1-48, and it shows this:
    SwitchStack01(config-if-range)#auto qos voip cisco-phone
    AutoQoS Error: AutoQoS already configured
    % Range command terminated because it failed on GigabitEthernet1/0/1
    If I attempt to remove "auto qos voip cisco-phone", it shows this:
    SwitchStack01(config-if-range)#no auto qos voip cisco-phone
    AutoQoS Error: AutoQoS not configured
    % Range command terminated because it failed on GigabitEthernet1/0/1
    When I do a "show run", it is no longer displayed for the first switch of the stack.So is it still applied to the interfaces or not?   Is this a bug?  Has anyone else experienced this?  This has happened to at least a couple stacks of 2960x's we have. 
    Thanks!

    It appears to be a bug in the code.  Open a TAC ticket with Cisco and send them the output and the IOS version you are using so they can help you resolve the issue.   Most likely, they recommend an upgrade.
    HTH

Maybe you are looking for

  • No internet

    I had no internet yesterday for 6 hours, it took 50 minutes to get through to anyone, they said I had a faulty hub, and would send me a new one, i then changed the hub and rang again this time waited 55 minutes to get through, they said I had a fault

  • Basic questions about Oracle CEP

    Hi there, We are considering different alternatives for handling some business rules for our educational platform and I am not sure Oracle CEP would be a viable option (I have read a few things on the internet about it), let me elaborate: We have use

  • BPC 75M - Modify Application error "Cannot connect to the Reporting Server"

    I have trouble with Modify Application, also in ApShell. Maybe you have a clue what it can be the problem. Configuration: single server BPC 7.5M SP3, Windows Server 2008 SP2, SQL Server 2008 SP2 Installation user is a domain user. No errors during in

  • Curve 9300 not able to connect email

    Having trouble setting up my email account, trying to link to BT Home Hub (BTinternet.com) but continually getting a massage that my 'username or password' is invalid, which of course it isn't. I've seen numerous discussion in forums about this issue

  • Email Script for php5

    I was running a basic form with Flash 8 and PHP 4.*.* so that customers could email a client of mine. My clients web hoster has since upgraded to PHP 5.2.0 and the form has quit working. Does anyone know what changed in the new version that would aff