Solved

HELP!!! HELP!!!  My users cannot access their SharePoint documents!

Posted on 2012-03-29
5
1,156 Views
Last Modified: 2012-04-09
I guess I need to make Alternate Access Mappings for my new SharePoint Foundation 2010 server.  I recently migrated the content from WSS 3.0 and now I am getting random user access issues, like could access documents now they cannot.  

The old WSS 3.0 use to users use to access it via the IP rather than the servername.

So, my question is how do I create extra AAM for my new SharePoint that include the IP and another AAM that includes the FQDN?

I have navigated to "Central Administration/Configure Alternate Access Mappings".

Do I want to add additional Internal URLs that include the IP and another that includes the FQDN?

Currently, I have two Internal URLs:

http://servername:14589
http://servername

One is for the Central Administration and one is for the Sites, correct?


Any suggestions?

Thanks in advance.
0
Comment
Question by:rsnellman
  • 4
5 Comments
 

Author Comment

by:rsnellman
ID: 37781903
Also, reason I believe it is due to the Alternate Access Mappings is I am seeing several of these warning logs under my Application Logs of the new SharePoint Foundation server.

Event ID: 8059
Source: SharePoint Foundation
Level: Warning


Alternate access mappings have not been configured.  Users or services are accessing the site http://servername with the URL http://servername.domain.com.  This may cause incorrect links to be stored or returned to users. If this is expect, add the URL http://servername.domain.com as an AAM response URL.
0
 

Author Comment

by:rsnellman
ID: 37781950
Also all the Zones are Default.  Everything I have dug around for on the Internet mentions using the "Edit Public URLs" and select "Intranet" for the zone.

I am not sure, but all I want is it to work like before when the WSS 3.0 utilized the server IP.  I believe that would solve all my headaches at this time.
0
 

Author Comment

by:rsnellman
ID: 37781979
Oh, lastly, why does the AAM window display the following:

Internal URL                                         Zone                         Public URL for Zone
http://servername                               Default                        http://servername
http://server IP                                    Default                        http://servername
http://servername.domain.com          Default                        http://servername


Why is the Public URL for Zone unchanged when I add the extra Internal URLs?

Thanks in advance.
0
 
LVL 51

Accepted Solution

by:
tedbilly earned 500 total points
ID: 37789931
Did you install SharePoint or did someone else?  Using the server name isn't a good choice for accessing SharePoint because if you have to upgrade the server or move SharePoint to a new server, the changed name will cause problems.

OK, first off using an IP isn't the right solution and using the server name will cause problems in the long term, however, if you installed using the server name then you cannot eliminate it completely or you will run into other problems.

The best way to fix this is to create an internal FQDN like share point.mydomain.com (or whatever you choose)  You can then add that name as a host name in IIS then reconfigure AAM to use the new FQDN as the Public URL.
0
 

Author Comment

by:rsnellman
ID: 37795835
Yes, I was the one who installed/setup SharePoint.  Of course, with no training, so I am not surprised it isn't setup with Best Practices in mind.

So, if I was to choose like intranet.mydomain.com that could work?  Also, how do I go about performing these steps you mentioned in IIS?

Also, I am planning to add a third-party SSL cert to it soon.

Lastly, how will this effect my users accessing their documents?  I mean currently, I have added the IP address & the URLs they are using to the AAM and (knock on wood) everything seems to working fine now.

However, I want to future proof the setup now rather than deal with the issues down the road.


Thanks again.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Join & Write a Comment

When it comes to showing a 404 error page to your visitors, you do not want that generic page to show, and you especially do not want your hosting provider’s ad error page to show either. In this article, I will show you how to enable the custom 40…
Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now