Can't access MS Client, Protocols, Services, etc.

heh heh I don't know about that "great minds" thing ...sometimes mine won't
work at all :

if I happen to defrag my brain and come up with anything ..I'll let you
know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think alike. I
have tried everything that you suggested, even LSPFIX. I, too, thought
that it might be a stack problem. I will try dleting the PWL files that
next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run this
...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have ...a
corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from device
manager in safe mode ?

this is about the only info I can seem to find( they seem to frown upon
my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you have
suggested. I removed everything from the Network including DUN and
VPN. Restarted the computer and reinstalled the NIC. I still have the
same problem when I try to access any of the Client or Protocol items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100 adapter
driver and let Windows detect and reinstall the driver software.
When that failed, I tried downloading an updated driver on another
computer and updated the computer in question. Starting in safe mode
didn't get me anywhere either. Can you think of any files that might
have to be re-registered like the MSHTML.DLL that could be causing
the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an error
message related to MSHTML.DLL when starting his computer. I was
able to re-register MSHTML.DLL and reinstall Internet Explorer to
remove the error messages. Now, I'm trying to configure the
computer to get back on the network, but when I try to add MS
Client for Windows, any Protocols, etc. the program is not
responding. I can click on the "Add" button, but when I try to
select "Client", or any of the other options, there is no response.
I have run System File Checker, and reinstalled the files
associated with the various clients, protocols, etc., but still no
response.

Does anyone have any ideas? I've never seen this sort of behavior.
I have run SpyBot, Ad-aware, Spyware Doctor, and Norton Corporate
anti-virus without any problems. I've run Scandisk (Thorough) and
nothing seems to correct the problem. I'd like to avoid
reinstalling Windows 98SE and all of the applications like Office
2000. I've used "msconfig" to load just the basic startup
programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let the NIC
reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the drill
is to remove "all" networking components in control panel/network.

reboot to safe mode and remove "all" instances of network adapters in
device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay tuned :

have you by chance tried extracting a new copy of the network control applet
? netcpl.cpl

it may be corrupt (geez that could explain something : )

"Haggis" wrote in message
...

heh heh I don't know about that "great minds" thing ...sometimes mine
won't work at all :

if I happen to defrag my brain and come up with anything ..I'll let you
know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think alike. I
have tried everything that you suggested, even LSPFIX. I, too, thought
that it might be a stack problem. I will try dleting the PWL files that
next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run
this ...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have ...a
corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from device
manager in safe mode ?

this is about the only info I can seem to find( they seem to frown
upon my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you have
suggested. I removed everything from the Network including DUN and
VPN. Restarted the computer and reinstalled the NIC. I still have the
same problem when I try to access any of the Client or Protocol
items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100 adapter
driver and let Windows detect and reinstall the driver software.
When that failed, I tried downloading an updated driver on another
computer and updated the computer in question. Starting in safe
mode didn't get me anywhere either. Can you think of any files that
might have to be re-registered like the MSHTML.DLL that could be
causing the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an error
message related to MSHTML.DLL when starting his computer. I was
able to re-register MSHTML.DLL and reinstall Internet Explorer to
remove the error messages. Now, I'm trying to configure the
computer to get back on the network, but when I try to add MS
Client for Windows, any Protocols, etc. the program is not
responding. I can click on the "Add" button, but when I try to
select "Client", or any of the other options, there is no
response. I have run System File Checker, and reinstalled the
files associated with the various clients, protocols, etc., but
still no response.

Does anyone have any ideas? I've never seen this sort of
behavior. I have run SpyBot, Ad-aware, Spyware Doctor, and Norton
Corporate anti-virus without any problems. I've run Scandisk
(Thorough) and nothing seems to correct the problem. I'd like to
avoid reinstalling Windows 98SE and all of the applications like
Office 2000. I've used "msconfig" to load just the basic startup
programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let the
NIC reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the drill
is to remove "all" networking components in control panel/network.

reboot to safe mode and remove "all" instances of network adapters
in device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay tuned
:

have you by chance tried extracting a new copy of the network control applet
? netcpl.cpl

it may be corrupt (geez that could explain something : )

"Haggis" wrote in message
...

heh heh I don't know about that "great minds" thing ...sometimes mine
won't work at all :

if I happen to defrag my brain and come up with anything ..I'll let you
know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think alike. I
have tried everything that you suggested, even LSPFIX. I, too, thought
that it might be a stack problem. I will try dleting the PWL files that
next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run
this ...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have ...a
corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from device
manager in safe mode ?

this is about the only info I can seem to find( they seem to frown
upon my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you have
suggested. I removed everything from the Network including DUN and
VPN. Restarted the computer and reinstalled the NIC. I still have the
same problem when I try to access any of the Client or Protocol
items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100 adapter
driver and let Windows detect and reinstall the driver software.
When that failed, I tried downloading an updated driver on another
computer and updated the computer in question. Starting in safe
mode didn't get me anywhere either. Can you think of any files that
might have to be re-registered like the MSHTML.DLL that could be
causing the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an error
message related to MSHTML.DLL when starting his computer. I was
able to re-register MSHTML.DLL and reinstall Internet Explorer to
remove the error messages. Now, I'm trying to configure the
computer to get back on the network, but when I try to add MS
Client for Windows, any Protocols, etc. the program is not
responding. I can click on the "Add" button, but when I try to
select "Client", or any of the other options, there is no
response. I have run System File Checker, and reinstalled the
files associated with the various clients, protocols, etc., but
still no response.

Does anyone have any ideas? I've never seen this sort of
behavior. I have run SpyBot, Ad-aware, Spyware Doctor, and Norton
Corporate anti-virus without any problems. I've run Scandisk
(Thorough) and nothing seems to correct the problem. I'd like to
avoid reinstalling Windows 98SE and all of the applications like
Office 2000. I've used "msconfig" to load just the basic startup
programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let the
NIC reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the drill
is to remove "all" networking components in control panel/network.

reboot to safe mode and remove "all" instances of network adapters
in device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay tuned
:

Haggis,

Thanks for all the time you have devoted to this issue. I will be returning
to the customer's office on Saturday. I'll give the extraction a try. I'm
also going to install a different Network Card, but I don't think the card
is the issue. I tried installing DUN and couldn't get any further when
trying to install a protocol for it.

Joe G.


"Haggis" wrote in message
...

have you by chance tried extracting a new copy of the network control
applet ? netcpl.cpl

it may be corrupt (geez that could explain something : )

"Haggis" wrote in message
...

heh heh I don't know about that "great minds" thing ...sometimes mine
won't work at all :

if I happen to defrag my brain and come up with anything ..I'll let you
know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think alike. I
have tried everything that you suggested, even LSPFIX. I, too, thought
that it might be a stack problem. I will try dleting the PWL files that
next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run
this ...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have
...a corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from device
manager in safe mode ?

this is about the only info I can seem to find( they seem to frown
upon my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you have
suggested. I removed everything from the Network including DUN and
VPN. Restarted the computer and reinstalled the NIC. I still have
the same problem when I try to access any of the Client or Protocol
items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100
adapter driver and let Windows detect and reinstall the driver
software. When that failed, I tried downloading an updated driver
on another computer and updated the computer in question. Starting
in safe mode didn't get me anywhere either. Can you think of any
files that might have to be re-registered like the MSHTML.DLL that
could be causing the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an error
message related to MSHTML.DLL when starting his computer. I was
able to re-register MSHTML.DLL and reinstall Internet Explorer to
remove the error messages. Now, I'm trying to configure the
computer to get back on the network, but when I try to add MS
Client for Windows, any Protocols, etc. the program is not
responding. I can click on the "Add" button, but when I try to
select "Client", or any of the other options, there is no
response. I have run System File Checker, and reinstalled the
files associated with the various clients, protocols, etc., but
still no response.

Does anyone have any ideas? I've never seen this sort of
behavior. I have run SpyBot, Ad-aware, Spyware Doctor, and
Norton Corporate anti-virus without any problems. I've run
Scandisk (Thorough) and nothing seems to correct the problem.
I'd like to avoid reinstalling Windows 98SE and all of the
applications like Office 2000. I've used "msconfig" to load just
the basic startup programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let the
NIC reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the drill
is to remove "all" networking components in control panel/network.

reboot to safe mode and remove "all" instances of network adapters
in device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay tuned
:

Haggis,

Thanks for all the time you have devoted to this issue. I will be returning
to the customer's office on Saturday. I'll give the extraction a try. I'm
also going to install a different Network Card, but I don't think the card
is the issue. I tried installing DUN and couldn't get any further when
trying to install a protocol for it.

Joe G.


"Haggis" wrote in message
...

have you by chance tried extracting a new copy of the network control
applet ? netcpl.cpl

it may be corrupt (geez that could explain something : )

"Haggis" wrote in message
...

heh heh I don't know about that "great minds" thing ...sometimes mine
won't work at all :

if I happen to defrag my brain and come up with anything ..I'll let you
know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think alike. I
have tried everything that you suggested, even LSPFIX. I, too, thought
that it might be a stack problem. I will try dleting the PWL files that
next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run
this ...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have
...a corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from device
manager in safe mode ?

this is about the only info I can seem to find( they seem to frown
upon my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you have
suggested. I removed everything from the Network including DUN and
VPN. Restarted the computer and reinstalled the NIC. I still have
the same problem when I try to access any of the Client or Protocol
items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100
adapter driver and let Windows detect and reinstall the driver
software. When that failed, I tried downloading an updated driver
on another computer and updated the computer in question. Starting
in safe mode didn't get me anywhere either. Can you think of any
files that might have to be re-registered like the MSHTML.DLL that
could be causing the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an error
message related to MSHTML.DLL when starting his computer. I was
able to re-register MSHTML.DLL and reinstall Internet Explorer to
remove the error messages. Now, I'm trying to configure the
computer to get back on the network, but when I try to add MS
Client for Windows, any Protocols, etc. the program is not
responding. I can click on the "Add" button, but when I try to
select "Client", or any of the other options, there is no
response. I have run System File Checker, and reinstalled the
files associated with the various clients, protocols, etc., but
still no response.

Does anyone have any ideas? I've never seen this sort of
behavior. I have run SpyBot, Ad-aware, Spyware Doctor, and
Norton Corporate anti-virus without any problems. I've run
Scandisk (Thorough) and nothing seems to correct the problem.
I'd like to avoid reinstalling Windows 98SE and all of the
applications like Office 2000. I've used "msconfig" to load just
the basic startup programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let the
NIC reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the drill
is to remove "all" networking components in control panel/network.

reboot to safe mode and remove "all" instances of network adapters
in device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay tuned
:

post back if you have any luck (or not)

I suppose a scanreg/ restore wouldn't so any good at this point...

I spend some of my spare time here because I like to see people solve
problems :
I hope at least I gave some alternate routes to take :

Cheers!
"Joe Gazda" wrote in message
...
Haggis,

Thanks for all the time you have devoted to this issue. I will be
returning to the customer's office on Saturday. I'll give the extraction a
try. I'm also going to install a different Network Card, but I don't think
the card is the issue. I tried installing DUN and couldn't get any further
when trying to install a protocol for it.

Joe G.


"Haggis" wrote in message
...

have you by chance tried extracting a new copy of the network control
applet ? netcpl.cpl

it may be corrupt (geez that could explain something : )

"Haggis" wrote in message
...

heh heh I don't know about that "great minds" thing ...sometimes mine
won't work at all :

if I happen to defrag my brain and come up with anything ..I'll let you
know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think alike.
I have tried everything that you suggested, even LSPFIX. I, too,
thought that it might be a stack problem. I will try dleting the PWL
files that next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run
this ...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have
...a corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from
device manager in safe mode ?

this is about the only info I can seem to find( they seem to frown
upon my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you
have suggested. I removed everything from the Network including DUN
and VPN. Restarted the computer and reinstalled the NIC. I still
have the same problem when I try to access any of the Client or
Protocol items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100
adapter driver and let Windows detect and reinstall the driver
software. When that failed, I tried downloading an updated driver
on another computer and updated the computer in question.
Starting in safe mode didn't get me anywhere either. Can you
think of any files that might have to be re-registered like the
MSHTML.DLL that could be causing the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an error
message related to MSHTML.DLL when starting his computer. I was
able to re-register MSHTML.DLL and reinstall Internet Explorer
to remove the error messages. Now, I'm trying to configure the
computer to get back on the network, but when I try to add MS
Client for Windows, any Protocols, etc. the program is not
responding. I can click on the "Add" button, but when I try to
select "Client", or any of the other options, there is no
response. I have run System File Checker, and reinstalled the
files associated with the various clients, protocols, etc., but
still no response.

Does anyone have any ideas? I've never seen this sort of
behavior. I have run SpyBot, Ad-aware, Spyware Doctor, and
Norton Corporate anti-virus without any problems. I've run
Scandisk (Thorough) and nothing seems to correct the problem.
I'd like to avoid reinstalling Windows 98SE and all of the
applications like Office 2000. I've used "msconfig" to load
just the basic startup programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let the
NIC reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the
drill is to remove "all" networking components in control
panel/network.

reboot to safe mode and remove "all" instances of network adapters
in device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay tuned
:

post back if you have any luck (or not)

I suppose a scanreg/ restore wouldn't so any good at this point...

I spend some of my spare time here because I like to see people solve
problems :
I hope at least I gave some alternate routes to take :

Cheers!
"Joe Gazda" wrote in message
...
Haggis,

Thanks for all the time you have devoted to this issue. I will be
returning to the customer's office on Saturday. I'll give the extraction a
try. I'm also going to install a different Network Card, but I don't think
the card is the issue. I tried installing DUN and couldn't get any further
when trying to install a protocol for it.

Joe G.


"Haggis" wrote in message
...

have you by chance tried extracting a new copy of the network control
applet ? netcpl.cpl

it may be corrupt (geez that could explain something : )

"Haggis" wrote in message
...

heh heh I don't know about that "great minds" thing ...sometimes mine
won't work at all :

if I happen to defrag my brain and come up with anything ..I'll let you
know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think alike.
I have tried everything that you suggested, even LSPFIX. I, too,
thought that it might be a stack problem. I will try dleting the PWL
files that next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run
this ...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have
...a corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from
device manager in safe mode ?

this is about the only info I can seem to find( they seem to frown
upon my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you
have suggested. I removed everything from the Network including DUN
and VPN. Restarted the computer and reinstalled the NIC. I still
have the same problem when I try to access any of the Client or
Protocol items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100
adapter driver and let Windows detect and reinstall the driver
software. When that failed, I tried downloading an updated driver
on another computer and updated the computer in question.
Starting in safe mode didn't get me anywhere either. Can you
think of any files that might have to be re-registered like the
MSHTML.DLL that could be causing the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an error
message related to MSHTML.DLL when starting his computer. I was
able to re-register MSHTML.DLL and reinstall Internet Explorer
to remove the error messages. Now, I'm trying to configure the
computer to get back on the network, but when I try to add MS
Client for Windows, any Protocols, etc. the program is not
responding. I can click on the "Add" button, but when I try to
select "Client", or any of the other options, there is no
response. I have run System File Checker, and reinstalled the
files associated with the various clients, protocols, etc., but
still no response.

Does anyone have any ideas? I've never seen this sort of
behavior. I have run SpyBot, Ad-aware, Spyware Doctor, and
Norton Corporate anti-virus without any problems. I've run
Scandisk (Thorough) and nothing seems to correct the problem.
I'd like to avoid reinstalling Windows 98SE and all of the
applications like Office 2000. I've used "msconfig" to load
just the basic startup programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let the
NIC reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the
drill is to remove "all" networking components in control
panel/network.

reboot to safe mode and remove "all" instances of network adapters
in device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay tuned
:

I'm sorry to say that the client has decided to trash his existing computer
and purchase another after the New Year. He was having so many problems with
it that he decided to give up on trying to fix it. He thinks that he can
purchase one of those cheap advertised desktops and his troubles will be
over. Boy, is he in for a rude awakening.

Thanks for all of your suggestions.

Joe G.

"Haggis" wrote in message
...
post back if you have any luck (or not)

I suppose a scanreg/ restore wouldn't so any good at this point...

I spend some of my spare time here because I like to see people solve
problems :
I hope at least I gave some alternate routes to take :

Cheers!
"Joe Gazda" wrote in message
...
Haggis,

Thanks for all the time you have devoted to this issue. I will be
returning to the customer's office on Saturday. I'll give the extraction
a try. I'm also going to install a different Network Card, but I don't
think the card is the issue. I tried installing DUN and couldn't get any
further when trying to install a protocol for it.

Joe G.


"Haggis" wrote in message
...

have you by chance tried extracting a new copy of the network control
applet ? netcpl.cpl

it may be corrupt (geez that could explain something : )

"Haggis" wrote in message
...

heh heh I don't know about that "great minds" thing ...sometimes mine
won't work at all :

if I happen to defrag my brain and come up with anything ..I'll let you
know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think alike.
I have tried everything that you suggested, even LSPFIX. I, too,
thought that it might be a stack problem. I will try dleting the PWL
files that next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run
this ...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have
...a corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from
device manager in safe mode ?

this is about the only info I can seem to find( they seem to frown
upon my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you
have suggested. I removed everything from the Network including
DUN and VPN. Restarted the computer and reinstalled the NIC. I
still have the same problem when I try to access any of the Client
or Protocol items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100
adapter driver and let Windows detect and reinstall the driver
software. When that failed, I tried downloading an updated
driver on another computer and updated the computer in question.
Starting in safe mode didn't get me anywhere either. Can you
think of any files that might have to be re-registered like the
MSHTML.DLL that could be causing the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an error
message related to MSHTML.DLL when starting his computer. I was
able to re-register MSHTML.DLL and reinstall Internet Explorer
to remove the error messages. Now, I'm trying to configure the
computer to get back on the network, but when I try to add MS
Client for Windows, any Protocols, etc. the program is not
responding. I can click on the "Add" button, but when I try to
select "Client", or any of the other options, there is no
response. I have run System File Checker, and reinstalled the
files associated with the various clients, protocols, etc., but
still no response.

Does anyone have any ideas? I've never seen this sort of
behavior. I have run SpyBot, Ad-aware, Spyware Doctor, and
Norton Corporate anti-virus without any problems. I've run
Scandisk (Thorough) and nothing seems to correct the problem.
I'd like to avoid reinstalling Windows 98SE and all of the
applications like Office 2000. I've used "msconfig" to load
just the basic startup programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let the
NIC reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the
drill is to remove "all" networking components in control
panel/network.

reboot to safe mode and remove "all" instances of network
adapters in device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay
tuned :

I'm sorry to say that the client has decided to trash his existing computer
and purchase another after the New Year. He was having so many problems with
it that he decided to give up on trying to fix it. He thinks that he can
purchase one of those cheap advertised desktops and his troubles will be
over. Boy, is he in for a rude awakening.

Thanks for all of your suggestions.

Joe G.

"Haggis" wrote in message
...
post back if you have any luck (or not)

I suppose a scanreg/ restore wouldn't so any good at this point...

I spend some of my spare time here because I like to see people solve
problems :
I hope at least I gave some alternate routes to take :

Cheers!
"Joe Gazda" wrote in message
...
Haggis,

Thanks for all the time you have devoted to this issue. I will be
returning to the customer's office on Saturday. I'll give the extraction
a try. I'm also going to install a different Network Card, but I don't
think the card is the issue. I tried installing DUN and couldn't get any
further when trying to install a protocol for it.

Joe G.


"Haggis" wrote in message
...

have you by chance tried extracting a new copy of the network control
applet ? netcpl.cpl

it may be corrupt (geez that could explain something : )

"Haggis" wrote in message
...

heh heh I don't know about that "great minds" thing ...sometimes mine
won't work at all :

if I happen to defrag my brain and come up with anything ..I'll let you
know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think alike.
I have tried everything that you suggested, even LSPFIX. I, too,
thought that it might be a stack problem. I will try dleting the PWL
files that next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run
this ...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have
...a corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from
device manager in safe mode ?

this is about the only info I can seem to find( they seem to frown
upon my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you
have suggested. I removed everything from the Network including
DUN and VPN. Restarted the computer and reinstalled the NIC. I
still have the same problem when I try to access any of the Client
or Protocol items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100
adapter driver and let Windows detect and reinstall the driver
software. When that failed, I tried downloading an updated
driver on another computer and updated the computer in question.
Starting in safe mode didn't get me anywhere either. Can you
think of any files that might have to be re-registered like the
MSHTML.DLL that could be causing the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an error
message related to MSHTML.DLL when starting his computer. I was
able to re-register MSHTML.DLL and reinstall Internet Explorer
to remove the error messages. Now, I'm trying to configure the
computer to get back on the network, but when I try to add MS
Client for Windows, any Protocols, etc. the program is not
responding. I can click on the "Add" button, but when I try to
select "Client", or any of the other options, there is no
response. I have run System File Checker, and reinstalled the
files associated with the various clients, protocols, etc., but
still no response.

Does anyone have any ideas? I've never seen this sort of
behavior. I have run SpyBot, Ad-aware, Spyware Doctor, and
Norton Corporate anti-virus without any problems. I've run
Scandisk (Thorough) and nothing seems to correct the problem.
I'd like to avoid reinstalling Windows 98SE and all of the
applications like Office 2000. I've used "msconfig" to load
just the basic startup programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let the
NIC reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the
drill is to remove "all" networking components in control
panel/network.

reboot to safe mode and remove "all" instances of network
adapters in device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay
tuned :

happy to try :

--
Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

Windows support http://www.aumha.org
"Joe Gazda" wrote in message
news:OtqdnRvv1YuSFD3enZ2dnUVZ_tudnZ2d@wideopenwest .com...
I'm sorry to say that the client has decided to trash his existing
computer and purchase another after the New Year. He was having so many
problems with it that he decided to give up on trying to fix it. He thinks
that he can purchase one of those cheap advertised desktops and his
troubles will be over. Boy, is he in for a rude awakening.

Thanks for all of your suggestions.

Joe G.

"Haggis" wrote in message
...
post back if you have any luck (or not)

I suppose a scanreg/ restore wouldn't so any good at this point...

I spend some of my spare time here because I like to see people solve
problems :
I hope at least I gave some alternate routes to take :

Cheers!
"Joe Gazda" wrote in message
...
Haggis,

Thanks for all the time you have devoted to this issue. I will be
returning to the customer's office on Saturday. I'll give the extraction
a try. I'm also going to install a different Network Card, but I don't
think the card is the issue. I tried installing DUN and couldn't get any
further when trying to install a protocol for it.

Joe G.


"Haggis" wrote in message
...

have you by chance tried extracting a new copy of the network control
applet ? netcpl.cpl

it may be corrupt (geez that could explain something : )

"Haggis" wrote in message
...

heh heh I don't know about that "great minds" thing ...sometimes mine
won't work at all :

if I happen to defrag my brain and come up with anything ..I'll let
you know!

"Joe Gazda" wrote in message
...
This only goes to show that great minds (or not so great) think
alike. I have tried everything that you suggested, even LSPFIX. I,
too, thought that it might be a stack problem. I will try dleting the
PWL files that next time I visit the customer.

"Haggis" wrote in message
...

hmm..I wonder if your TCP stack may be buggered ...can't hurt to run
this ...

http://cexx.org/lspfix.htm



"Haggis" wrote in message
...

just an after thought ...try deleting any *.pwl files you may have
...a corrupt password file could be the culprit


"Haggis" wrote in message
...
yes , but did you remove the NIC (and any other adapters) from
device manager in safe mode ?

this is about the only info I can seem to find( they seem to frown
upon my doing so much research...better get back to work! LOL)


"Joe Gazda" wrote in message
...
Thanks for your quick response, but I've already tried what you
have suggested. I removed everything from the Network including
DUN and VPN. Restarted the computer and reinstalled the NIC. I
still have the same problem when I try to access any of the
Client or Protocol items.

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
The first thing that I did was to remove the Linksys LNE100
adapter driver and let Windows detect and reinstall the driver
software. When that failed, I tried downloading an updated
driver on another computer and updated the computer in
question. Starting in safe mode didn't get me anywhere either.
Can you think of any files that might have to be re-registered
like the MSHTML.DLL that could be causing the failure?

Joe G.

"Haggis" wrote in message
...

"Joe Gazda" wrote in message
...
I have a customer running Windows 98SE. He was getting an
error message related to MSHTML.DLL when starting his
computer. I was able to re-register MSHTML.DLL and reinstall
Internet Explorer to remove the error messages. Now, I'm
trying to configure the computer to get back on the network,
but when I try to add MS Client for Windows, any Protocols,
etc. the program is not responding. I can click on the "Add"
button, but when I try to select "Client", or any of the other
options, there is no response. I have run System File Checker,
and reinstalled the files associated with the various clients,
protocols, etc., but still no response.

Does anyone have any ideas? I've never seen this sort of
behavior. I have run SpyBot, Ad-aware, Spyware Doctor, and
Norton Corporate anti-virus without any problems. I've run
Scandisk (Thorough) and nothing seems to correct the problem.
I'd like to avoid reinstalling Windows 98SE and all of the
applications like Office 2000. I've used "msconfig" to load
just the basic startup programs.

Thanks for any help you can send my way.

Joe G.
Dearborn, MI


is your network adapter installed ok ? no errors in device
manager...boot to safe mode , multiple copies of NIC ?

in safe mode , remove all network adapters ..reboot and let
the NIC reinstall ..then try your MS client etc.

let us know :




I went and did a little research ...from what I can see , the
drill is to remove "all" networking components in control
panel/network.

reboot to safe mode and remove "all" instances of network
adapters in device manager.

the reboot and reinstall NIC and Client....I can't see any other
quick fixes ...but someone else may jump in with one ...stay
tuned :