Solved

Exchange only allow domained computers to connect remotely

Posted on 2012-03-17
1
378 Views
Last Modified: 2012-03-26
I have a 2008SBS server.  When I first configured Exchange, I went to godaddy not really knowing what I was doing and purchased 5 SSL certificates.  I then went to expert-exchange and asked how to install the certificated onto my server.  I was given a website which I followed the instructions as best as I could however I was still confused as to what I was doing.  This could be the problem, but I don't know if it is also a setting in the server for my problem.

Fast forward into the future.  I have attempted to connect five computers to my exchange server.  Two of them were part of my Domain and the other three were not.
All five computers range from XP to Windows 7
Connecting via outlook 2007 or 2010.
All five computers access my exchange server remotely.

The two computers connected to my domain connect without any problems.  The three that are not part of my domain will not connect unless VPN is connected.

Bringing up VPN... I remembered another behavior.  I have created a user for myself and added my computer to the domain.  Part of the installation I added allowed myself to access my VPN remotely.  However, recently I tried adding another VPN account and even if I give this VPN account admin rights... the new account gets rejected and the VPN fails.  My account is the only VPN account which works on a non-domained computer and domained computer. The VPN is hardly ever in use... meaning only one computer is using the VPN.  There are not multiple users access the VPN at this time.

What are your recommendations on resolving this problem?
0
Comment
Question by:timarnold000
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 27

Accepted Solution

by:
davorin earned 500 total points
ID: 37735139
The non domain computer should trust the certificate used for outlook anywhere and when you configure outlook on non-domain computer do NOT check name at the start. You need to configure exchange proxy settings before that (on more settings->connection->...)
This link is for outlook/exchange 2010, but for 2007 version is basically the same.
http://www.petenetlive.com/KB/Article/0000519.htm
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Domain on O365 6 56
exchange, owa 4 49
Exchange server take over 4 57
Exchange 2013 fills up C drive with logs 4 29
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
This video discusses moving either the default database or any database to a new volume.

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question