[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2065
  • Last Modified:

Outlook Web Access could not find a mailbox for NSESERVER3\IUSR_NSESERVER3.

Hello Experts:

I have an Emergency that I cannot figure out.  When my users are trying to access their email via OWA--they are getting this message from the IE 7 browser.

Outlook Web Access could not find a mailbox for NSESERVER3\IUSR_NSESERVER3. If the problem continues, contact technical support for your organization and tell them the following: The mailbox may be stored on a Microsoft Exchange 2000 or Microsoft Exchange 2003 server, or the Active Directory user account was created recently and has not yet replicated to the Active Directory site where this Client Access server is hosted.

Can anyone help me?  Thanks
0
huntersp3
Asked:
huntersp3
  • 13
  • 3
  • 3
1 Solution
 
poweruser32Commented:
can you test it out with ie6?it may be the ie version
0
 
huntersp3Author Commented:
It was working fine with any brower
0
 
poweruser32Commented:
have any changes been made or applied to the server?-try a reboot when there is no one using it
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
huntersp3Author Commented:
the changes I was making was installing a SSL certificate on the server and then restarted IIS services
0
 
huntersp3Author Commented:
Hello Poweruser32:

I have rebooted the Exchange 2007 server and still no luck.  I have migrated all the mailboxes from exchange 2003 over to exchange 2007--where I have I missed this one?
0
 
huntersp3Author Commented:
Hello Everyone:

I think my problem is that I don't have a mailbox called NSESERVER3\IUSR_NSESERVER3 that resides on Exchange 2007--how to I correct this issue.  I really need some advice--my field users are totally disconnected from their email.  I appreciate the help!!
0
 
huntersp3Author Commented:
Hello Everyone:
Here is the complete message I am getting when I am trying to browse to the OWA on Exchange 2007:

Any ideas are appreciated.

Outlook Web Access could not find a mailbox for NSESERVER3\IUSR_NSESERVER3. If the problem continues, contact technical support for your organization and tell them the following: The mailbox may be stored on a Microsoft Exchange 2000 or Microsoft Exchange 2003 server, or the Active Directory user account was created recently and has not yet replicated to the Active Directory site where this Client Access server is hosted.
0
 
poweruser32Commented:
have you configured the firewall to point to the new ex 2007 server ??port 443 if you are using owa with ssl
0
 
huntersp3Author Commented:
Hello Poweruser:

Every thing was working perfectly until earlier today--I found that one of the co-workers messed with the permissions in IIS and I believe that is what has messed up everything.  All the field users were able to logon to OWA with no problems before this happened.  Any thoughts on how to correct it?
0
 
SembeeCommented:
The error you are getting is because anonymous has been enabled somewhere it shouldn't. The account name you are seeing is the anonymous account on the machine.

As this is Exchange 2007 I would suggest deleting the Exchange virtual directories and recreating them using PowerShell so that the permissions are back to default.
Then find the co-worker who messed about with the permissions and suggest they update their CV and remove their admin rights as they don't have a clue what they are doing.

Simon.
0
 
huntersp3Author Commented:
Hello Sembee:

I am still new to Exchange 2007--can you give me the steps or procedures on deleting the Exchange virtual directories and recreating with power shell...Thanks for the help!!
0
 
huntersp3Author Commented:
Hello Sembee:

I successfully deleted the owa directory and recreated the new owa directory using power shell but when I try to use the owa--I get  440 Login Timeout.  Any idea?
0
 
SembeeCommented:
Do you get the login timeout immediately, or do you get any prompts at all?
Have you enabled forms based authentication?

Simon.
0
 
huntersp3Author Commented:
Hello Sembee:

I get the login timeout immediately.
0
 
huntersp3Author Commented:
Hello Sembee:

Also, about 10 minutes ago, I finished following these instructions at http://support.microsoft.com/kb/941201 and still get the 440 Login Timeout.  
0
 
SembeeCommented:
Did you do the iisreset?
I am not convinced the authentication is working correctly. You should get a prompt.
What URL are you using?

https://host.domain.com/owa
https://servername/owa

Try using the FQDN, which should stop IE from trying to use integrated authentication.

Simon.
0
 
huntersp3Author Commented:
Hello Sembre:

Yes, I did reset IIS using the iisreset /noforce.  I tried both https://mail.nationalsteelerection.com/owa and https://nseserver3/owa and still get the same result.  No doubt I have something wrong with permissions.
0
 
huntersp3Author Commented:
Hello Sembee:

Well, I am in deep trouble with my boss.  I am not to go home until this is fixed..geez.  Do you think coming from a SBS 2003 server over to Exchange 2007 has something to do with it?  All my users in house is getting their email with no problems.  

Most concerned
Steve
0
 
huntersp3Author Commented:
Sembee and others--thanks for the help.  The email is up and going now.  I followed the steps at http://support.microsoft.com/kb/941201 -- again--and it worked!!
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

  • 13
  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now