Problems connecting a non-domain joined outlook to exchange

Hello,
i'm having issues configuring outlook (be it 2007, 2010 or 2013 all fail the same) on non-domain joined computers in the LAN to a exchange 2013 server.
I select manual config, in server we put "mail.domain.local" and user "domain\user" and it bounces with "cannot complete action, the connection to exchange is not available, outlook must be online".
We tried with external full email address, nothing
tried setting the outlook anywhere proxy, same, tried using ip address, same
it simply refuses to configure.
any ideaS?

Hi,
Generally, the external non-domain joined computers can connect to Exchange 2013 by using Outlook Anywhere and the Autodiscover service to auto-setup the Exchange account.
If the auto-setup for Exchange account fails, please check the Autodiscover service and Outlook Anywhere configuration by the following command:
Get-OutlookAnywhere | FL
Directly access the following URL in IE respectively, and check whether an Error 600 returns:
Https://autodiscover.domain.com/autodiscover/autodiscover.xml
Https://mail.domain.com/autodiscover/autodiscover.xml
Please make sure the the ExternalHostName parameter for Outlook Anywhere is configured to your external namespace for Exchange 2013 (for example: mail.domain.com).
In Exchange certificate, please make sure the namespace mail.domain.com is included in your trusted certificate which is assigned with IIS service.
For manual Exchange account setup, please run the following command to get the mailbox GUID for server name configuration:
Get-Mailbox UserA | FL Identity,ExchangeGuid
Then go to Control Pane > Mail to configure the Outlook profile. In Server Settings, import the [email protected] into the Server box and click Check Name to have a try.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

Non-Domain joined clients connect to server initially but cannot connect via Launchpad

Running SBS 2011 Essentials in a small office. Running XP/Vista/7 clients. All working fine until we swapped routers. Old router died, new router was installed.
Now all domain-joined PC's connect as normal, but all NON-Domain-Joined PC's cannot access the server via the launchpad. I get the "The server appears to be offline. Do you want to sign in to offline mode?" box.
Tried removing PC from the SBS Dashboard, uninstalling the connector from the client, restarting client, and reinstalling the connector. I can install the connector (using
http://<server ip>/connect , but not http://<servername>/connect
). Connector installs but it still tells me the server is offline when trying to use dashboard or launchpad on the client.
Note: I can add a network location or Map a network drive to ther server after inputting my network password from Windows.
Any Services to check? Firewalls exceptions to ensure? Advice?
EDIT: Dashboard on Server shows Client, sometimes as online, sometimes as offline.

Sounds like name resolution issue to me.
Are all your clients set to use the IP of the Essentials Server for their primary DNS?
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Windows 2012 R2 ADRMS domain controller version and Non-domain-joined Mac Client with outlook 2011

Hi,
What is the AD version for Windows 2012R2 ADRMS? Is it possible to have Windows 2003 R2 DC with Windows 2012R2 ADRMS?
Any installation guide Non-domain-joined Mac Client with outlook 2011?
What is the SQL version for Windows 2012R2 ADRMS?
Please advise. Thanks.
Kelvin Teang

Hi Kelvin -
There is no RMS Client for Macs. That functionality is actually provided through the Office for Mac application (this is different compared to the PC). Domain-joined clients will autodiscover the RMS server and should be able to create and consume
protected content. Non-domain-joined clients cannot automatically discover their RMS server. In this scenario, prepare a protected document or email from a domain-joined machine and send it to your non-domain-joined users. They will open
the document or email up and the URLs contained in the publishing license of the document will direct them to the correct RMS server.
I hope that helps!
Micah LaNasa
Synergy Advisors
synergyadvisors.biz

Non domain-joined Clients (CES/CEP)

Hello Everyone!
This is my first post to the security forum and it is not an overly familiar tech for me so please be gentle. :)
I am looking at building a lab to test a web based application for a client. The client has very stringent security requirements and as such have mandated the need for both the web server to be secured using SSL certs and requires the connecting
users to have a certificate. The infrastructure will be hosted in a central DC in it's own AD forest whilst the users connecting in will have their own AD as they work for different companies. Each user will have an AD account within the hosted
environment. My initial thought was to provide public certs for the web servers but my problem was providing certificates to the clients. Clearly using public certs would be very expensive. After a bit of research I stumbled across the following:
http://blogs.technet.com/b/askds/archive/2010/05/25/enabling-cep-and-ces-for-enrolling-non-domain-joined-computers-for-certificates.aspx
What I am trying to understand is, will the combination of Certificate services & CES/CEP effectively do away with the need for public certs in this instance? Can I simply use the internal authority to publish certificates to the web server and
to the end users?

Yes - I think this is one of the scenarios CES/CEP have been developed for.
End users would have to trust your internal CA and validate the chain, so intermediate CAs should be found via AIA URLs. But since you need user - not computer - certificates this is simpler than described in the article as users do not need to be local
admins to import a root. (But on principle the admin of a user's home AD could restrict this though I have never encountered that.)
You would need to publish the CES/CEP services via a reverse proxy and external users would have to configure the enrollment HTTP URLs and enter their AD credentials in the hosted AD when connecting.
As users have imported your CA certificate they will also trust the web server's certificate issued from the same CA.
Elke

DNS working intermittently for non-domain joined machines

I have a small single Server 2012 based network, with about 90% windows clients. DNS is running on the Windows Server 2008 machine, but DHCP is provided via a unix based firewall machine. Within the DNS configuration I have all of my windows
clients (mostly Windows 8.x clients, but there are a few Windows 7 ones as well) and a few *nix ones as well. All of the Windows clients are domain joined, except for one machine which is currently running Windows 10 preview, though it was a Windows
7 machine originally. In the DNS configuration I have a number of statically entered A records, used to give my *nix machines a name on the local network.
When trying to access systems by name (via ping or by other services), there is a very consistent behavior - my domain joined machines are able to resolve all names 100% of the time without any issues. However, the non-domain joined machines, both
Windows and not, are consistently inconsistent. To be more precise, when I try to resolve a name it will randomly work and randomly not. IP setup and configuration looks correct, meaning they have valid IP, DNS is set to my Windows Server,
default gateway, etc. are all correct. Pinging external machines (ie google.com, etc.) works 100% of the time, but trying to ping any internal machine is a total crap shoot. The only exception to this is the Windows Server 2012 machine itself,
which always works.
From past experience I know that the moment I join a machine to the domain all of the DNS issues goes away, which is fine for the Windows boxes but not so much for the rest. I also have visitors occasionally come by, who I cannot expect to join my
domain just to make things work normally.
This network originally started life out as Windows Server 2003 domain, but was upgraded to 2012 about two months ago. I have been seeing this problem for years, but have always assumed it to be a Server 2003 issue and figured it would go away when
I upgraded. Nope...
Any ideas as to the cause of this and what I can do about it?
Thanks,
peter

Its really weird - I can ping an address and not have it work, then do a NSLookup of the same address against my DNS server and it resolves just fine. Take a look at this screen copy below:
C:\Users\Peter>ping apollo.bakonet.local
Ping request could not find host apollo.bakonet.local. Please check the name and try again.
C:\Users\Peter>nslookup apollo.bakonet.local 192.168.124.9
Server: orac.bakonet.local
Address: 192.168.124.9
Name:    apollo.bakonet.local
Address: 192.168.124.27
C:\Users\Peter>ping apollo.bakonet.local
Ping request could not find host apollo.bakonet.local. Please check the name and try again.
C:\Users\Peter>ipconfig /all |more
Windows IP Configuration
   Host Name . . . . . . . . . . . . : Win10
   Primary Dns Suffix . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : bakonet.local
Ethernet adapter Ethernet:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-21-CC-65-1B-8F
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 3:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : A0-88-B4-A2-41-81
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
   Connection-specific DNS Suffix . : bakonet.local
   Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6205
   Physical Address. . . . . . . . . : A0-88-B4-A2-41-80
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::fc47:8a91:6b25:bd0e%2(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.124.64(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, January 5, 2015 7:34:47 PM
   Lease Expires . . . . . . . . . . : Tuesday, February 3, 2015 7:15:20 PM
   Default Gateway . . . . . . . . . : 192.168.124.1
   DHCP Server . . . . . . . . . . . : 192.168.124.1
   DHCPv6 IAID . . . . . . . . . . . : 60852404
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-C6-18-82-00-21-CC-65-1B-8F
   DNS Servers . . . . . . . . . . . : 192.168.124.9
                                       24.229.54.212
                                       216.144.187.199
   Primary WINS Server . . . . . . . : 192.168.124.9
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : EC-55-F9-F5-14-76
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Does this actually make sense? Obviously the DNS server is online, it works and when a lookup is requested directly it works, and the DNS server is listed as first in the IP configuration. So why would it not work?!

Create a certificate for non domain-joined PCs

We have a standard AD domain wit a CA and SharePoint/Exchange servers, hosted internally and externally with TMG 2010 as our firewall. For the external hosting, we have an external certificate from one of the main certificate providers. Internally, our domain-joined
PCs look to the CA to get their trusted certificate from.
This is the issue I am encountering:
Our external users (the ones whose PC is not joined to our domain) are fine when they access our SharePoint and Exchange services externally.
However, when they are connected via VPN, they receive a certificate error and when I look in Certificate > Certification path, I can see that it says:
"DOMAIN NAME" Issuing CA1 > "NAME OF SHAREPOINT WEBSITE".
When such a PC connects to the same website when NOT connected via VPN to the domain, they receive:
"DOMAIN NAME" Root CA > "DOMAIN NAME" Issuing CA1 > "NAME OF SHAREPOINT WEBSITE".
How can I create a certificate for these non-domain joined PCs so that I can import the certificate in the Trusted Root Certification Authorities store? Thank you!

It sounds like the question you are really asking is :
How do I designate the internal root CA as a trusted root CA
Run certutil -addstore root RootCert.crt (this must be run from an administrative command prompt)
This designates the root CA as a trusted root on the client. You also may want to install the intermediate cert to the store (you are not clear on what VPN product you are using, so it may or may not do proper chain building).
Run Certutil -addstore CA IssuingCA.crt
Brian

Change default key size on non Domain joined CA.

Hello,
I have one standalone non domain joined CA I would like to change the default key size of all issued certs to 2048. Since it is a stand along, there are no AD template to modify. Can this be changed in the registry?
Shawn

CAPolicy.inf is the way to go.
See the following thread
http://social.technet.microsoft.com/Forums/windowsserver/en-US/ce001d8f-c722-4429-83cb-328b92876292/how-to-change-root-certificate-keys-length-and-validity-period?forum=winserversecurity
Hth, Anders Janson Enfo Zipper

Licensing for non domain joined machines

Good Day
would additional licensing be required to manage non domain joined machines or would this be covered by the current EA. can someone explain how licensing for the management of non domain machines would work?
thanks
daniel

Hi,
There is no difference if you don't want to license them differently and if that is possibly in you agreement, so you should contact you MS License reseller.
You could buy a System Center Configuration Manager CAL if you want to manage it, that will only cover ConfigMgr and not Endpoint protection for instance. So you should really contact your reseller and see what is the most optimal solution for you company/organisation.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Install AADSync on a Workgroup server (non-domain joined)

Does anyone has experiences with installing AADSync on a non-domain joined server (workgroup). A company with multiple forests wants to have a "neutral" server for the identity synchronisation. It looks like the tool is installing fine, but can
there be some configuration issues?

This is supported. See here:
"Your computer can be stand-alone, a member server or a domain controller. "
ref: http://msdn.microsoft.com/en-us/library/azure/dn757602.aspx
Mike Crowley | MVP
My Blog --
Planet Technologies

Domained laptop - slow logon when connected to non-domain network

Hi,
I'm looking for ideas on how to solve or workaround this issue, so any help would be appreciated. Please note that this doesn't appear to be the usual type of "slow login" problem - in fact I'm pretty certain the issue is caused by public DNS
servers which return placeholder IP addresses for unknown domains, rather than correctly reporting them as being unknown, which is making XP "hang up" looking for servers which don't really exist. Either way, it's causing a lot of problems for our remote
users.
The scenario is this. When domain-member laptops are not on the domain network, they can take anywhere between 5-30 minutes to login. This issue only occurs when the network they're connected to presents DNS servers which resolve unknown DNS
hosts/domains to "placeholder" sites. Whilst Windows 7 laptops do also seem to suffer from this, login delays on those are at worst a couple of minutes, whereas the Windows XP machines are affected for much longer.
Maybe a bit more info will make it clearer :)
The AD namespace shares the external domain, and there are public DNS records for the external domain, but obviously not for internal hosts (like DCs). So internally, the FQDNs of the domain controllers are "DC1.company.com", "DC2.company.com" etc.
When the laptop is connected to users home network, users can logon quickly (<30 seconds), as long as the DNS server offered by DHCP on that network doesn't return an IP for hosts/domains which don't exist publicly. If they do, login takes 5-30 minutes.
I've confirmed this by doing a lookup of the domain on the affected networks to ascertain which DNS servers return placeholder IPs rather than reporting that name resolution isn't possible. For example, OpenDNS's servers (208.67.222.222, 208.67.220.220)
return placeholders, Google's (8.8.8.8, 8.8.4.4) don't. Using OpenDNS to lookup "dc1.company.com" returns their placeholder IP of 67.215.65.132, using Google's returns "can't find dc1.company.com: Non-existent domain". OpenDNS is being used
as an example, increasingly ISP's seem to be using redirection, we're getting this issue with BT and Virgin Media networks, plus a couple of others.
So, if I manually set DNS on a laptop to use Google's servers, then connect it to one of the affected networks, login is virtually instantaneous. I remove the manually configured DNS servers and allow DHCP to present the ISP's own servers, login is
seriously delayed.
From this I can only assume that the fact that the names are resolving at all is causing the delay. I've removed possibly contributory factors from the equation, such as roaming profiles, redirected folders, mapped drives, group policy etc which the
workstation might be trying to access and causing a delay, as well as checking that fast logon optimization is active.
At the moment we're having to tell users to not connect to the network until after they've logged in, which you'd think wouldn't be that big a deal but you know what users are like :)
I appreciate this issue really seems due to bad practice by ISPs rather than with Windows itself, but we really need a fix we can apply ourselves. Reconfiguring users' home networks really isn't an option, there's too many of them, plus that wouldn't
solve the problem when they're using other networks (hotels etc). I don't think setting "good" DNS servers manually is an option, certainly I can't think of a way that would still work when they're connected to our internal LAN.
I'm thinking there must be some way we can set a timeout or something on the workstations so they don't spend so long trying to communicate with what they think are domain servers, but dispite much searching, I've been unable to find anything that works.
So, any help would be gratefully recieved.
Thanks

Thanks for the reply Martin, unfortunately it didn't help matters, but after pondering for a while (and eventually kicking myself for missing something so obvious) I did come up with a solution.
Basically, just set up public DNS A records for the internal servers and point them to 127.0.0.1 (setting up a wildcard DNS entry for the domain also pointing to 127.0.0.1 would do the same thing).
Sure enough logon now takes about 5 seconds, even on the Windows 7 machines (which were only taking a minute or so anyway).
Loopback is the best place to point these to, Pointing them to a public server didn't work, and pointing them at a non routeable private IP didn't work either.
To help anyone else confirming this is also the cause of their slow logon issue - when all three conditions are met it's time to mess with your public DNS!
The FQDN of the domain is public (company.co.uk) and not local (company.local).
The DNS servers in use on the network (or the ISP's DNS servers to which DNS requests are forwarded) return placeholder IPs for unknown host addresses, rather than a "non-existent domain or host" error. This can be confirmed by pinging (or doing an
nslookup) on the affected machine, for a host for which no public DNS record exists (ie ping wibble.microsoft.com) - if an IP address is returned then the DNS servers in use are resolving unknown hosts/domains to a placeholder IP.
If you allow the machine to login on the external network, then run a
ipconfig /displaydns you'll see entries for attempts to resolve internal servers themselves, plus lookups relating to the AD domain such as
_msdcs.gc._tcp._ldap.internaldomain.co.uk and such - these shouldn't be there off-domain, and I believe they indicate the machine thinks it's on the domain, even though it isn't.
Hope this helps someone else out.
Ray Von

Problem connecting with non-repository owner

I'm using OWB 10gr2 with Oracle DB 10gr2
I've created a repository and can connect with the designer using that repository owner.
Within designer, I enabled another DB user for access (he got the OWB-role "everyone"). He is shown in the gloabl explorer -> security -> users.
But when I try to connect with the designer using the non-repository owner, I get some german error message saying something like "No repository available for this user".
The db user has the database roles OWB_xxx. He can connect to the database and access (read/write) the repository schema.
OMB+> OMBCONNECT o_owbrep/o_owbrep@afxdq008:1521:sdbx USE REPOSITORY 'o_owbrep'
Verbunden.
OMB+> OMBCONNECT f344204/meta@afxdq008:1521:sdbx USE REPOSITORY 'o_owbrep'
OMB01118: Herstellen einer Verbindung zum Repository nicht möglich. (Establishing a connection to the repository is not possible)
PRS-00511: Sie können zum Repository o_owbrep keine Verbindung herstellen, weil es nicht vorhanden ist oder Sie kein registrierter Benutzer sind.
(You cannot connect to the repository o_owbrep because it does not exist or you are not a registered user)
Message was edited by:
user518882
Added results using ombplus.

There are 2 different errors, the latter is a syntax problem. If you own the repository you can connect without the USE REPOSITORY clause.
OMB+> OMBCONN sales/sales@localhost:1521:orcl102
OMB01118: Could not connect to repository! PRS-00510: You need to specify which
repository to work on to establish the database connection.
Simply use:
OMB+> OMBCONN sales/sales@localhost:1521:orcl102 USE REPOSITORY 'OWB'
Connected.
The initial post is something else... the user I connect with in the above statement is also a target user. Should not matter. It is also in Windows XP. Does it work if you use "target user"?
JP

Can Password Reset Work for Non Domain MS Outlook (2007, 2010 and 2013) Clients? NOT OWA, Please

Hi All,
I migrated from Exchange 2007 to Exchange 2013. I have configured expired password reset and it works fine on OWA (for both internally and externally accessed users) and all computers joined to my domain running MS Outlook clients. However, my users wants
it to work for all MS Outlook client of computers not joined to my domain.
How can I go about this? Does expired password reset work on MS Outlook client (2007, 2010 and 2013) computers not joined to the domain?
Please, help

Hello,
Based on my known, I'm afraid that there is no way to reset expired password if your Outlook client computers not joined to the domain.
For external users, we only reset password via owa.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Problem connecting to non-apple routers with WEP key

Hi there, have tried to connect to two wireless routers recently which have WEP keys. One gives me "Connection timed out" after about 5 seconds and the other says "incompatible security". The passcode is too long to enter if I choose any of the WEP 40/128-bit options (it's 32 characters long!)
Any help appreciated.
Thanks,
Jon

Hi.
I can't connect to WEP networks either with Leopard 10.5.1.
It just says "incompatible Security". I've tried it for one hour without any luck.
Why doesn't Apple realize that there are millions of WEP encrypted networks out there and that it is essential to be able to connect to them. (it worked with Tiger, didn't it?)
Is there a knowledge base article out there what to do about it?
I just can't walk to hotel managers and ask them to switch to WPA, especially if they don't have a clue how to do that and older windows computers won't be able to connect any more.
Why a transparent menu bar but no way to connect to WEP networks?
I'm very disappointed. Apple, fix this! (now!)
Is there actually a way to get your money back for Leopard if this basic things don't work anymore?
Thank you for any help.

NDES & Non Domain Joined Devices

Hi Guys
So I've been working on a problem to get a client mobile devices (Laptops, iOS, Andriod et al) to authenticate to their wireless Network using Certificates.
The solution is 90% complete but I've come across a problem with NDES and how I can get iOS, Android and windows mobile devices getting root certificates and the device/user certificates essentially "Over the Air".
I've researched a few MDM solutions but that only works if the device is company owned. The reason being is that if the mobile devices aren't company owned we can't install the required MDM apps on them which will enable us to control them and therefore
install Root Certificates and the like.
I'm curious to know who else out there has configured something like this before.
The systems I'm working with are: a Cisco WLC, NPS, AD, AD CA, NDES (Win2012).
Any help will be greatly appreciated.
Prince K.
vtechnology.com.au

Hi,
how I can get iOS, Android and windows mobile devices getting root certificates and the device/user certificates essentially "Over the Air".
I haven’t done it myself, though here are some resources I searched for you:
Installing the root CA on iOS
http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_installing_root_CA_iOS.html?lang=en
Installing the root CA on Android
http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_installing_root_CA_android.html?lang=en
Installing the root CA on Windows Phone
http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_installing_root_CA_windows_phone.html?lang=en
Please Note: Since these web sites are not hosted by Microsoft, these links may change without notice. Microsoft does not guarantee the accuracy of this information.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Having problems connecting iPhone 5 with our company's Exchange 2003. Is this a known issue and is there a fix?

I'm not the only one in our company experiencing this, so far i haven't heard of anyone with an iPhone 5 who is able to connect. I'm wondering if people in other companies that have Exchange 2003 also have the same issue or is this isolated to ours.
The errors i get are not being able to verify: "Unable to verify account information." This used to happen before but when i chose to save settings, it would usually work after a while. But this time, with the iPhone 5, i kept getting "Cannot Get Mail" "The connection to the server failed".
I did this with a restore from back up, and a wiped phone, same results. My colleague with a fresh out of the box phone with no previous IOS backups, also has the same errors.
So, anyone else still using Exchange 2003 and experiencing the issues?

Hi Guys,
I got exchange mail working. It seems issue is around "Push". I enabled "push", account verified & all worked well. After that I disabled push (I do not want it & to save mobile data use).
By googling, I found many have got it up & apple may fix it in it next iOS udpate.
Regards,
Mathew

Problems connecting a non-domain joined outlook to exchange

Similar Messages

Maybe you are looking for