Announcement

Collapse
No announcement yet.

New backend not accessible through front end

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • New backend not accessible through front end

    Hi all

    Setup new backend server, Windows Server 2003 R2 (SP1) with Exchange 2003 SP2. I have moved my mailbox to it which works fine through Outlook 2003 and i can go direct to the Exchange server through IE and see it through OWA.

    But when I go to the Frontend server (Windows 2000 SP4, Exchange 2003 SP1) it keeps asking for username and password and after three attempts i get Unauthorised.

    I have set the domain on the security tab on the HTTP virtual directory to the same as the other backends (Windows 2000 SP4, Exchange 2003 SP1), and the firewall ports are all set the same.

    What am I missing???!!
    Server 2000 MCP
    Development: ASP, ASP.Net, PHP, VB, VB.Net, MySQL, MSSQL - Check out my blog http://tonyyeb.blogspot.com

    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

  • #2
    Re: New backend not accessible through front end

    I have tried changing the new backends HTTP security settings. I have taken off integrated and left only basic with the domain set as DOMAIN\ which is the same as the Windows 2000 SP4 boxes.

    This does not work. When i change it to just DOMAIN it works.

    Is this an IIS incompatibility between 2000 and 2003 in an Exchange setup?

    We are adding another front end which will be Windows Server 2003 R2 (SP1) and Exchange 2003 SP2 soon so I can try that out. In the mean time any suggestions please post them.

    Thanks.
    Server 2000 MCP
    Development: ASP, ASP.Net, PHP, VB, VB.Net, MySQL, MSSQL - Check out my blog http://tonyyeb.blogspot.com

    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

    Comment


    • #3
      Re: New backend not accessible through front end

      You seem to have missed the golden rule with frontend servers.

      The frontend server should always be the same or higher version than the backend server. That goes for service packs.

      Your frontend should be upgraded to SP2 then you may see an improvement in the operation.

      Simon.
      --
      Simon Butler
      Exchange MVP

      Blog: http://blog.sembee.co.uk/
      More Exchange Content: http://exchange.sembee.info/
      Exchange Resources List: http://exbpa.com/
      In the UK? Hire me: http://www.sembee.co.uk/

      Sembee is a registered trademark, used here with permission.

      Comment


      • #4
        Re: New backend not accessible through front end

        So if i upgrade the front end to SP2 you think it will work?

        But what about the IIS differences? One is 5 (2k SP4) and one is 6 (2k3 SP1)?
        Server 2000 MCP
        Development: ASP, ASP.Net, PHP, VB, VB.Net, MySQL, MSSQL - Check out my blog http://tonyyeb.blogspot.com

        ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

        Comment


        • #5
          Re: New backend not accessible through front end

          Well the new Front end is in (2003 R2 Sp1, Exchange 2003 SP2) and it didn't quite work. I got a horrible looking OWA screen - looked like it didn't have a CSS. I ran Microsoft Update and installed three missing patches and SHAZAM!

          It works fine now... on the new front end.

          The old one will be going soon - hopefully!
          Server 2000 MCP
          Development: ASP, ASP.Net, PHP, VB, VB.Net, MySQL, MSSQL - Check out my blog http://tonyyeb.blogspot.com

          ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

          Comment

          Working...
          X