Freitag, 27. April 2012 17:38
I want to know if I set up a new Site correctly. I need to create a new site collection separate from our main web site. I did the following:
1. created a new web application, where I set the host header, name, and public url
2. created a new site collection, where I selected the web application in step #1. I set the title and in the url,
after "sites" I put in a site name.
3. I can see the site in IIS.
What I would like to do now is go to the site and create a couple of sub sites. I can't get to the site I created yet. Is that because the DNS entry for it needs to be created? I also thought I would be able to get to it from the SP server, but I can't.
Freitag, 27. April 2012 18:02
You are correct.
If yoiu give a web application a URL and host header, then it can be accessed using that URL, but the browser needs to be able to resolve the URL to an IP address. Add a DNS entry for it, or if you just want to test on the server, add it to the servers hosts file (windows/system32/drivers/etc/hosts). Open a Notepad as administrator and edit the file and add a line with your url and the servers ip or 127.0.0.1
Then, you should be ok, the procedure you described is the correct one. You shoulkd have two web applications with the last site collection in the latter web app.
- Als Antwort markiert mhoran Freitag, 27. April 2012 21:26
Freitag, 27. April 2012 18:05
From a diff station
How do you try to reach it?
You should use http:///sites/site_name/
Each time you create a web app you have an IP address + TCP_port
If TCP_Port = 80, isn't necesarry to use it
YOu can try to reach it using
If you can reach it by IP address but not using name , is a problem with DNS resolving - you shoul duse DNS or keep NETBIOS in your LAN
If you can't - is a problem with station's firewall filtering. Check FW config and check again
Romeo Donca, Orange Romania (MCSE, MCTS, CCNA) Please Mark As Answer if my post solves your problem or Vote As Helpful if the post has been helpful for you.
- Bearbeitet romeo donca Freitag, 27. April 2012 18:05
Freitag, 27. April 2012 18:22
Thanks Thomas. I meant to ask one other thing as well. When the Public URL is created in step #1(create web app), it retains the port number at the end ( ex, ":1234"). Is is okay if I remove that from the URL?
Freitag, 27. April 2012 18:46
That only works, at least for me, if I don't give it a public url.
Freitag, 27. April 2012 19:16
One main rule to remember:
If its not in the Alternate Access Mappings collection, you can't use it.
Any URL, IP address, Servername or any other name you want to use to access a web application(can actually be a site collection as well but thats a different story for a different time) has to be:
1.Resolvable, in DNS, In Hosts file, as servername or be the localhost or ip address.
2.Added to the Alternate Access Mappings.
3Added as a host header in the bindings of the web site in IIS (will be managed automatically but needs to be chacked/verified)
In your situation, a site collection can be:
Portnumber has to be referenced only and always if you're not using default port 80.
Freitag, 27. April 2012 19:20
Creating a web application correctly involves picking an app pool. Normally you want to re-use an exist application pool.
DNS needs to be updated for users to browse your site. Your host file is a local dns, so you can update that on your client and it should browse. Most users on windows computers dont have rights to update their host files, so you'll want it in your public DNS asap.
as a best practice, dont modify the host files of servers unless its absolutely necessary, dont disable the loopback unless its absolutely necessary, and dont browse sharepoint from the servers, you are not guaranteed to see the same behavior end users will. Always browse from a client.
Please mark my response as an answer if appropriate.
Freitag, 27. April 2012 21:25good advice. Thanks
Freitag, 27. April 2012 21:25thanks for the great advice.