What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Sharepoint 2007 Alternate Access Mappings

Sharepoint 2007 Alternate Access Mappings — Mon, 19 Mar 2007 11:50:36 GMT

PingBack from http://www.decatec.it/blogs/2007/03/19/Sharepoint+2007+Alternate+Access+Mappings.aspx

SharePoint Alternate Access Mappings

Aaron Robertson-Hodder's SharePoint and Office 2007 Blog — Mon, 19 Mar 2007 13:13:55 GMT

I came across the second part of Troy Starr's Trilogy on Alternate Access Mappings in SharePoint 2007.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

MikeWal2 — Mon, 19 Mar 2007 15:49:00 GMT

Perfect timing. What about VMs?

I have a VM at servername DEV1

I need to access it via DEV1.VMLab.companyname.com

(same for the Central Admin site only add :nnnnn)

So I first added these two addresses to my list of Trusted Sites and *amended* the two default settings from http://DEV1 to http://DEV1.VMLab.companyname.com

Should I have amended the settings or added new ones alongside them. (I tried that and it didn't seem to work as well).

Now the only minor snag I have is that

DEV1.VMLab.companyname.com will go to http://DEV1.VMLab.companyname.com/default.aspx

but

DEV1.VMLab.companyname.com:nnnnn goes nowhere.

(However http://DEV1.VMLab.companyname.com:nnnnn works fine after converting to DEV1.VMLab.companyname.com:nnnnn/default.aspx.)

Any comments ?

Mike Walsh

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

David McKenzie — Mon, 19 Mar 2007 18:40:59 GMT

Thanks for this post Troy.

Oddly enough we started having some (previously) very confusing issues after implimenting a DNS alias last week.

"Alternate Access Mappings" sounds "optional" but really isn't.

Great post.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Troy Starr [MSFT] — Tue, 20 Mar 2007 12:17:20 GMT

Hi Mike -

You can amend or add, it's up to you. Amending means that they will now be the only URLs that SharePoint offically recognizes. Adding additional public URLs means that SharePoint will recognize them as well.

For the http://dev1.vmlab.companyname.com:nnnnn URL, is it defined as a public URL and associated with the correct web application? If you're browsing to it and not getting anywhere, you can use a net sniffing tool such as Fiddler to see what URL SharePoint is trying to send you to via its HTTP 302 redirect response.

- Troy Starr

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

MikeWal2 — Wed, 21 Mar 2007 13:33:23 GMT

Thanks for reading adnd responding Troy.

I can actually access http://dev1.vmlab.companyname.com:nnnnn">http://dev1.vmlab.companyname.com:nnnnn OK.

The odd thing is that here my browser insists on the preceding http:// otherwise it doesn't recognize the URL at all

With http://dev1.vmlab.companyname.com there is no such problem - i.e. I can write dev1.vmlab.companyname.com and its OK.

I suspect this has nothing to do with alternate access mappings though :)

What I now have is

a) replaced the default as above

plus

b) [as custom] http://dev1 and http://dev1:nnnnn

so I can access the site as dev1 when I'm on the server. At least that's the theory.

Mike

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Troy Starr [MSFT] — Thu, 22 Mar 2007 01:20:30 GMT

Hi Mike -

Ah, yes, if you have port numbers in your URL, then you need to preface the hostname with "//" at minimum in your browser address bar before it'll go find the address you're looking for. That's just the browser's behavior, not SharePoint. :-)

- Troy Starr

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Martin Edelius — Fri, 23 Mar 2007 17:47:22 GMT

Great post, it sure clears up a couple of question marks I have had lingering above my head about AAM.

Thanks!

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

JamesLiang — Fri, 30 Mar 2007 01:59:33 GMT

Thanks your post. but I still have problem. Because our site include port number, user input URL like http://server4:1234, now I create a alternet access mapping like abc.com but I still need input http://abc.com:1234. can you tell me what happen?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Troy Starr [MSFT] — Sat, 31 Mar 2007 08:05:53 GMT

Hi James -

This might be covered under mistake #4. Are you using a reverse proxy server that can perform port translation or are users directly accessing your SharePoint server? If they're directly accessing the SharePoint server, then your AAM URL will need to use the same port number as your IIS binding. So your options there would be:

1. Have users type in http://abc.com:1234">http://abc.com:1234.

2. Extend your web application into an additional zone with an IIS binding on port 80. This would allow you to type in http://abc.com.

- Troy Starr

Anonymous Access not working with AAM

oneill3 — Tue, 03 Apr 2007 11:37:22 GMT

Wondering if anyone can help me?

I setup a basic sharepoint site, with everything on the same box.

I can get the anonymous access to work if I connect to web server using the server's name in the URL (e.g http://server_name), however, when I try to connect to the server using the alias (e.g. http://alias) it logs me onto the site with my windows username and password.

I had this running on a Virtual server no problems however now that I set it up on its own server it doesn't work.

If checked all of the settings and the anonymous stuff is all turned on. I've tried to use the AAM, but no luck there.

Is there someone else I can look?

Does anyone have any suggestions?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

mlt — Wed, 04 Apr 2007 03:49:45 GMT

Can you provide more information on recommended best practices for the following: We have a Web application that has been extended to use forms authentication. So, one web site uses windows authentication for authoring, the other uses forms authentication and is accesbile via the Internet. We need to add SSL capabilities to the forms auth site. We would like our public url to be the same for http and https (example: http://www.contoso.com and https://www.contoso.com). Can you provide specific guidance on this. Thanks.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

mlt — Wed, 04 Apr 2007 03:53:36 GMT

One more thing about the question I posed above. We need to be able to maintain session state when the user switches between http and https!!

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

David Mielcarek — Wed, 04 Apr 2007 23:58:30 GMT

I noticed you mentioned that 'localhost' will not work if AAM is not set-up to handle this reference.

I looked a test install of sharepoint I have been playing with and there are no AAM's for 'localhost', however, I was able to get to the Central Admin by doing http://localhost:[port] and it opened up.

Thoughts?

Dave

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Troy Starr [MSFT] — Sun, 08 Apr 2007 22:29:40 GMT

Hi folks -

oneill3: What does your AAM table look like? Was the http://alias URL added as a public URL or an internal URL? If it was added as a public URL, did you extend the web application into a new zone for it and then did you configure the authentication provider of that zone to enable anonymous access? Also, what resource is requiring authentication? You could use a tool such as Fiddler for IE to findo out.

mlt: You would need to have each URL (HTTP and SSL) be a public URL in its own zone, so you would need to extend the web application into 2 additional zones for forms authentication. I don't know if you'd be able to maintain session state, though.

Dave: SharePoint will give it its "best effort" to figure out which web application and zone you're trying to reach when you browse to an URL that isn't in AAM and redirect you appropriately. Sometimes it works, sometimes not. That best effort shouldn't be considered reliable and doesn't work at all if you're in a pure object model/API scenario rather than a web browsing scenario.

- Troy Starr

Anonymous Access not working with AAM

oneill3 — Tue, 10 Apr 2007 04:26:02 GMT

Hi Troy,

thanks for the reply. I added the alias as an internal URL. The authentication I am refering to is when you open IE and browse to the Sharepoint site it automatically logs in you with your windows username. The site I have configured is an internal site, however, the site needs to have anonymous access turned on. When I use an alias on the anonymous site, sharepoint automatically logs you in. If I connect to the site using the server name, not using an alias, the anonymous works fine. Any suggestions?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Troy Starr [MSFT] — Wed, 11 Apr 2007 20:36:08 GMT

Hi oneill3 -

See my earlier reply, re: using Fiddler to see which resource is issuing the HTTP 401 response, which is causing the authentication.

- Troy Starr

How does this affect web service calls from "within" Share Point?

jonas — Thu, 12 Apr 2007 01:53:45 GMT

Hi Troy,

Thanks for some great info!!

I have a question how AAM affects in particular the Data View Web part calling web services (SoapPTAdapter).

We have had a lot of "problems" with the DVWP and WSS3/MOSS. The scenario is as follows:

We have a web site NOT extended by Share Point where we host a web service. We configure a DVWP to call this external web service. The DVWP will NOT use NTLM to call the WS???

(Looking at the IISLog reveals this)

A workaround is to add the external URL (the one to the site NOT extended by Share point) to AAM of the Web Application where the DVWP resides...???

And suddenly the calls from the DVWP will use NTLM to authenticate to the web service.

This is VERY strange to me, can you please tell me how the DVWP or the SoapPTAdapter

is affected by AAM.

Thanks in advance!

/Jonas

Undesired http to https redirect

dulay — Fri, 13 Apr 2007 16:48:22 GMT

Hello Troy,

I'm having a very strange behavior and I can't pinpoint the cause. I have a web application with two zones. The default zone is configured with one url using https and websso for authentication. The intranet zone is configured w/ a different url using http and NTLM authentication (for the crawler).

The strange behavior is when i access the intranet zone through our load balancer, my 302 redirect location header to the welcome page specifies https even though i accessed the site using http. If I go through the load balancer straight to the welcome page, my response remains http. What's strange about the 302 response is that even though the location header is https, the url in the body of the response is http.

If i bypass the load balancer and go straight to one of the web front ends by updating my hosts file, I get the desired behavior. I'm redirected to the welcome page over http.

I know. I know. You're going to say it's the load balancer, but we've spent a couple days troubleshooting this from both ends w/ no obvious cause. Any ideas?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Jonas — Sat, 14 Apr 2007 00:30:17 GMT

Hi,

I have sent an email before asking about how AAM affects the SoapPTAdapter.

I have now traced down the issue to the call to SPSite.ValidateDomainCompatibility.

Thanks

/Jonas Nilsson

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Troy Starr [MSFT] — Sun, 15 Apr 2007 22:54:40 GMT

Hi folks -

Jonas: Glad to see you were able to find out the cause. :-)

Dulay: My guess is that the URL of the web request being passed from the load balancer to the SharePoint server either:

1. Doesn't match any of the URLs in AAM, so it tries to fall back to the Default zone's public URL.

2. Does match one of the URLs assigned to the Default zone in AAM, so it's using the Default zone's public URL.

I recommend using a network sniffing tool to make sure that the protocol scheme, HTTP HOST header, and TCP destination port of the request that is received by SharePoint from the load balancer matches an URL assigned to the Intranet zone.

- Troy Starr

AAM and WebServices

Jonas — Tue, 17 Apr 2007 17:40:48 GMT

Hi Troy,

I found the cause but I don't want to belive I can't call web services accross Web Applications ;)

To remove our web service from the equation I tried the following and it returned the same error:

1) Create a DataFormWeb part using SharePoint Designer and put it on web application http://server:80

Consume data from the Lists.asmx Web Service that resides on Web Application http://server:85

WSS won't allow this, if I look in the WSS log file I se entries like this:

http://server/_vti_bin/webpartpages.asmx and http://server:85/_vti_bin/lists.asmx are not in the same web application. Their domains cannot be compatible.

I belive this is logged from SPSite.ValidateDomainCompatibility. That is being called by the SoapPTAdapter internally.

Can you verify that I'm not supposed to be able to call across Web Applications by design.

Is there some setting that I can change to allow this?

Thanks in advance

/Jonas Nilsson

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

BobC — Wed, 18 Apr 2007 22:19:40 GMT

Consider the following and let me know if I'm approaching this correctly.

Goal: One url for internal users NTLM access, same url for external FBA users. So, when you are inside you use https://mystuff.myco.com and get a standard windows login. Same url for external users connecting from the outside should get an FBA prompt.

We have unique ip addresses for the internal and external, but we are having trouble with AAM.

Any ideas are appreciated.

What every SharePoint administrator needs to know about Alternate Access Mappings (Part 3 of 3)

Microsoft SharePoint Products and Technologies Team Blog — Thu, 19 Apr 2007 03:14:54 GMT

In Part 1 of my blog series on Alternate Access Mappings, I gave a brief introduction to the feature

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Troy Starr [MSFT] — Fri, 27 Apr 2007 04:57:11 GMT

Hi folks -

Jonas: The SPSite.ValidateDomainCompatibility exists to help prevent cross-site scripting attacks. So, if it's blocking you, then it's probably doing so intentionally. :-) I'm not aware of a way to turn it off.

Bob: This is similar to how one must configure Search to crawl host-named site collections that are not using NTLM authentication (http://technet2.microsoft.com/windowsserver/WSS/en/library/378c4673-0814-4255-a79c-7c4b6a4732a51033.mspx). It's not really something we recommend unless you have to (and with Search, you have to because it cannot authenticate using forms authentication).

- Troy Starr

How to configure Alternate Access Mappings (AAM) successfully

Duray Akar's Blog — Sat, 28 Apr 2007 00:51:05 GMT

To avoid many questions and simplify troubleshooting, I would suggest this order when configuring AAM,

Host Multiple Domain based web sites in WSS 3.0

Amit.Nuke — Wed, 02 May 2007 23:09:42 GMT

I have a server with wss 3.0 installed and configured. I have to deploy 3 domain name based sites on wss.

For ex http://www.site1.com

http://www.site2.com

http://www.site3.com

Each site would have its own content database.

How do i achieve this?

AAM and web services (again ;)

Jonas — Wed, 02 May 2007 23:51:48 GMT

Roy,

Thanks for answering!

First: It might seem off topic to ask all these questions about DataViews and Web Services in comments to your post about AAM. But all my debugging points in the direction AAM and changes made deep in the OM related to AAM. So please bear with me ;)

"Jonas: The SPSite.ValidateDomainCompatibility exists to help prevent cross-site scripting attacks. So, if it's blocking you, then it's probably doing so intentionally. :-) I'm not aware of a way to turn it off."

I still can't really buy this. Why would you try to prevent "cross site scription" deep inside the OM?

I have another scenario that exposes the same behavior:

First: All this works if I use Kerberos authentication, I only have these issues using NTLM.

1) Create a DataFormWebPart calling the OTB Lists.asmx web service on the same Web Application.

(

Page is http://server/default.aspx">http://server/default.aspx

Web Service : http://server/_vti_bin/Lists.asmx">http://server/_vti_bin/Lists.asmx

)

2) Add a new external URL to AAM for http://server (http://portal.comapny.com)

3) Access this application using a external name "http://portal.company.com

I will get an error from the DataFormWebPart.

4) Access the page using http://server/default.aspx">http://server/default.aspx (Everything works)

To get it up and running I have to EXTEND the

Web application. Adding the url to AAM is not enough.

Any thoughts on this?

Thanks in advance!

/Jonas Nilsson

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Victor — Thu, 24 May 2007 23:06:07 GMT

Hi Troy,

Thank you so much for the articles - very well done!

I am wondering if you could advise direction to resolve the issue:

1. I created AAMs as discribed in Part 1.

2. It looks like it works - when I access a library, all links inside the library are translated from the internal to the external URLs.

3. The issue - when I try to check-in/check-out a Word file to the library it displays/uses still the Internal (!!!) URL that cannot be resolved on the Internet.

4. Everything is simplified - default WebSite Collection and simplest library.

5. ISA 2006 used as a firewall, proxy server

6. The problem appears - no matter if the link translation is enabled or disabled on the ISA 2006.

7. I noticed that some other people also has absolutely the same problem.

Please advise - thank you so much!

Sincerely,

Victor.

What every SharePoint and EPM administrator needs to know about Alternate Access Mappings

Christophe Fiessinger's Blog — Thu, 07 Jun 2007 23:50:36 GMT

Useful links if you need to configure reverse proxy for instance: ¾ http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx

I'm Indexing and I only get errors...

Joel Oleson's SharePoint Land — Thu, 14 Jun 2007 23:47:15 GMT

Got this message from a user responding to a comment they saw in a previous post... http://blogs.msdn.com/joelo/archive/2006/11/16/upgrading-from-wss-3-0-b2tr-to-rtm.aspx

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Ryan — Wed, 27 Jun 2007 18:19:46 GMT

So, am i reading this correctly in saying that you can not have http://site1.domain.com in both the internal and Internet zones, where DNS plays the main key in directing the user to the correct zone?

I have customers that do not want 2 URLs when working on a site, then telling their internet customers a different url to access.

All you need to know about Alternate Access Mappings (AAM)

Mirrored Blogs — Fri, 17 Aug 2007 23:04:46 GMT

Troy Starr of the WSS Test Team has written an excellent 3-part article detailing AAM. The details can

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Elio — Fri, 24 Aug 2007 11:42:56 GMT

Hi Troy (sorry by my english, I'm still learning).

I have my application working properly in the default zone (http://internalurl.com). When I extend my web application to the internet I can't access to it , because I have an URL for internet (http://internalurl.internet.es), but (we're not using ISA server) the reverse proxy uses internal IP's to redirect the request and not internal URL's so, I don't have another internal URL to redirect the request and doesn't work with IP's, could you give me any ideas??

Thanks :-)

Všetko o Alternate Access Mappings (AAM)

Cvalik's blog — Sat, 15 Sep 2007 12:25:05 GMT

Troy Starr napisal velmi pekny 3-dielny serial o AAMČasť 1Časť 2Časť 3

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

carol — Fri, 05 Oct 2007 10:27:33 GMT

Hi Troy,

I need some help...we have an application working properly when we accessing from intranet. In this case we use this url "http://server.domain/sites/LibraryName/default.aspx".

But when we try to access from internet it doesn't works properly.

To access from internet we use "http://externalURL" then this URL is translated for "https://externalURL2:port" and users have to login this page. Then they entry into sharepoint docs library correctly using this url "https://externalURL2:port/http/server.domain/sites/LibraryName/default.aspx" and here users can navigate. But when you try to select one document, it tries to find it in "https://server.domain/http/server.domain/sites/LibraryName/DocumentName", the first part of the URL (externalURL2:port) is tranlated by the server.domain?¿?And obviously, a message notifying the document was not found appeared...

We have defined the ExternalURL in AAM as internet zone and the externalURL2:port as extranet. I understand this is a wrong config but I don't be sure what I should use...Please, any help will be welcome...

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Aitor Wehrli — Mon, 08 Oct 2007 19:13:34 GMT

Hi Troy & Carol,

Did you get any solution for your last issue? .I have a similar problem and I would be pleased if you could tell me any news.

Please contact me at aweh4538@hotmail.com.

Thansk a lot.

Aitor

Troubleshooting WSS Search - EventID 2424 & 2436

Mirrored Blogs — Tue, 20 Nov 2007 02:57:32 GMT

Corpo: Olá pessoal, Bom, este é um artigo muito interessante ... basicamente por tratar de alguns detalhes

re: Load Balanced URL and AAM

Gary — Tue, 04 Dec 2007 01:56:55 GMT

Hi Troy,

You may have already answered this one, so my apologies in advance.I have 2 webservers behind a citrix load balancer (netscaler). I also have an application server and a sql database server. After creating the web application and a load balanced url "portal.domain.com" and creating my site collection everything appears to be normal at first glance. I can connect to http://portal.domain.com/ without any issues. Intermittently Moss appears to redirect some requests using the port number I specified and IE with throw cannot display page errors. After digging around it appears that MOSS intermittently tries to append the specified port 11080 within the URL for some links. Not sure why? If I go to site settings the site url listed is http://portal.domain.com:11080/. If I try to connect to this url I receive a cannot display page error. Port 11080 is the port that is configured between the web servers and the load balancer. The VIP on the load balancer was confgured to render any http request using the standard port 80.

Any help would be greatly appreciated.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Eddie V — Wed, 05 Dec 2007 17:56:33 GMT

Hello Troy

I have implemented AAM and i can access our intranet internally using http://intranet and publicly using http://intranet.endvizionz.com, but the mysite seems to have some issues. it was working ,but then it stopped. Another thing i noticed is that our http://intranet will hang in the afternoon and become unresponsive internally but not externally. Should, i extend my web apps?

URL mapping

Ramz — Fri, 18 Jan 2008 12:41:40 GMT

Hi Troy,

Thats a good one!!!

I have a question.. What if i want to modify my subsites and pages. For e.g. my url has http://server/pages/page1.aspx which i need to change to http://server/page1.aspx. How should i go about doing it. Please help as i am terribly stuck :(

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Zino — Mon, 21 Jan 2008 07:25:33 GMT

I have an internet website that I want our employees to be able to access it from anywhere... using the same url http://intranet.mycompany.com regardless where they are. If they access it from outside the domain using http://intranet.mycompany.com it would change the url to httpS://intranet.mycompany.com, and accessing it from inside the domain, it should not use ssl.

Any idea how to configure my aam, isa and dns to do that?

What is SharePoint in Testers View and What are the Functionalities

Gracy — Fri, 25 Jan 2008 09:17:18 GMT

What is SharePoint in Testers View and What are the Functionalities?

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

Val — Wed, 06 Feb 2008 22:52:45 GMT

Great article! Being a newbie to Sharepoint, I used it when the loadbalancer came into play and set up my site flawlessly.

One question though, my site has SSRS 2005 reports and in the default zone, they render fine but not in the internet zone. Is this possible to do with Reporting Services 2005 and MOSS 2007? Is there a hotfix or work around?

Thank you!

Microsoft SharePoint Products and Technologies Team Blog : What every SharePoint administrator needs to know about Alternate Access Mappings

SharePoint Thinks, Links and Clinks — Wed, 09 Apr 2008 16:14:48 GMT

A series of three posts regarding configuring and understanding one of the top reasons that SharePoint

MOSS Form Based Authentications

Man On The Way — Wed, 21 May 2008 07:35:42 GMT

MOSS Form Based Authentications Part 1 - http://msdn2.microsoft.com/en-us/library/bb975136.aspx Part 2 - http://msdn2.microsoft.com/en-us/library/bb975135.aspx Part 3 - http://msdn2.microsoft.com/en-us/library/bb977430.aspx MOSS Alternate Access Mappings

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

prakask — Mon, 09 Jun 2008 14:44:06 GMT

need to give alias to my web application. for eg

I have created an iis website on teaf server with port number 23465

So if I need to access that website we will type http://servername:portnumber (i.e) http://teaf:23465

But my requirement is I need to access site with url http://epsdashboard insteaed of http://teaf:23465

Help on this regard is highly appreciated.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

yhd — Thu, 12 Jun 2008 22:38:38 GMT

I didn't use reverse proxy server. With http://Sharepoint in the default Zone, I added Http://www.axy.com to the Internet Zone. Is it enough?

In our intranet, why some computers couldn't access Http://www.axy.com?

Thanks.

re: What every SharePoint administrator needs to know about Alternate Access Mappings (Part 2 of 3)

AJ79 — Thu, 26 Jun 2008 15:36:24 GMT

does anyone have any ideas on the below warning we are getting in event viewer:

The start address <sts3://server/contentdbid={f9f16a37-b9fc-4f59-a2ea-a9e2a369f712}> cannot be crawled.

Context: Application 'Search index file on the search server', Catalog 'Search'

Details:

Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (0x80041205)

Understanding extranet setup for MOSS 2007

SharePoint — Wed, 04 Mar 2009 20:08:34 GMT

Links: Design extranet farm topology (Office SharePoint Server) Downloadable book: Planning an Extranet

Useful Sharepoint Links

a blog or 2 — Tue, 16 Jun 2009 17:46:10 GMT

Useful Links · MOSS Video Demos (Total 14 Modules) · Before You Begin with SharePoint Server 2007 · MOSS

web tasarım

web tasarım — Sun, 09 Aug 2009 18:12:32 GMT

super thank you http://www.parcakontorbayiniz.com mıracle.