• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

NT4 & Ras Service problems

S

Sharpy1969

Junior Member
Hi Guys perhaps someone could help me out?...

I am having problems with a machine and the RAs service. On startup i get the "service has failed to startup check event log" msg and these are the errors:

Source: Remote Access
Event ID: 20074
Point to Point Protocol engine was unable to load the module.

Source: Remote Access
Event ID: 20067
Remote Access Connection Manager failed to start because the Point to Point Protocol failed to initialize.

Source: Service Control Manager
Event ID: 7023
The Remote Access Connection Manager service terminated with the following error:
The specified module could not be found.

Source: Service Control Manager
Event ID: 7001
The Remote Access Autodial Manager service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The specified module could not be found.

When double clicking the dialup networking icon i get "Rasman Initialization error 711"

My knowledge of NT is quite sketchy to say the least but so far i have uninstalled tcp/ip, netbui, ras and reinstalled them. I have also installed service pack 6a.

Any suggestions?...i'm pulling out what little hair i have!
 
Did you intall the patch for the RPC exploit/blaster worm? That thing fscks up NT4 RRAS.
If you have, remove it and see if RAS works. If it does, go to MS's site. There should be a new version of the security update that doesn't cause RAS to fail.
 
Yes, I think you helped me as well. I got a call from one of my remote users, he said he could not log in when dialing up (NT 4 RAS as well). Kept saying bad username or password. Checked EVERYTHING I could think of and everything seemed to be fine. I uninstaled the patch, reinstalled it and so far I noticed some other people dial'd in last nite, so it appears all is well. M$ really sucks!
 
Glad to help guys. This drove us nuts for a couple of days with a couple of large clients with older servers. Guess this is MS's subtle way of telling you it's time to upgrade, huh? 😉
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top