Tag Info

Hot answers tagged

6

1) Because the Microsoft SharePoint Foundation Web Application service is running on your App Layer. Go to Central Admin -> Manage services on server, select your App server, then stop this service. 2) DNS entries are the way to target a WFE for end user access. End users will only go to the WFE DNS is pointed at (or if DNS is pointed at a VIP, to the ...


4

As a Best Practice, you never want to reference your SharePoint installation using the machine name so you are on the right track. Add "portal.mysp.test" to your DNS Add "portal.mysp.test" as the name of your Default or Intranet zone in SharePoint You might need to also add "portal.mysp.test" as a host header to your SharePoint web application in IIS. ...


3

This is a difficult topic to describe in words only. I recommend you take a look at this link which I think does a great job of illustrating how to manage host headers, alt access mappings, and even ssl if applicable. ...


2

The first thing you will need to do is configure an Internal URL in your Alternate Access Mappings for http://rootsite in the zone used by http://sharepointrootsite so that SharePoint knows what to respond to. You might also need to manually add http://rootsite to the host headers in the IIS on the farm hosting http://SharePointrootsite. Those two changes ...


2

Without knowing more information about your environment, then it is hard to give you exact advice. You should not just go in and start making changes to DNS unless you are authorized to do so within your company's environment. And since you do not know how to install/find the DNS MMC snap-in, I am going to bet that is probably not something you have ever ...


2

What you describe is actually the recommended way to change a web application's URL. http://technet.microsoft.com/en-us/library/cc262366(v=office.15).aspx Essentially, the process is to go to CA, remove the site from IIS (you can safely leave the IIS site to preserve your web.config changes) then re-extend to the default zone.


1

Unfortunately that's one of the limitations of Office 365 SharePoint Online. You neither have access to IIS settings nor can you deploy a server-side component to redirect to another page with an HTTP 301 or 302.


1

This is big risk, SharePoint always upset from these kind of activities as per my experience.are you going to change the domain name as well or not? in theory if nothing going to change all the accounts and DNS remain same, you will be ok. I would recommend to stop the SharePoint during this process so no corruption happen and also Please take the backup of ...


1

If anyone ever has the same problem, I found a solution to this: instead of hardcoding the wreply parameter, I first access the SharePoint site + "/_forms/default.aspx" with a request that does not follow redirects and has the user agent set. The response has a Location header that I get and which contains a wreply parameter. Only the left part (in the Uri ...


1

You will find it easier if you setup DNS entries for your web application urls. This will help if you need to change servers in the future etc. That way they will be set automatically (in future, set your host header value while creating the web application). You can still modify this now. First create a DNS entry (for example myintranet.contoso.com) which ...


1

After reading that IE automatically puts a URL into the internet zone when it includes a period (.), which forces the browser to ask for credentials, I created a new DNS record - a Host (A host this time), with name 'portaldev' pointing to my IP 12.3.4.567. I added the new binding to IIS and in Alternate Access Mappings added an internal URL pointing to the ...


1

Add a binding to the iis and modify the alternate access mapping in the ca for the webapplication. hope that helps?


1

For the most part, John is correct. However, if you have some hardware handling your DNS, such as an F5 box, it is possible to create rules there that will route requests to one farm or another based on the site URL being requested. For example, a rule could be created that would route all //intranet.domain.com/sites/SiteA to 2013 while requests to ...


1

Are you sure that the port 800 has been whitelisted in your firewall on your Windows Server ? You could also run netstat on the server and make sure that the port 800 is not internally used by something else, preventing thus a proper use for the web application. Regarding your AAM is > http://svr:800 an internal url (and thus added as so ?) ...


1

Turns out the barracuda web filter was the issue. You need to add a static route in it to make it talk http traffic across two domains. I hate that thing. It causes so many issues and has so many limitations.


1

Yes before you try to access http://hostA.abc.com through anything but the object model you have to add the DNS entry (or modify the hosts file) Creating the site only changed the IIS site for the WebApplication to listen to any request on port 80 not caught by any other IIS site, but for the traffic to reach this server you have to set up DNS.


1

Might be a long shot. But can you create a Alternate Access Map for http://plymouthrock:4321 and http://coleshill:4321 and then try accessing the new URLs after you have created a DNS Entry on your DC. http://coleshill:4321 I pressume is on the ColesHill Server , which should be able to browse to the site from itself if you create a Local Host Entry within ...


1

Javascript might be disabled Try adding example.com to your trusted sites in IE to allow javascript to run on pages within example.com



Only top voted, non community-wiki answers of a minimum length are eligible