Internetworkers: http://www.ibiblio.org/internetworkers/

[matusiak <dave AT matusiak.org>]

Judy --

Did you have any power protection on the D-Link router?  If not, 'Ol 
Sparky may have gotten you.  The red flag for me is that the WAN LED is 
blinking.  Now, if there were data passing, this would be normal.  But 
since things *don't* appear to be working, I would say that is a 
diagnostic indicator that the unit may need repair and/or replacement.

Can you contact your DSL provider to see if they will swap one out for 
you?  I'd try that first (altho they may charge for such a service).  
Thankfully, it sounds like that unit took the brunt of the damage and 
your laptop is A-okay.

Out of curiosity, which "Ethernet light" stays on when directly 
connected?  Is this a PCMCIA card modem on the laptop?  Or is it a 
built-in modem off the laptop motherboard.  Doesn't make too much 
difference, but I'm trying to visualize how all this is connected.  
Hope this helps some.

dave m.

On Jul 23, 2004, at 9:52 AM, Judy Hallman wrote:

> Lightening took out my DSL service last night. I'm debugging. Dialup
> works. If I bypass the router and connect the modem directly to my 
> laptop,
> I can connect to Bellsouth. I get an error message that the phone line 
> is
> busy, but it connects anyhow. (Error 676 The phone line is busy)
>
> I can't connect through the router -- a D-Link DI-624. The lights on 
> the
> router look correct -- power on, local network on, WLAN LED on, M1 LED
> solid light on (indicates the DI-624 is ready), WAN LED is blinking 
> (this
> LED blinks during data transmission). The M2 LED is _off_ (a solid 
> light
> indicates the unit is defective).
>
> The modem is a Westell Wirespeed. When I connect directly to my laptop,
> the Ethernet light is on. When I connect it to the router, the light 
> stays
> off.
>
> Looks to me like the router thinks its OK and the modem thinks its OK 
> but
> they won't talk to each other.
>
> Any thoughts?
>
> Judy Hallman (hallman AT rtpnet.org, http://www.rtpnet.org/hallman)
> Executive Director, RTPnet, NC (http://www.RTPnet.org/)