Dear TechNetMy Company has the policy to give access to users to only one AD computer. Currently remote users use VPN to access their emails in Outlook. I have setup Outlook Anywhere for such users but it prompts for Username/Password continously and does not authenticate at all.Domain Admins Account having access to all the AD computer/Servers using Outlook 2003/2007, Outlook Anywhere works perfectly fine. No Authenticatin issue and my authentication is set to BASIC.I have given access to Exchange Server also to Company Users but no success. I do not know where to start looking for the issue.Please adviseThanksShivam

On Sun, 29-Nov-09 03:29:12 GMT, ProfDoc wrote:>Dear TechNetMy Company has the policy to give access to users to only one AD computer. Currently remote users use VPN to access their emails in Outlook. I have setup Outlook Anywhere for such users but it prompts for Username/Password continously and does not authenticate at all.Asking for credentials is understandable from non-domain joinedmachines. The repeated request for authentication usually points to acation mechanismas between the client and server.Does using OWA allow them to access their mailbox?>Domain Admins Account having access to all the AD computer/Servers using Outlook 2003/2007, Outlook Anywhere works perfectly fine. Ignoring the larger question about why a Domain Admin would haveaccess to any mailboxes at all, are they using a VPN connection orRPC-Over-HTTPS?Is there some authentication happening before the user is connected tothe Exchange server?>No Authenticatin issue and my authentication is set to BASIC.I assume that "my" refers to the settings in your Outlook profile forthe Exchange Proxy Settings? Or does it refer to the settings on somevirtual directory on the server?>I have given access to Exchange Server also to Company Users but no success. I do not know where to start looking for the issue.Please adviseThanksShivam On /what/ is your authentication mechanism set to basic, and how didyou set it to be that way?xchangeconnectivity.com and tried todiagnose the problem using that tool? If not, go do it now.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Hi Shivam, I would like to explain it is normal the Outlook is not able to logon through Outlook Anywhere if the user is restricted to logon only one AD computer. You need to remove the policy in order to allow the users to logon through Outlook Anywhere from other clients. ~~~~~~~~~~~~~~~~ Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com ~~~~~~~~~~~~~~~~

Hi Shivam,Any further question regarding the issue?Thanks,Mike

Dear Rich Q : Does using OWA allow them to access their mailbox A: Yes, using OWA allows them to access their mailbox Q : DOmain Admins using VPN or RPC over HTTPS ? A : RPC over HTTPS Q : Is there any authentication happening? A : Username/Password screen comes up but putting the details does not authenticate as the prompt reappears for those users who have access to only 1 AD Computer. Q : BASIC Authentication A : BASIC through out as set on Exchange Server itself. Server Organisation ---> Client Access Role and then in the Action Pane click properties ------> Outlook Anywhere TAB ----> Client Authentication Method is set to BASIC Q : TestExchangeConnectivity.com A : ALL Tests failed TestExchangeConnectivity.com results Testing RPC/HTTP connectivityRPC/HTTP test failedTest StepsAttempting to resolve the host name mail.caac.org.au in DNS.Host successfully resolvedAdditional DetailsIP(s) returned: 165.228.207.135 Testing TCP Port 443 on host mail.caac.org.au to ensure it is listening and open.The specified port is either blocked, not listening, or not producing the expected response. Tell me more about this issue and how to resolve itAdditional DetailsA network error occurred while communicating with remote hostException Details:Message: No connection could be made because the target machine actively refused it 165.228.207.135:443Type: System.Net.Sockets.SocketExceptionStack Trace:at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally() Thanks again for all the help Regards Shivam

Thanks Mike I can take your answer as the final word because I am not finding any solution to this problem except to carry on with VPN. The only thing that is surprising me that if this is a probelm and is known to Exchange Community then are they doing something to rectify it (Microsoft Team). Anyway if my BOSS does not agree to give access to all the AD computers to a user then I have to carry on with VPN connection. Thanks for all your help RegardsShivam

On Sun, 6-Dec-09 03:55:03 GMT, ProfDoc wrote: [ snip ]>Exception Details:Message: No connection could be made because the target machine actively refused it 165.228.207.135:443Type: System.Net.Sockets.SocketExceptionStack Trace:at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally() I tries to connect to the IP address using HTTPS and failed. UsingHTTP gives me the typical "This web site is under construction" webpage. Adding a /owa or /exchange virtual directory doesn't help.http://mail.caac.org.au/owa gets a 404. So doeshttp://mail.caac.org.au/exchange.Of course I don't know how your connectivity or URLs are set up, butit seems that only port 80 is open and not 443.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP