IP Stack problems win98se

Any ideas on what would cause the ip stack to blow up on a
win98se machine? Try to run winipcfg get Winsock failed
errors. Same with ping function.

In article <04c101c3a570$975c88d0$(E-Mail Removed)>, "Justin"
<(E-Mail Removed)> wrote:
>Any ideas on what would cause the ip stack to blow up on a
>win98se machine? Try to run winipcfg get Winsock failed
>errors. Same with ping function.

Lots of things could cause the problem: installing bad software,
overwriting a system file, hardware problems, . . .

If you'll post another message with details of the problem, including
the complete text of the error messages, someone can probably tell you
how to fix it.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

Most likely incorrect installtion. Update firmware and drivers if possible.

I have had this problem once with a D-Link card. Got a LinkSys and it
worked fine.

Steve Winograd [MVP] wrote:
> In article <04c101c3a570$975c88d0$(E-Mail Removed)>, "Justin"
> <(E-Mail Removed)> wrote:
>> Any ideas on what would cause the ip stack to blow up on a
>> win98se machine? Try to run winipcfg get Winsock failed
>> errors. Same with ping function.
>
> Lots of things could cause the problem: installing bad software,
> overwriting a system file, hardware problems, . . .
>
> If you'll post another message with details of the problem, including
> the complete text of the error messages, someone can probably tell you
> how to fix it.

>-----Original Message-----
>In article <04c101c3a570$975c88d0
$(E-Mail Removed)>, "Justin"
><(E-Mail Removed)> wrote:
>>Any ideas on what would cause the ip stack to blow up on
a
>>win98se machine? Try to run winipcfg get Winsock failed
>>errors. Same with ping function.
>
>Lots of things could cause the problem: installing bad
software,
>overwriting a system file, hardware problems, . . .
>
>If you'll post another message with details of the
problem, including
>the complete text of the error messages, someone can
probably tell you
>how to fix it.
>--
>Best Wishes,
>Steve Winograd, MS-MVP (Windows Networking)
>
>Please post any reply as a follow-up message in the news
group
>for everyone to see. I'm sorry, but I don't answer
questions
>addressed directly to me in E-mail or news groups.
>
>Microsoft Most Valuable Professional - Windows Networking
>http://mvp.support.microsoft.com
>
>Steve Winograd's Networking FAQ
>http://www.bcmaven.com/networking/faq.htm
>.
>

Thanks everyone. We killed the NIC card and reg entries
associated with it, reinstalled a new one along with the
new drivers etc. It is running like a champ now. Think
that a dll may have been overwritten during a software
install by the user, which was the intitial issue. Didn't
know that in my origianl post.