"John Wunderlich" wrote:

> =?Utf-8?B?TWlsdA==?= <M***@discussions.microsoft.com> wrote in
> news:EA57D73A-BDC2-4039-B271-A04B6CC43A2C@microsoft.com:
>
> > My Comcast broadband cable access has failed for an hour or two
> > several times in the last month. Comcast is of no help.
> >
> > When it fails, my modem power, receive and pc activity lamps are
> > on. The send lamp is flashing. And the on line lamp is off. I've
> > tried removing the router and connecting the modem directly to my
> > computer. And I've tried rebooting. Neither action restores my
> > connection.
>
> Cable modems are typically configured to only give out one IP address
> to one device.  If you have a router connected to the modem, then the
> router gets that IP address.  If you disconnect the router and
> connect the computer directly to your modem, the modem sees a 2nd
> device and won't give out an address unless the modem is unplugged
> from the wall power then repowered -- in which case the first device
> it sees gets the IP address.  (i.e. Power cycle the modem, not the
> computer).
>
>
> >
> > I looked in Windows Event Viewer/System/ Properties. I find this
> > error message:
> > "The IP address lease 192.168.1.2 for the Network Card with
> > network address 0080AD7XXXXXX has been denied by the DHCP server
> > 0.0.0.0. {The DHCP Server sent a DHCPNACK message}."
> > As I read the error message, it seems to say that Comcast's server
> > is the problem.
>
> When a computer negotiates for an IP address, it sometimes takes a
> shortcut step of saying "Last time I had IP address XXX.XXX.XXX.XXX"
> to the DHCP server in hopes of getting the same address.  If, for
> whatever reason the DHCP server doesn't like this address, it will
> negotiate an alternate address and this error appears in the Event
> log. This error is perfectly normal and shouldn't be a concern.  In
> your case, this error originates in a DHCP negotiation between your
> computer and your router -- not the modem or your ISP.  This error
> would be expected if you disconnect your computer from your router
> and connect it directly to the modem as the modem would not give out
> a 192.168.x.x address.
>
> > If I do nothing, the connection restores itself in an
> > hour or two.
>
> More than likely, there was just a disruption in service which was
> corrected during that time.
>
> HTH,
>   John
>
>