Okay, here is the situation.
I effectilvely have 3 offices involved.
Office A
Office 1
both different companies.
Office 1 has users sitting in Office A. We will call these people Office 1A.
Office A has it's own domain and shares it's infrastructure with another smaller organization called Office 1A. Office 1A's users' are using computers associated with Office A's domain; however, they use a VPN to retrieve drives and email from their parent company, Office 1. Office 1 and Office A are in different cities.
Office A and Office 1's domains are not trusted. Office A and Office 1 both use ISA server 2006. There is a site-to-site VPN between Office A and Office 1 so that user's within Office 1A do not have to fire off personal VPN tunnels. VBScripts on the users' desktops map the drives and send Office 1 domain credentials across the VPN.
So - here is where it gets confusing:
We purchased a server for Office 1A running Windows server 2008/Hyper-V. We've replicated the shared data and installed Exchange 2007 on that server. Those servers were built at Office 1 so that they could join the Office 1 domain, then we brought them to Office A. This server has hard coded IP addresses, but these addresses are still within the IP range at Office 1. The hope was to continue to allow these servers to traverse the same VPN for replication, but allow Office 1A users faster access to data files and email while onsite at Office 1.
Everything seemed to be working; however, there is a major glitch.
It appears that Office 1A users require NTLM authentication for Outlook Anywhere while at Office 1 and Basic Authentication while working remotely. Keep in mind that when Office 1A users are out of the office at Office 1A, they use personal VPN's back to Office A, as Office A's Exchange 2007 server is the one that has Outlook Anywhere enabled on it.
Does anyone have any idea why this would be the case?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I thought it supported these auth types:FBA, basic, digest, and Windows Integrated
And since you have ISA, FBA can be an issue.
have a look here and see if this helps:
http://www.isaserver.org/t
Business Accounts
Answer for Membership
by: debuggerauPosted on 2009-09-22 at 17:01:12ID: 25398847
Are you sure it is not kerberos authentication rather that NTLM, that is quite old, or are you running the domain in mixed mode?
Authentication methods vary according to the trustworthiness of the client, I'm wondering if you've enabled forms auth, disabled basic auth or run the microsoft best practices analyser as yet?
Basic Auth should be ok over an encrypted VPN, if setup right, but is there some usability issue with your config? because I'm lost to see the actual problem..