I have Sharepoint site published in Intranet. Most of the time I configure modules and site collection via http://myserver link. But some users have to use ip address: http://xxx.xxx.xxx.xxx
Users that access site via ip address observe strange behavior - children sites menus work inappropriate and some services looks misconfigured.
How can I solve this issue?
Thank you in advance!
How is the "myserver" DNS name configured ? Did you have an entry in the company DNS added or did you modify some host files ? In the second case, this explains the problem. You can either modify all host files (not recommended at all) or add a real DNS entry to the DNS server.
The strange behavior is typical of Alternate Access Mapping problems, but I advise to solve the first problem and the second will disappear.
Related
i would like configure website under port 80 in iis8.
i need to setup this without changing ipaddress and portnumber.
but it is showing following error message.
could you please help us to find the solution we are running out of time.
You can solve this one of two ways:
Stop the other website that is using the same IP and port
or
Add a host name to your website's binding that makes it unique from the other site(s).
In IIS, each site must have a unique combination of host name, IP address and port number.
There is always a default website on IIS.
Locate it on your left pan of IIS manager by clicking on sites, click on Default Web site and check your right pan, locate the manage website section and stop it.
Then add your website by right-clicking on site and add website, configure it and use default application pool
i'm running sharepoint 2010 foundation, on win7. since installing SP2010, none of my other localhost websites load in the browser. i'm either prompted for a login, or it just returns blank pages. i've tried putting my other websites within the SP-80 directory in iis7, which allowed the pages to load, but required a login. i tried various combinations of windows authentication on different iis7 directories, but nothing worked. i'm left with the impression that iis7 requires a single port 80 directory, rather than distinct, named directors, with separate permissions. the issue could be complicated by having my other sites mapped to a virtual directory, requiring my admin creds, to allow iis access to the files.
my question is, is it possible to host public, unprotected, port 80, web sites, along with SP2010? i'm not very experienced with IIS, so please forgive me if i'm overlooking the obvious.
sure it is possible. While creating WebApplications in SharePoint you're able to specify the port, the WebApplication will run on.
You should have a look at your Site Settings within IIS. SharePoint is by default not running on anonymous authentication mode.
Please analyze if you do have site collections created under Web Application using Powershell or from Central Admin
If you have Web Application created but no Site Collections, then you will get same issue
Sandeep
If you want other sites on IIS on the same port on the same machine, you'll need to declare IIS host headers. When you create a new Site in IIS, there is a bindings section (IIS 7.5 - in IIS6, I believe it's just called Host Headers) - set your bindings to be myotherwebsite.com or myotherwebsite.local. Make sure the names you use in your bindings match DNS names that are pointing to that machine, either through public DNS (if it's a public site) or through your local hosts file (\windows\system32\drivers\etc\hosts) if it's only for your local use.
Going the host headers route, you bypass the sharepoint execution stream completely - set your site up just as you would any other.
I am working under localhost.
In IIS Manager 7.5, windows server 2008.
After adding a new application in "Application pools", I added a new asp.net web application site using that application pool.
The problem is how can I run that website on localhost to check whether the site is working correctly or not?
People told me that I have to add bindings "domains" for that site and run the site using those domains. But that is not convenient as every time adding a new site on IIS, I need to have a domain to check the result?
I think it should be possible to run the site under localhost somehow but I dont know.
Any ideas?
Thanks in advance.
The simplest way is to add a virtual directory to your default web site within IIS. Point that virtual directory to the directory to which you installed/copied your website.
The you can either browse from IIS or type the virtual directory name (preceeded by localhost/) into your browser address bar.
If the problems is with "domains" yo do not have to buy domains. By asigning different port numbers on localhost you can add new bindings.
As I know adding binding is essential for IIS to understand which site should be opened.
For example you can assign port numbers like
80 -default- , 81,82 ... 8090...
I have two intranet website but they are as folders under default website so I would access as //server-internal/websitedirectory1/ adn //server-internal/websitedirectory2. Users don't like this. They want to access with some meaningful name like website1.intranet.com and website2.intranet.com. How can I achieve this? Thanks a lot.
You will have a problem if these two "sites" share session information. Test this by setting up two virtual folders.
You need to add multiple Web Sites in IIS and set them to respond to different Host headers (in Properties)
You'll also need to set up DNS.
Is there a way to setup subdomains udner Xp Pro IIS for something like test.localhost
Can it be done via IIS or the hosts file? Need to do a tets on a site that uses pathign back to the root so having the site ina virtual directory like localhost/test causes issues.
As you're probably well aware that out of the box IIS 5.1 only supports one web site. What you can do is use the adsutil.vbs tool to create a second site in IIS 5.1 and configure it to use that.
The following article explains the process:
IIS: Creating Multiple Web Sites within IIS on Windows 2000 and Windows XP Professional
There's even a GUI widget to make life easy:
http://www.firstserved.net/support/downloads
So in a nutshell:
Create a second site using one of
the methods above (set the IP
address to your machine's primary IP
address)
Add a host header for
test.localhost domain to the new
site
Edit the HOSTS and add an entry for
test.localhost pointing at the IP
address above
Easiest way is to just switch the document root of the lone site you already have to the different folder with the target site. Then you can switch it back when done.
If you are building stuff in virtual directories off the root, this shouldn't even effect any ongoing projects.
I seem to recall there was a tool which did this for you, but I've forgotten it's name and coordinates.
Create a new website in IIS. The host header value should be your subdomain like "sub.localhost", and then add the domain to your hosts file.
open with notepad the file c:\windows\system32\drivers\etc
and add this line:
127.0.0.1 mysuper-site.com.net.blabla
Then browse to this site: http://mysuper-site.com.net.blabla