!!! Exchange 2010 is the Best version of ALL !!!!

I start blogging a lot about 2010 so much to talk, all in once the best version of exchange in many aspects in my eyes. I am truly loving Exchange 2010 and can write one or more article per day , no joke, because Exchange 2010 has so much to talk about.

The changes in database tables, the new structure or DB, makes it more efficient ***Faster*** and goodbye SIS (- : ,goodbye SG (storage groups), another 70 percent reduction introduced in Exchange 2010,( maybe even more) on top of improvement have been introduced in exchange 2007, JBOD.

Finally off load the exchange off the SAN (huge savings to everyone) and first time in history fully redundant messaging experience with no third party or SAN solution right out the product itself.

The new power of Exchange start shining with DAG (data availability Group) will make your messaging environment fully redundant with two server, and fail over is handled by natively with the application. The user experience is blip most of the time.

Not to mention more is given with exchange, your compliant regulatory requirements, email archiving solution is also comes with the product. This is incredible value, better faster, and the most comprehensive version of messaging application with ***less*** complexity.

Well as I said so much to talk about 2010, I truly believe not upgrading to exchange 2010 will cause lost in revenue to the business and that is why exchange 2010 will be the best version and most powerful version ever in the MS messaging history.

I recommend download the public version and see the power with your own eyes, you will be amazed with all new futures and the power.

Download 2010 here

Oz Casey Dedeal

MVP (Exchange)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

Http://smtp25.blogspot.com (Blog)

Https://telnet25.spaces.live.com (Blog)

Https://telnet25.worldpress.com (Blog)

530 5.7.1 Client was not authenticated Exchange 2010

Problem:

After new installation you are able to sent mail out but not able to receive emails.The sending host is receiving fallowing command on SMTP handshake from your mail server “530 5.7.1 Client was not authenticated”

Solution:

I had one of my previous post same issue with Exchange 2007, please do remember, the product exchange is being delivered to you totally secure, and even anonymous access has not been turned on, you as an Exchange administrator must do it.

to understand and see the your server response , you need to open telnet session to your server and use standard SMTP commands to see what is going on so on your exchange server lets start installing Telnet client first

Open DOS or PowerShell and type below

servermanagercmd -install telnet-client

Now on the same screen type

helo  ( hit enter) 220 mail2.smtp25.org Microsoft ESMTP MAIL Service 250 mail2.smtp25.org Hello [10.10.10.10] mail from:Telnet25@Gmail.com ( Use yours) hit enter 530 5.7.1 Client was not authenticated

As you see the server response is “530 5.7.1 Client was not authenticated”

Now lets take care of that, open EMC , go under your Server configuration, hub transport server default receive connector, properties, click on last tab “permission Groups” place check mark into “Anonymous users” click apply and ok.

Now go back to DOS window we opened earlier,

telnet to your mail server on port 25 one more time,

this time you will get

Telnet mail3 25 220 mail3.smtp25.org Helo 250 mail3.smtp25.org Hello mail from:telnet25@Gmail.com 250 2.1.0 Sender OK

Now your mail server is ready to accept mails from outside

Previous article

Oz Casey Dedeal

MVP (Exchange)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

http://smtp25.blogspot.com/ (Blog)

https://telnet25.spaces.live.com/ (Blog)

https://telnet25.worldpress.com/ (Blog)

WS Management could not connect to the specified destination Exchange 2010

Problem:

Accessing Exchange 2010 OWA received fallowing error.”Connecting to remote server failed with the fallowing error message: WS Management could not connect to the specified destination (mail3.smtp25.org:443)

Solution:

Check to make sure WWP (Worldwide publishing service is started) you can open DOS or Power Shell

Type “Services.msc” to open GUI services management console to see the state of the service.

If you are doing this from Power Shell

Restart-Service W3SVC

You can also use

Net stop W3SVC

Net Start W3SVC

Reference PowerShell Usage

Oz Casey Dedeal

MVP (Exchange)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

http://smtp25.blogspot.com/ (Blog)

https://telnet25.spaces.live.com/ (Blog)

https://telnet25.worldpress.com/ (Blog)