Some Can and Some Cant

Hi!

My client has a 2000 Server. (NOT SBS) All the service packs are installed.

He has a small cheap NetGear Router.

Two times the other day, 4 of his 10 computers could not connect to the
Internet. The remaining newer computers could. I could ping www.yahoo.com
with the newer XP Professional computers but not the older XP Professional
computers.

I did not try to ping an IP Address. All the computers on the network have
been scanned for viruses with the latest Symantec Virus Scanner and I also
Ran LavaSoft on all of them. Those tools did not find any problems.

I can ping the server's NetBios name with all the computer even when I can't
ping the Internet. So there is not a cabling problem.

What else can I look for that could cause this problem>

Dale

When you ping yahoo.com:

1. If you get a host not found error, the problem is likely DNS. Run
ipconfig /flushdns between tests.

2. If the name resolves but the request times out, the problem is likely
the default gateway.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Bikini Browser" <(E-Mail Removed)> wrote in message
news:#S6QknE#(E-Mail Removed)...
> Hi!
>
> My client has a 2000 Server. (NOT SBS) All the service packs are
installed.
>
> He has a small cheap NetGear Router.
>
> Two times the other day, 4 of his 10 computers could not connect to the
> Internet. The remaining newer computers could. I could ping
www.yahoo.com
> with the newer XP Professional computers but not the older XP Professional
> computers.
>
> I did not try to ping an IP Address. All the computers on the network
have
> been scanned for viruses with the latest Symantec Virus Scanner and I also
> Ran LavaSoft on all of them. Those tools did not find any problems.
>
> I can ping the server's NetBios name with all the computer even when I
can't
> ping the Internet. So there is not a cabling problem.
>
> What else can I look for that could cause this problem>
>
> Dale
>
>
>
>
>

Thanks for the idea for DNS Flush. I will try that. It has worked for me
before But I didn't think to check that. I also forgot to try to ping an IP
address versus a host name. I can't believe I forgot to test that while I
was there.

>>If the name resolves but the request times out, the problem is likely
> the default gateway.<< What would you check about the default gateway? Do
> you mean the Router might be bad? What do you mean?

Dale


"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in
message news:OE2F1xE%(E-Mail Removed)...
> When you ping yahoo.com:
>
> 1. If you get a host not found error, the problem is likely DNS. Run
> ipconfig /flushdns between tests.
>
> 2. If the name resolves but the request times out, the problem is likely
> the default gateway.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Bikini Browser" <(E-Mail Removed)> wrote in message
> news:#S6QknE#(E-Mail Removed)...
>> Hi!
>>
>> My client has a 2000 Server. (NOT SBS) All the service packs are
> installed.
>>
>> He has a small cheap NetGear Router.
>>
>> Two times the other day, 4 of his 10 computers could not connect to the
>> Internet. The remaining newer computers could. I could ping
> www.yahoo.com
>> with the newer XP Professional computers but not the older XP
>> Professional
>> computers.
>>
>> I did not try to ping an IP Address. All the computers on the network
> have
>> been scanned for viruses with the latest Symantec Virus Scanner and I
>> also
>> Ran LavaSoft on all of them. Those tools did not find any problems.
>>
>> I can ping the server's NetBios name with all the computer even when I
> can't
>> ping the Internet. So there is not a cabling problem.
>>
>> What else can I look for that could cause this problem>
>>
>> Dale
>>
>>
>>
>>
>>
>
>