Last post Jan 27, 2008 05:53 PM by firstname.lastname@example.org
Jan 22, 2008 10:21 AM|romkol|LINK
I have Windows Server 2003 R2 Enterprise and 4 asp.net apps
now i can access them by
How can I configure iis to use different dns names to apps for example:
PS: I'm using apps only for local intranet
Jan 22, 2008 10:30 AM|noahb|LINK
If this is only for intranet access, you can edit the Hosts file (c:\windows\system32\drivers\etc\hosts (i think that's the location on your standard win box)) on the machines to reflect the ip -- you could change it so that
http://www.microsoft.com points to
http://192.168.1.1 (be careful, this would also stop people from visiting ms's website -- that's not nice, maybe you're better off using youtube.com as a side affect you'll increase productivity ;)
I terms of the subdirectories I would have to do some research -- I don't know off hand how to accomplish that.
Jan 22, 2008 10:34 AM|romkol|LINK
and what about port - it's not by default = 8080 ?
Jan 22, 2008 10:41 AM|mjnorman|LINK
If you already have DNS set up, whoever handles that would need to set up a DNS name for you. Or if you are a fairly small organization, you can use the host file solution cited above. For the domain name mapping, here are the instructions from Microsoft
for IIS 6, should be roughly the same for 2003 Server. In your case, the Host Header in the wizard would be "example1.com", "example2.com", etc.
Jan 23, 2008 10:50 PMemail@example.com|LINK
You can't directly. In IIS, if you use a non-standard port it has to be specified on the URL. You need to use URL Rewriting to do this, either in ASP.NET or through an ISAPI filter such as ISAPIRewrite.
See the forums at www.iis.net for full information.
Jan 23, 2008 11:28 PM|mjnorman|LINK
Never tried it, but why can't you have a default.aspx page set up on the port 80 website (example1.com), that does a simple response.transfer to the other site with port 8080. It will show up in the address bar on redirect, but you could hide it with isapi_rewrite
like you suggested.
Jan 27, 2008 05:53 PMfirstname.lastname@example.org|LINK
Never tried it, but why can't you have a default.aspx page set up on the port 80 website (example1.com), that does a simple response.transfer to the other site with port 8080.
Then you need an IP address for each site, or you need to manage a port 80 site with host headers that points to a port 8080 site. If you could do either, there would be no need for the non-standard port to begin with.