I just upgraded my work PC from XP to Vista. I had an MS VPN connection set
up to connect to my home network which worked fine under XP. Now in Vista,
the connection still works but Vista wants to use that route as the default
which means I am unable to access any of my internal work resources
(Intranet, Exchange, etc.). I have already tried disabling the AutoTuning
feature in Vista. Anyone else have this problem and know how I can go back to
the way XP use to handle the VPN connection??
>I just upgraded my work PC from XP to Vista. I had an MS VPN connection set
> up to connect to my home network which worked fine under XP. Now in Vista,
[quoted text clipped - 5 lines]
> to
> the way XP use to handle the VPN connection??
You need to go into the properties of your VPN connection on the Vista
client machine and uncheck the "Use default gateway on remote network"
checkbox. Its similar to what you did in XP...
http://www.microsoft.com/technet/community/columns/cableguy/cg1003.mspx

Signature
Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
Sooner Al [MVP] - 29 Jan 2007 19:30 GMT
>>I just upgraded my work PC from XP to Vista. I had an MS VPN connection
>>set
[quoted text clipped - 13 lines]
>
> http://www.microsoft.com/technet/community/columns/cableguy/cg1003.mspx
Specifically in properties click on the Networking tab, select "Internet
Protocol 4" then Properties, then Advanced. In the IP Setting window uncheck
the "Use default gateway on remote network" checkbox. Note this can be a
security risk to your office network. See the Cable Guy article I pointed
you to earlier for a discussion of that.

Signature
Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
dr3w2k - 29 Jan 2007 19:47 GMT
I have already done that. Still doesn't work.
> >>I just upgraded my work PC from XP to Vista. I had an MS VPN connection
> >>set
[quoted text clipped - 19 lines]
> security risk to your office network. See the Cable Guy article I pointed
> you to earlier for a discussion of that.
dr3w2k - 29 Jan 2007 22:14 GMT
I was able to fix the problem. I had set a static DNS server in the VPN setup
and that was causing the problem. I removed that DNS server and am now able
to access both remote and local networks.
> I have already done that. Still doesn't work.
>
[quoted text clipped - 21 lines]
> > security risk to your office network. See the Cable Guy article I pointed
> > you to earlier for a discussion of that.
Sooner Al [MVP] - 29 Jan 2007 22:22 GMT
>I was able to fix the problem. I had set a static DNS server in the VPN
>setup
> and that was causing the problem. I removed that DNS server and am now
> able
> to access both remote and local networks.
Thanks for the feedback. I am sure that will help someone in the future...

Signature
Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
dr3w2k - 29 Jan 2007 22:36 GMT
Spoke a bit too soon. Everything seems to work except the local network
shares. When connected, if I try to access a local share, I get:
"M:\ is not accesible. The specified account does not exist."
Any thoughts?
> >I was able to fix the problem. I had set a static DNS server in the VPN
> >setup
[quoted text clipped - 3 lines]
>
> Thanks for the feedback. I am sure that will help someone in the future...
DACTech - 30 Jan 2007 21:35 GMT
Map to it as an IP address rather than the name. I have a similar issue where
I map to a non domain share(ie workgroup) and when I reboot or log off and
back on it can't connect anymore. Doing this by IP solves it!
> Spoke a bit too soon. Everything seems to work except the local network
> shares. When connected, if I try to access a local share, I get:
[quoted text clipped - 10 lines]
> >
> > Thanks for the feedback. I am sure that will help someone in the future...