Announcement

Collapse
No announcement yet.

NLB OWA "Page Cannot be found" for one user.

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

  • NLB OWA "Page Cannot be found" for one user.

    Hi,

    I'm struggling to understand quite what is happening here but basically I currently have one user who gets a "Page cannot be found" error when accessing OWA using the NLB name or IP address. There are no other users that have problems and I can confirm he can access his email without a problem when accessing either server in the NLB pair directly.
    I have tested this on multiple machines, all of which work for other users.

    Anyone have any thoughts?
    Attached Files
    cheers
    Andy

    Please read this before you post:


    Quis custodiet ipsos custodes?

  • #2
    Re: NLB OWA "Page Cannot be found" for one user.

    Did you managed to try Explicit logon for this affected users?......any improvement?

    * Can you check on the primary or seconday SMTP address to see if / is added by any-chance?

    Cheers
    Aravind

    Comment


    • #3
      Re: NLB OWA "Page Cannot be found" for one user.

      Thanks for the response,
      I removed all exchange attributes from this user and then resetup access to the old mailbox with no change. I have found https://mail.domain.com works but mail.domain.com/exchange doesn't.
      No oddities in the email addresses definitely though.
      Will be looking more into this tomorrow.
      cheers
      cheers
      Andy

      Please read this before you post:


      Quis custodiet ipsos custodes?

      Comment


      • #4
        Re: NLB OWA "Page Cannot be found" for one user.

        Hi,

        A slightly further update, does anyone know what generates the url?
        I can see the number 2 is appended here on the failed site, the user account doesn't have this anywhere I can see. It is possible something was changed by the support desk incorrectly?

        Failing site when adding /exchange
        https ://site.domain.com/exchange/Julia.Roberts2/Inbox/?Cmd=contents

        Working site without /exchange
        https ://site.domain.com/Julia.Roberts/Inbox/?Cmd=contents
        Last edited by AndyJG247; 9th March 2009, 16:51.
        cheers
        Andy

        Please read this before you post:


        Quis custodiet ipsos custodes?

        Comment


        • #5
          Re: NLB OWA "Page Cannot be found" for one user.

          Originally posted by AndyJG247 View Post
          Failing site when adding /exchange
          https ://site.domain.com/exchange/Julia.Roberts2/Inbox/?Cmd=contents

          First of all let's get the priorities right.

          Can I have an autograph of the user and possibly a date???

          Secondly, I am not sure if this will help but it's worth a go. Can you check the users attributes with AD Explorer to see if any of the attributes was changed somehow.
          Last edited by L4ndy; 9th March 2009, 16:56. Reason: Quote added just in case user name changed !!
          Caesar's cipher - 3

          ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

          SFX JNRS FC U6 MNGR

          Comment


          • #6
            Re: NLB OWA "Page Cannot be found" for one user.

            I will ask her and let you know...

            I've been using ADSI edit to look at the account and can't see anything that looks out of place, I have found another user with the same name in a different domain so it may be possible that someone edited it to solve a conflict.

            I've found this also works
            https ://site.domain.com/exchange/[email protected]/
            cheers
            Andy

            Please read this before you post:


            Quis custodiet ipsos custodes?

            Comment


            • #7
              Re: NLB OWA "Page Cannot be found" for one user.

              Thanks e_aravind & L4ndy,
              It appears the user was originally conflicting with another user in another domain within our forest. The original [email protected] was duplicated so someone added 2 to the end of the name. Exchange got confused somehow so I removed the first.last2 from the users and OWA worked pretty much straight away. Most odd that this only affected the /exchange site though.
              cheers
              Andy

              Please read this before you post:


              Quis custodiet ipsos custodes?

              Comment

              Working...
              X