I did a test myself last night from Vista. It dials in with no problem, outlook opens fine, and I can go to \\servername\sharename and no problem. One thought, I have the firewall client for vista installed and laptop is a domain member which is going back and forward work/home -----Original Message----- From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Thor (Hammer of God) Sent: Thursday, January 25, 2007 7:08 AM To: isapros@xxxxxxxxxxxxx Subject: [isapros] Re: OT: Vista VPN Client Credentials Anyone? Bueller? Anyone? Is there anyone out there who is VPN'ing into a network on a non-domain machine with Vista? Is it time to post to the Focus-MS list??? t On 1/24/07 12:36 PM, "Thor (Hammer of God)" <thor@xxxxxxxxxxxxxxx> spoketh to all: > Greetings... I'm hoping this something stupid that I'm just not seeing, but > I'm having an issue automatically authenticating to a remote network under > my VPN credential in Vista (x64). > > With XP, on a non-domain, standalone workgroup box, I can create a standard > VPN client and log on to the remote network using my user account on remote > network domain. Though I'm logged on interactively as a local user on that > XP box, when I go to \\host.domain.com, my VPN credentials are automatically > used to access shared resources on the remote network. Same thing with > connecting to a remote SQL box (requiring integrated auth). No problems at > all with XP, been doing it for years. > > However, with Vista, the credentials I use to log onto the remote network > are NOT being used when I access resources on the remote network. Browsing > to the share point results in a logon box being displayed. If I attempt to > connect to a SQL box, it says "not a trusted connection" (as it would if my > local user is being used.) WTF? I've looked through and set everything > that I can, including setting the location as "Work" and "Home." I do NOT > want to have to join the box to the remote domain. > > Anyone know what I'm doing wrong?? Thanks. > t > > > > >