• Forum
  • About
  • Archives
  • Categories

    • Posts Tagged ‘exchange’

    Exchange 2007 OWA on non standard port


    2010 - 05.06

    Tags: , , , , , ,
    Posted in Geek | No Comments »

    I don’t know about you, but I’m planning on removing my old Exchange and I can’t be bothered to flap about backend and front-end, redirects and all that crap. As I move my users from 2003 to 2007 I want a nice easy transition. Outlook does this fine and copes, but obviously OWA changes.

    Rather than worry about certificates, I decided just to open up another port for external and push that through to the new Exchange server. To do this, do the following:

    1) On your Router, go to NAT and set port forwarding to be external port 4444 to go to your Exchange servers IP and port 443.

    2) On your MSExchange server, open IIS Admin, right click “Default Web Site”, properties. Set the HTTPS port to 4444. Apply, OK. Fire up a CMD window and type “iisreset /restart /noforce”.

    3) Open Exchange Management Console, Server Configuration, Client Access, choose the server in the top pane and then open the properties of OWA in the bottom pane. Set the External URL to https://your_ip:4444/owa

    Click Apply, OK.

    That’s it, you should now be able to navigate to your external IP/owa on port 4444 and open mailboxes on that exchange box without a hitch.

    MS Exchange 2007 ISAPI error


    2010 - 03.10

    Tags: , , , , ,
    Posted in Geek | No Comments »

    We all love a bit of complaining about Microsoft and then they went out and made sure we’d bitch, by allowing 32bit and 64bit .NET apps with a plugin to IIS, and then not allow them to run concurrently.

    The trap I’ve fallen in to is that I am suffering with the amazing Service Unavailable screen on my OWA. The event log is screaming at me with W3SVC-WP errors:

    ISAPI Filter ‘C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\\aspnet_filter.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    —–

    Okay, so we know this sucks. Finding the info to fix can be a little tricky so here, fire up a cmd shell and run these 2 lines:

    cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

    %SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i

    The first line allows 64bit only, the second reinstalls asp .NET.

    Go take a look at your OWA or Exchange web services and they should be back to normal.

    Exchange 2007/2010 smtprelaytotirg


    2010 - 01.31

    Tags: , , ,
    Posted in Geek | No Comments »

    I installed a Windows 2007 Exchange server in to my 2003 environment this week. All went well apart from that the mail sending from the 2007 test mailboxes ended up in a queue called smtprelaytotirg. The error message given being 451 4.4.0 Primary Target IP Address Responded with (501 5.5.4 Auth Command Cancelled).

    This queue is basically where 2007 is failing to deliver because it can’t route correctly.

    The resolution in this case for me was easy. All the connectors were in place as they should be, but the transport for SMTP on the original master 2003 Exchange server had limited access to certain IP addresses.

    I added the IP address for the new Exchange 2007 server and bang, 20 mins later the queue is empty.

    Just a minor hurdle :) Oh, the other one to watch out for is making sure it can resolve either by IP or FQDN for the SMTP server, it’ll fail on netbios or just a single name. Anyone still relying on WINS needs shot in the face with a screw driver.