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.
Related
its my first time using this and as a newbie I have many questions. Any help are appreciated.
My ultimate goal is to have reports created from database that will be able to be accessed by other end users on website so they can view/filter the report data online in a shared way with some user control settings.
So I have already made my reports in the visual studio linking to databases.
And I have also set up the Reporting Service Configuration Manager so that I can access SSRS home page and the site setting at http://'127.0.0.1'/Reports/Pages/Folder.aspx
Now my question is, how will the other end users be able to get onto the website and get access to the reports I created with SSRS? Do I upload the reports in .rdl on my report site manually or do I deploy it from VS? How do I turn my '127.0.0.1/Reports' into a public site for other user's access? Or do I have to create it using a sharepoint?
Thanks so much, I need a guidance to head toward the right direction! :)
Now my question is, how will the other end users be able to get onto the website and get access to the reports I created with SSRS?
Users will need 2 things from you to access the site: the server name/address, and a means of authenticating to it. By default, authentication is handle via Windows domain auth (which you can change, with varying degrees of effort...).
Do I upload the reports in .rdl on my report site manually or do I deploy it from VS?
It actually makes no difference in the end; do whichever you find easier. (There are also plenty of other ways to deploy reports, such as through powershell!)
How do I turn my '127.0.0.1/Reports' into a public site for other user's access?
Well you're halfway there - At this point, you could probably open up your firewall (port 80, maybe 443 depending on your config), and have people connect to your computer via IP or hostname - for example, if your computer's IP was 12.34.56.78, they could visit 12.34.56.78/Reports/ and access the site. If you have a means of creating a URL and pointing it to your SSRS server, you might need to open the configuration manager again and bind that URL to SSRS.
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 will be using one hosting account with several domains parked on it along with a main domain name. I need to be able to show different content based on what domain is being accessed. So, my question is, how can I test this locally?
I have Vista
I use XAMPP
Any help with this would be greatly appreciated?
You can define multiple domains in your hosts file.
you can find it C:\Windows\System32\drivers\etc
There are examples written there to help you understand, how it works. then create a page lets say index.php and parse the domain there and redirect it to relevant domain.
I have a couple of applications/sites running on different ports on my IIS server. I need to publish pages that are common between these sites. What is the easiest way to do this?
I can't redirect.
You can create a virtual directory in all your sites that share the same folder.
when you change the page on the "base" folder, it will reflect on all the sites.
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.