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

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.
rsnellmanIT ManagerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rsnellmanIT ManagerAuthor Commented:
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
rsnellmanIT ManagerAuthor Commented:
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
rsnellmanIT ManagerAuthor Commented:
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
Ted BouskillSenior Software DeveloperCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rsnellmanIT ManagerAuthor Commented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.