806 refusing to cooperate. - comp.dcom.sys.cisco

Hi there. I have a LAN in my home composed of 2 PCs, both of which run Windows 98SE. Both PCs are connected via a CISCO 806 broadband router primarily for internet connection sharing and secondarily for filesharing. My ISP is Insight Communications (InsightBB) and I receive high-speed [coax] cable internet access from them. I have owned the 806 router since 2002 and previously used it (successfully) to share a DSL connection. I've used the 806 to split my Insight cable connection for over a year now. When I initially configured the 806 to use my cable connection I was able to simply use the CISCO Router Web Setup (CRWS) Quick Setup option to automagically <not sic> negotiate all the settings for the connection--and it worked. A few times (but by no means frequently) I have executed a 'reload' command directly at the console in an effort to allay occasional network slowdown. A few other times, I unplugged the router, but only when there was a thunderstorm/etc. occurring. IOW, the router basically functioned without any babysitting and was rarely if ever reconfigured using the CRWS. A few nights ago, Insight performed some "maintenance" of some kind on the equipment at their end (there was notice in advance) which knocked me--and presumably all the other people in the service area (or whatever) that I reside in--off the internet. Everyone's service was supposed to be restored on the following day. On that following day, after power-cycling my cable modem and the 806 (at Insight's behest), I proceeded to run the CRWS Quick Setup (just as I had in the past)--but this time, I received an error message telling me that the router was unable to ping my ISP, and, as a result, no IP was assigned to my WAN interface/internet port. I tried releasing and renewing the WAN interface's IP, but that resulted in an error and still no IP was assigned to E1 (the WAN int). Now mind you, both E0 (LAN) and E1 (WAN) were up (Layer 1) and had their line protocols up (Layer 2). I was able to send pings back and forth between my 2 PCs and the 806 was doling out proper private IPs to both of them (IOW, NAT and LAN-side DHCP were working). So, I tried manually entering all the necessary configs and settings into the 806 using CRWS Advanced Setup, but still no luck. BTW, I should mention here that eerily enough, when I checked WINIPCFG on both my PCs (this is Win98SE, don't forget =) my ISP's DNS server addresses (both the primary and secondary addys) showed up--even after I released and renewed the IP configs in *both* PCs, and despite the fact that the router was unable to dynamically locate the addresses (or so it told me). In any event, I disconnected the 806 and tried connecting my cable modem straight to my PCs. I tried both of them (seperately, of course) and they were both able to connect to the internet without a hitch. Many resettings of the 806 to factory defaults, RELOADings at the console, and various power-cyclings later, I'm still unable to get that blasted thing to find my ISP's DHCP and DNS servers or accept the values when I manually config 'em. I've checked and rechecked. I'm sure you can imagine my frustration at this point. =) I would greatly, greatly appreciate it if anyone could shed any light on my problem. My personal feeling about my next step is that maybe I should try and upgrade the router's IOS or try and refresh the contents of its flash and webflash (none of the above which I've ever done to this router, so I'm a tad hopeful), but on the other hand, I've gotten by for 4 years without needing to update anything (and besides, every time I've ever tried to use the CRWS-based upgrade option, it has failed--and I mean *always*). Basically, I'm frustrated and need some fresh perspective from people who know more about this than I do. I only know enough to get me into trouble. And that's where I am. =) Thanks a million in advance to anyone who offers some help. I will (and do) greatly appreciate it. Cheers.

Time to learn to use the IOS command line interface Plug into the console port so that you can capture the following output to post here show version show run ! now enable logging if not already on conf t logging buffer 10000 debug no logging console exit wri mem clear log ! see if router attempts to obtain a DHCP address from ISP debug dhcp detail ! disconnect/reconnect cable sh log

Merv wrote: > Plug into the console port so that you can capture the following output > to post here I followed all your instructions. It bears noting that I had just executed RELOAD from the command line and then used the "Reset to Factory Defaults" option in the CRWS before I performed your commands. I don't know if that'll change whatever it is you were expecting to see. In any case, thanks very much for your helping hand so far, I really appreciate it. ?????>sh ver Cisco Internetwork Operating System Software IOS (tm) C806 Software (C806-O3SY6-M), Version 12.2(4)YH, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) Synched to technology version 12.2(7.1)T TAC Support: http://www.cisco.com/tac Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Thu 23-May-02 22:34 by ealyon Image text-base: 0x80013170, data-base: 0x807432E4 ROM: System Bootstrap, Version 12.2(4r)XM3, RELEASE SOFTWARE (fc1) ROM: C806 Software (C806-O3SY6-M), Version 12.2(4)YH, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) Router uptime is 1 hour, 3 minutes System returned to ROM by reload System image file is "flash:c806-o3sy6-mz.122-4.YH.bin" CISCO C806 (MPC855T) processor (revision 0x501) with 30720K/2048K bytes of memory. Processor board ID VMS06290CVU (3705055196), with hardware revision 0000 CPU rev number 5 Bridging software. 2 Ethernet/IEEE 802.3 interface(s) 128K bytes of non-volatile configuration memory. 8192K bytes of processor board System flash (Read/Write) 2048K bytes of processor board Web flash (Read/Write) Configuration register is 0x2102 ?????#sh run Building configuration... Current configuration : 942 bytes ! version 12.2 no service pad service timestamps debug uptime service timestamps log uptime service password-encryption ! hostname Router ! ! ip subnet-zero ip dhcp excluded-address 10.10.10.1 ! ip dhcp pool CLIENT import all network 10.10.10.0 255.255.255.0 default-router 10.10.10.1 lease 0 2 ! ip audit notify log ip audit po max-events 100 ! ! ! interface Ethernet0 ip address 10.10.10.1 255.255.255.0 ip nat inside no cdp enable hold-queue 32 in hold-queue 100 out ! interface Ethernet1 ip address dhcp client-id Ethernet1 ip nat outside no cdp enable ! ip nat inside source list 102 interface Ethernet1 overload ip classless ip http server ip pim bidir-enable ! ! access-list 23 permit 10.10.10.0 0.0.0.255 access-list 102 permit ip 10.10.10.0 0.0.0.255 any ! line con 0 exec-timeout 120 0 stopbits 1 line vty 0 4 access-class 23 in exec-timeout 120 0 login local length 0 ! scheduler max-task-time 5000 end ?????#conf t ?????(config)#logging buffer 10000 debug ?????(config)#no logging console ?????(config)#exit ?????#wri mem ?????#clear log ?????#debug dhcp detail (Here, I unplugged my cable modem from my router, then plugged it back in before going on) ?????#sh log Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns) Console logging: disabled Monitor logging: level debugging, 0 messages logged Buffer logging: level debugging, 297 messages logged Logging Exception size (2048 bytes) Count and timestamp logging messages: disabled Trap logging: level informational, 70 message lines logged Log Buffer (10000 bytes): : 0.0.0.0 for peer on Interface: Ethernet1 01:12:41: Temp sub net mask: 0.0.0.0 01:12:41: DHCP Lease server: 0.0.0.0, state: 1 Selecting 01:12:41: DHCP transaction id: 3E29 01:12:41: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs 01:12:41: Next timer fires after: 00:00:02 01:12:41: Retry count: 1 Client-ID: 0009.b74d.f92b 01:12:41: DHCP: SDiscover: sending 289 byte length DHCP packet 01:12:41: DHCP: SDiscover 289 bytes 01:12:41: B'cast on Ethernet1 interface from 0.0.0.0 01:12:41: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFFA3E 01:12:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1, changed sta te to up 01:12:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x22334456 01:12:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 01:12:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x22334456 01:12:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x5686A64B 01:12:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x17A5367C 01:12:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x17A5367C 01:12:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x5F543804 01:12:43: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x46CB793E DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3E3A 01:13:13: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xC80A6CCF 01:13:13: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFB0BA 01:13:13: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFB0BA 01:13:14: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x29F0FC03 01:13:15: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x6138AD0E 01:13:16: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFF8824 01:13:16: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFF8824 01:13:17: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x63DF 01:13:17: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x8878B836 01:13:18: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:18: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:18: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x6138AD0E 01:13:19: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 01:13:19: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 01:13:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFD812 01:13:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xAE408856 01:13:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFD812 01:13:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFFA3E 01:13:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFFA3E 01:13:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFF8AEE 01:13:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFF8AEE 01:13:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x13C68 01:13:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:21: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x13C69 01:13:21: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xCABC346E 01:13:21: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xF678E292 01:13:21: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xF678E292 01:13:22: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC5A2 01:13:22: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC5A2 01:13:22: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3C343370 01:13:22: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x12138 01:13:22: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x8E0D7462 01:13:22: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x8E0D7462 01:13:23: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x5CF50253 01:13:23: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3E3A 01:13:23: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x5CF50253 01:13:23: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3E3A 01:13:23: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x12139 01:13:25: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:25: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xB69EAA00 01:13:25: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:25: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x82989600 01:13:25: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:27: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x7D2A 01:13:27: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x7D2A 01:13:27: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1E8234CA 01:13:27: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1E8234CA 01:13:28: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x7016 01:13:29: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:29: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:29: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x5F6FC03 01:13:30: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xC80A6CCF 01:13:30: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xE99EAA00 01:13:30: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xB5989600 01:13:31: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x63DF 01:13:31: DHCP: QScan: Purging entry 01:13:31: DHCP: deleting entry 80EC5084 0.0.0.0 from list 01:13:31: Temp IP addr: 0.0.0.0 for peer on Interface: Ethernet1 01:13:31: Temp sub net mask: 0.0.0.0 01:13:31: DHCP Lease server: 0.0.0.0, state: 8 Purging 01:13:31: DHCP transaction id: 3E29 01:13:31: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs 01:13:31: No timer running 01:13:31: Retry count: 0 Client-ID: 0009.b74d.f92b 01:13:32: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 01:13:32: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 01:13:33: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x14848 01:13:33: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x327C6979 01:13:33: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x327C6979 01:13:34: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3E3A 01:13:34: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x13545638 01:13:34: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3E3A 01:13:34: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x14849 01:13:35: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xCABC346E 01:13:36: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 01:13:36: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:37: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27D8036 01:13:37: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27D8036 01:13:37: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x7298 01:13:37: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x7298 01:13:38: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1FE7070B 01:13:38: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1FE7070B 01:13:38: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xADEA8F27 01:13:38: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xADEA8F27 01:13:41: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3774 01:13:41: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:41: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3774 01:13:41: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:41: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x589FAA00 01:13:41: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xD047A300 01:13:41: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x24999600 01:13:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1907 01:13:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1D470DE2 01:13:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x73C 01:13:42: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x73C 01:13:43: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFAD46 01:13:43: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFAD46 01:13:44: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x50E00EB2 01:13:44: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x50E00EB2 01:13:44: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 01:13:44: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 01:13:44: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x6568 01:13:44: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x6568 01:13:44: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xE1FBFC03 01:13:45: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3E3A 01:13:45: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3E3A 01:13:46: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3674 01:13:46: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3674 01:13:46: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x348A300 01:13:47: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x63DF 01:13:48: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xA1490DBD 01:13:48: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x7016 01:13:48: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC86E 01:13:48: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC86E 01:13:49: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC1B8 01:13:50: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC1B8 01:13:50: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 01:13:52: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFB0BA 01:13:52: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:52: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFB0BA 01:13:52: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 01:13:52: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x6448 01:13:52: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x6448 01:13:52: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xCABC346E 01:13:52: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC78A 01:13:52: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC78A 01:13:53: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFF930C 01:13:53: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFF930C 01:13:53: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x8391DB00us..: xid: 0x3C343370 01:13:06: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x3E3A

To initially acquire an IP address via DHCP, 4 packets need to be exchanged between the DHCP client (your 806 router) and the ISP's DHCP server. DHCP Discovery -> ISP DHCP Offer <- ISP DHCP Request -> ISP DHCP Ack <- ISP >From the debug output it can be seen that your router is sending the Discovery packet: 01:12:41: DHCP: SDiscover: sending 289 byte length DHCP packet 01:12:41: DHCP: SDiscover 289 bytes 01:12:41: B'cast on Ethernet1 interface from 0.0.0.0 Your router appears to never receive a DHCP Offer from the ISP. You need to contact your ISP and go thru a troubleshooting exercise where they confirm that: 1. they are receiving the DHCP request which can be identified via the MAC address 2. That they are sending a DHCP offer back to your PC If you can get them to expalin the nature of the change that they made to their network the other night. Post the results from that conversation.

I wonder if due to the network changes you are now encountering this little gem: CSCdw27367 Bug Details Headline DHCPDISCOVER with disabling broadcast flag Product IOS Feature DHCP Components Duplicate of Severity 3 Severity help Status Resolved Status help First Found-in Version 12.2(2)XK01 All affected versions First Fixed-in Version 12.2(7.4), 12.2(7.4)T, 12.2(7.4)S, 12.2(4)YA, 12.2(7.6)B, 12.2(9.4)DA, 12.2(15)BW, 12.2(15)BX, 12.2(15)ZN Version help Release Notes Symptom: The problem occurs when an ethernet interface is configured as DHCP client (ip addr dhcp) but cannot get ip address form DHCP server, connected via an ADSL modem: Client PCs-----[Cisco806]----[ADSL Modem]---[DHCP server] e0 e1 DHCP client However, it works fine in case a Windows PC or a 3rd party router is used instead of a Cisco router. The working scenario: 3rd. party's router or Windows PC --------ADSL modem-------------DHCP server It also works fine if the Cisco router was directly connected to the DHCP server: c806-----------------[directly connected]----------DHCP server Workaround: None. Further description: The problem here is with the ADSL modem (carrier supplied) which blocks all downstream broadcast. The current implementation of IOS sends DHCPDISCOVER with broadcast flag=ON. The IOS DHCP client would like to receive broadcast reply and hence the Broadcast flag is set to ON. However, with the ADSL modem, the OFFERs/ACKs broadcast from the server is blocked. hence the Cisco 806/Cisco 1710 can not get the ip address. 3rd. party's router and Windows PC send DHCPDISCOVER with broadcast flag=OFF, so it works fine in that scenario. Solution: A new CLI command, to configure the DHCP client to set the Broadcast flag ON or OFF. Router(config)# [no] ip dhcp-client broadcast-flag This command can configure DHCP client to set/not set broadcast-flag ON; "broadcast-flag" ON will be the default setting. Will your router take the command: no ip dhcp-client broadcast-flag

Merv wrote: > Will your router take the command: > no ip dhcp-client broadcast-flag I'll answer this one first since it'll take less time: yes, my router *does* accept 'no ip dhcp-client broadcast-flag'. I entered it and then tried everything in CRWS again to reconfigure my connection, but nothing changed at all. I got a single alert on the console when Quick Setup failed: 06:09:50: %IP-4-CLASS: Bad IP address and mask 0.0.0.0/0 in class_resolve() Dunno if that helps... In any case, 'no...dhcp broadcast...' didn't seem to help. > You need to contact your ISP and go thru a troubleshooting exercise > where > they confirm that: > 1. they are receiving the DHCP request which can be identified > via the MAC address Unfortunately, the tech support rep I dealt with wasn't evidently high-level enough to understand exactly what I was asking him when I mentioned the DHCP "4-way handshake" that you described in your reply to my OP. However, he did verify that he could "see" (he didn't go into detail) the MAC of the 806's E1 int (the WAN int) and actually read the MAC to me--so that much was true. But eerily enough, despite the fact that 'sh int e1' and even the 'Interface Summary' in the CRWS told me that E1's IP was "unassigned" (and yes, both 'sh int e1' and the 'Interface Summary' claimed that the "Internet address will be negotiated using DHCP"), the tech support rep told me that he could "see" E1's IP addy as a 10.x.y.z number! I even tried to 'tracert' out to E1 to see if I could get it to show on the DOS prompt--and I was able to tracert to E0 (LAN int). However, the trace gave me a 'host unreachable' I believe and refused to show me any address at all for E1. That, I thought, was really bizarre... [confirm that:] > 2. That they are sending a DHCP offer back to your PC Again, the tech support rep wasn't very helpful in this regard, though he did try his best. I'm not sure what he was seeing, but I specifically asked if he could sniff the traffic to identify these packets and he stated that he didn't have any packet sniffing software. Beyond that, I simply told him several times what you pointed out to me in the DHCP log in hopes that at least ONE of his monitoring programs (or whatever) would be able to tell him what was going on, but I don't think he got it. None of the other instructions he gave me were very notable: the majority of things he had me do were of the "power-cycle the modem and router and plug the one in before the other" variety. In any case, I'm going to move on because I believe the story he had to tell about the "maintenance" done to my service area is more enlightening than this. > If you can get them to expalin the nature of the change that they made > to their network the other night. > Post the results from that conversation. Okay. Here goes... =) Well, before this "maintenance" was performed to my service area, as I said, everything worked fine. I'm unsure if this is common practice for broadband or specifically cable ISPs, but if I ever changed the device that plugged straight into my modem (for example, if I went from PC--->ROUTER--->MODEM and then changed to simply PC--->MODEM) I would pull strange IPCONFIG info from DHCP and would be redirected in my web browser to a page set up by my ISP. The purpose of this page was to "register" the MAC address of the device I was using to plug directly into my modem. Obviously, if I changed the device, the MAC would change, and they would need me to "re-register" the MAC with their "registration server". Now, the first reason I bring this up is that I never had trouble registering or re-registering my MAC when necessary. I don't believe I ever had a hiccup. The second reason I mentioned it, is that the tech support rep told me that *this* process is what was "upgraded" when Insight performed their "maintenance" in my service area. He actually flat out told me that AT&T was somehow responsible for Insight's "old" registration servers and that Insight for some reason decided to divest AT&T and set up their own internally maintained registration servers. He indicated (correctly) that anyone who decides to just up and reinvent the wheel will be guaranteed to be plagued with bugs. Interestingly enough, he was referring to the fact that Insight's "new" registration servers had apparently been causing "most customers with routers"--his own words--connection problems. (As an aside, he said that most customers without routers didn't experience any difficulty which was also my experience; in fact, I'm plugged straight into my modem as I write this.) However, the problem wasn't simply a matter of working out the bugs in an existing system that's being moved: the rep revealed to me that Insight had actually changed the MAC registration system and process when they moved to these new servers. Whereas the "old" system required the user at home to manually tell the ISP via a web browser redirect that their MAC addy had changed, the "new" system was what the rep called (I belive, but don't quote me) a 'self-provisionary' system or perhaps 'self-provisioning' or 'auto-provisioning' system. Now, the registration servers *automagically* figure out the MAC has changed and simply reassign your new device the proper IPCONFIG stuff. (I bet they did this to keep down complaints. Manually re-registering *was* a little annoying.) The only problem is that apparently this 'self-provisioning' system isn't intelligent enough to properly mate with routers. The rep himself told me that people with all different brands of routers were having issues and that Insight was scrambling to figure out what they could do to get everyone reconnected. He tried to manually delete my entries from the registration server on his side and have me reconnect and manually re-register myself (again, through a page in my browser; guess they realized they'd need a backup plan), but that was to no avail. He confirmed that my router just wouldn't pull the proper IP no matter what we tried (despite the fact that you showed me the router was sending out DHCP requests in my log). The bottom line, according to the rep, was that this new MAC registration system was a waste of time and effort because he felt it was very problematic. One of the last things he asked me to do was 'upgrade my firmware' which I dissuaded him from wanting to try since I don't believe he understood that this isn't your garden variety Linksys toy router. =) Apart from that, he said he'd fill out a case form and pass it on to his higher-ups and someone with more knowledge and ability there would examine it and try to get me a solution at a later time. He advised me to connect to the internet without my router for the time being, and I downloaded ZoneAlarm PF so I'm not totally naked on the internet. But in any event, getting a consumer-grade/end-user/garden variety router apparently isn't really a good or viable option either. One last thing of interest. Hours after my conversation with tech support (in fact, just before I connected to the internet to write this), I had left my cable modem unplugged and just a bit ago power-cycled it to get online. After the modem became ready, I released/renewed my PC's DHCP stuff in WINIPCFG. Instead of pulling a valid public IP, the PC was handed a 192.168.100.x addy, and it had no DNS servers, default gateway, or DHCP server listed (I think; DHCP server may have been a 192.168.x.y addy as well). Mind you, I was plugged straight from my PC's NIC into the modem (and my router assigns 10.10.10.x private IP's anyhow; also, my Windows APIPA is the default 169.x.y.z and not 192.x.y.z) so *Insight* was giving me this crap. I continued to release/renew my PC for a few minutes (maybe 3, tops) and *finally* I received a valid public IP. I don't know what that means, if anything. I do believe that's my whole story. I don't know what you'll make of it, but I'm eager to hear it. Thanks very much for helping me out and listening to all this business! I really appreciate it. Cheers!

Woow .... I would have thought that tan ISP would have done more extensive testing before implementing a new provisioning system. Could post the debug dhcp output with the "no ip dhcp-client broadcast-flag" command configured conf t no ip dhcp-client broadcast-flag logging buffer 10000 debug no logging console exit wri mem clear log ! see if router attempts to obtain a DHCP address from ISP debug dhcp detail ! disconnect/reconnect cable sh log

Okay, I did as you said. I wasn't sure if I waited long enough or what have you after I SH'ed LOG the first time, so I cleared the log and did it again (and I did unplug the cable the second time as well). Here it is: ?????#sh log Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns) Console logging: disabled Monitor logging: level debugging, 0 messages logged Buffer logging: level debugging, 37 messages logged Logging Exception size (2048 bytes) Count and timestamp logging messages: disabled Trap logging: level informational, 18 message lines logged Log Buffer (10000 bytes): 00:02:56: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFD812 00:02:56: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFD812 00:02:57: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 00:02:57: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 00:02:59: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x63DF 00:03:01: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 00:03:01: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 00:03:03: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x4F5E 00:03:03: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x4F5E 00:03:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1, changed sta te to down 00:03:09: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x5BD662DB 00:03:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1, changed sta te to up 00:03:11: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xA9B8EC00 00:03:12: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x7EB0AD18 00:03:13: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 00:03:13: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 00:03:13: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 00:03:14: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x4F5E 00:03:14: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x4F5E 00:03:15: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xE61FBAB4 00:03:16: DHCP: Try 6 to acquire address for Ethernet1 00:03:16: DHCP: allocate request 00:03:16: DHCP: zapping entry in DHC_PURGING state for Et1 00:03:16: DHCP: new entry. add to queue 00:03:16: DHCP: SDiscover attempt # 1 for entry: 00:03:16: Temp IP addr: 0.0.0.0 for peer on Interface: Ethernet1 00:03:16: Temp sub net mask: 0.0.0.0 00:03:16: DHCP Lease server: 0.0.0.0, state: 1 Selecting 00:03:16: DHCP transaction id: 3042 00:03:16: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs 00:03:16: Next timer fires after: 00:00:02 00:03:16: Retry count: 1 Client-ID: 0009.b74d.f92b 00:03:16: DHCP: SDiscover: sending 289 byte length DHCP packet 00:03:16: DHCP: SDiscover 289 bytes 00:03:16: B'cast on Ethernet1 interface from 0.0.0.0 ?????#clear log Clear logging buffer [confirm] ?????#sh log Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns) Console logging: disabled Monitor logging: level debugging, 0 messages logged Buffer logging: level debugging, 620 messages logged Logging Exception size (2048 bytes) Count and timestamp logging messages: disabled Trap logging: level informational, 20 message lines logged Log Buffer (10000 bytes): 00:05:55: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x22334456 00:05:55: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x22334456 00:05:58: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 00:05:58: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 00:05:58: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x2E0E7C66 00:05:58: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x2E0E7C66 00:05:58: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xE96D24A6 00:05:59: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x32BFEC00 00:05:59: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 00:05:59: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 00:06:01: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xE4B9B300 00:06:01: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 00:06:02: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x4F5E 00:06:02: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x4F5E 00:06:03: DHCP: Try 9 to acquire address for Ethernet1 00:06:03: DHCP: allocate request 00:06:03: DHCP: new entry. add to queue 00:06:03: DHCP: SDiscover attempt # 1 for entry: 00:06:03: Temp IP addr: 0.0.0.0 for peer on Interface: Ethernet1 00:06:03: Temp sub net mask: 0.0.0.0 00:06:03: DHCP Lease server: 0.0.0.0, state: 1 Selecting 00:06:03: DHCP transaction id: 3045 00:06:03: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs 00:06:03: Next timer fires after: 00:00:02 00:06:03: Retry count: 1 Client-ID: 0009.b74d.f92b 00:06:03: DHCP: SDiscover: sending 289 byte length DHCP packet 00:06:03: DHCP: SDiscover 289 bytes 00:06:03: B'cast on Ethernet1 interface from 0.0.0.0 00:06:05: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x6AA102DD 00:06:05: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 00:06:06: DHCP: SDiscover attempt # 2 for entry: 00:06:06: Temp IP addr: 0.0.0.0 for peer on Interface: Ethernet1 00:06:06: Temp sub net mask: 0.0.0.0 00:06:06: DHCP Lease server: 0.0.0.0, state: 1 Selecting 00:06:06: DHCP transaction id: 3045 00:06:06: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs 00:06:06: Next timer fires after: 00:00:02 00:06:06: Retry count: 2 Client-ID: 0009.b74d.f92b 00:06:06: DHCP: SDiscover: sending 289 byte length DHCP packet 00:06:06: DHCP: SDiscover 289 bytes 00:06:06: B'cast on Ethernet1 interface from 0.0.0.0 00:06:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1, changed sta te to down 00:06:09: DHCP: SDiscover attempt # 3 for entry: 00:06:09: Temp IP addr: 0.0.0.0 for peer on Interface: Ethernet1 00:06:09: Temp sub net mask: 0.0.0.0 00:06:09: DHCP Lease server: 0.0.0.0, state: 1 Selecting 00:06:09: DHCP transaction id: 3045 00:06:09: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs 00:06:09: Next timer fires after: 00:00:02 00:06:09: Retry count: 3 Client-ID: 0009.b74d.f92b 00:06:09: DHCP: SDiscover: sending 289 byte length DHCP packet 00:06:09: DHCP: SDiscover 289 bytes 00:06:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1, changed sta te to up 00:06:11: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27F0 00:06:11: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27F0 00:06:11: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 00:06:11: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x1124 00:06:12: DHCP: QScan: Timed out Selecting state 00:06:13: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xF5B96E4F 00:06:13: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xDDC899AD 00:06:14: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x8878B836 00:06:14: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x4F5E 00:06:14: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x4F5E 00:06:16: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC980 00:06:16: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xFFFFC980 00:06:17: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xE7BFEC00 00:06:17: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xF541E74B 00:06:18: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x86BAB300 00:06:18: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x210C 00:06:18: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x210C 00:06:20: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x2E8984E6 00:06:21: DHCP: Received a BOOTREP pkt Not for us..: xid: 0xA706069D 00:06:21: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 00:06:21: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x27C6 Thanks tremendously for the help. Cheers.

And you had "no ip dhcp-client broadcast-flag " configured? I have to ask - it is just my nature ... I guess I should have asked you to repost your sh run after doing the sh log. It is a real mystery (at least to me) how Windows can get a DHCP assigned IP address and your router cannot. However I gather from your posts that you are not alone. The DHCP server does not know that the requesting device is a router ( well unless it looked up the first 6 characters of the MAC address which is the vendor code. I did an Ethereal trace and Windows definitely set the DHCP broadcast-flag bit = 0 you could always try configuring the Windows PC MAC address on the router's outside interface to see what happens ... conf t int e 1 mac-address hhhh.hhhh.hhhh ! where hhhhhhhhhhhh is Windows PC MAC address exit wri mem

Merv wrote: > And you had "no ip dhcp-client broadcast-flag " configured? I have to > ask - it is just my nature ... I guess I should have asked you to > repost your sh run after doing the sh log. Yeah, I really did have 'no ip dhcp...' configured. I followed all your instructions. In any event, here's my 'sh run' log. I'm fairly sure I changed nothing since my last post, except the MAC address of int E1 (which I changed as per your instructions). I'll let you know if that makes any difference. > I did an Ethereal trace and Windows definitely set the DHCP > broadcast-flag bit = 0 You traced what using Ethereal? My traffic? I'm not sure what you're talking about there. In any case, thanks again for the continuing help. I really appreciate it. ?????#sh ru Building configuration... Current configuration : 1053 bytes ! version 12.2 no service pad service timestamps debug uptime service timestamps log uptime service password-encryption ! hostname ????? ! no logging buffered no logging console ! ip subnet-zero ip dhcp excluded-address 10.10.10.1 ! ip dhcp pool CLIENT import all network 10.10.10.0 255.255.255.0 default-router 10.10.10.1 lease 0 2 ! ip audit notify log ip audit po max-events 100 no ip dhcp-client broadcast-flag ! ! ! interface Ethernet0 ip address 10.10.10.1 255.255.255.0 ip nat inside no cdp enable hold-queue 32 in hold-queue 100 out ! interface Ethernet1 mac-address 00e0.295e.f4c9 ip address dhcp client-id Ethernet1 ip nat outside no cdp enable ! ip nat inside source list 102 interface Ethernet1 overload ip classless ip http server ip pim bidir-enable ! ! access-list 23 permit 10.10.10.0 0.0.0.255 access-list 102 permit ip 10.10.10.0 0.0.0.255 any no cdp run ! line con 0 exec-timeout 120 0 stopbits 1 line vty 0 4 access-class 23 in exec-timeout 120 0 login local length 0 ! scheduler max-task-time 5000 end

Similiar Articles:

806 refusing to cooperate. - comp.dcom.sys.cisco
Hi there. I have a LAN in my home composed of 2 PCs, both of which run Windows 98SE. Both PCs are connected via a CISCO 806 broadband router primar...

IOS upgrade through Xmodem in 2500 series router - comp.dcom.sys ...
806 refusing to cooperate. - comp.dcom.sys.cisco IOS upgrade through Xmodem in 2500 series router - comp.dcom.sys ... 806 refusing to cooperate. - comp.dcom.sys.cisco IOS ...

SNMP Traps to Syslog with increased severity - comp.dcom.sys.cisco ...
806 refusing to cooperate. - comp.dcom.sys.cisco... Communications (InsightBB) and I receive high ... comp.dcom.sys.cisco Hi all, i configured SNMP on the Cisco Router ...

PIX 515E Changing from DSL to Cable ISP - comp.dcom.sys.cisco ...
806 refusing to cooperate. - comp.dcom.sys.cisco I don't know if that'll change whatever it ... to obtain a DHCP address from ISP debug dhcp detail ! disconnect/reconnect ...

Limit Distance Mates - comp.cad.solidworks
806 refusing to cooperate. - comp.dcom.sys.cisco... class 23 in exec-timeout 120 0 login local length 0 ... system isn't intelligent enough to properly mate with ...

connect to cisco console from cyclades acs - comp.dcom.sys.cisco ...
806 refusing to cooperate. - comp.dcom.sys.cisco connect to cisco console from cyclades acs - comp.dcom.sys.cisco ... Radius Vendor ID on Cisco Secure ACS - comp.dcom.sys ...

VPN with duplicate LAN subnets - comp.dcom.sys.cisco
806 refusing to cooperate. - comp.dcom.sys.cisco I have a LAN in my home composed of 2 PCs, both of ... password-encryption ! hostname Router ! ! ip subnet-zero ... flag ...

Assigned IP pool from ACS to VPN 3000 - comp.dcom.sys.cisco ...
806 refusing to cooperate. - comp.dcom.sys.cisco Assigned IP pool from ACS to VPN 3000 - comp.dcom.sys.cisco ... 806 refusing to cooperate. - comp.dcom.sys.cisco Assigned ...

how to get lease DHCP expiration time? - comp.unix.solaris ...
806 refusing to cooperate. - comp.dcom.sys.cisco how to get lease DHCP expiration time? - comp.unix.solaris ... 806 refusing to cooperate. - comp.dcom.sys.cisco examine it ...

CONTROLLER-5-UPDOWN, LINEPROTO-5-UPDOWN? - comp.dcom.sys.cisco ...
806 refusing to cooperate. - comp.dcom.sys.cisco CONTROLLER-5-UPDOWN, LINEPROTO-5-UPDOWN? - comp.dcom.sys.cisco ... 806 refusing to cooperate. - comp.dcom.sys.cisco...

806 refusing to cooperate. - comp.dcom.sys.cisco | Computer Group
Hi there. I have a LAN in my home composed of 2 PCs, both of which run Windows 98SE. Both PCs are connected via a CISCO 806 broadband router primar...

7/25/2012 7:59:15 PM