Cisco VPN Start Before Logon vs Logon to AD and then to Cisco VPN
We are using the latest (for Windows 7) version of Cisco VPN and we have been noticing a problem with accessing the Exchange 2007 Management Console. If I chose Start Before Logon for VPN and then access the Exchange 2007 Management Console, it launches without any problems. If I logon to AD first and then VPN and access the Exchange 2007 Management Console, I get the following error: get-ExchangeServer Error: Domain contoso.corp cannot be contacted or does not exist The specified does not exist or cannot be contacted. get-UMServer Error: Domain contoso.corp cannot be contacted or does not exist The specified does not exist or cannot be contacted. Our Windows 2008 R2 DCs are used for authentication and we also have Windows 2003 DCs in our forest. We use split tunneling for the VPN and this has been working until recently. I think this is either a DNS or AD issue. Has anyone else seen this?
June 25th, 2012 3:32pm

May I know the relationship between the domain you logon and the domain contoso.corp? What do you mean "chose Start before logon on for VPN"? In this scenario, what is your current ueser account? What is your TCP/IP statu before and after you logon VPN? Ivan-Liu TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2012 2:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics