Exchange Server 2013 with RADIUS authentication

Hello,
I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
I am using Windows Server 2012, I already installed Exchange Server 2013 on it and everything works as intended.
But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS server which is not on my Windows Server 2012. I have to use their RADIUS server, the RADIUS server from the
company where I am doing my internship.
I already created a NPS and added the RADIUS Client + Remote RADIUS Server Groups. I created a Connection Request Policies with the condition:
User Name *
I forwarded the Connection Request to the Remote RADIUS server that I created in Remote RADIUS Server Groups and then I registered the NPS in th AD. But it's still not working.
Maybe I did something wrong or I misunderstood something or does this even work with Exchange Server 2013? To authenticate mailbox users with a RADIUS server before they can login into their mailbox and use their mailbox?
Thanks in advance.

On Wed, 26 Mar 2014 09:21:25 +0000, DavidIntern wrote:
I already put the NPS as a RADIUS proxy. I followed this check list http://technet.microsoft.com/en-us/library/cc772591.aspx
But the things is I want to make it work with our freeRADIUS2 that we have in place here. Without changing our freeRADIUS2. But I found out this is not possible since we are not using any Active Directory with it. Since I am still a newbie in this environment,
I am not sure if it is possible.
But my main question was if it was possible to use freeRADIUS2 and that my NPS would be the RADIUS proxy. So my question is answered, if I understood right, without making any changes to our freeRADIUS2 this is not going to be possible right? Because we have
no AD?
Our setup is freeRADIUS2 + MySQL database where all the users are stored.
As I mentioned in my previous response this really isn't the right place
for this question but why would you want to try to use a MySQL store for
authenticating against Exchange in the first place when you've already got
an authentication store (Active Directory) that is tightly integrated with
Exchange?
I still really don't understand what it is you're trying to accomplish nor
why you're trying to use such a complicated, convoluted method to
authenticate Exchange users.
Paul Adare - FIM CM MVP
Any sufficiently advanced bug is indistinguishable from a feature.

Similar Messages

Exchange Server 2013 with a RADIUS server (freeRADIUS).

Hello,
I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
I am using Windows Server 2012, I already installed Exchange Server 2013 on it and everything works as intended.
But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS server which is not on my Windows Server 2012. I have to use their RADIUS server (freeRADIUS), the RADIUS server
from the company where I am doing my internship.
I already created a NPS and added the RADIUS Client + Remote
RADIUS Server Groups. I created a Connection Request Policies with the condition:
User Name *
I forwarded the Connection Request to the
Remote RADIUS server that I created in Remote RADIUS Server Groups and then I registered the NPS in th AD. But it's still not working.
Maybe I did something wrong or I misunderstood something or does this even work with Exchange Server 2013? To authenticate mailbox users with a RADIUS server before they can login into their mailbox and use their mailbox?
Thanks in advance.

Hi,
I suggest we refer to the following article to double confirm the Network Policy Server is registered properly.
http://technet.microsoft.com/library/cc732912.aspx
Thanks,
Simon Wu
TechNet Community Support

Exchange Server 2013 and RADIUS server(freeRADIUS2)

I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
I am using Windows Server 2012, I already installed Exchange
Server 2013 on it and everything works as intended.
But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS
server which is not on my Windows Server 2012. I have to use their RADIUS server ( freeRADIUS2 ), the RADIUS server from
the company where I am doing my internship.
I already did the checklist that is on http://technet.microsoft.com/en-us/library/cc772591.aspx. I configured the NPS as
a RADIUS proxy, because that's what I need.
So after doing everything that is on that checklist, my question is:
Is it possible that the Exchange Server 2013 will use my NPS which is now configured as a NPS RADIUS proxy to authenticate my mailbox users that I have on my Exchange Server 2013?

thanks for such a quick response.
Just a small question about the link that you put. Does member server mean other server other than domain controller?
Regards,
Yes, Also the server on which you are installing Exchange should have exchange installed.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange Server 2013 with 3rd party wild Card Certificate shows Invalid

Hi Team,
I've Exchange Server 2013 SP1. Imported a valid 3rd party wild Card Certificate but the status is continuously showing "Invalid" on all my 2013 servers. Any help?
Thank you.
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

Hello,
Can you enable it on the Exchange Services like, IIS, SMTP without any issues?
If the certificate is for OWA, is there any certificate issue when you accessing OWA?
Run the following command to get the Exchange Certificate information and post them for researching:
Get-ExchangeCertificate |FL
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Cisco PI 1.3 - Internal Server Error with RADIUS-authentication

Hi,
I have a problem with a Cisco Prime Infrastructure 1.3 (Appliance, fully patched) that I'm trying to authenticate against a Radiator RADIUS-server.
From the RADIUS-server's point of view it looks fine, but I just get an HTTP Status 500 internal error (see attached image) when trying to log in.
I'm not the one managing the RADIUS-server but I got the following debug sent from them:
Wed Oct 30 08:52:06 2013: DEBUG: Packet dump:
*** Received from 10.36.0.132 port 17235 ....
Code:       Access-Request
Identifier: 102
Authentic: REMOVED
Attributes:
        User-Name = "test-user"
        User-Password = REMOVED
        NAS-IP-Address = 10.36.0.132
        Message-Authenticator = REMOVED
Wed Oct 30 08:52:06 2013: DEBUG: Handling request with Handler 'Client-Identifier=/^prime[.]net[.]REMOVED[.]se$/', Identifier 'Network-Prime-AAA'
Wed Oct 30 08:52:06 2013: DEBUG: Deleting session for test-user, 10.36.0.132,
Wed Oct 30 08:52:06 2013: DEBUG: Handling with Radius::AuthUNIX:
Wed Oct 30 08:52:06 2013: DEBUG: Radius::AuthUNIX looks for match with test-user [test-user]
Wed Oct 30 08:52:06 2013: DEBUG: Radius::AuthUNIX ACCEPT: : test-user [test-user]
Wed Oct 30 08:52:06 2013: DEBUG: AuthBy UNIX result: ACCEPT,
Wed Oct 30 08:52:06 2013: DEBUG: Handling with Radius::AuthFILE:
Wed Oct 30 08:52:06 2013: DEBUG: Radius::AuthFILE looks for match with test-user [test-user]
Wed Oct 30 08:52:06 2013: DEBUG: Radius::AuthFILE ACCEPT: : test-user [test-user]
Wed Oct 30 08:52:06 2013: DEBUG: AuthBy FILE result: ACCEPT,
Wed Oct 30 08:52:06 2013: DEBUG: Access accepted for test-user
Wed Oct 30 08:52:06 2013: DEBUG: Packet dump:
*** Sending to 10.36.0.132 port 17235 ....
Code:       Access-Accept
Identifier: 102
Authentic: REMOVED
Attributes:
        cisco-avpair = "NCS:virtual-domain0=ROOT-DOMAIN"
        cisco-avpair = "NCS:role0=Admin"
        cisco-avpair = "NCS:task0=View Alerts and Events"
        cisco-avpair = "NCS:task1=Device Reports"
..the rest of the AV-pairs removed
Does anyone have any idea on what the the problem is, or some tips on how to troubleshoot? (rebooting and ncs stop/start has no impact on the issue)
//Charlie

I ran into a similar issue this morning in my lab. After I issued ncs status - the database service came back as not running. I stop/started the Prime services and it came up. Once all the services were running my WLC imported with no issues. I also deployed another server for another lab and it had issues with the clocking being out of sync.

Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

Hi Team,
Need urgent help in resolution of following error:
Environment Details: VMware ESXi 5.5 (vMotion)
Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
Prerequisites: Installed
Error: Installation gives Error at Step 10 during installation of Mailbox Service
Error Details Below:
Error:
The following error was generated when "$error.Clear();
if ([Environment]::OSVersion.Version.Major -ge 6)
$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
$reg= join-path (join-path $env:SystemRoot system32) reg.exe;
$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
if ((get-service wsbexchange).Status -eq "Running")
Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
Exchange /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
" was run: "Process execution failed with exit code 1.".

Resolved ! :)
Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
Thanks to all.

Exchange Server 2013 does not deliver mail as they arive.

I need Help and guidance on this problem. I have installed Exchange server 2013 with SP1 on Server 2012. Install Went perfect no error. It on a server with 2 TB storage. 16G
memory. Exchange 2013 is the only application running on the box. DNS service is also running on the box. I can see the mail arrive in the mail Box Queue with the Queue Viewer and they would just sit there and then after a 15 to 30 min delay it release the
mail to the mail boxes. The only error or warning I am seeing in the logs are the 6002 warning. Any suggestion would be greatly appreciated.

Please share message header of one of the delayed message. It will help to narrow down the issue.
Do you see any connection failures in connectivity logs.
Do you have multiple 2013 servers in your exchange environment ?
Lets fix it.
Received: from Xchngsvr.A.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32 via Mailbox
Transport; Fri, 25 Apr 2014 13:31:33 -0400
Received: from Xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 25 Apr
2014 12:30:44 -0400
Received: from xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server id 15.0.847.32 via Frontend
Transport; Fri, 25 Apr 2014 12:30:37 -0400
Received: from mia0vm-cass03.colo.sonicwall.com ([208.17.117.5])
by
xchngsvr.a.com (SonicWALL 7.4.5.1391)
with ESMTP id 201404251630370000228;
Fri, 25 Apr 2014 12:30:38 -0400
Received: from mail1.fieldsolutions.com ([98.129.95.107])
by
mia0vm-cass03.colo.sonicwall.com (SonicWALL 7.4.4.8439)
with ESMTP id
201404251631070343409; Fri, 25 Apr 2014 09:31:07 -0700
Received: from localhost (localhost [127.0.0.1]) by mail1.fieldsolutions.com
(Postfix) with ESMTP id F32731031781
for <[email protected]>; Fri, 25 Apr 2014
11:31:06 -0500 (CDT)
MIME-Version: 1.0
To: <[email protected]>
From: Field Solutions <[email protected]>
Subject: WIN#: 649890 NEW Signage - Reply-To: <[email protected]>
Content-Type: multipart/alternative;
boundary="=_747eac72d0ea92652b25d7d469d7165b"
Message-ID: <[email protected]>
Date: Fri, 25 Apr 2014 11:31:06 -0500
X-Mlf-KeyWords: preapproved,dollars$$$,pay,toner,expectations,fl,dollars,guarantee,voltage,confi
X-Mlf-Language-Detected: NoLanguageFilter_English
X-Mlf-Connecting-IP: 50.244.134.141
X-Mlf-Country-Code: US
X-Mlf-Rules: rn;7.24
X-Mlf-Rules-Pos-Features: WORD_voltage_2.97;WORD_configuration_2.51;WORD_inputs_2.50;WORD_documentation_2.
X-Mlf-Rules-Neg-Features: WORD_preapproved_-1.85;SUBJ_dollars$$$_-1.74;SUBJ_pay_-1.56;WORD_toner_-1.53;WOR
X-Mlf-Sliderbars: N4,B4,S4,L4,Q4,G4,A4,I4
X-Mlf-Version: 7.4.4.8439
X-Mlf-Threat-History: nothreat
X-Mlf-Threat-Detailed-History: nothreat;none;none;none
X-Mlf-UniqueId-History: i201404251631070343409
X-Mlf-Connecting-IP: 208.17.117.5
X-Mlf-Country-Code: --
X-Mlf-Threat: nothreat
X-Mlf-Threat-Detailed: nothreat;none;none;cloud-nj
X-Mlf-UniqueId: i201404251630370000228
Return-Path: [email protected]
X-MS-Exchange-Organization-Network-Message-Id: 5ea15b9c-561d-4a2a-d03e-08d12ebad75d
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: Xchngsvr.a.com
X-MS-Exchange-Organization-AuthAs: Anonymous
There is only one Exchange server in the Organization

Load balancing Exchange Server 2013 in coexistence

I am trying to load balance our Exchange 2013 CU7 environment with Citrix Netscaler. I am trying to start the process to migrate our users from 2010 SP3 to 2013 CU7. Every once in a while I experience a looped login when trying to login to OWA. You enter
your username and password and it loops right back to the login page... stopping you from ever logging in.
This made me think it was something with session affinity on the load balancer... however I thought they didn't need that anymore. So I'm wondering if since i'm in coexistence with 2010 it still is required.
I have no users on 2013 yet so all my test accounts are on 2010.
My environment:
3x Exchange 2013 CU7 CAS/MBX combined
3x Exchange 2010 CAS
3x Exchange 2010 MBX
2x Citrix Netscaler 10.5 VPX
Does anyone know the proper way to configure this? Information on Netscaler for this would be great but it doesn't have to be related to Netscaler. I'm just looking for the proper session affinity values for Exchange 2013 with 2010 coexistence.

Hello. Perhaps you have problems in the CAS Exchange.
Suggest that the test plan.
1. Check the operation through
Troubleshooting Exchange Server 2013 with Test Cmdlets
Get-webservicesvirtualdirectory
Get-oabvirtualdirectory
Get-owavirtualdirectory
Get-ecpvirtualdirectory
Get-ActiveSyncVirtualDirectory
Get-AutodiscoverVirtualDirectory
Test-ServiceHealth
Test-MapiConnectivity
Test-OutlookConnectivity
Test-OutlookWebServices
Test-WebServicesConnectivity
Test-EcpConnectivity
Test-ActiveSyncConnectivity
Test-PowerShellConnectivity
2. In turn one of the output of the CAS and balancing on a test machine, through HOST file list the test CAS. If all CAS correct answer, then check Netstsaler.
MCITP, MCSE. Regards, Oleg

Exchange Server 2013 - DAG Failure

Exchange server 2013 with two Mailbox server role and One CAS server role with DAG Enabled on it.
Exchange server went live with 150 Mailbox on both the server distributed evenly.
Both mailbox server lost connectivity and unable to communicate with CAS server.
Outlook and OWA user unable to connected to their mailboxes.
Both the Mailbox server went down disrupting the mailflow.
Later found that Cluster Node wasnt responding in timely fashion. Had to remove the Mailboxes from the DAG and later remove the DAG configuration.
Disable Replication network on each of the mailbox server and rebooted it.
Re gain network connectivity to the Mailboxes and they are back on online.
What could be the issue.
Both mailbox server are rich in resources which can be ruled here

Hello,
According to your description, your network configure may be issue.
We recommend you assign static IP address for cluster server to check the result.
Cara Chen
TechNet Community Support

Exchange server 2013 send and received issue

Hi Support,
I have install Exchange Server 2013 with server 2012 ( my domain not resisted but mail send & received in local for practice then live ) but few days back some changes in dns and ecp and mail stop sending and receiving. how to verify my exchange server
2013 working fine. Please give the step check perpoes.

dear Pardeep, you said it was working fine then you did some DNS changes..
i would suggest you best troubleshooting step is to go to exrca.com and perform the tests and from there we take it up.
Secondly you can verify your config from the below link.
http://www.techieshelp.com/exchange-2013-step-by-step-configuration/
in DNS you need to make sure you have atleast MX and A record done for your server having email services installed.
for ECP... i would we would take this later lets check the mail sending and receiving first. use the above links
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Exchange server 2013 proxy authentication

Hi All,
I wanted to know what is the recommended proxy authentication for exchange server 2013.
I have observed the following from different proxy authentications:
1. Negotiate: By default, the proxy authentication is set to negotiate and uses anonymous as Log on network security(un-encrypted MAPI)
2. Basic: It always prompts for the user credentials and uses encrypted MAPI.
3. NTLM: Use negotiate at MAPI level by default
Please provide me some information on different authentication mechanisms and the one which is recommended to use.
Thanks,
Srinivas.

Hi Srinivas,
According to my knowledge, there are my views below:
Basic authentication: If you select this authentication type, Outlook will prompt for username and password
while attempting a connection with Exchange.
NTLM authentication: If you select this authentication type, exchange does not prompt users for a user
name and password. The current Windows user information on the client computer is supplied by the browser through a cryptographic exchange involving hashing with the Web server. If the authentication exchange initially fails to identify the user, the browser
will prompt the user for a Windows user account user name and password. So, when Outlook is trying to connect to Exchange and if the machine is domain joined, there isn’t a need to provide password.
Negotiate authentication: Enabled by default in Exchange 2013. This is a combination of Windows integrated
authentication and Kerberos authentication. If we employ negotiate authentication, exchange will authenticate the client using NTLM authentication type and if unable to verify authenticity, will challenge the client to authenticate using a username and password.
And you could set the authentication type like this:
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
The command below for your reference:
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalHostname "internalServer.contoso.com" -InternalClientAuthenticationMethod Ntlm -InternalClientsRequireSsl $true -ExternalHostname "externalServer.company.com" -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $true -IISAuthenticationMethods Negotiate,NTLM,Basic
If you have any further questions, please let me know.
Best regards,
Eric

Issues with setting up Exchange Server 2013

Hi All
Not sure what im doing wrong yet i am having issues with exchange server 2013.
Currently I have got general SMTP Mail flow working. as long as i log onto the local servers OWA (https://10.x.x.x/owa) i can log into a users mailbox. i have tested sending and recieving mail using this and it works.
My main issue now is with accessing the OWA externally via our website. (owa.xx.xx.au/owa) or connecting ANY Outlook to the server.
When i connect to the exchange server via outlook it asks for the password again multiple times never authenticating it then time's out and says:
" the action cannot be completed. the connection to microsoft exchange is unavailable, outlook must be online or
connected to complete this action "
then when i click on OK it goes to the General Tab and under microsoft exchange server: the name for it appears as
[email protected]
with mailbox set as:
=SMTP:[email protected]
Currantly on our DNS i have
mx= 10 mail.xx.xx.au
CNAME= autodiscover = mail.xx.xx.au
CNAME= OWA = mail.xx.xx.au
A = mail = 12.34.56.78
On our modem/router i have set one-to-one nat to our firewall IP
On our firewall i have
SMTP SAT and NAT to Exchange server
HTTPS Sat and NAT to exchange Server
HTTP Sat and Nat to exchange Server
Port 587 SAT and Nat to exchange server
pop SAT and NAt to exchange server
Im willing to bet its something stupid i have overlooked but i was wondering if anyone would be able to help me out
Regards
Sibsy

Hello,
Firstly, please follow the Shadab's suggestion to check related virtual directory settings.
Please make sure you use certificate that's created by a CA that's trusted by the client computer's operating system.
Please use get-outlookanywhere | fl cmdlet to check ExternalClientAuthenticationMethod. By default, the authentication is Negotiate.
Cara Chen
TechNet Community Support

Exchange Server 2013 - Lab setup with internal emails only

Hi,
I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
go over the internet.
I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
Regards,
Nithin

Hi,
You need not to configure send/receive connectors for internal email.
The following article for your reference:
http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
Default Receive connectors created during setup
Certain Receive connectors are created by default when you install the Mailbox server role.
Default Receive connectors created on a Mailbox server running the Transport service
When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
These connectors are the following:
Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
mentioned, their TransportRole value is HubTransport.
To view the default Receive connectors and their parameter values, you can use the
Get-ReceiveConnector cmdlet.
Default Receive connectors created on a Front End Transport server
During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
In a typical installation, no additional Receive connectors are required.
Niko Cheng
TechNet Community Support

Exchange Server 2013 // MFCMAPI could connect with errors

While connecting with Exchange Server 2013 I have started facing problem with my application.
My application fails to connect to Exchange with below parameters, then i have tried using MFCMAPI to if everything is okay. MFCMAPI could connect with above errors.
And I have tried with program using below parameters, i still get network error from MAPI call. Can you kindly help, I can provide any additional
details needed.
___ props[prop_count].ulPropTag = PR_PROFILE_UNRESOLVED_NAME;
    props[prop_count].Value.lpszA   = <ProfileUnresolvedName>;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_UNRESOLVED_SERVER;
    props[prop_count].Value.lpszA   = <[email protected]>;
    prop_count++;
    // Setting this to TRUE causes OpenMsgStore() to fail with MAPI_E_UNCONFIGURED
    props[prop_count].ulPropTag      = PR_CONVERSION_PROHIBITED;
    props[prop_count].Value.b        = FALSE;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_CONFIG_FLAGS;
    props[prop_count].Value.l       = CONFIG_SERVICE /*| CONFIG_PROMPT_FOR_CREDENTIALS
| CONFIG_SHOW_CONNECT_UI */;
    prop_count++;
    props[prop_count].ulPropTag     = PR_DISPLAY_NAME;
    props[prop_count].Value.lpszA   = <Mailbox Profile Name>;
    prop_count++;
    //Above setting used to be sufficient to connect using RPC
    //Below parameters added to connect via HTTPS
    LPSTR pwszUser = "domain\\username"; //also tried
[email protected] AND username
    LPWSTR pwszPassword = L"paswword"; // Password has been encrypted using CryptProtectData
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_W;
   props[prop_count].Value.lpszW = L"https://ProxyHostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_NONE;      // RPC_C_HTTP_AUTHN_SCHEME_NTLM,
RPC_C_HTTP_AUTHN_SCHEME_BASIC
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_FLAGS;
    props[prop_count].Value.l = PRXF_ENABLED | PRXF_SSL;// | PRXF_IGNORE_SEC_WARNING; // | PRXF_IGNORE_SEC_WARNING;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_PRINCIPAL_W;
    props[prop_count].Value.lpszW = L"msstd:certificateserverhostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_GSS_NEGOTIATE;
// RPC_C_AUTHN_WINNT, RPC_C_AUTHN_GSS_NEGOTIATE, RPC_C_AUTHN_NONE
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_USER_W;
    props[prop_count].Value.lpszA = pwszUser;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PASSWORD;
    props[prop_count].Value.bin.lpb = dataBlobOut.pbData;
    props[prop_count].Value.bin.cb = dataBlobOut.cbData;
    prop_count++;
    DB( (DB_PR _T("ConfigureExchangeService() About to configureMsgService\r\n"),
this ) );
    hres = lpServiceAdmin->ConfigureMsgService( exchUID, 0, config_flags, prop_count, props
    I still get MAPI_E_NETWORK not found
Are there any configuration changes need to be done on Exchange Server?
Is there any mistake in above parameters?
Kindly suggest.

You can refer Dave's blog post @
http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx
DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

AD RMS 2012 integration with exchange server 2013

AD RMS 2012 integration with exchange server 2013
I would like to have a knowledge About this Topic
1.what is differrent if we use internal SSL certificate with Public Certificate and in this case i would like to use Mobile Phone I eed to import Root Certificate ?
2.Do I have problem? If I start to install AD RMS 2012 with SQL EXpress after that I want to chage it to SQL Server ?
3.when I use SQL Expres what I can do after Disk is full (10 GB)?
4.If AD RMS is down It will affect with email that it is already sent ?
5. Which Edition of outlook can produce IRM protected documents
6. To Use AD RMS Server 2012 through OWA, Outlook and Moblie Phone ,a CAL is required or not ?

Could you post the list of sites:
appcmd list site
The ones listening on port 80:
appcmd list site /bindings:http/*:80:
And on port 443:
appcmd list site /bindings:https/*:443:
Step by Step Screencasts and Video Tutorials

Exchange Server 2013 with RADIUS authentication

Similar Messages

Maybe you are looking for