When we log in to the Sharepoint site, we must enter domain\username. Is there a way to bypass entering the domain name?

The domain is where your username is stored. Without pointing it there it has no idea who you are. Another way would be to login locally with an administrator account.

Yes. If you're using intergrated authentication you probably need to add your sharepoint URL to your browser's local intranet list. That wayyou won'tbe prompted for your credentials.If you're using basic authentication you can set the default domain in IIS.

The only way I can get this to work is to make the Sharepoint server a member server of my domain. Then import thedomain user objectsinto the "add users" feature of Sharepoint. Make sure the windows integrated authentication is set in IIS. The users only have to login once with their domain credentials (assuming they login to the domain everyday) andcheck the "remember password" checkbox.

I do not think the question is entering the login information. The question is how to avoid entering the domain in addition to the username while you are logging in... If I am not mistaken IIS 6.0 has a default domain name setting, but please verify...

>If I am not mistaken IIS 6.0 has a default domain name setting, but please verify.. This is *incorrect* for SharePoint sites. There the server name is always assumed as the "domain". So writing in only username would work fine if username is a local user on the server where the SharePoint system is running but not otherwise. Instead of bothering about needing to write domain name in addition to username, the problem should be avoided altogether by a) making sure that the site is in the Intranet Security Zone for IE 6 / 7 and that the default value of "automatic login only in the Intranet zone" is still selected. OR b) if the site isn't in the Intranet, by specifying for the IE Security zone that it is in that Login is "automatic login using current name and password". (Both these quotes are from memory but the texts are in essence correct) Mike Walsh

Mike Walsh MVP wrote: >If I am not mistaken IIS 6.0 has a default domain name setting, but please verify.. This is *incorrect* for SharePoint sites. Are you sure Mike? I have a WSS3 site setup for a single domain. It's setup on one IIS site with intergrated authentication only for internal access, so users aren't prompted for credentials at all there. But I also have this same sharepoint site mapped with alternate access mappings to a second IIS website, with basic authentication only. For this site I have specified the default domain in IIS, and users only need to enter their username, and do not need to prefix it with the domain. I can understand the behaviour you describe if basic and intergrated authentication were enabled on the same IIS website.

I'd better confess that my experience of this has been with internal sites (WSS 2.0 in fact) that have (thus) not been using AAM. I don't see why that kind of WSS 3.0 sites shouldn't work in the same way. Then it is logical that you are accessing servername or the nnn.nnn.nnn.nnn equivalent of that and thus when you go to such an address the servername is what is assumed when you write just a username. I haven't experience of basic authorization coupled with AAM and so have no problems in accepting that things are different then. I'd better change my 'always the servername' to 'usually the servername' Mike Walsh

Trying to add to the previous post ... When you authenticate yourself in Windows (to anything) there are three elements - Name, Password and Domain. Typically only the first two boxes are available for entry and "Domain" is there but already has either no value or a specific value. If you need to over-ride that domain value you need to right a new "domain" value which you do in the Name box by writing the "domain" then a backslash and then the username. If you have logged in to your client as a Domain user, then the Domain location is filled with the domain you logged in as. Hence if that was how you logged in to your PC when you access a SharePoint site that is also in that domain (and for which domain users (some or all) have been given access rights) and enter (if forced to) your name then that domain is assumed. If however that server is in a different domain to the one you have logged into (and you for example either been given a username in the SharePoint server itself or a username in the domain where the SharePoint server is located), then your assumed domain (the login to the client PC domain) is the wrong one and it needs to be overwritten. In the above two cases that means that you need to login as a) server'sdomain\username_in_that_domain b) servername\username_in that_server Now suppose you haven't logged into your PC as a domain user. This would be typically for two reasons a) (in a company) you don't want to be restricted in what you can do on your PC by company policies for domain users b) your PC isn't in a domain (it's at home maybe). In this case the hidden Domain box is empty and so when you now access a SharePoint site and write username it assumes what is the default value of the site which is servername. In such a case you can access the site by only writing username if you have been given rights to access the site as a local user on the server itself but otherwise you need to prefix username with domainname\ it order to over-ride the "domain" servername and replace it with the correct domain name. Does that just add to the confusion, or does it help ? Mike Walsh

In addition to what Mike said, it really depends upon your situation. If users are logging in from a computer that is in the same domain as the SharePoint server, then you can use Integrated Windows Authentication. In this scenario, make sure that this option is selected in the IIS website your SharePoint site is running on, as well as in IE for the user's computer. However, if the SharePoint site is an extranet (available outside the company network), then this will likely not work for users trying to access the site from their home computer, which brings us to the 2nd scenario.The way we've done this is to configure ONLY Basic Authentication in the IIS site and then add the domain to the Default domain text box. This works fine, but unfortunately sends a user's credentials in clear text. To prevent this, we used a self-signed SSL cert to keep traffic encrypted even though its using Basic Authentication.Of course you may want to experiment with using both Integrated Windows and Basic Authentication and possibly get a mixture of both behaviors. Mike may be able to answer that scenario better than myself.Ross

Ross Cosner said: Thank you! This solved my problem of users having to enter a domain prefix signing on to SharePoint from the outside. Now they can just enter their username.

> Instead of bothering about needing to write domain name in addition to username, the problem should be avoided altogether by [...] I disagree. 1. Some users sharing one desktop client need to login with a different user on the same machine. So this problem can't be avoided altogether. 2. Non IE-browsers like Firefox or Iron get it right by assuming the user belongs to the same domain the browsers host is in (I guess), no further configuration needed. We use integrated authentication and only IE8 is bothering users with requiring domain prefixes.

Just wanted to add my thoughts on this based on recent work on MOSS: While sending credentials in clear text for basic authentication is generally considered OK where SSL is enforced, another option is to use HTML forms authentication with an ISA server sat in front of the Web tier. If you delegate basic authentication from the ISA server, there is no need for user to enter "domain\username" when logging in.Benjamin Athawes Twitter: @benjaminathawes Blog: http://mossblogger.blogspot.com Mail: mail at bathawes.com