OWA problems

What are you having them enter in the username field when they're prompted by OWA?  It should be their domain username/password, which is not the same thing as their email address.

I'm using domain/username and I have tried username only and username@parkcountysheriff.net.

try entering it in using the format:  netbiosdomainname\username

Another possible combination might be username@netbiosdomainname

It's definitely not the format.  It has to be a setting somewhere.  I don't think permission because i can connect with other users with the same permissions.

Do you have just a single Exchange server?

I have two.  But...  I can connect to mailboxes on either one, just not the ones with the different email format.  Also I can point to either one in the address and it will connect those parkcounty.local users.

so the people with the parkcountysherriff.net email addresses are the ones that cannot connect to OWA, even though their mailbox is stored on the same Exchange server as everyone else?

By any chance were these accounts migrated from another windows domain?

Correct on both.  I upgraded from 2000 to 2007.  But all accounts were migrated.

I would check the event logs on your Exchange servers, as well the IIS logs.  Most like the IIS logs will give you the most direct explanation, but sometimes they're kinda tricky to decipher, so that's why I suggest looking at the system/application logs first.

You also should consider running the Exchange Best Practices Analyzer to make sure all the settings in your system are correct.  I generally use this tool to find major issues--I don't always follow every single little suggestion they have.  It's helpful because it can easily find major issues like missing global address lists or registry entries.

Not really seeing anything that stick out.

In the IIS logs, are you seeing the failed attempts by parkcountysherriff.net people to login to OWA?

Im not sure i they are failed but I am seeing them.

2009-04-09 16:52:36 192.168.0.182 GET /owa/ - 443 - 72.175.44.202 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+InfoPath.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) 401 2 5 46
2009-04-09 16:52:43 192.168.0.182 GET /owa/ - 443 - 72.175.44.202 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+InfoPath.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) 401 1 3221225584 15
2009-04-09 16:52:45 192.168.0.182 GET /owa/ - 443 - 72.175.44.202 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+InfoPath.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) 401 1 3221225584 31
2009-04-09 16:52:58 192.168.0.182 GET /owa/ - 443 - 72.175.44.202 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+InfoPath.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) 401 1 3221225584 78
2009-04-09 16:53:15 192.168.0.182 GET /owa/ - 443 - 72.175.44.202 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+InfoPath.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) 401 1 3221225581 31
2009-04-09 16:53:35 192.168.0.182 GET / - 443 - 72.175.44.202 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+InfoPath.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) 401 2 5 592
2009-04-09 16:53:59 192.168.0.182 GET / - 443 - 72.175.44.202 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+InfoPath.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) 401 1 3221225584 31
2009-04-09 16:54:29 192.168.0.182 GET / - 443 - 72.175.44.202 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+InfoPath.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) 401 1 3221225581 93
2009-04-09 16:54:43 192.168.0.182 GET / - 443 - 72.175.44.202 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+InfoPath.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) 401 1 3221225584 15

When you go into the properties for the domain user accounts that have the parkcountysherriff.net addresses, what does it list under the "account" tab on the left side of the "user logon name (pre-Windows 2000)" section?

pre windows 2000 name is the same as the user logon name.

No I mean what does it list on the left side (it will be grayed out).

Here is a screen
account.doc

Sorry I was in the EMC.

it says "parkcounty\"

And you've tried logging on to OWA using "parkcounty\username"  for the username field?

I think I got it.  The several that I had been testing were locked down to logging on to specific computers.  I found one that had all access and he works.  I will add our exchange servers on someone that does not work as see if that fixes it.

You definitely pointed me in the right direction.  If this works I'll award you points!!!!1

Thanks!!!!!

Ok that was it, but.....  I added my two exchange servers and no go.  I then added a DC still no go.  I then switched to all computers and it worked.  I really don't want to leave it this way any idea which computers he would have to have access to????

Thanks again for the time and help!!!!

I'm kinda confused as to what you did in the next-to-last post.  What do you mean when you say "locked down to logging on to specific computers"?

Under the account tab there is a button that says "Log on to.."  From here you can select the computers that the user have permissions to log on to.  Some users have all computers and these users could get onto OWA.  Some users had a specific list of computers that they can log on to.  Apparently there is a computer that the user needs to logon to to get to OWA.  I would have thought it would have been our exchange servers and maybe a DC, but this did not work.  

Thanks esmith for the help!!!  I found an article that sais you could put the domain name in and it would work.  However the article also stated that the field can only accept so many characters, which mine is greater than. I just can't believe there isn't a way to do this without enabling "all computers"

Anway thanks again for all the help!!!

Dylan