Anyone on RAS services???

P

Pal

Hello.

It was all working fine in my W2K server. This morning
noticed that RAS user was unable to connect to the RAS
server. The event log shows, Event ID: 20152. The current
configured authentication provider failed to initialize
successfully. The parameter is incorrect. Tried several
times to restart the service but no use. Also deleted the
RAS configuration and recreated but back to same errors.

I am not sure how to proceed on this error to get the RAS
service up and running. Thank you in advance for your
help.

Pal.
 
M

Manjari Bonam [MSFT]

Authentication provider failed to load and initialize. This could be because

(1) If configured for RADIUS authentication:

a. check whether the rasrad.dll file exists under
%SystemRoo%\system32.

b. RADIUS server name is misspelled or RADIUS server is not running.

(2) If configured for Windows authentication:

IAS Server initialization failed


Resolution:
 
M

Manjari Bonam [MSFT]

(1) If you configured RADIUS authentication:

If Radius authentication is configured by mistake, you can reconfigure RRAS
for Windows Authentication using Server
a. Snap-in.

b. See whether the radius server name is spelled correctly, server is
up and reachable.

(2) If configured for Windows Authentication:

Check the local machine's event viewer for IAS specific events.
 
P

Pal

Hi,

My server is "Windows authentication". Secondly, I didn't
find any service by name IAS in the services and no
specific errors reported in the Event viewer.

Pal.
 
M

Manjari Bonam [MSFT]

Sorry about the IAS part.
Do you see any other suspecting events ?
 
S

Sharoon Shetty K [MSFT]

There were many instances of this error while upgrading SBS and this was
related to the remote access policies being corrupted, or some files being
missing.

The below solution was helpful to people in that scenario please elt me know
if it solves your problem too-

Expand the dnary.md_ and ias.md_ files from the CD and copy them to the
winnt\system32\ias folder after backing up the old ones.

Run the following commands from the command prompt:
C:\Program Files\Common Files\System\Ole DB>regsvr32 oledb32r.dll
C:\Program Files\Common Files\System\Ole DB>regsvr32 oledb32.dll
 
S

Srivatsan [MSFT]

If that doesn't work, you can try registering ias*.dlls under system32
directory.

Steps: (1) Goto %Windir%\system32
(2) run regsvr32 of the following files:

regsvr32 /s iasacct.dll
regsvr32 /s iasads.dll
regsvr32 /s iashlpr.dll
regsvr32 /s iasmmc.dll
regsvr32 /s iasnap.dll
regsvr32 /s iasperf.dll
regsvr32 /s iaspipe.dll
regsvr32 /s iaspolcy.dll
regsvr32 /s iasrad.dll
regsvr32 /s iasrecst.dll
regsvr32 /s iassam.dll
regsvr32 /s iassdo.dll
regsvr32 /s iassvcs.dll
regsvr32 /s iasuserr.dll
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top