Friday, December 20, 2013

550 5.7.1 Client does not have permissions to send as this sender

Status: offline Clients like IMAP and POP3 uses the Client <servername> Receive -Connector. In order to allow clients to submit messages via this connector, you need to issue below command: 

get-receieveconnector Client <servername> | add-adpermission -user AU -extendedrights ms-Exch-SMTP-Accept-Authoritative-Domain-Sender 
RE: 550 5.7.1 Client does not have permissions to send as this sender


In adsiedit under :  Configuration - Services - Microsoft Exchange - 
<organization name> - Administrative Groups - Exchange Administrative Group
- Servers - <Servername> - Protocols - SMTP Receive Connectors - Client <servername>

Right click and click properties, click the security tab and grant the Authenticated users group the Accept Authoritative Domain Sender allow permission.

Other settings can be checked is as follows

From EMC 
check  logintype,

We checked the settings on the Outlook and is correct. SPA is unchecked.
In Advanced we have IMAP port as 993- SSL.
In outgoing server we have "use same server as incoming server" checked.

Tested mail flow but incoming IMAP passes the test and Sending mail SMTP fails.

Tuesday, December 17, 2013

How Mail from outlook sent to another outlook via Exchange server

The Mail Submissions Service on the Exchange 

2010 Mailbox Server notifies the Hub 

Transport Server that a message is in the Outbox. The 

Store Driver on the Hub Transport 

Server retrieves the message from the Mailbox Server. 

RPC is used for communication between the Hub and the 

Mailbox Server.

Monday, December 16, 2013

Netmon from Command Prompt

Netmon from Command Prompt

Start > Run type CMD click OK. 

cd "c:\Program Files\Microsoft Network Monitor 3"

C:\nmcap.exe /network * /capture /file ExchangeTrace-client.chn:100M 

c:\nmcap.exe /Network * /Capture /CaptureProcesses /File ExchangeTrace.chn:100M

In the below example the client IP is and the server IP is
nmcap.exe /Network * /Capture "(ipv4.Address == and ipv4.Address ==" /CaptureProcesses /File ExchangeTrace.chn:100M

Netmon Command
IPv4.address == IP address 

Microsoft Exchange server Common Scripts from Exchange Management Shell

How to find Mailbox is Shared Mailbox

C:\Get-mailbox -Resultsize unlimited | Where-object {$_.Isshared -eq $True}

An alternative way to identify possible problematic receive connectors by using Exchange Management Shell, is if the queue delivery type is SmtpRelayToRemoteAdSite. To do this, run the following shell commands:
$remotesite = (get-queue | where {$_.LastError -like "451 4.4.0*"}).NextHopDomain

get-exchangeserver | where {$ -like '*'+$remotesite} | get-transportserver | Get-ReceiveConnector | where {$_.Bindings -like '*:25*'} | where {$_.AuthMechanism -notlike '*Exchange*'

From blog

This command spins through all your mailbox servers and reconnects all the uniquely identified but disconnected mailboxes in any one of the mailbox stores:
$Servers = Get-ExchangeServer 

$Servers | ` 
Where { $_.IsMailboxServer -Eq '$True' } ` | ForEach { Get-MailboxStatistics -Server $_.Name ` 
  | Where { $_.DisconnectDate -NotLike '' } ` | ForEach { Connect-Mailbox -Identity `$_.DisplayName -Database $_.DatabaseName} }

Want to know what version of Exchange Server each of your servers is running? Type:
Get-ExchangeServer | Format-Table Name, *Version*

Want to create a group of test users in your lab? Use this command:
1..100 | ForEach { Net User "User$_" MyPassword=01 /ADD /Domain; Enable-Mailbox "User$_" }

Wednesday, December 11, 2013

File share folder is inaccessible from the Exchange server 2010

File share folder is inaccessible from the Exchange server.

We checked and found the folder permission is fine.

We added the "Exchange subtrusted system", still the same issue.

We click the "Share" under "Network file and Folder sharing" (>apply > OK)

Now issue is resolved.

Friday, December 6, 2013



  • Stateless protocol

  • In computing, a stateless protocol is a communications protocol that treats each request as an independent transaction that is unrelated to any previous request so that the communication consists of independent pairs of requests and responses.

  • AutoDatabaseMountDial

  • lossy failover
  • The default setting is GoodAvailabilitywhich translates to 6 or fewer logs 

  • BestAvailability (12 or fewer logs missing) and Lossless (0 logs missing).

  • from 
  • Host or Local Candidate – The actual IP address bound directly to the remote client’s host operating system.  This could include multiple candidates as the remote host could contain multiple physical or virtual network adapters including any active VPN clients.  Most often this will be a single IP address of the active interface on a Lync client’s workstation.
  • Reflexive or STUN Candidate – The public IP address assigned to the client’s immediate firewall perform network address translation.  In most home networks this would be the public IP addresses assigned by an ISP (either dynamically or statically) to the premises modem or router, depending on the type of service.
  • Relay or TURN Candidate – The publically accessible IP address assigned to the media relay server which is allocated to the client.  In Lync Server this is the public IP address assigned either directly to the external A/V Edge interface or the public IP address allocated to a NAT device (e.g. firewall) which is performing static network address translation to a private IP address assigned directly to the Edge Server.  In the event that an Edge Pool is deployed then this would be the IP address of one of the individual servers in the pool. 

  • Wednesday, December 4, 2013

    scripts to find how many users are logon using OWA

    Method 1: 
    You can find the output when you run get-logonstatistics from the article below:
    View Logon Statistics

    Method 2:
    Besides, you can use logparser to analyze it
    C:\Program Files (x86)\Log Parser 2.2\logparser.exe" "SELECT TOP 10 cs-username, Count(*) AS OWAHits INTO OWAActivity.gif FROM C:\Inetpub\logs\LogFiles\W3SVC1\u_ex*.log WHERE cs-uri-stem LIKE '/OWA/' AND cs-username IS NOT NULL GROUP BY cs-username ORDER BY OWAHits DESC" -charttype:Bar3D -o:CHART -view:ON
    "C:\Program Files (x86)\Log Parser 2.2\logparser.exe" "SELECT TO_STRING(time, 'HH') AS Hour, COUNT(*) AS Hits INTO hitPerSecond.jpg FROM C:\Inetpub\logs\LogFiles\W3SVC1\u_ex*.logGROUP BY Hour ORDER BY Hour ASC" -i:IISW3C -o:CHART -chartType:ColumnClustered -chartTitle:"Hourly Hits" -groupSize:420x280

    Method 3:
    We can run the command below to get the current number of outlook or OWA user who is connecting to Exchange Servers.
    Get-Counter "\MSExchange RpcClientAccess\User Count" -ComputerName  name|ft
    Get-Counter "\MSExchange OWA\Current Unique Users" -ComputerName  name |ft

    OWA session with name of the user
    Get-Mailbox | Get-LogonStatistics | Where-Object {$_.ApplicationID -eq "Client=OWA"| Select-Object UserName,LastAccessTime | ConvertTo-Html -Title "OWA actives sessions" -PostContent "<b>Thierry MILLE (c) 2011</b>" | Out-File C:\owa.htm; Send-MailMessage -From -To -Subject "OWA sessions" -Attachments C:\owa.htm -SmtpServer; Remove-Item C:\owa.htm