Sharepoint login is domain\username, but not in OWA. possible to set default domain when logging in?

Sorry, I really don't understand what you're trying to explain

We do not run sharepoint Portal Server, we run STS 2.0.

When users log in, through the website, the link to OWA just points them to http://mail.xxx.co.uk/exchange. They then log in normally with their AD username and Password

My question stated:

"With outlook web access, staff just login with their username and password...but with sharepoint, they have to put "<domain>\username". Until recently I thought that there would no way round this, but am confused as to why OWA doesn't need the domain and sharepoint does?"

I need the Sharepoint login to either not require or automatically place the "<domain>\" before the name

>>I need the Sharepoint login to either not require or automatically place the "<domain>\" before the name


I am fairly certain that this is not possible.

ok thanks, I will apply for a refund

note to any other experts: If you know of any way I can avoid having to put the "domain\" before the username on a sharepoint login, please can you advise

thanks

rgford,

Users shouldn't have to use <domain>\user to log into WSS.  On the directory security tab in IIS for your companyweb page, make sure that Anonymous Access isn't checked, and then just check Integrated Windows Authentication.

That should be all you need.

Jeff
TechSoEasy

Hi Jeff

There is no anon access here. Integrated Windows Authentication is the default, and what were using. However, my problem is when logging in from outside, this happens because the domain isn't automatically inserted. i.e. INSIDE our networkk, the login box is populated with "DOMAIN\John" for example....but form outside, that information isn't known. If the user doesn't insert the domain, then the login box returns with "www.xx.co.uk\john" and asks for the password again. I want to find where that www.xx.co.uk comes from and change it so the default is the domain....or solve it another way?

IT shouldn't insert the domain --- I just tested a remote sharepoint site and only used my login name (without domain), and it worked fine... give me a few minutes to check out why.

Jeff
TechSoEasy

rgford,

Check to make sure that the permissions of all appropriate folders haven't been changed.  There is a complete listing of those here:  http://support.microsoft.com/kb/812614

Because the condition you are talking about (having to use the domain name) would indicate that a folder or file doesn't have the correct permissions assigned.  Because this behaviour is not normal (that's what my third grade teacher used to say about ME -- finally, I get to say it about someone/thing else!).

Jeff
TechSoEasy

Hi Jeff

Give this a try by all means: https://cds.rgford.co.uk (our remote sharepoint install)...try any login name, press OK and see what is returned

Meanwhile I will look through the KB article above, thanks

George

I think this has to do with not having a separate AD OU for Sharepoint... while I don't have a lot of experience in this area because I generally work with WSS in a Small Business Server environment, I have tested a few of these things in my lab environment.

You may want to review: http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsc05.mspx which will show you how to alter this behavior.

Jeff
TechSoEasy

Jeff

That article, although interesting, doesn't seem to directly solve this problem. It is for Sharepoint installations where uses can be created who aren't registered in Active Directory.

Thanks anyway

ah -HA! And I also need to DISABLE Integrated windows authentication - just found that out!

What is now slighlty annoying is that previously, staff logins were "carried over" into Sharepoint, as I used a GPO to put the address of the SP server in "trusted sites". Now, it's asking everyoen for a password every time they load up the intranet (sharepoint)

Is there any way I can make use of both authentication methods?

The solution is to extend the existing sharepoint site to another instance in the central administration page.

This sets up the same site on 2 different IIS servers, but still sets them up as applications under sharepoint.

Give one your outside headers and the other one special internal headers.

So the outside would be www.webpage.com and webpage.com on port 80 with basic authentication and use the SSL certificate.
The inside would be www.webpageinternal.com and webpageinternal.com on port 80 with integrated authentication.

Then through local DNS point webpage.com's A record to webpageinternal.  So for both internal and external access they go to webpage.com but internally it is redirected to webpageinternal.  They never see the difference.