RE: Network disappears, now "unreachable" -- complicated problem I thi
- From: "Kevin" <Kevin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 2 Jan 2006 07:42:04 -0800
Did you ever resolve your problem? I'm having a similar problem with Win XP
PRO. DHCP just won't acquire an IP address from the Router. Believe you me
I've tried everything.
o Tried another router
o tried another cable
o tried another nic
o rebuilt WinXP Pro
o on the phone with Microsoft - 3 hrs
o on the phone with Verizon - 1/2 hour
o on the phone with Belkin - 1 hour
I'm going to try a fixed IP address next, but I was just wondering if you
fixed your problem?
--
Regards,
Kevin
"Richard" wrote:
> While my son was using his computer the other night to IM his friends
> and to save a file on a networked drive, the network disappeared. Two
> things were happening around that time: a microsoft XP update arrived
> and, it appears later from reading the log, Symantic Anti-virus
> quarantined a Trojan.Stwoyle virus.
>
> At this point:
>
> 1) The wired network connection won't acquire an address through
> DHCP. I've given it an alternate address that's within the range of
> the network.
>
> 2) A USB wireless device can acquire a DHCP address and connects to
> our wireless network, but doesn't get us into any computers or to the
> router.
>
> 3) Browsers can't find anything.
>
> 4) Pinging the router or anything else on the network produces
> "destination host unreachable."
>
> 5) 'net view' and usually 'network neighborhood' produce a correct
> list of the two XP computers on the network, but not the linux machine
> running samba. If I click on one of the computers or one of the listed
> shares in network neighborhood it tells me that it's not available.
>
> What have I done?
>
> 1) pulled my hair out.
> 2) Followed the instructions on the Symantec site regarding the virus.
> None of the registry entries that it said to look for were actually in
> my registry.
> 3) Followed the instructions on Microsoft knowledge base 909444 about
> problems that can occur after the latest critical update (MS05-051).
> 4) Gone back to a system restore point from before the update and the
> virus.
> 5) Run system file checker successfully (sfc /scannow)
>
> Still no joy.
>
> Suspicious things that may or may not mean anything:
>
> 1. 'pathping' to the router address shows that there is 100% loss
> between the host with its legit network address and the same host with
> an address of 0.0.0.0 Shouldn't this ping go directly from the host to
> the router address?
>
> 2. netstat -r shows a whole host of information, but none of it
> reveals a route to the router address which is also the gateway and DNS
> server.
>
> So, nothing is getting out of my computer to the network.
>
> Any ideas and assistance would be much appreciated. Thanks in advance.
>
> Richard
>
>
.
- Prev by Date: Re: Bridge building
- Next by Date: Problem accessing by machine name or IP address -- localhost works fine
- Previous by thread: Re: Bridge building
- Next by thread: Problem accessing by machine name or IP address -- localhost works fine
- Index(es):
Relevant Pages
|
