Vista VPN issues

It seems like lots of people are having issues with Networking in Vista.
I've seen lots of posts on them, but no sign of any fixes on the horizon. I
personally only have issues with the VPN support in Vista. I'm experiencing
the following:

1) Intermitantly, when I go to the "Connect To" window from the start menu,
it says the VPN connections require an internet connection, despite the fact
that I have access to the Internet. This can be worked around by going to
the "Manage Network Connections" window where I can connect.

2) While connected to a clients VPN from my work network, I will eventually
not have access to my own network resources. When connecting to resources in
my internal network, it will try the ID I used in the VPN instead of the
domain id I'm signed onto the machine with. Eventually my network id gets
locked out. The two ids are of the format LocalDomain\jbailey and
VPNDomain\jbailey, but this shouldn't have anything to do with it. This
NEVER occured with Windows XP, so I'm certain that this is related to Vista.

The first issue is annoying, but can be easily worked around, but the second
issue is a true pain. I end up having to go into my server and unlock my
account (fortunately I can do this as I'm also the administrator). If anyone
has a workaround for the second issue I would really appreciate it.

Thanks in advance for any assistance you can offer.

John, can you try giving the FQDN [complete name with dns suffix] name to access the resources?

I dont understand how the a/c gets locked and what you unlock on the server (I assume this to be RAS Server) - please explain.
>> "Eventually my network id gets locked out."
>> I end up having to go into my server and unlock my account (fortunately I can do this as I'm also the administrator).

Thanks,
Dinesh.
[This posting is provided "AS IS" with no warranties, and confers no rights.]

"John Bailey" <JohnBailey@discussions.microsoft.com> wrote in message news:17AA360D-FF11-41D9-95F4-8118720E7623@microsoft.com...
> It seems like lots of people are having issues with Networking in Vista.
> I've seen lots of posts on them, but no sign of any fixes on the horizon. I
> personally only have issues with the VPN support in Vista. I'm experiencing
> the following:
>
> 1) Intermitantly, when I go to the "Connect To" window from the start menu,
> it says the VPN connections require an internet connection, despite the fact
> that I have access to the Internet. This can be worked around by going to
> the "Manage Network Connections" window where I can connect.
>
> 2) While connected to a clients VPN from my work network, I will eventually
> not have access to my own network resources. When connecting to resources in
> my internal network, it will try the ID I used in the VPN instead of the
> domain id I'm signed onto the machine with. Eventually my network id gets
> locked out. The two ids are of the format LocalDomain\jbailey and
> VPNDomain\jbailey, but this shouldn't have anything to do with it. This
> NEVER occured with Windows XP, so I'm certain that this is related to Vista.
>
> The first issue is annoying, but can be easily worked around, but the second
> issue is a true pain. I end up having to go into my server and unlock my
> account (fortunately I can do this as I'm also the administrator). If anyone
> has a workaround for the second issue I would really appreciate it.
>
> Thanks in advance for any assistance you can offer.

What happens is that my domain account gets locked out. I am connecting to
the vpn for a client, but I am still connected to my internal domain.
Accessing the resource via the fqdn does not help. The access to the remote
domain is fine, its my internal access that gets screwed up.

I have two Vista machines and one that is still on Windows XP professional
and the issue occurs on both Vista machines. I never have any problems when
connected via the Windows XP machine. I am going to have to reload my Vista
machines with Windows XP Pro if I can't find a resolution to this issue as it
is just taking to much time.

"Dinesh Agarwal" wrote:

> John, can you try giving the FQDN [complete name with dns suffix] name to access the resources?
>
> I dont understand how the a/c gets locked and what you unlock on the server (I assume this to be RAS Server) - please explain.
> >> "Eventually my network id gets locked out."
> >> I end up having to go into my server and unlock my account (fortunately I can do this as I'm also the administrator).
>
> Thanks,
> Dinesh.
> [This posting is provided "AS IS" with no warranties, and confers no rights.]
>
> "John Bailey" <JohnBailey@discussions.microsoft.com> wrote in message news:17AA360D-FF11-41D9-95F4-8118720E7623@microsoft.com...
> > It seems like lots of people are having issues with Networking in Vista.
> > I've seen lots of posts on them, but no sign of any fixes on the horizon. I
> > personally only have issues with the VPN support in Vista. I'm experiencing
> > the following:
> >
> > 1) Intermitantly, when I go to the "Connect To" window from the start menu,
> > it says the VPN connections require an internet connection, despite the fact
> > that I have access to the Internet. This can be worked around by going to
> > the "Manage Network Connections" window where I can connect.
> >
> > 2) While connected to a clients VPN from my work network, I will eventually
> > not have access to my own network resources. When connecting to resources in
> > my internal network, it will try the ID I used in the VPN instead of the
> > domain id I'm signed onto the machine with. Eventually my network id gets
> > locked out. The two ids are of the format LocalDomain\jbailey and
> > VPNDomain\jbailey, but this shouldn't have anything to do with it. This
> > NEVER occured with Windows XP, so I'm certain that this is related to Vista.
> >
> > The first issue is annoying, but can be easily worked around, but the second
> > issue is a true pain. I end up having to go into my server and unlock my
> > account (fortunately I can do this as I'm also the administrator). If anyone
> > has a workaround for the second issue I would really appreciate it.
> >
> > Thanks in advance for any assistance you can offer

I have also had a problem similar to this. I solved this by setting the policy “Security Settings\Local Policies\Security Options\Network access: Do not allow storage of credentials or .NET Passports for network authentication” = Enabled.

Maybe it will work for you to…