How to I configure my connections so that I can have a VPC machine in Domain A authenticate via Kerberos to resources in Domain A when the host machine belongs to Domain B using a VPN that is in Domain B. I have a Windows Server 2008 (32bit not R2)VPC (Microsoft Virtual PC 207) machine running on a Windows Vista 64bit machine. The VPC belongs to a domain that is used for development. The Vista host machine belongs to my general corporate domain. When I'm in my office and connected to the network I have no issues using kerberos within the VPC to authenticate to my development resources. When I'm at home or out of the office and I use the VPN (microsoft VPN client), I connect to the corporate general network, and I'm able to access all resources from both the hose and VPC, but authentication isn't working properly. Some key points here is that the VPC cannot get a Kerberos ticket, and MSSQL will not allow windows authentication. MSSQL returns an error message that states that the machine is not part of a trusted domain.This is a development domain that is not part of a forest level trust.Again, through the office, everything is fine on VPC and host. When using the VPN, VPC domain isn't properly recognized, though access to resources can be obtained, authentication isn't working properly.Any help here would be appreciated.

Hi, When you said When I'm at home or out of the office and I use the VPN (microsoft VPN client), I connect to the corporate general network, and I'm able to access all resources from both the hose and VPC, did you mean the Virtual Machine can access the resource in domain A? Are the two domains located in the same network? It looks to me like the Virtual Machine cannot connect to the DC in Domain A for Kerberos authentication when the host machine connects to the corporate network through the VPN connection. Please run the command nltest /dsgetdc: /force on the Virtual Machine to check if it can locate a DC in Domain A. If it fails, I suggest that you post this issue in the VPC discussion group first to confirm if the host machine can share the VPN connection with the Virtual Machine and to verify that the network settings is correct. Discussions in Virtual PC http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.virtualpc&cat=en_US_4596fe15-89c0-4fa3-9c96-22b2f0d124ca&lang=en&cr=US Alternatively, you may establish a VPN connect on the Virtual Machine as well to check if the issue goes away. Thanks.

I will try this while on VPN. Just to be certain, I ran it while at the office (where everything works) and it located the proper DC.As for the networks. While in the office and hardwired I see that the two networks are using different class C addresses.I will confirm the differences while using the VPN this evening.P.S: I've found a workaround that seems to work, but doesn't seem like it should be the final solution. I've created a shortcut using the runas command to force the credentials. When I do this the Kerberos authentication works within that browser instance.C:\Windows\System32\runas.exe /netonly /user:<DOMAIN\USERNAME> "C:\Program Files\Internet Explorer\iexplore.exe"Thanks for the assist.