I've got a user who has upgraded to Windows XP SP2. After the upgrade all of his VPN connections located in the Network Connections windows disappeared. When trying to create a new connection he get through the welcome screen on the wizard and clicks Connect to the network at my workplace. The next screen, which specifies how to connect (Dial Up or VPN) has both the radio buttons greyed out.

Unfortunately he works remotely so I have no access to his system.

I don't see what is preventing the user from creating the connection. Perhaps something in the TCP/IP connection has gone awry? Re-install TCP\IP?

Any thoughts?

Thanks in advance.

Title Edited - Please follow new posting rules from now on.

--Zxian

Has SP2 closed a needed port? Does the Windows firewall block outbound traffic?

Sorry I can't be much help-I've been behind a hardware firewall for so long I can't recall the default behavior of the Windows Firewall...I just shut it off and forget about it...obviously.

I've disabled Windows Firewall and the buttons are still greyed out. Re-enabled the Firewall to no avail.

Check the following registry key:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan

Value: ObjectName

Type: REG_SZ

Data: LocalSystem

If ObjectName is not set to LocalSystem, change it. Reboot for changes to take effect.

Have you checked this one?

sp2 & VPN connects

Check the following registry key:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan

Value: ObjectName

Type: REG_SZ

Data: LocalSystem

If ObjectName is not set to LocalSystem, change it. Reboot for changes to take effect.

Cluberti,

Can you go into detail what this reg value specifies? LocalSystem is the value on my system, however, I'm hesitant to make any changes to the user's system without some clarification on what I'm changing and an idea of what the repercussions may be.

I've not been able to reach this user as of yet, so, I'm unaware if his value in the registry is set to LocalSystem or not.

Thanks for the info, your responses are appreciated!

Have you checked this one?

sp2 & VPN connects

Must4ng,

That article assumes you have a VPN connection created and that the connection is successful. My user is unable to create a VPN connection using the Create a New Connection Wizard. Other thoughts/suggestions?

Check the following registry key:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan

Value: ObjectName

Type: REG_SZ

Data: LocalSystem

If ObjectName is not set to LocalSystem, change it. Reboot for changes to take effect.

Cluberti,

Can you go into detail what this reg value specifies? LocalSystem is the value on my system, however, I'm hesitant to make any changes to the user's system without some clarification on what I'm changing and an idea of what the repercussions may be.

I've not been able to reach this user as of yet, so, I'm unaware if his value in the registry is set to LocalSystem or not.

Thanks for the info, your responses are appreciated!

This value that tells the service what user to start as.

Doesn't creating a VPN connection within XP also require the Telephony service be running? Or maybe it's that it requires the Remote Access Connection Manager service, which has a dependency on the Telephony service. Anyway, check that both of those services are running. I just double checked that on my workstation (we disable both of those services as part of our standard rollout). With them disabled the options were greyed out...but available with the services running.

Cluberti,

It was the Telephony service which was preventing the VPN connection. Once the user enabled that service (probably rebooted, too) the option became available. He will test the VPN connection this evening.

He did say that he had upgraded to XP SP2 about 4 months ago (never brought up that fact that he wasn't able to connect anymore or that his connections had vanished!), though, I'm thinking he may have had a XP Home edition loaded for whatever reason and decided to upgrade to XP Pro SP2 since Home edition does not support VPN connections.

Who knows.

Cluberti, thanks for the suggestions--enabling the Telephony service resolved the issue.