August 30, 2008 01:15am pdt

Member Login

Hall of Fame

Yearly

1Robbie_L... 475,766
2tedbilly 444,395
3zephyr_hex 267,670
4liebrand 178,599
5cobrachen 170,815
6Pillalamarr... 128,090
7clayfox 121,425
8moss_guru 119,545
9NBSO_ISS 109,825
10cmv131 86,525
11DaleHarris 73,731
12adaco 72,330
13TechSoEasy 64,675
14rich_0794 63,150
15JamieMcA... 60,250
16ApexCo 58,135
17zell71 55,445
18whoajack 47,120
19bhanukir7 39,100
20Addihul 34,475
21furu 32,700
22tnorcross 27,350
23vivekthan... 22,800
24olca02 20,580
25gamesmei... 19,350

	[x] Attachment Details

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

Zone: MOSS-Sharepoint

Tags: sharepoint, login, domain

We are running sharepoint on our intranet for staff to use on a Windows 2003 server. There is no anonymous access, staff login in with their domain username and password which is carried over from their login.

Problem is, I have opened sharepoint (and outlook web access) up to outside through our website, so staff can use them from home. 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? Surely they both use Microsoft Integrated Authentication? It's the inconsitency that is confusing staff.

Furthermore, is there any way I can set Sharepoint or IIS up so that this is the default domain? at the moment, if a user doesn't put the domain in before their usrname, the auth box returns with "www.sitename.ext\<username>"....would it be possible to change something in IIS so this values before the slash said "<domain>"?

Thanks in advance

George

Start your free trial to view this solution

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.2

Question Stats

Zone: Networking

Question Asked By: rgford

Solution Provided By: TechSoEasy

Participating Experts: 3

Solution Grade: A

Translate:

Loading Advertisement...

Open Discussion

Comment by TTAsupport

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.

Comment by TTAsupport

The above may be a bit misleading, so let me rephrase that it sets them up as 2 different IIS VIRTUAL or PHYSICAL servers. By doing Virtual you can have both sites under port 80 on the same machine.

20080723-EE-VQP-34