We have Windows 2008R2 dedicated server which is pointing a domain. Let us say domain name "TestDomain" under that as given in Image "Default Web Sites" having many application those can be acessed by www.TestDomain.com/appA,www.TestDomain.com/appB,etc. Now I need to create submain something like "www.franchise.TestDomain.com". I could configure the same as given in image but I have configured subdomain with Port Number 80. Will it be a problem if we have "Default Web Site" and "Franchise" running on same port number?
You can run all the sites you want under the same port, as long as the hostname (in your case testdomain.com and franchise.testdomain.com) varies.
So the answer is yes, you can do that without any problems.
Related
I have a network setup containing two machines.
On one machine I have a site hosted with IIS.
I have added an entry in the HOSTS file pointing my local IP to this domain
10.42.12.105 to - www.mysite.come. Then I configured to accept incoming calls on TCP Port 80. By going to windows firewall with advance security
Inbound Rules -> Action -> New Rule, select "Predefined" and then select the last item - World Wide Web Services(Http) and allow the connection. Also allowed port 80 too.
I can access the site with www.mysite.com with no problem on the same machine.
what I would like to do is be able to view this site from my other machine on the same network.
Can anyone see where I'm going wrong?
A host file is a way to tell 1 machine to map a web address to an IP address, like an alias. It only works on the machine containing the HOSTS file. For example, I could add a line in my hosts file which could map your URL www.mysite.com to 127.0.0.1. My browser would think your site is on my PC now.
So, if you want to set up this alias/name-mapping for multiple machines, you will need to add a host entry, on each machine (so they all have this mapping), or add this mapping to your local DNS (on your domain controller or router).
To check your firewall rules and IIS config, try having your test PC go to the IP address instead of the alias (from HOSTS).
We are having a situation where we have to create use the site with different ports
1) 80 goes to site -xyz
2) 1443 goes to some other site - abc.zyx which uses same root folder.
SO we have added 1443 to iis server bindings along with a new private ip. This site as of now uses same root folder as the root site with port as 80.
Now the privateip:port is not coming up. Need to view the same site with port 1443.
Kindly help
Thanks
Vivek
Im not exactly sure what you are asking but you can create two separate sites in IIS to look at the same root folder as long as they have different host names.
The same can be said about ports. You can add multiple ports in the sites bindings as long as they are actually different ports.
Just make sure all ports are open on the firewalls. You should be OK.
I have an MVC4 web application
In setting it up on IIS7.5 I added the application to the "Default Website" and set up a virtual directory under http://localhost/myApplication
However, this forced me to change many of my controller calls (specifically js ajax calls) which I previously called in Cassini like "/Home/Index", I now had to change them to "/myApplication/Home/Index" for them to work on my local IIS.
NOW, when I publish it to a remote hosting server I have to change it BACK to "/Home/Index" for it to work.
This cannot be the most productive way to traverse the development -> testing -> production cycle.. What step am I missing?
I tried to create the applications virtual directory on on just http://localhost/ without appending the application name so that I can call "/Home/Index" at all three stages but it complains that http://localhost/ is already mapped to inetpub/wwwroot.
Thanks for your time.
The steps are like this:
Publish your website to a new folder in inetpub/wwwroot (or the place where your applications are kept) like "inetpub/wwwroot/myapp"
Go to IIS management, create a new web-site, assign it any free port (like 11001 or something, > 1024 at least) and point it to a folder from the step 1. Bind it to all IP addresses available or to 127.0.0.1
Start the web-site.
Access it using http://localhost:11001/ (or any other port you've set)
Problem is that by default any browser uses port 80 to request a web page, and that port is taken by the default web-site. You have to manually override it or create a site on another port. IIS usually warns you about port collisions.
If you don't want to have port number in the address, alternatively you can work with host header on port 80. You may have to make local host entry for the host header given to the site.
I've got 2 applications running on my local machine. One sharepoint and another IIS application:
localhost:43442
localhost:5080
I've installed ARR and need to configure it to run these 2 apps on a host and port but when adding a new server, it only accepts a server name rather than its port as well.
Any help?
For me, I needed to add a server to my server farm, called localhost. Clicking Advanced Settings... lets you specify the http and https ports. Set those to the ports that you would like your domain proxied to.
After that, create an inbound rule for URL Rewrite that matches the HTTP_HOST condition with a pattern of your website domain that the server is acting as a proxy for. Select Route to Server Farm for the action and select the specified server farm.
I added a new Inbound Rule and it worked :)
I'm runnning IIS 7 on my local dev machine. My website is up and running. To access the website, I need to enter the url with the port number in the browser's address bar (www.ScoobyDoo.dev:91). What do I need to change so I only need to enter the www.ScoobyDoo.dev portion of the url? I've done this before but I'm drawing a blank. Port 80 is hosting a different website so I can't just move this one to the default http port.
Thanks!
If you want multiple sites to reside on the same IP address then you need to use HTTP Host Headers.
Provided that your existing website doesn't use SSL then you can use host headers. To configure host headers in IIS7 you modify the "Bindings" (there's a menu item for this in the right hand side Actions pane for the site):
You want to add/edit your bindings for each site that resides on the same IP address, for example for your scoobydoo.dev site:
The caveat here is that if you have users already browsing your first site by IP address then they will need to be redirected to the site using its domain name.
You can do this by adding a site bound to the raw IP address and creating a HTTP Redirect.
I'm not sure what you're expecting to do here. If something else is binding to port 80, and your web server is binding to port 91, then you'll need to specify port 91 in the web browser when making a request to the server. By default, without being explicitly given a port in the address, a web browser will make the request on port 80 (or 443 for SSL).
You might be able to add an entry to your hosts file (c:\windows\system32\drivers\etc\hosts) where you map the non-specified port version to the specified port version, but I don't think it'll work. That file is for DNS resolution, not port mapping. Worth a try though, I suppose.
Can you clarify a bit on what exactly you're expecting? Or what you think you may have done before? I wonder if you're not giving us the whole picture here.