Kvatz
asked on
Routing and Remote Access not starting; can't set up advanced network connection XP Pro SP2
I cannot get the Routing and Remote access service to start, and when I try to set up an advanced connection it hangs after choosing "host" and "next" when it should give choices like infrared, etc. I have done several of the things suggested here in other posts, icluding importing the RAS registry key from a working XP Pro computer, setting all the permissions to "allow" for everything, deleting the EAP 25 and 26 folders from RASMAN, etc., etc. The one error I inevitably get in the Event Viewer is "Unable to load C:\WINDOWS\System32\iprtrm
I have also tried to get a dialup connection to work with an ISP (Earthlink) but it always connects and gives the error 172--wrong protocols. It does this, too, on AOL dialup, so I don't think it's the ISP. I think this may be all part of the same problem, but I don't know.
I do have a working XP SP2 computer from which I can export and import any keys that are necessary.
Any ideas?
Thanks.
Ken
I have also tried to get a dialup connection to work with an ISP (Earthlink) but it always connects and gives the error 172--wrong protocols. It does this, too, on AOL dialup, so I don't think it's the ISP. I think this may be all part of the same problem, but I don't know.
I do have a working XP SP2 computer from which I can export and import any keys that are necessary.
Any ideas?
Thanks.
Ken
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, I have been through the KB 299013.
I have the rarepair.exe -- don't know if it's a current version --and I'll try it again.
Thanks very much.
I have the rarepair.exe -- don't know if it's a current version --and I'll try it again.
Thanks very much.
Sure, Please do let me know if it worked. I will be more than happy to find more solutions for you..:)
ASKER
Complete (I think) success!!!
Here are all the details if anyone is interested. Maybe this answer will show up in a future search by someone else with some of the same issues.
I just ran rarepair.exe as you suggested, it uninstalled the components, reinstalled them, and the Routing and Remote Access Service started up immediately.
Not only that, but Incoming Connection appeared under My Network Places, I was able to get into the Add a New Connection Wizard, there was a completely different appearing interface now for adding a dialup modem connection to the Network Places, and the dialup connection to my ISP, Earthlink, worked seamlessly instead of giving the various protocol errors. IOW, no connection problems, finally!
It has been almost a year since this particular computer has functioned normally in terms of networking and connections. I had tried to do a rarepair much earlier, and it failed, probably because it could not at that time install the necessary files.
I think it all started when I upgraded my MB early in 2006 and tried to do a repair install of XP SP1 and then upgrade it to SP2. I couldn't get the files to copy then from the XP disk i386 directory, or even the one on my HD. I sort of did a force install of SP2, and eventually got most of the services running, all except for RRAS and the dialup. Then, last week, I tried to install .Net Framework 3.0 in order to get a new New York Times Reader to install. I couldn't get .Net Framework 3.0 to install and was told to uninstall the IIS Service and reinstall it. I couldn't reinstall the IIS because Windows would not expand and copy the necessary files again from the i386 directory, starting with staxmem.dll. I searched that out and found MS KB894351 which said that if "Setup cannot copy the file staxmem.dll" to perform various operations involving the secedit.sdb file, which I did. Then I was able to reinstall the IIS service, and the .Net Framework 3.0, and the Reader.
I think the secedit.sdb operations which enabled the IIS service files to be copied and installed must have /also/ fixed the problem using rarepair.exe which, as I said before, had failed previously. I don't know this for sure.
The moral of this story may be that when you upgrade a MB, do a clean install of XP rather than a repair install. It will save time in the end. It's possible that my XP SP2 was corrupted prior to the MB upgrade, but I have been told by others that repair installs of XP always lead to problems down the line--always.
To BAMIT99, I can only thank you hugely for getting me on the right track and getting the problem fixed.
Ken
Here are all the details if anyone is interested. Maybe this answer will show up in a future search by someone else with some of the same issues.
I just ran rarepair.exe as you suggested, it uninstalled the components, reinstalled them, and the Routing and Remote Access Service started up immediately.
Not only that, but Incoming Connection appeared under My Network Places, I was able to get into the Add a New Connection Wizard, there was a completely different appearing interface now for adding a dialup modem connection to the Network Places, and the dialup connection to my ISP, Earthlink, worked seamlessly instead of giving the various protocol errors. IOW, no connection problems, finally!
It has been almost a year since this particular computer has functioned normally in terms of networking and connections. I had tried to do a rarepair much earlier, and it failed, probably because it could not at that time install the necessary files.
I think it all started when I upgraded my MB early in 2006 and tried to do a repair install of XP SP1 and then upgrade it to SP2. I couldn't get the files to copy then from the XP disk i386 directory, or even the one on my HD. I sort of did a force install of SP2, and eventually got most of the services running, all except for RRAS and the dialup. Then, last week, I tried to install .Net Framework 3.0 in order to get a new New York Times Reader to install. I couldn't get .Net Framework 3.0 to install and was told to uninstall the IIS Service and reinstall it. I couldn't reinstall the IIS because Windows would not expand and copy the necessary files again from the i386 directory, starting with staxmem.dll. I searched that out and found MS KB894351 which said that if "Setup cannot copy the file staxmem.dll" to perform various operations involving the secedit.sdb file, which I did. Then I was able to reinstall the IIS service, and the .Net Framework 3.0, and the Reader.
I think the secedit.sdb operations which enabled the IIS service files to be copied and installed must have /also/ fixed the problem using rarepair.exe which, as I said before, had failed previously. I don't know this for sure.
The moral of this story may be that when you upgrade a MB, do a clean install of XP rather than a repair install. It will save time in the end. It's possible that my XP SP2 was corrupted prior to the MB upgrade, but I have been told by others that repair installs of XP always lead to problems down the line--always.
To BAMIT99, I can only thank you hugely for getting me on the right track and getting the problem fixed.
Ken
Hey Thank you Ken for your kind words !!!..:)
It is quite possible that the Security Settings in your Computer got corrupted due to which services were not able to access System\Dll files properly and as a result were causing issues. I am assuming here that you may have reset the Security Database which in turn provided the default access to all the Services and thus you were finally able to install IIS and run RAREPAIR.EXE too!!! :)
It is quite possible that the Security Settings in your Computer got corrupted due to which services were not able to access System\Dll files properly and as a result were causing issues. I am assuming here that you may have reset the Security Database which in turn provided the default access to all the Services and thus you were finally able to install IIS and run RAREPAIR.EXE too!!! :)
ASKER
I even ran the C:\wmi\wmidiag.vbs WMI diagnostic program today, and for the first time in a year it reports no problem!
Interesting observation--in the device manager, under Network adapters, there is now something called a RAS Async Adapter which wasn't there before, and it has a yellow exclamation point. If I update the driver under "choose your own" it updates it, says to reboot, but the adapter is still there. And it cannot be uninstalled.
This is not a problem, aparently, but strange. I wonder what it is?
Ken
Interesting observation--in the device manager, under Network adapters, there is now something called a RAS Async Adapter which wasn't there before, and it has a yellow exclamation point. If I update the driver under "choose your own" it updates it, says to reboot, but the adapter is still there. And it cannot be uninstalled.
This is not a problem, aparently, but strange. I wonder what it is?
Ken
I think it is normally created if you use a PPPOE Connection to connect to the Internet so are you?...
http://support.microsoft.com/kb/299013