Upgrade to XP Pro from Home on Compaq Laptop Destroys Net Connection?

[docw]

Hi. I'm so glad to have found this great online community at last!

Having this "problem" I attempted to "Search" out the answer in a previous thread to no avail. I hope that this is the proper place to post this query. While there may well be, in fact hopefully, a relatively simple solution, I'm humbled by my inabilty to find it!

Strangely, after performing an upgrade to XP Pro on a Compaq Presario laptop that came with Windows XP Home installed, the ability to connect to the internet via dialup was suddenly lost!

I tried many things including just going to "Control Panel", then Network and Internet Connections, and creating a New connection. I also tried a fresh install of the AOL 8.0 software as well.

I think I tracked it down to a #711 connection error. Therefore the problem seems to relate to an inabiltiy to start the "Remote Access Connection Manager" since I get an error message, #5, that "could not start on local computer."

Similarly, I can not start the "Remote Access Auto Connection Manager," getting a #1068 error message "could not start the remote access auto connection manager on local computer. The dependency service or group failed to start."

It also seems that the wizard(s), to which one is so often prompted, do not work properly either in this case. There's possibly some kind of configuration error it seems - somehow, somewhere?

It just won't let me turn on the RACM or the Remote Access Auto Connection Manager no matter what!

FWIW, when doing the upgrade/install, curiously, the dynamic version appeared to not go through properly due to a lost internet connection and so I had to do a static one.

Also, I'd thought the default value for XP Pro, as well as XP Home, was to have these already started and "on!"

Is it somehow possibly seeing/thinking that the local computer/network is not giving access/permission and so it won't start! Is this feasible? Or likely ?

All I really want to do now is to simply get this one laptop computer going with ability to dialup access to the web for now. It's perhaps seeing a nonexistent LAN as "down" and this unable to grant permission perhaps? I think it will not let the computer access the internet directly since it is theoretically dissconected from the LAN based on the unplugged LAN depiction in network connections! It's conceivably looking for an entire domain, not just one computer with no LAN connection?

In any case, I'll need to make the laptop able to use a dialup connection to an ISP somehow!

If you have any ideas for a solution please let me know. Kindly let me know what you think. Thanks again, in advance.

Very gratefully,

Mark

[Confused]

What does phone and modem connections show under control panel?
Chas

[docw]

Thanks very much, Chas.

Under the phone and modem options menu, it indicates:

a home dialing option checked with the proper area code noted.

a Conexant 56K ACLink modem set on on COM 3. Its' location is PCI bus 0, device 8, function 0. It is working properly and enabled. FWIW, I'd also lowered the port speed down to 57,600 in an attempt to get a proper and stable connection - to no avail.

Also, a number of telephony options are installed on this computer including the Microsoft H.323 Telephony Service Provider. (And the telephony option is started!)

Again, the modem itself appeared to check out just fine with the basic toubleshooting tests.

Curiously with AOL, it attempts, via dialup, to connect in order to obtain the menu of dialup numbers successfully. Yet when the AOL dialups are tried, it seemingly has some difficulties, in contrast to the previous good experiences with XP Home. It always takes three rather long attempts to connect and then as the frontpage AOL menu loads, there is an error noted in the top right hand corner that "AOL has detected that there is a 'problem' with your internet connection. You should sign off and shut down your computer and try again." Nothing is available online with such a "connection" including the help menu. Naturally, no one at AOL can tell me what the problem is, sadly!

In contrast, attempting to connect to Netzero via the local dialup number leads to generating an immediate error connection message (#711).

Is there anything else, specifically, that you might need to know?

Thanks again,

Mark

[Confused]

From MS knowledge database;
http://support.microsoft.com/default...b;en-us;330163
Chas

[docw]

Thanks, Chas.

Yes, thanks. I'd also found this information, and it confirmed my earlier thoughts. Yet, I seemingly can't start the services as required. Sorry, I was perhaps less than entirely clear above when I noted in the initial post:

---

...Therefore the problem seems to relate to an inabiltiy to start the "Remote Access Connection Manager" since I get an error message, #5, that "could not start on local computer."

Similarly, I can not start the "Remote Access Auto Connection Manager," getting a #1068 error message "could not start the remote access auto connection manager on local computer. The dependency service or group failed to start."

It also seems that the wizard(s), to which one is so often prompted, do not work properly either in this case. There's possibly some kind of configuration error it seems - somehow, somewhere?

It just won't let me turn on the RACM or the Remote Access Auto Connection Manager no matter what! ...

----

How can I do this? I'm denied access for some reason. If I could do it, that is "START" these services, I would!

I'll need to know how to do so!

Perhaps I'll need to just eliminate the LAN connection? Should I try to do this via the Device Manager?

I'm desperately trying to figure out what might have caused this "problem."

Any "solutions" are more than welcome!

Thanks again,

Mark

[young&dumb]

you could try this http link

it worked for me when I installed xp pro over xp then I got the same symptoms.

[docw]

Thanks. Sadly, I'd somehow missed this initially. Possibly it was because I did not, at least knowingly, do a "RESTORE!" Perhaps MS consdiers the upgrade to "Pro" from "Home" as a restore or something?

In any case, did you actually do the suggested "resolution" and reinstall SP1 or pergrom the suggested "workaround" and use "regedit" to delete the two registry subkeys in question?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\25

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\26

Since I can't access the internet any longer via the "disabled" Compaq notebook that actually needs it, a fresh download of "SP1a" directly to it is seemingly not posssible. Or is it?

I guess I'll have to order the "SP1a" CD and wait the suggested 2-4 weeks? It's only $10., but wow, that's a real long time, no?

Any suggestions anyone? Is there an alternative perhaps?

Or should I perhaps just do a quick regedit and take my chances?

Thanks again all!

[Confused]

SP1 download give option to save to disk. That's what I did and then burnt it to CD. Do you have anyone with a high speed connection and a burner?
Chas

[docw]

Concerning the question, "do you have anyone with a high speed connection and a burner," the answer is, sadly, nah, not really! Yet I'll try to locate someone who perhaps still has the XP "SP1" on disk (perhaps from the Action Pac) and just try it I guess. There's no real downside, and it's probably better than tampering with the registry I suppose.

I do wonder though if I should be convinced that this is the "problem?" Conceivably, the "SP1" was pre-installed in the OEM Home version, I suppose, and the upgrade was possibly like "an XP restore?"

I guess very few folks actually do the upgrade to Pro from XP and this is not a widespread problem!

Thanks again all.

[Confused]

The upgrade probably wiped out the SP1. I have Pro and did a repair because of a freezing problem I was having and afterwards had to reinstall SP1 and something like 20 security upgrades that had been previously been loaded. You can go to Control Panel, right click and open System. Under General Tab it will show if SP1 is installed.
Chas

[young&dumb]

I did the suggested workaround... worked fine for me but then again depends on how comfy you are working with the registry.

[docw]

Thanks everyone!

Updating, I decided to just go ahead and use the suggested workaround and edit the registry. It only took a minute or two!


And FWIW, so far so good, thankfully.


And I simply did the XP "SP1" download via a dialup to the net. Slow, but it seemingly worked jsut fine.

Thanks very much, once again all!

[waldosrevenge]

Windows Update has just posted a notation about such an error...yet another critical update is required to fix such an occurence.

The basics of what I read is to re-install XP SP1...

[docw]

Yes! Surprisingly, at least to me, this has apparently not been a very widespead issue! Very few seemingly choose to upgrade from XP Home to XP Pro! Yet I'm thrilled to have it resolved nonetheless! Thanks again all.