I have created sharepoint application for internal use. But it is not accessed in network, but my sharepoint Central Administration site is accessed on network. Plz tell me what should i do?
There are so many things you can do to find out how this happened.
1. Can you access the application from the server itself?
..1). If not, check the IIS and SharePoint log file to see if the site is up.
..2). If yes, check your firewall configration, may it block your app's port or block your users
2. Your site has any site head? Have you have your DNS points to it?
3. Have you put your users into the site's member group?
4. Check your SharePoint server's windows event log, is there any error message in the Application catelog?
Anyway, you must first make sure the site is up and then make sure your end users can reach it.
Related
Hi all and sorry for the long title. I've had the management of a SharePoint 2010 farm environment tossed to me and while most things are working one thing is not. None of our users are able to connect to any of the sites in this farm with SharePoint Designer. They all get the dreaded "server could not complete the request" message followed by the eternally helpful MS error message "Object moved. Object moved to here."
I've dug around everywhere I can think to look and the closest explanation I see is that it may have something to do with our SP server hosting 5 SP applications, all with their own host headers. The things I find seem to suggest that Designer won't play with SP servers featuring multiple host headers...but I have to think that can't be the case. SharePoint encourages you to make use of host headers when setting up your applications.
I've tried installing Designer directly onto the server itself: no dice.
I've tried setting up the sites without a host header: sites don't work (and it wouldn't be a permanent fix because the user base this farm serves are barely computer literate so asking them to use IP addresses will be like Armageddon)
I've checked the farm settings to ensure that use of Designer is allowed: it is.
For this intranet instance, we do apparently have 5 separate IP addresses tracking to this box that will eventually host 5 SP applications (if that helps).
I'm a developer and not a server or network admin so any guidance or advice from anyone who's run into this and found a fix would be most welcome.
First of all update Sharepoint Designer and Sharepoint to the latest service pack and do an iisreset and use Sharepoint Designer 2010 for access Sharepoint 2010 Farm.
Enable anonymous authentication for the SharePoint web application in IIS.
See this KB2758431 for more details, this is for Sharepoint 2013 but I think is still valid for 2010.
Set the registry DisableLoopBackCheck entry
Check the ULS Log and Event Viewer for error messages.
Here a little explanation about IIS name resolutions of Sharepoint.
You have to check the DNS, the IIS host header (foreach web site) and settings from the client.
If there are an entry into DNS corresponding to an hostheader of web application you must use this name for accessing the sharepoint web site, try with the FQDN (i.e. if the entry in DNS is Server01 and you are on mydomain.lan you must use for connecting: http://server01.mydomain.lan), check also from your client a ping to the address to see if you reach the server.
If there are no entry into the DNS, add to your hosts file the hostheader of the corresponding sharepoint site and try (same thing as for the DNS, see above).
I have two different SharePoint sites on my server which are separated using host headers on IIS.
Everything seems to work fine but I cannot open my sites using SharePoint designer 2013 and it doesn't give any sensible error to work on.
I tried to connect on server as well as on my local machine and tried both domain and IP but nothing seems to work.
Any help would be appreciated.
Thanks,
you must enable sharepoint designer on the web application settings, in central administration.
then, make sure you are site collection admin and enable spd on site collection settings
if you are trying to connect locally, make sure you can resolve the server address. optionally create a hosts entry
My SharePoint setup is:
2 Web Front End servers, 1 of those WFE servers is also the application server then there is another server for my SQL database.
Server 2 which is the WFE and App Server combined is able to access all the site collections. Server 1 however can only access the root collection and is unable to access any other site collections I've created, Business Intelligence Centre for example.
To access the root collection I type in:
http://test1:100/ and I receive the Standard SharePoint team webpage.
If I alter the address to http://test2:100/ it opens up the same page without a problem.
When I navigate to http://test2:100/dept/bic/Pages/Default.aspx it opens with the BIC without a problem. As soon as I change the text from test2 to test1 then I get a 404 error. From what I've read I need to do some work in the Configure Alternate Access Mappings section under System Settings in Central Admin, however I'm lost at what I need to do in order for Server 1 to see this BIC site.
Here is an example of Server 2 accessing the home page, then the BIC
Now here is when I use Server 1 to access the home page, then the BIC
Any help is appreciated.
You're right about the alternate access mappings. Although some of the sites might respond like in your situation, SharePoint will only respond properly with an AAM configured for a given URL. In your case, when you have more than one web server, you need to use some kind of load balancer. You can look at using Windows Load Balancing services or you can work with your network team and use a hardware load balancer. Once you implement load balancing, you will create a new alternate access mapping with a new DNS name that will effectively point to both servers.
I have Sharepoint on the cloud and I can access it from anywhere, except home. At home I have a ClearOS and I can´t go through to my Sharepoint Portal.
I guess that I may need to open some ports, right? Whic ports?
Port 80. SharePoint runs as a normal website, unless you're trying to access Central Admin or using SharePoint Designer.
You shouldn't need to explicitly open port 80, especially if you can access other websites.
You should post more info about any errors you are getting.
Likely you need to have your Sharepoint site bypassed in the proxy server settings section. Sharepoint can use proprietary bits (ikr? Microsoft doing something proprietary?) that get borked when passing through the proxy or content filter.
If you list the site(s) in the Web Proxy module (bypass section at the bottom) it will create appropriate firewall rules that will skip over using the proxy and content filter for that site.
Cheers.
We have been running WSS 3.0 for our intranet. We are going to be moving our internet site to WSS 3.0. The vast majority of people will access the new internet site anonymously. My question is in regards to the few people who will need to authenticate so that they can access intranet material from the internet.
We are going to host the intranet and internet sites on the same server. WSS 3.0 has already been installed, updated, and configured for our intranet. What would be the best way to set up the internet site collection so that it can be accessed anonymously but also so that when a user authenticates they can access intranet content as well? Currently the only way to access the intranet is to be on the companies domain with credentials that have access to it. What we would like to do, if possible, is use the login form that is built into WSS to make access to intranet content available opposed to setting up a sub domain.
You may use SharePoint alternte mapping feature as described in this article.
Configuring Multiple Authentication Mechanisms with Alternate Access Mappings in Windows SharePoint Services 3.0
I'm assuming that your Internet site collection and intranet site collection are not the same site collection with what I'm about to write. I am assuming, however, that they are housed in the same web application. If that's the case (and I understand enough of the specifics), here's how you'd carry out what you're trying to do:
Establish a Web application to house your site collections. You've already taken care of this (since you have your site collections available to you internally). In setting up a Web application, it (by default) is exposed at a URL (or server:port) through the Default zone mapping. For our purposes here, we'll assume that this is the URL through which you want to access the site internally (on your Intranet).
In order to expose your site collections via the Internet, you're going to want to extend the Web Application housing them. This is done through Central Admininstration > Application Management > Create or Extend Web Application. In extending the Web Application, you're creating another IIS site with (ideally) a publicly-accessible URL that can be exposed to the Internet. You'll be asked to pick a zone as part of the process; given your needs, I'd go with "Internet."
At this point, the Internet zone (you just extended) is still setup to use Windows authentication and Active Directory as it's membership provider. Though you probably want to keep AD as a membership provider (based on what you've stated), you'll probably want to look at enabling Forms-Based Authentication (FBA) on your Internet zone. Microsoft has a video on that here: http://technet.microsoft.com/en-us/windowsserver/sharepoint/dd355701.aspx. Note: you won't want to use the SQL membership provider if you intend to continue using Active Directory accounts. Instead, you'll have to wire-in the Active Directory Membership Provider for FBA. Some info on that can be found here: http://blogs.msdn.com/solutions/archive/2007/08/27/forms-based-authentication-fba-in-wss-3-0-moss-2007.aspx.
At this point, your Default zone site should use NTLM and an intranet-available URL. Your Internet zone site should use FBA and have an Internet-available URL. You'll need to enable anonymous access on your public site collection for the Internet zone. This is done through a combination of Central Administration changes and changes from within the site collection itself (http://www.mindsharpblogs.com/ben/archive/2007/02/11/1557.aspx). Important point: when going into the site collection to enable anonymous access, be sure to go through the Internet URL; don't go through the default zone (i.e., the intranet zone).
With all of these things in-place and your site collections (or more specifically, the IIS site servicing the Internet zone Web application) wired-up to the outside world, you should be good to go.
I made a number of assumptions as I wrote this, so you may (obviously) need to adjust. Setting up anonymous access isn't overly hard, but there are a lot of steps to it. If you hit hiccups along the way, don't be afraid to search for answers. Many folks have done it successfully ... but more often than not, there are challenges along the way.
Good luck!
You can also create a web application for your intranet use, so user's who are in the domain get access through an internal URL authenticated, and then extend that web application for the extranet application for anonymous users....