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

Similar Messages

10.7.3 MBP Wifi Problem - Endless Timeouts & Dropped connections

I've been reading around here a bit already and so I know many other people are having Wifi issues with Lion, but given that there are so many discussions and so many pages of talk, it's hard to go through it all, and using the search I haven't found anything that's quite similar to what I'm experiencing, so I'm starting a new topic...
Basically, I've got a late 2006 MacBook Pro, installed 10.7.1 (form 10.6.8) on in back in Aug 2011 and everything seemed to be fine. I updated to 10.7.2 sometime in Jan and still didn't notice any issues, but wasn't using Wifi at all at the time.
Then in Feb I moved and started using wifi (with a Cisco N router), and noticed that often, the system would not automatically reconnect to the network after waking up from sleep. Just selecting the network manually worked on the first try every time though, so it wasn't so bad.
At the end of April, I finally got around to installing the 10.7.3 update. I read it was supposed to fix wifi issues and so was looking forward to it. It installed fine and didn't seem to cause any problems...
2 days later I moved again (to India), and all **** broke loose... Now, I can rarely connect to wifi (a Beetel G router, configed with WPA). Around 25% of the time, the network won't show up in the list (despite being a clear 5ft from the base station), and when it does show up, 95% of the time I get a "connection timeout" error - often immeadiately, but sometimes it takes about 10sec to respond. On the same network, 2 Win 7 Dells and an iPad 1 all work flawlessly - it's not the router...
One the occasions that I am able to connect, it usually works fine, but if I put the computer to sleep and wake up again, there's no guarentee that the connection will work again - it's back to the lottery. And sometimes even when it's connected, the wifi stays (according to the menu indicator) but the internet connection disappears (to the point I can't even ping the router - 100% packet loss, let alone any internet server)
I've tried zapping everything I can think of (PRAM, SMC), repairing permissions, clearing the remembered networks from the System Prefs, deleting old Locations and creating new ones etc. I have a clean install of 10.7.1 that I booted off of, but it still had the same issues!
Here's the Wifi output from System Profiler (trying to use "Home Network"):
Software Versions:
CoreWLAN:          2.1.2 (212.1)
CoreWLANKit:          1.0.2 (102.2)
Menu Extra:          7.0.2 (702.1)
configd plug-in:          7.1.2 (712.1)
System Profiler:          7.0 (700.3)
IO80211 Family:          4.1.2 (412.2)
WiFi Diagnostics:          1.0.1 (101.1)
AirPort Utility:          6.0 (600.92)
Interfaces:
en1:
Card Type:          AirPort Extreme
Firmware Version:          Atheros 5416: 2.1.14.9
MAC Address:          00:XX:XX:XX:XX
Locale:          FCC
Country Code:          IN
Supported PHY Modes:          802.11 a/b/g/n
Supported Channels:          1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 149, 153, 157, 161, 165
Status:          Not Associated
Local Wi-Fi Networks:
Home Network:
PHY Mode:          802.11g
BSSID:          80:a1:d7:4a:d0:02
Channel:          1
Network Type:          Infrastructure
Security:          WPA Personal
Signal / Noise:          -77 dBm / -96 dBm
MGMNT:
PHY Mode:          802.11g
BSSID:          80:a1:d7:4a:d0:03
Channel:          1
Network Type:          Infrastructure
Security:          WEP
Signal / Noise:          -77 dBm / -96 dBm
RC:
PHY Mode:          802.11g
BSSID:          00:1e:40:57:67:61
Channel:          6
Network Type:          Infrastructure
Security:          WPA Personal
Signal / Noise:          -97 dBm / -96 dBm
Vivek:
PHY Mode:          802.11g
BSSID:          00:24:b2:94:ea:06
Channel:          11
Network Type:          Infrastructure
Security:          WEP
Signal / Noise:          -94 dBm / -96 dBm
nischai:
PHY Mode:          802.11n
BSSID:          58:6d:8f:c3:ea:2a
Channel:          6
Network Type:          Infrastructure
Security:          WPA2 Personal
Signal / Noise:          -90 dBm / -96 dBm
noor:
PHY Mode:          802.11g
BSSID:          00:24:b2:7e:26:72
Channel:          11
Network Type:          Infrastructure
Security:          WPA Personal
Signal / Noise:          -90 dBm / -96 dBm
One thread here I read had someone suggesting to run the Airport debugger in Terminal and posting the output - here's the results:
Sat May 5 09:52:00.823 <kernel> IO80211ScanManager::startScan: Broadcast scan request received from pid 622 ().
Sat May 5 09:52:00.824 <kernel> IO80211ScanManager::startScan: Initiating scan.
Sat May 5 09:52:00.824 <kernel> __ieee80211_newstate: INIT -> SCAN (arg 0xffffffff)
Sat May 5 09:52:00.824 <kernel> ieee80211_check_scan: active scan, duration 24000, desired mode auto, append, nopick
Sat May 5 09:52:00.824 <kernel> ieee80211_start_scan: active scan, duration 24000, desired mode auto, append, nopick
Sat May 5 09:52:00.824 <kernel> scan_next: chan   1g ->   1g [active, dwell min 8 max 8]
Sat May 5 09:52:00.865 <kernel> [80:a1:d7:4a:d0:02] new beacon on chan 1 (bss chan 1) "Home Network"
Sat May 5 09:52:00.865 <kernel> [80:a1:d7:4a:d0:02] caps 0x411 bintval 100 erp 0x4
Sat May 5 09:52:00.873 <kernel> [80:a1:d7:4a:d0:03] new beacon on chan 1 (bss chan 1) "MGMNT"
Sat May 5 09:52:00.873 <kernel> [80:a1:d7:4a:d0:03] caps 0x411 bintval 100 erp 0x4
Sat May 5 09:52:00.909 <kernel> scan_next: chan   1g ->   6g [active, dwell min 8 max 8]
Sat May 5 09:52:00.917 <kernel> [58:6d:8f:c3:ea:2a] new probe_resp on chan 6 (bss chan 6) "nischai"
Sat May 5 09:52:00.919 <kernel> [58:6d:8f:c3:ea:2a] caps 0x411 bintval 100 erp 0x4
Sat May 5 09:52:00.920 <kernel> [58:6d:8f:c3:ea:2a] new probe_resp on chan 6 (bss chan 6) "nischai"
Sat May 5 09:52:00.920 <kernel> [58:6d:8f:c3:ea:2a] caps 0x411 bintval 100 erp 0x4
Sat May 5 09:52:00.928 <kernel> [58:6d:8f:c3:ea:2a] new probe_resp on chan 6 (bss chan 6) "nischai"
Sat May 5 09:52:00.928 <kernel> [58:6d:8f:c3:ea:2a] caps 0x411 bintval 100 erp 0x4
Sat May 5 09:52:00.992 <kernel> scan_next: chan   6g -> 11g [active, dwell min 8 max 8]
Sat May 5 09:52:01.47 <kernel> [00:24:b2:7e:26:72] new beacon on chan 11 (bss chan 11) "noor"
Sat May 5 09:52:01.47 <kernel> [00:24:b2:7e:26:72] caps 0x411 bintval 100 erp 0x0
Sat May 5 09:52:01.75 <kernel> scan_next: chan 11g ->   7g [active, dwell min 8 max 8]
Sat May 5 09:52:01.158 <kernel> scan_next: chan   7g -> 13g [active, dwell min 8 max 8]
Sat May 5 09:52:01.241 <kernel> scan_next: chan 13g -> 52a [passive, dwell min 8 max 8]
Sat May 5 09:52:01.327 <kernel> scan_next: chan 52a -> 56a [passive, dwell min 8 max 8]
Sat May 5 09:52:01.409 <kernel> scan_next: chan 56a -> 60a [passive, dwell min 8 max 8]
Sat May 5 09:52:01.492 <kernel> scan_next: chan 60a -> 64a [passive, dwell min 8 max 8]
Sat May 5 09:52:01.575 <kernel> scan_next: chan 64a -> 36a [active, dwell min 8 max 8]
Sat May 5 09:52:01.657 <kernel> scan_next: chan 36a -> 40a [active, dwell min 8 max 8]
Sat May 5 09:52:01.741 <kernel> scan_next: chan 40a -> 44a [active, dwell min 8 max 8]
Sat May 5 09:52:01.823 <kernel> scan_next: chan 44a -> 48a [active, dwell min 8 max 8]
Sat May 5 09:52:01.906 <kernel> scan_next: chan 48a ->   2g [active, dwell min 8 max 8]
Sat May 5 09:52:01.920 <kernel> [04:4f:aa:b4:dc:f9] new beacon on chan 2 (bss chan 2) ""
Sat May 5 09:52:01.920 <kernel> [04:4f:aa:b4:dc:f9] caps 0x431 bintval 100 erp 0x0
Sat May 5 09:52:01.992 <kernel> scan_next: chan   2g ->   3g [active, dwell min 8 max 8]
Sat May 5 09:52:02.74 <kernel> scan_next: chan   3g ->   4g [active, dwell min 8 max 8]
Sat May 5 09:52:02.157 <kernel> scan_next: chan   4g ->   5g [active, dwell min 8 max 8]
Sat May 5 09:52:02.239 <kernel> scan_next: chan   5g ->   8g [active, dwell min 8 max 8]
Sat May 5 09:52:02.321 <kernel> scan_next: chan   8g ->   9g [active, dwell min 8 max 8]
Sat May 5 09:52:02.388 <kernel> [00:26:15:61:4c:87] new beacon on chan 9 (bss chan 9) "BSNL_AP"
Sat May 5 09:52:02.388 <kernel> [00:26:15:61:4c:87] caps 0x431 bintval 100 erp 0x0 country info 49 4e 49 01 0d 14
Sat May 5 09:52:02.403 <kernel> scan_next: chan   9g -> 10g [active, dwell min 8 max 8]
Sat May 5 09:52:02.486 <kernel> scan_next: chan 10g -> 12g [active, dwell min 8 max 8]
Sat May 5 09:52:02.569 <kernel> scan_next: chan 12g -> 149a [active, dwell min 8 max 8]
Sat May 5 09:52:02.655 <kernel> scan_next: chan 149a -> 153a [active, dwell min 8 max 8]
Sat May 5 09:52:02.738 <kernel> scan_next: chan 153a -> 157a [active, dwell min 8 max 8]
Sat May 5 09:52:02.821 <kernel> scan_next: chan 157a -> 161a [active, dwell min 8 max 8]
Sat May 5 09:52:02.903 <kernel> scan_next: chan 161a -> 165a [active, dwell min 8 max 8]
Sat May 5 09:52:02.991 <kernel> scan_next: done, [ticks 32630, dwell min 8 scanend 56413]
Sat May 5 09:52:02.993 <kernel> __ieee80211_newstate: SCAN -> INIT (arg 0xffffffff)
Sat May 5 09:52:02.993 <kernel> ieee80211_init_node[1132] old_auth 5
Sat May 5 09:52:02.994 <kernel> IO80211ScanManager::getScanResult: All scan results returned for pid 622.
Sat May 5 09:52:05.765 <airportd[804]> _handleNewMessage: Received XPC message, event = ASSOC_EVENT, pid = 622
Sat May 5 09:52:05.766 <airportd[804]> associate: INFO: airportd associate: network=<CWNetwork: 0x7f9fd8c11fc0> [ssid=Home Network, bssid=80:a1:d7:4a:d0:02, security=WPA Personal, rssi=-76, channel=<CWChannel: 0x7f9fd8c185b0> [channelNumber=1(2GHz), channelWidth={20MHz}], ibss=0], is8021X=0, remember=1
Sat May 5 09:52:05.781 <airportd[804]> associate: INFO: Checking if admin authorization is required
Sat May 5 09:52:05.802 <kernel> __ieee80211_newstate: INIT -> SCAN (arg 0x0)
Sat May 5 09:52:05.802 <kernel> ieee80211_check_scan: active scan, duration 24000, desired mode auto, append
Sat May 5 09:52:05.802 <kernel> ieee80211_check_scan: check scan cache
Sat May 5 09:52:05.802 <kernel> macaddr          bssid         chan rssi rate flag wep essid
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.802 <kernel>
Sat May 5 09:52:05.807 <kernel>
Sat May 5 09:52:05.807 <kernel> ieee80211_init_node[1132] old_auth 5
Sat May 5 09:52:05.807 <kernel> __ieee80211_newstate: SCAN -> JOIN (arg 0x0)
Sat May 5 09:52:05.812 <kernel> __ieee80211_newstate: JOIN -> AUTH (arg 0xc0)
Sat May 5 09:52:05.813 <kernel> ieee80211_cancel_scan: cancel active scan
Sat May 5 09:52:05.813 <kernel> scan_next: done, [ticks 32912, dwell min 8 scanend 56413]
Sat May 5 09:52:05.813 <kernel> parseWPAIE: groupCipherType = 3 pairwiseCipherType = 3 authSel = 2
Sat May 5 09:52:05.813 <kernel> initWithInterfaceAndIE: _myMacAddress 00:17:f2:e6:81:a1
Sat May 5 09:52:05.813 <kernel> setPMK: PMK SET!
Sat May 5 09:52:05.815 <kernel> ieee80211_tx_timeout: state AUTH
Sat May 5 09:52:05.815 <kernel> [80:a1:d7:4a:d0:02] ieee80211_scan_assoc_fail: reason 1
Sat May 5 09:52:05.815 <kernel> [80:a1:d7:4a:d0:02] sta_assoc_fail: reason 1
Sat May 5 09:52:05.815
Sat May 5 09:52:05.815 <kernel> __ieee80211_newstate: AUTH -> SCAN (arg 0x1)
Sat May 5 09:52:05.815 <kernel> [80:a1:d7:4a:d0:02] ieee80211_scan_assoc_fail: reason 1
Sat May 5 09:52:05.816 <kernel> ieee80211_init_node[1132] old_auth 5
Sat May 5 09:52:05.816 <kernel> ieee80211_check_scan: active scan, duration 24000, desired mode auto, append
Sat May 5 09:52:05.816 <kernel> ieee80211_check_scan: check scan cache
Sat May 5 09:52:05.816 <kernel> macaddr          bssid         chan rssi rate flag wep essid
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel>
Sat May 5 09:52:05.816 <kernel> ieee80211_start_scan: active scan, duration 24000, desired mode auto, append
Sat May 5 09:52:05.816 <kernel> scan_next: chan   1g ->   1g [active, dwell min 8 max 8]
Sat May 5 09:52:05.834 <kernel> ieee80211_cancel_scan: cancel active scan
Sat May 5 09:52:05.834 <kernel> __ieee80211_newstate: SCAN -> INIT (arg 0xffffffff)
Sat May 5 09:52:05.834 <kernel> ieee80211_init_node[1132] old_auth 5
Sat May 5 09:52:05.835 <kernel> en1: Terminating supplicant.
Sat May 5 09:52:05.835 <kernel> RSNSupplicant: Releasing authenticator for 00:00:00:00:00:00
Sat May 5 09:52:05.835 <airportd[804]> associate: Apple80211Associate2() failed with error -3905
Sat May 5 09:52:21.354 <kernel> IO80211ScanManager::cachePurge: clearEntries[0] Firing!
Sat May 5 09:52:21.354 <kernel> IO80211ScanManager::cachePurge: Rescheduling in 14 seconds.
Sat May 5 09:52:35.354 <kernel> IO80211ScanManager::cachePurge: clearEntries[0] Firing!
Sat May 5 09:52:35.354 <kernel> IO80211ScanManager::cachePurge: NOT Rescheduling.
I'm pretty savy with computers and have dealt with all kinds of stuff before, but this one is beyond me, and is really annoying! I konw my machine is old, but it was totally useable up until these Wifi issues, and now wifi is basically useless.
From what I've read, it seems like its a driver issue with the Atheros card in my machine, but most people seem to be complaining about dropped connections (mine rarely drops) rather than timeout connection issues. I've also never had the "hardware not found" issue that many people have, so I think this is something different.
Anyone out there have any advice? I'm getting close to losing it with wifi since the update!

Sorry - to add:
I don't think it's a question of WPA vs. WPA2, or even channel number - I have 2 identical routers here and neither work (both default to WPA Ch 11) but I changed one to WPA2, new SSID, various channels and still had the same problems.
Another thing to note that should be irrelevant, but who knows: the Firewire controller on my machine died back in Fall 2010 - to the point where the system won't start-up unless I remove the IOFirewire***.kext from /System/Library/Extensions , and as soon as I do that, it works flawlessly (minus Firewire). It meant I had a **** of a time installing Lion becuase I can't boot off the Recovery Partition (which has the drivers baked into it), but by cloneing my HD, installing Lion onto the clone via a borrowed machine, removing the .kext's and cloning back, I got it on and everything seems to be fine otherwise... I posted about that problem before, but never got any answers. And it wasn't just me, my father has a late 2007 MBP and the same firewire issue happened to his within 5 days of mine (not a power spike - I think it was shortly after some system update if I remember correctly).

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.

Cisco SD2008 v3 switch dropping connections every few hours

Hi, I have a Cisco SD2008 v3 switch at the office that routinely drops connections every few hours and must be turned off/on to get back up. It doesn't seem to drop all connections, but some boxes plain and simply become unreachable.
I've double-checked that there aren't any looping cables. The network infrastructure wasn't touched, as we had a cheap unbranded switch before (which amusingly didn't have any problems other than an annoying fan) and just put the Cisco in.
I've googled a bit and found some references to this problem, which leads me to believe it's reasonably widespread. Is there a firmware update of some sort for this equipment? Any ideas?

Hi Bruno,
If you would be so kind as to ring the good folks at the Small Business Support center regarding this issue.
http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
If there is a known problem with this older product it should be replaced. You cannot update the unmanaged switch with new firmware as I guess that can only be done in a factory.
But the older SD2008 has been refreshed by the new technology SD2008T (100 series) which are really quite advanced compared to the older SD series switches.
http://www.cisco.com/cisco/web/solutions/small_business/products/routers_switches/100_series_switches/index.html
regards Dave

Can not connect with dhcp - renew dhcp lease will switch directly to manuel

If have the following problem
I us apple Airport extreme to connect to internet.
I have 5 Macs, all connecting with airport . They work fine with DHCP. Since 2 weeks I have a problem that one computer – a mac book pro with 10.5.6 will not connect.
When I switch to dhcp and select renew dhcp lease it switch directly back to manuell. I have no chance to connect with dhcp.
Has anyone a suggestion?
Thanks

Wonder why Apple hasn't chimed in on this one...
Whenever you have an issue like this where it's fine, then DHCP stops working for any reason.... Reset the PRAM.
How to:
Apple Logo -> Restart.
After the screen goes black -> Hold down all 4 keys until you hear the third Bong.
"Option"+[Apple Logo OR key to the left of the space bar]"P""R"
After the third BONG or Apple Chime whatever you want to call it. The system's Parameter Ram or to the PC Crowd the CMOS has been reset. This resets your clock, brightness, volume, etc.... So things will get reset along the way but it also resets the IRQ and DMA stats on the logic board. Ala, reseting your Airport's Connection to the logic board, Controllers, etc.

Dropped connectivity - Unable to contact DHCP

I have been dropping connectivity every hour or so. When I try to repair, it fails to reset IP because it is unable to contact DHCP. If I unplug the router for a minute, then it reconnects. I have three computers that connect to the router. 2 wireless, 1 ethernet. It seems to affect them all at the same time. It seems to be getting progressively worse, that is meant time to failure is getting shorter and shorter.
The router is about 4 years old.
Any suggestions?

Forgot to say my router is a BEFW11S4 V2
Thanks

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.

Cisco wrt54g2 drops ip assigned by Motorola modem

For some reason, a couple of days from today, my Cisco wrt54g2 drops ip assigned by Motorola modem.
It gets it back after a while (10 mins) and works for another 15 minutes.
The firmware is uptodste, I just upgraded it today.
What could be causing this behavior?

Well all of a sudden it stopped doing it SO OFTEN. Its still does it but every 3 or 5 hours or so.
Now the weird thing is that the devices dont hold on to the password for some reason. I have 2 ipads and 2 iphones and i have to input the 26digit hex key everytime we come home and want to connect. My macbook air seems to hold on to the password just fine though.
I just changed the cable. But as I said, Im not sure yet if that fixes the problem because now I get internet pretty much all night from the moment i come home from the office til i fall asleep and thru next morning, and just have to release/renew dhcp lease when i come back home the next day. So Ill know tomorrow. Ill post back.

SQL Server AlwaysOn Failover threshold and Lease Timeout

Hi experts,
I found each time when I were building/restoring another log shipping(standby) server. It would cause ERR [RES] SQL Server Availability Group: [hadrag] Failure detected, diagnostics heartbeat is lost(in cluster log) and A connection timeout has occurred on a previously established connection to availability replica 'DL980-4' with id(in errorlog). I google and find a document (http://download.microsoft.com/download/0/F/B/0FBFAA46-2BFD-478F-8E56-7BF3C672DF9D/Troubleshooting%20SQL%20Server%20AlwaysOn.pdf ) indicated that “This may be a performance issue”. I run restore database and AlwaysOn synchronizing on the same 10GbE link at the same time.
Should I increase
leaseTimeout from 20000 to 100000 and
HealthCheckTimeout from 30000 to 300000?
Does it work to prevent unnecessary failover.
Please refer to
(http://blogs.msdn.com/b/psssql/archive/2012/09/07/how-it-works-sql-server-alwayson-lease-timeout.aspx )
parag
10-18-2013 3:19 AM
Hi Denzil
we seem to see lease expires very frequently when the server is under very high cpu pressure .. our failure condition level is 1
is it possible to prevent this situation . the problem is when lease expires,all the current connections seem to be dropped . wondering if there is a way to prevent this ..
Also is it possible to affitinize the always on health check process to a particular core
Thanks for your help!

Hi Dennis
Should I increase
leaseTimeout from 20000 to 100000 and
HealthCheckTimeout from 30000 to 300000?
Does it work to prevent unnecessary failover.
1. you can increase the timeout parameter, but when the fail-over time slight delay will be there (its a work around solution)
2. You may require to check the Network connections. (Cluster Heartbeat & public network)
3. Have you update the latest patches of OS & DB?
4. If possible raise the ticket to Microsoft. they may give some update for Cluster resource update based on your issue
Regards
Sriram

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

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

Macbook Pro (late 2013) drops connection

I purchased my MBP 13 inch (late 2013) in November. Just recently my internet connection randomly drops when I either open a specific webpage or just randomly cuts off. The wifi signal aleways appears to be on, but I can't open any webpages and ping (on terminal) always shows an error when the signal cuts off. The only temporary way to solve this is to restart my computer. However, this happens almost every hour and it gets extremely annoying. I've tried it with multiple networks and wireless connections— all have the same symptoms. Should I go to the Apple Store to get my MBP replaced or is there a fix?

Did you try Renewing the DHCP lease?

E4200 dropping connections

my e4200 updated with latest 1.00.1 firmware is constantly dropping connections from the outside to existant lan servers running low traffic services when my machine is using torrent or internet gaming.( call of duty modern warfare )
anyone else with that behavior ?
when will cisco fix this ?
cheers

lordgrinz,
I believe you. I just wanted to point out there are many users not experiencing issues (given their needs and the features they use). Given this, there are perhaps specific scenarios / setups under which the issues occur, some of which may not be Cisco's fault (software or hardware conflicts with equipment from other manufacturers).
For example, when I used my Rosewill wireless utlity (came with my 802.11n USB adapter), it conflicted with something that caused the E4200 to stop broadcasting wireless / lock up on the wireless side.
I stopped using the Rosewill utlity and the issue has not happened again in over a week (I reproduced the issue by reenabling the utlity at one point and within two days I experienced the same problem again).
It also did not happen the first few weeks when I was not using the Rosewill utlity and had occurred another time when I used it right after getting the router (i.e. during the 2 periods of time during which the utility was disabled I had zero issues and the two times I turned the utility back on, the problem occurred again.
(I only liked the Rosewill utility for it's advanced view of wireless networks in my area, including their exact signal strength, channel etc. I think SSIDer, as an alternative, provides this anyway).
That is just one example.
I am not saying the E4200 does not have flaws (I believe there are some documented DHCP issues that some have experienced etc.).
I am only saying that with my setup and the features I use, my E4200 has been rock solid.

I have to renew DHCP lease every few seconds to stay online

I'm having trouble staying online. I can surf 2-3 pages, then it will not load the next page. I hit renew DHCP lease and the page will load but I am doing this every every 20 seconds. I spoke to my ISP (Time Warner) for almost an hour and could not solve it. They said everything was fine on their end and it sounds like a computer problem. I've used this computer and internet connection for over a year without ever renewing DHCP lease now I do it all the time. Any advice would help.

I'm having the exact same problem. Sometime the pages will work for a while. Then the internet will start dropping out for a few days at time.
I've reset and restarted everything, tried everything that I can think of. The only thing that seems to help is to renew the DHCP lease whenever it starts to happen. It will load one, maybe two, websites, and then the browser just says "connecting to (insert website here)"
Please help, Next step is calling up AppleCare, which I would rather not do if I could. I'm a college student and i use my laptop to take notes during classes. (I type much faster than I can write)

Cisco 867VAE drops connection on DHCP lease timeout

Similar Messages

Maybe you are looking for