Technical Problem: Need Hardware/DSL Genius

[msd]

OK...I am a software guy who knows VERY little about hardware. Here's the problem.

Running WinXP Pro. The single machine is connected directly into a Westell DSL modem (older model) which is connected to Verizon online. I had the service for about three years with no problems.

About six months ago, a strange phenomenon begins. The DSL modem's activity (ethernet) light would begin to flash steady and I would lose all ability to send/receive any packets. All web sites were could not be displayed, no mail access, no nothing. I reboot the machine and turn off/turn on the DSL modem and everything is good for a half hour and then the same thing.

I tried everything. I probably spent close to ten total hours on the phone with Verizon DSL tech support and they swear it's not the modem...ok when I reset it, it works so maybe they're right.

I even tried switching providers to another DSL provider (Comcast) on the off chance that it was the modem...same problem. Then, on a lark, I switched out the ethernet card...problem goes away and went away for 6 months. No issues...at all.

And now...the problem is back...

So, my question...does the "it works for a half hour and then the activity light begins to blink steady and I am dead" phenonenon sound familiar to anyone strong in the way of DSL fu?

Am I resigned to replacing the NIC every 6 months for 20 bucks?

Thanks in advance,
matt

 

[3catcircus]

Check the status of XP's built-in firewall...

 

[dogoftheunderworld]

it's gotta be the modem

I'm pretty sure the Westell modems were the ones that had a tendancy periodically crud out. I would have your carrier change to a newer(and different brand) modem. Also, make sure you check for firmware updates for the modem as well.)

Brian
<><

 

[Vascant]

Sounds like a stupid trojan I had a few months ago..
I would make very sure the system is clean of all unhealthy vermin but be warned, the CR is pretty high so bring a cleric.

 

[msd]

Sounds like a stupid trojan I had a few months ago..
I would make very sure the system is clean of all unhealthy vermin but be warned, the CR is pretty high so bring a cleric.

Yeah...my latest conversation with Verizon suggested that this might be the case, but SpySweeper (with the latest definitions) says I'm cool.

Should I be using something in addition to SpySweeper to check?

 

[Chroma]

Try both <a href="http://www.safer-networking.org/en/index.html">Spybot Search & Destroy</a> and <a href="http://www.lavalsoft.de">AdAware</a>, with updated definitions to see what you've got lurking on your system. I've had them find things SpySweeper missed.

 

[Setanta]

This might be unwanted software, but not spyware. The next time this behaviour is happening, open your network control panel, and double click on your local area connection. In the window that opens up, look at the packets sent number. If it's incrementing rapidly (like, if your computer is idle, and it's sending more than a few packets a second), something is very wrong.

At that point, some virus programs might be able to help, or maybe not. If you're network savvy, you could download a sniffer like Ethereal (google) and figure out exactly what's up, then google a fix. If neither of those steps help, then you might have to:

1) Buy a hardware firewall (all windows broadband users should have one). I like Netgear, but there are plenty of other brands.
2) Put it between your PC and DSL/Cable modem.
3) Format your harddrive and reinstall everything.
4) Be careful about e-mail attachments and downloads from untrustworthy sites.
5) Use a relatively secure browser and e-mail program if you're not already.

Hopefully you don't have to take step 3, but there are trojans and what not that can be hard to get rid of.

 

[Davek]

I had a similar problem with my laptop. My laptop has onboard network port and a firewire port. There was a mini-port bridge that was bridging the two ports.

I was having access problems when I noticed that both ports were running through the bridge. I deactivated the bridge, and activated the network port by itself, and that seemed to fix the problem.

Unfortunately this mini-port bridge seems to reset itself (or mayby windows update triggers something that reactivates it) so periodically I have to repeat the process.