Local Area Connection properties problem/error - unable to access

Hi -

I have a problem in accessing the properties of my Local Area
Connection under the Network Connections folder. When I right-click
on the Local Area Connection, then click on Properties, I would get a
box saying something like "Windows has encountered a problem..." and
asks to send an Error Report. When I click on Debug, the box goes
away and the desktop seems to just refresh itself. The one time I
managed to get some info (by looking at the "technical details" of the
problem), I saw stuff like: netshell.dll, explorer.exe,
code:0xc0000005, Flags: 0x00000000, Record: 0x0000000000000 (not sure
how many zeroes), Address: 0x0000000075d30f20. Typically, I'd only
get this error box the first time I try this after I've re-booted.
All other times, the desktop would just refresh itself.

I can access properties only if I disable the connection. I'm using
XP Home with an on-board Realtek network adapter. I connect directly
to a Motorola surfboard modem.

I've tried the following suggestions from this newsgroup (nothing
seems to work):
- uninstall NIC under Device Manager and let Windows detect card when
re-installing; reboot.
- regsvr32 netshell.dll and ole32.dll; reboot.
- I tried sfc/ scannow to look for corrupted files, but come up with
nothing.

I would appreciate help on this - the reason why I'm doing this is
because I seem to run into internet connectivity problems, and while I
was debugging it with my ISP, we had to try and get into the TCP/IP
properties using the method above, and I would get this error.
Naturally, the ISP person decides it's a problem with my computer and
would not help me any further ((

If you're also curious about the type of internet connectivity problem
I have (just in case these are related) - I would be surfing fine for
a day or two and then I would lose my connection (which would require
a reboot, or a enable/disable of the local area connection, or a
ipconfig release/renew - depending on how the planets are aligned).
When I was debugging this with my ISP, we determined that I am getting
a good signal. Under command prompt, I can NOT ping a URL address
(i.e. www.something.com), but I CAN ping it's IP address (i.e.
xx.xxx.xx.xxx). At this point the ISP person said it was a DNS
problem and THAT's when we tried to get into the properties
button....and here I am today.

Thanks!!!! (I'll be away for the next 3 days, so please don't think
I'm ignoring you if I don't post it right back).

An update so far -

I also tried to regsvr32 netcfgx.dll and netman.dll to no avail. Both
done in Safe Mode with Networking. No go.

Tried to reset TCP/IP stack via netsh int reset C:\resetlog.txt. Also
tried hitting the "Repair" button on the Local Area Connection.

Also tried my ISP's suggestion of uninstalling Zonealarm. No go there
either.

I am *so* close to just re-installing the original PC setup. (XP came
pre-installed) Maybe I should wait for XP SP2 before going ahead?

(Edwin R.) wrote in message . com...
Hi -

I have a problem in accessing the properties of my Local Area
Connection under the Network Connections folder. When I right-click
on the Local Area Connection, then click on Properties, I would get a
box saying something like "Windows has encountered a problem..." and
asks to send an Error Report. When I click on Debug, the box goes
away and the desktop seems to just refresh itself. The one time I
managed to get some info (by looking at the "technical details" of the
problem), I saw stuff like: netshell.dll, explorer.exe,
code:0xc0000005, Flags: 0x00000000, Record: 0x0000000000000 (not sure
how many zeroes), Address: 0x0000000075d30f20. Typically, I'd only
get this error box the first time I try this after I've re-booted.
All other times, the desktop would just refresh itself.

I can access properties only if I disable the connection. I'm using
XP Home with an on-board Realtek network adapter. I connect directly
to a Motorola surfboard modem.

I've tried the following suggestions from this newsgroup (nothing
seems to work):
- uninstall NIC under Device Manager and let Windows detect card when
re-installing; reboot.
- regsvr32 netshell.dll and ole32.dll; reboot.
- I tried sfc/ scannow to look for corrupted files, but come up with
nothing.

I would appreciate help on this - the reason why I'm doing this is
because I seem to run into internet connectivity problems, and while I
was debugging it with my ISP, we had to try and get into the TCP/IP
properties using the method above, and I would get this error.
Naturally, the ISP person decides it's a problem with my computer and
would not help me any further ((

If you're also curious about the type of internet connectivity problem
I have (just in case these are related) - I would be surfing fine for
a day or two and then I would lose my connection (which would require
a reboot, or a enable/disable of the local area connection, or a
ipconfig release/renew - depending on how the planets are aligned).
When I was debugging this with my ISP, we determined that I am getting
a good signal. Under command prompt, I can NOT ping a URL address
(i.e. www.something.com), but I CAN ping it's IP address (i.e.
xx.xxx.xx.xxx). At this point the ISP person said it was a DNS
problem and THAT's when we tried to get into the properties
button....and here I am today.

Thanks!!!!

Another update -

Installed XP Service Pack 2 (SP2) last night - now I can access
properties properly without having to disable the Local Area
Connection )))))) I don't know what it fixed, maybe a corrupt .dll
file (although the sfc /scannow didn't report any previously)?

Hopefully SP2 will also get rid of my intermittent connection problem.
We will see.......

(Edwin R.) wrote in message . com...
An update so far -

I also tried to regsvr32 netcfgx.dll and netman.dll to no avail. Both
done in Safe Mode with Networking. No go.

Tried to reset TCP/IP stack via netsh int reset C:\resetlog.txt. Also
tried hitting the "Repair" button on the Local Area Connection.

Also tried my ISP's suggestion of uninstalling Zonealarm. No go there
either.

I am *so* close to just re-installing the original PC setup. (XP came
pre-installed) Maybe I should wait for XP SP2 before going ahead?

(Edwin R.) wrote in message . com...
Hi -

I have a problem in accessing the properties of my Local Area
Connection under the Network Connections folder. When I right-click
on the Local Area Connection, then click on Properties, I would get a
box saying something like "Windows has encountered a problem..." and
asks to send an Error Report. When I click on Debug, the box goes
away and the desktop seems to just refresh itself. The one time I
managed to get some info (by looking at the "technical details" of the
problem), I saw stuff like: netshell.dll, explorer.exe,
code:0xc0000005, Flags: 0x00000000, Record: 0x0000000000000 (not sure
how many zeroes), Address: 0x0000000075d30f20. Typically, I'd only
get this error box the first time I try this after I've re-booted.
All other times, the desktop would just refresh itself.

I can access properties only if I disable the connection. I'm using
XP Home with an on-board Realtek network adapter. I connect directly
to a Motorola surfboard modem.

I've tried the following suggestions from this newsgroup (nothing
seems to work):
- uninstall NIC under Device Manager and let Windows detect card when
re-installing; reboot.
- regsvr32 netshell.dll and ole32.dll; reboot.
- I tried sfc/ scannow to look for corrupted files, but come up with
nothing.

I would appreciate help on this - the reason why I'm doing this is
because I seem to run into internet connectivity problems, and while I
was debugging it with my ISP, we had to try and get into the TCP/IP
properties using the method above, and I would get this error.
Naturally, the ISP person decides it's a problem with my computer and
would not help me any further ((

If you're also curious about the type of internet connectivity problem
I have (just in case these are related) - I would be surfing fine for
a day or two and then I would lose my connection (which would require
a reboot, or a enable/disable of the local area connection, or a
ipconfig release/renew - depending on how the planets are aligned).
When I was debugging this with my ISP, we determined that I am getting
a good signal. Under command prompt, I can NOT ping a URL address
(i.e. www.something.com), but I CAN ping it's IP address (i.e.
xx.xxx.xx.xxx). At this point the ISP person said it was a DNS
problem and THAT's when we tried to get into the properties
button....and here I am today.

Thanks!!!!