Problem enabling/disabling ethernet connection

[philrock]

I recently put together a computer with an Intel D945PSNLK motherboard and an Intel P4 LGA775 processor. The machine works quite well in almost all regards, except that I'm not able to easily enable and disable the ethernet connection. I'm using the ethernet driver that came with the motherboard. The ethernet controller is built into the motherboard.

On another machine I have, I put a shortcut to the ethernet connection in the Quick Launch area. If currently enabled, and I click on the shortcut, a Local Area Connection Status window comes up. I click on disable, and Windows complies. If currently disabled, and I click on the shortcut, I get a quick "Enabling..." message, then I'm enabled.

On the new machine, if currently enabled, and I click on the icon, the Local Area Connection Status window comes up, but when I try to disable I get the message "It is not possible to disable the connection at this time. This connection may be using one or more protocols that do not support Plug-and Play, or it may have been initiated by another user or the system account." If currently disabled, and I click on the icon, I get the messages: "Enabling..." then "Connection failed!"

The only way I can enable or disable the connection is to go into the properties and configuration of the connection - not at all convenient. For now, if I want to be off line, I have resorted to turning off the DSL modem. Also not convenient, because when I want to go back on line, the modem takes a couple of minutes to get up to speed.

How can I get the new machine to behave the way the old one does with regard to enabling/disabling the ethernet connection?

 

[bcastner]

Try:

Start | RUN | cmd
netsh int ip reset reset.log
netsh winsock reset

Reboot.

Start | RUN | cmd

net stop cryptsvc
ren %systemroot%\System32\Catroot2 oldcatroot2
Reboot your computer.

 

[bcastner]

This could be a driver issue, but I tend to doubt it.

SYMPTOMS
If you have a network device driver with an unsigned co-installer and you use the Windows XP operating system, you cannot disable or enable the device from the Network Connections folder (that is, you cannot right-click the device and then click Enable/Disable).

You can, however, enable or disable the device from the Device Manager.

Source:

http://support.microsoft.com/default.aspx?scid=kb;en-us;318291

This usually means that the Cryptographic Service has stopped and is not running.

 

[dglienna]

Create two batch files

Kill:
ipconfig /release_all

and the other one

Fix:
ipconfig /renew

Save them as .cmd files, and click on one to kill the connection, and the other to renew it.

I do this to kill the WZS Service occasionally.

-David
2006 Microsoft Most Valueable Professional (MVP)
2006 Dell Certified System Professional (CSP)

 

[linney]

If you have a software firewall you can most probably use a setting from that to block all Internet access.

Clicking Work Offline in IE can also stop a lot of Internet access.

 

[philrock]

Thank you for your responses.

bcastner, your suggestion did not work. I'm a lightweight when it comes to these things, so I followed your instructions without fully understanding them. The system gave what looked like reasonable responses to each command. Did these commands do anything I should reverse?

bcastner, in your 2nd message you quoted Microsoft as saying, "If you have a network device driver with an unsigned co-installer..." Would Intel provide such a driver?

Perhaps I should have said more about the situation. I'm running XP Home Edition. I'm not on a real network - just my machine and a DSL modem with a single ethernet port.

 

[philrock]

Is it possible to create a script file that duplicates what I do when I go through the long processes of enabling and disabling?

 

[linney]

Many large software companies produce unsigned drivers (HP for example), it doesn't mean the driver is faulty, just that the driver has not been submitted to, or tested by, Microsoft and certified suitable for Windows.

 

[bcastner]

I agree. But if you read the article the use of an unsigned driver for your network adapter would lead to the behavior the original poster is asking about:

CAUSE
The Device Manager runs in the logged-on user context and is, therefore, allowed to disable or enable devices with unsigned co-installers. However, the request from the Network Connections folder to enable or disable devices is sent to a LocalSystem service, which is not allowed to enable or disable devices because an unsigned co-installer cannot be trusted to run in the logged-on user context.

STATUS
This behavior is by design.

And, do not shoot the messenger.

 

[bcastner]

Q1: "bcastner, your suggestion did not work. I'm a lightweight when it comes to these things, so I followed your instructions without fully understanding them. The system gave what looked like reasonable responses to each command. Did these commands do anything I should reverse?"

A1: No. The first command rebuilds your TCP/IP service. The second command rebuilds your Winsock stacks.

Q2: "bcastner, in your 2nd message you quoted Microsoft as saying, "If you have a network device driver with an unsigned co-installer..." Would Intel provide such a driver?"

A2: Probably not. As I mentioned earlier it seemed to me unlikely as a cause. But the KB article does describe your circumstance.

As I mentioned earlier the most common cause of this is a problem with the Cryptographic Service.

I would check your Events Manager cache to see if this service is reporting errors or is stopped.

 

[bcastner]

Is your driver current?

http://downloadfinder.intel.com/scr...XP+Professional&lang=eng&strOSs=44&submit=Go!

 

[bcastner]

Hunch time:

1. Copy/paste the below into Notepad and save as C:\disable_fix.cmd :

regsvr32 softpub.dll
regsvr32 Wintrust.dll
regsvr32 Initpki.dll
regsvr32 Dssenh.dll
regsvr32 Rsaenh.dll
regsvr32 Gpkcsp.dll
regsvr32 Sccbase.dll
regsvr32 Slbcsp.dll
regsvr32 Mssip32.dll
regsvr32 Cryptdlg.dll

2. Start, Run, and enter CMD

3. At the CMD box, enter C:\disable_fix.cmd

Say OK if prompted. Type exit to return to XP and test again.

 

[philrock]

bcastner,

disable_fix.cmd ran successfully but did not fix the problem.

Updating the LAN driver did fix the problem. Thanks a million for your help!

 

[bcastner]

Good, and thanks for the feedback.
You sure as heck have a clean Cryptographic service now as well!

Best,
Bill Castner