I have setup Sharepoint Services on one of our servers, and it is working, and can be accessed from outside our building using the domain name we registered for it, i.e. share.domain.org. However, from inside our building where the server is located, it cannot be accessed in any way. We have tried the internal IP, 192.168.1.6, the internal URL http://servername.domain.local,and every other way possible. It always comes up with a "HTTP 400 Bad Request" and "Web page cannot be found". I believe I have entered the proper info in the Sharepoint Central Admin page under "Alternate Access Mappings.

I have been on the phone with various support people we use, who have a high degree of expertise (but not necessarily on Sharepoint), and no one has been able to solve this problem. From the server itself I can ping the site using IP #s or the internal domain name, so it looks like the DNS settings are OK. Just can't bring up the default site itself.

Any advice here would be very appreciated!

Richard

Richard,

You will need to post some more information regarding your configuration of AAM. You could take a look at the following series of blogs that explain how AAM is setup as this may help you solve your problem.

http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx

Andrew

Thanks for the article, but unfortunately I could not understand it completely, and was not sure how to apply it to my situation. I'm a newcomer to this. But here is how my AAM is currently setup:

http://servername:36003...............default............http://servername:36003

http://share.domain.org ...............Internet...........http://share.domain.org

http://share.domain.local..............Intranet...........http://share.domain.local

http://192.168.1.6 .......................Intranet...........http://192.168.1.6

Where servername is the name of the server, and domain our public domain name. And note that this Sharepoint site IS accessable from outside via the internet.

I am pretty sure some if this is wrong, so any help in correcting these settings will probably solve my problem.

Thanks!

Have you added http://share.domain.local as a host header entry in IIS for the web application?

Andrew

Yes. I have the default IPhost header as "share.domain.org" and

a second entry for the IP address 192.168.1.6with the host header value of "share.domain.local"

A quick update: I was just able, for the first time, to access our Sharepoint site internally. I used the URL: http://share.domain.org/default.aspx, and the Sharepoint home page came up. Finally! However, not all the links function properly. For instance I can click on the Calendar link and view the calendar, but many of the other links, i.e. to Tasks, and others, return a "Web page not found" page. What can I do to ensure that all the links within the Sharepoint site work?

Thanks.

Rohisa, - some progress

SharePoint will (if configured correctly) return the correct URL for any generated links.

It's probably worth reviewing how you added the AAM entries?

Did you add the entries using the 'Add Internal URLs' option? or did you use 'Edit Public URLs'?

You need to do the former, if not delete the entry and create using the 'Add Internal URLs' option.

Andrew

Thanks, I tried that, but it did not change anything. What's odd is that I can succesfully go to any link that has a complete URL. i.e. that it directly calls a page, such as: http://share.domain.local/Lists/Calendar/calendar.aspx, which includes the name of the target file, calendar.aspx. However, some links, like for Tasks, are like this: http://share.ppmhv.local/Lists/Taskswith no specific page called with an .aspx suffix.

Might this be caused by some things still needing to be setup within Sharepoint?

An update to my last post: Turns out some URLs that DO include a page.aspx also do not work. I still think my AAMs are not right. Here is what they are, can someone please comment on whether this looks right or not?

Internal URL Zone Public URL for Zone

http://terminalserver:36003 Defaulthttp://terminalserver:36003
http://terminalserver Default http://terminalserver
http://share.ppmhv.local Intranethttp://192.168.1.6
http://192.168.1.6 Intranet http://192.168.1.6
http://share.ppmhv.org Internethttp://share.ppmhv.org

Note: terminalserver is the name of this computer.

Rohidas,

What looks correct to me from this

http://share.ppmhv.org Internethttp://share.ppmhv.org

Which you confirm works.

What is key here is thr Public URL for the Zone, this is the one that will be provided for when accessed.

I suggest you remove the two Intranet entries and then use the Add Internal URL and put http://share.ppmhv.local (assuming this is what you use to connect internally).

This will create an entry

http://share.ppmhv.local Intranet http://share.ppmhv.local

I assume that intially your application was created using the port number hence the http://terminalserver:36003 entry, your could also remove the additional entry for the default zone.

One other question, have you added any of these by using the Extend an Existing web application (possible for the http://share.ppmhv.org)?

Andrew

Andrew,

Your advice worked like a charm! I can now access all the parts of the Sharepoint site. Thanks so much!

One question, you suggested removing the additional entry of http://terminalserver. Before seeing your answer, I had already removed the one that had the port# 36003 on it. Was that the right one to remove? I haven't tested the site from outside the building here yet, but just want to make sure I didn't delete something I shouldn't have.

Thanks again.

Richard

Richard,

Glad your sorted

On the http://terminalserver removal I had assumed that this was added after the initial site creation as SharePoint gives nice port numbers by default like 36003. Assuming you have manually updated the IIS web site to work on port 80 then you shoud be fine.

Best advise, just test the URLs you need and if it's working you're good to go

Andrew