Rasman - 20027

  • Thread starter Thread starter Michael S. Androsov
  • Start date Start date
M

Michael S. Androsov

I received next message in the Event Log on Windows Professional 2000
(SP4) workstation:
Source: Rasman
ID: 20027
Remote Access Connection Manager could not start because NDISWAN could
not be opened. Restart the compyter. Can't find file.

What's a problem?

Michael S. Androsov
EXPOCENTR
 
I suspect that the ndiswan.sys in the %windir%\system32\drivers is missing.
Can you check if the driver is present on your machine? Did you do anything
specific on the machine before you got this event?

--

Thanks
Sharoon
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Sharoon Shetty K said:
I suspect that the ndiswan.sys in the %windir%\system32\drivers is missing.
Can you check if the driver is present on your machine? Did you do anything
specific on the machine before you got this event?

--

Thanks
Sharoon
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
Click to expand...

Yes, ndiswan.sys exists in this directory.
Before I'm trying to change
HKLM\SYSTEM\CurrentControlSet\Services\ndiswan\Start = 4, but after
this message I return this parameter to 3.

Michael S. Androsov
EXPOCENTR
 
Since you have disabled(4) ndiswan, you might have to restart the computer
after changing the start type to 3.

--
Kadir

(e-mail address removed) [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Michael S. Androsov said:
"Sharoon Shetty K [MSFT]" <[email protected]> wrote in message
I suspect that the ndiswan.sys in the %windir%\system32\drivers is missing.
Can you check if the driver is present on your machine? Did you do anything
specific on the machine before you got this event?

--

Thanks
Sharoon
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
Click to expand...

Yes, ndiswan.sys exists in this directory.
Before I'm trying to change
HKLM\SYSTEM\CurrentControlSet\Services\ndiswan\Start = 4, but after
this message I return this parameter to 3.

Michael S. Androsov
EXPOCENTR
Click to expand...
 
I'm restarted the computer more one times.

Michael S. Androsov
EXPOCENTR

Kadirvel C Vanniarajan said:
Since you have disabled(4) ndiswan, you might have to restart the computer
after changing the start type to 3.

--
Kadir

(e-mail address removed) [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Michael S. Androsov said:
"Sharoon Shetty K [MSFT]" <[email protected]> wrote in message
I suspect that the ndiswan.sys in the %windir%\system32\drivers is missing.
Can you check if the driver is present on your machine? Did you do anything
specific on the machine before you got this event?

--

Thanks
Sharoon
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.

I received next message in the Event Log on Windows Professional 2000
(SP4) workstation:
Source: Rasman
ID: 20027
Remote Access Connection Manager could not start because NDISWAN could
not be opened. Restart the compyter. Can't find file.

What's a problem?

Michael S. Androsov
EXPOCENTR
Click to expand...

Yes, ndiswan.sys exists in this directory.
Before I'm trying to change
HKLM\SYSTEM\CurrentControlSet\Services\ndiswan\Start = 4, but after
this message I return this parameter to 3.

Michael S. Androsov
EXPOCENTR
Click to expand...
Click to expand...
 
Back
Top