OWA requires domain\login?

[JBruyet]

Hey all,

I have an E2k server that was moved to new hardware. It works great except for one issue--if someone tries to login using OWA they are required to enter the DOMAIN and their login name. We didn't need that for the previous server. How can I tweak my current E2k server so it only needs the login name and password? My finance manager especially would like to not have to include the domain name when he logs in.

Thanks in advance,

Joe Brouillette

 

[JBruyet]

So there's no way to have OWA automatically assume the domain when someone logs in to check their e-mail?

Thanks,

Joe Brouillette

 

[Davetoo]

If the users are on the same domain as the Exchange server, then they don't have to enter their domain, even if it asks for it.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[JBruyet]

Hi Lander215,

Let me explain a little more. When my users are logging in to OWA it's over the internet. When they get the login window they used to be able to put their name in the Login Name field and their password in the Password field and login. Now, when they login over the internet, they have to enter their login name in the following format: DomainName\LoginName. If they enter their login name without the domain name they can't login to OWA. No error messages, no explanations of what the problem is, the login window just keeps popping up. Any more ideas?

Thanks,

Joe Brouillette

 

[Davetoo]

And this just started happening out of the blue?

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[N0ktar]

Open IIS that handles OWA, in the properties of your Exchange folder click on Directory Security, than Access and Authentication Control. Check Basic Authentication, uncheck Integrated Windows Authentication.
Just make sure you understand, Basic Authentication means clear text over the Internet so pretty much any sniffer could easily log your passwords. I would suggest implementing SSL, than you can go with Basic Auth since the information exchange is encrypted by the socket layer.

 

[JBruyet]

Hi N0ktar,

Nope, that didn't do it. OWA still requires someone logging in to enter DomainName\LoginName in order to log onto the server. Any other ideas?

Lander215, this started happening after we moved our Exchange data over to the new server. I don't know enough about Exchange to fix it, and I don't want to pay $105 just to have the tech walk through the door to take a look at it. Although if the General Manager says it's starting to bother him I'll have to do that.

Thanks for the replies,

Joe Brouillette

 

[JBruyet]

And N0ktar, I tried it with the domain name in the domain box (Edit Basic Authentication) and without the domain name in the domain box.

Thanks,

Joe Brouillette

 

[bulkmail]

In ESM, go to the smtp virtual server. Go to properties,delviery, and advanced. Set the masquerade domain.

 

[blarsen2003]

I was just trying to figure that out... I got some help on Experts Exchange site...

Open IIS Manager
Expand Default Web Site
Right-Click on Exchange and select Properties
Select the Directory Security tab.
Both Basic and Integrated authentication should be checked (unless the server is a Front-end. In that case only Basic is checked)
Click on Authentication.... Edit button
Default Domain... Select Button
Select your Domain
Select OK, OK, and OK.
This should allow your users to just type in their username. You should not have to restart the IIS Admin or W3Svc.

 

[blarsen2003]

I don't suppose anyone has an easy solution to adding forms authentication to OWA 2000... I've seen a bunch on 2003 OWA, but none on 2000. I would like to avoid having users choose "remember login" on the Windows Login form...and have users opening other "dumber users" emails

 

[JBruyet]

I had a tech come in to fix it, and there was an issue with a shared folder that didn't exist. Exchange is now running smoothly internally and externally. Thanks for the help.

Joe

 

[ovenegas]

JBruyet did the tech tell you what folder it was. I am having the same problem with my OWA. Thanks

 

[JBruyet]

Varay,

My problem had something to do with a free/busy folder that never was created. He created it and then everything started working. I don't remember anything specific about the folder he created. I just checked my work order/invoice and all it mentioned was the missing free/busy folder.

HTH

Joe