I need the community's help on this.
We have TFS 2010 and SharePoint services installed on a server in our internal network and I can access it fine via servername/sites/DefaultCollection/.
We're trying to give access to external teams to the same site.
When we try to access publicIP/sites/DefaultCollection/
we get a 404 NOT FOUND error (publicIP points to the IP of the TFS server).
I noticed that in Team Foundation Server Administration Console in the [General] tab is says:
DefaultCollection URL: servername:8080/tfs/DefaultCollection/
While at the [SharePoint Site] tab under Default Site Location shows: servername/sites/DefaultCollection/.
When I try locally servername/tfs/DefaultCollection/ I get the same error (404 NOT FOUND).
So it seems like when we try to visit publicIP/sites/DefaultCollection/ it actually goes to publicIP/tfs/DefaultCollection/ without the address changing on the browser.
How can I make this work?
Any help will deeply appreciated.
Have you set up alternate access mappings in Sharepoint?
Go to Administrative Tools -> Sharepoint Central Administration.
Click on the "Operations" tab
In the "Global Configuration" section, select "Alternate access mappings"
Select "Edit Public URLs"
There you can add a new URL for the "Internet" site so that external users can access Sharepoint. Note that this URL may need to be a fully qualified domain name, not an IP address. (However I've never tested with an IP address.)
Related
I have deployed fresh SharePoint 2013 instance on VM. I am able to create Web-Application and Site-Collection successfully. I can even access my site, create folder, file through web browser.
However, I am not able to access REST APIs for the same site and getting below error. Please have a look on below snippet:
GET http://xx.xx.xx.xx/_api/web/lists
Getting error as "The Web application at http://xx.xx.xx.xx could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application."
Please suggest.
are you using with host name or IP?
if you are using hostname, you should add new entry in hosts file.
Structure:
IP Host Name
xxx.xxx.xxx.xxx contoso
http://support.sherweb.com/Faqs/Show/how-to-edit-the-hosts-file-windows
Or
You can modify alternate access mappings.
https://learn.microsoft.com/en-us/sharepoint/administration/configure-alternate-access-mappings
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
I am setting up web applications on a development box (which I have remote access to) and I am looking to set the domain name, since we currently have to use an IP address to access the sites.
The server is Windows 2003, so I am using IIS 6. What are the steps to configure this?
I have searched Google, but I am possibly searching on the wrong terms as I can't find anything with steps to configure it.
You can set the hostheader on the property pages of the website (Web Site tab, Advanced Button).
Look here
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.