Erreichbarkeit einer Sharepoint-Sitecollection
Allgemeine Diskussion
Alle Antworten
-
Hallo,
lies Dir mal bitte den folgenden Artikel durch: SharePoint publishing concepts and considerations
Once this is set this way, we tell AAM to treat that bogus URL as the internal URL, and then UAG takes care of the rest. One thing that’s unique about this situation is that the IIS running the SharePoint server needs to KNOW about this, and this is not always automatic. This is referred to here (http://technet.microsoft.com/en-us/library/cc261814(office.12).aspx) as mistake 4. If you EXTEND the web application in SharePoint and use the bogus hostname, this should be fine, as the extension process configures IIS correctly. Sometimes, though, you don’t need to extend the application, and that may not work.
This is also discussed here: http://technet.microsoft.com/en-us/library/cc298636(office.12).aspx
If the process has not been done correctly, the symptoms would typically be a 400 error – “bad request”, coming from the SharePoint IIS. IIS issues that error because it receives a request for the bogus hostname (fakeinside, in our example above) which it does not recognize, as none of the host-headers on any of its sites has been configured with it. Ideally, the appropriate action would be to extend the SharePoint application using the bogus hostname. Alternatively, you could also add it to IIS manually, using the following steps:
1. On the server running SharePoint Products and Technologies, open the IIS manager
2. Click on Sites
3. Locate and click on the site that corresponds to the SharePoint site that you intend to publish via UAG. For example: “SharePoint – 80”.
4. In the Actions pane, click Bindings.
*Note the binding settings for the port used by the site. For example: 80
5. Click on the site binding, and click Add
6. Set the bindings’ Type, Post and IP Address to be identical to what you noted in step 4. The settings will not conflict, because the new binding will have a host header that the other one does not.
7. In the host name box, type the FQDN host name that you assigned as the Replacement host header in the Farm host name setting. For example: “fakeinside”
8. Click OK
9. Click Close
10. Exit the IIS Manager.
Und auch Troubleshooting Alternate Access Mappings in SharePoint
Gruss,
Alex
-
Hallo,
wenn das Problem besteht, mm eine mögliche Lösung zu diesem zu finden, müssen wir einen privaten Kommunikationskanal mit Dir erstellen. Dieser nutzt auch um zusätzliche Informationen zu sammeln.
Kannst Du bitte eine e-Mail an dieser E-Mail-Adresse mit Deinem Namen, Deiner e-Mail-Adresse und Telefonnummer senden, damit wir Dich erreichen zu können?
Danke und Grüße,
Alex
