Vexing problem, is not malware, help please?

LlarionLlarion St. Petersburg FL
edited February 2007 in Science & Tech
See the attached thread for granular particulars andf logfiles...
http://www.short-media.com/forum/showthread.php?t=54372

The short form:

- My wife's machine stopped talking to the network, no changes were made to network infrastructure; it worked, then suddenly it didn't.
- Did all due diligence to eliminate malware. (See other thread)
- NIC will not pull IP address from DHCP server (Router is SonicWALL TZ-150)
- NIC will accept static IP assignment within the subnet, but will still not connect.
- Cannot ping gateway, any LAN address , or any WAN address.
- Eliminated NIC as the problem (?), installed different NIC (Compaq NC3134), same results
- Did non-destructive OS reload from factory restore partition, no difference.
- All other network devices (including my machine, wireless access points, and print servers) all functioning normally.
- Trying to avoid destructive OS reload, but it's looking grim.

Machine in question is HP Pavilion A1600N, Dual core A64, XP Media Center. NVidia onboard NIC.

Any ideas?

Thanks very much in advance!

Comments

  • LlarionLlarion St. Petersburg FL
    edited February 2007
    PLEASE DISREGARD, PROBLEM HAS BEEN DISCOVERED AND FIXED!
    There is a small switch on the network that this machine is plugged into and a port appears to be bad on it; I got to messing with it and discovered it; it was not a red flag because the other AP attached to it was working fine, and link lights were present, and I'd reset the switch, but I hadn't done any port-juggling.

    Time for a new switch... :)

    Thanks to everyone who has read and/or assisted!!!
  • TroganTrogan London, UK
    edited February 2007
    Glad you figured it out! :thumbsup:
  • mtroxmtrox Minnesota
    edited February 2007
    Nice job. Its not always easy to diagnose bad hardware. It tends to be the 15th thing you consider after all the software avenues are exhausted.
  • LlarionLlarion St. Petersburg FL
    edited February 2007
    mtrox wrote: »
    Nice job. Its not always easy to diagnose bad hardware. It tends to be the 15th thing you consider after all the software avenues are exhausted.

    Funny you should say that; because I'm a hardware guy, and I should have been more thorough in doing the hardware diligence first before I got all caught up in malware intrigue. But, sometimes, it's the dumbest things you don't test, and I should know better.

    But, the good news is, I learned a ton about malware diagnosis in this exercise, so I'm better prepared to help others with it now!

    Plus, I be foldin'. :D
  • LincLinc Owner Detroit Icrontian
    edited February 2007
    Llarion wrote: »
    Plus, I be foldin'. :D
    Welcome to the team and site! :cool: Glad to have you here.
Sign In or Register to comment.