you see a "hello world"...which is the default.htm,, its not the website in the folder /nitnoid, which is DNN 4.0.1 and has a default.aspx to kick off..
Using IIS Manager (Admin Tools), right click on your website, and select properties. Under the dcouments tabs, make sure default.aspx is in the list, and moved to the top. While you are there, click on the ASP.NET tab and make sure 2.0 is selected.
i still dont' have it working the way it should.....but
www.nitnoid.com does come up if I change the properties in the Default Web Site settings.
Home Directory has to be set to c:\websites\nitnoid and my DNN for nitnoid will come up.....
however this means I can't get any other DNN site to come up as well....another site I have loaded on this same IIS is
www.freeyardsale.com which has its own virtual diretory and its own folder under c:\websites
Does IIS on winXP support more than a single domain name?? -- its appears not!!????
DotNetNuke supports unlimited domain names using the portal alias.
You do not install DotNetNuke for every domain, all the domains should point to the same installation of DotNetNuke. It really sounds like your IIS configuration is messed up and needs some TLC.
There are a few thing that it helps to be clear on to get this all to work. There are different mechanisms available to have a user's request routed to a specific web site on your DNN and IIS system. Both IIS and DNN have their own mechansims, both work
quite well, and they work well together. However, if you are hosting multiple sites and multiple virtual directories it can get confusing.
When a reqest comes to IIS it can be distinguished by the combination of three factors:
IP address
Port number
Host name
The server versions of IIS let you create distinct Web Sites as long as each site is unambiguosly identified by these factors. For example, on Windows Server I can have four distinct web sites:
IP:10.1.2.3
IP: all unassigned. Port 80. Host name: MyWebA.com, MyWebB.com
IP: 10.1.2.4. Port 8080. Hostname: any
IP all unassigned. Port 80. Hostname: any
Site 1 will respond to all HTTP requests on its IP address (10.1.2.3)
Site 3 will respond to all site requests on its IP address and port number
Site 2 will accept any other requests. However, it will only respond to requests for the site names MyWebA.com and MyWebB.com
Site 4 will be the default bucket and catch any requests the others did not get.
IIS on Windows XP only allows one web site. However, it can have multiple virtual directories. This means that on XP you can't have the combination of IP/Port/Hostname route requests to a specific directory. Any valid combination of IP/Port/Hostname will
always get routed to the single Site. On XP you can only route requests to distinct Virtual directories by specifying an Alias or directory name. So, on XP you cannot have
www.MySiteA.com go to one virtual directory and
www.MyStieB.com go to a different virtual directory (that requires a server version of IIS or some extra software). On XP you can have wwwMySiteA.com go to one Virtual directory and
www.MySiteB.com/SiteB go to a different virtual directory because it has a distinct virtual directory alias on the second example.
So, on XP you have to distinguish your virtual directories by directory name. You get one default Root web directory, and then other requests are routed by the first driectory name. When setting up DNN you first need to make sure tht at least one IIS web
site will accpet its requests. On XP that means your default web site should probably be like #4 and accept all requests.
Now DNN has its own mechanism for routing requests. Typically, DNN is installed in a single virtual directory (and normally in the default root virtual directory). You set up the DNN virtual directory to accept all requests that match the IP/Port/Hostname
combinations you want to support. Typically you want DNN in a web site that is set up for something like IP all unassigned. Port 80. Hostname: any. This will catch any requests.
DNN then looks at the Hostname and port number in the requests to determine which of its Portals gets the request. It looks for an exact match. So,
www.MyWebA.com is different from MyWebA.com which is different from MyWebA.com:8080. For every Hostname (and port number) that you want DNN to handle, you must have a properly defined Alias set of for a Portal (under site
settings). Also, remember that if you want your Portal to respond by IP Address (http://10.1.2.3/) then you must register the IP address as an alias for the portal. DNN sees the IP address as another hostname.
If a request gets routed by IIS to your DNN install and DNN cannot find a matching Portal alias, DNN uses the default portal for your install which by default is the first portal that you installed. If your requests are being handled by the default portal
that means that
1.IIS is routing the requests to your DNN install
2.You probably don't have a Portal with the proper Hostname and Port number set up in DNN so DNN is passing the request to its default portal.
You can set up distinct DNN installs in separate virtual directories or web sites, but you don’t normally do this just to have two portals. If all you want is multiple portals, use a single install and use the
DNN portal alias mechanism. Sepearate DNN install and its extra complexity is mostly used for development, testing, or if you just want to keep two sites completely isolated, or if two sites could not share the same web.config (let’s say because one site required
a different membership provider than the another, or a user…).
You can setup virtual directories in IIS and make as many DDNs as you want, by installing the files as you did in c:\dotnentnuke. Then in each installation, just adjust the database settings in web.config. You can use separate SQL Server databases, or using
your exisiting database or by changing the objectQualifier in web.config. The objectQualifier prefixes your database and stored procedures with whatever value you use. Just don't modify it after installing DotNetNuke.
FYI, objectQualifiers are part of the DotNetNuke core. The real purpose of an objectQualifier is to separate the data in a shared SQL server environment where the user is given a single database, and does not have permissions to create additional databases.
The objectQualifier prefixes the tables to allow multiple DotNetNuke installations along with other SQL applications which is very common with many hosting providers.
If a module does not support objectQualifiers, it should not be called a DotNetNuke module, period.
dlykins
Participant
800 Points
160 Posts
Re: multiple portals on same IIS server
Dec 11, 2005 09:57 PM|LINK
I still have never beena ble ot get this to work....
i registered a domain name: www.nitnoid.com, that points to an IIS virual direction i named "nitnoid".
how come when I type www.nitnoid.com my website doesn't come up,,, when it works when I am on the server using : http://localhost/nitnoid
???
djbaldwin
Participant
1025 Points
205 Posts
Re: multiple portals on same IIS server
Dec 12, 2005 12:23 AM|LINK
Login as host to http://localhost/nitnoid
Under Admin|Site Settings at the bottom of the page, add a new portal alias called www.nitnoid.com
I hope this is of some help to you.
dlykins
Participant
800 Points
160 Posts
Re: multiple portals on same IIS server
Dec 12, 2005 01:13 AM|LINK
I did this earlier...it still doesn't work....
you see a "hello world"...which is the default.htm,, its not the website in the folder /nitnoid, which is DNN 4.0.1 and has a default.aspx to kick off..
help!
djbaldwin
Participant
1025 Points
205 Posts
Re: multiple portals on same IIS server
Dec 12, 2005 01:37 AM|LINK
Using IIS Manager (Admin Tools), right click on your website, and select properties. Under the dcouments tabs, make sure default.aspx is in the list, and moved to the top. While you are there, click on the ASP.NET tab and make sure 2.0 is selected.
I hope this fixes your troubles.
dlykins
Participant
800 Points
160 Posts
Re: multiple portals on same IIS server
Dec 12, 2005 01:44 AM|LINK
yes...they are all set properly..
asp.net is set to 2.050xxxx.
default.aspx is at the top..
i tried to attach screen shots..but can't...
In IIS should my nitnoid virtual directory be under the branch Default Web Site??
what else is there??
do you want to login to the portal and look at the alises yourself?
if so, lets take this off-line and i'll give you a userid......email me: dlykins@cinci.rr.com
or call: 513-722-4924 (cincinnati, oh)
dlykins
Participant
800 Points
160 Posts
Re: multiple portals on same IIS server
Dec 12, 2005 02:11 AM|LINK
i still dont' have it working the way it should.....but www.nitnoid.com does come up if I change the properties in the Default Web Site settings.
Home Directory has to be set to c:\websites\nitnoid and my DNN for nitnoid will come up.....
however this means I can't get any other DNN site to come up as well....another site I have loaded on this same IIS is www.freeyardsale.com which has its own virtual diretory and its own folder under c:\websites
Does IIS on winXP support more than a single domain name?? -- its appears not!!????
djbaldwin
Participant
1025 Points
205 Posts
Re: multiple portals on same IIS server
Dec 12, 2005 02:24 AM|LINK
DotNetNuke supports unlimited domain names using the portal alias.
You do not install DotNetNuke for every domain, all the domains should point to the same installation of DotNetNuke. It really sounds like your IIS configuration is messed up and needs some TLC.
EmperorWal
Participant
792 Points
166 Posts
Re: multiple portals on same IIS server
Dec 12, 2005 11:16 AM|LINK
There are a few thing that it helps to be clear on to get this all to work. There are different mechanisms available to have a user's request routed to a specific web site on your DNN and IIS system. Both IIS and DNN have their own mechansims, both work quite well, and they work well together. However, if you are hosting multiple sites and multiple virtual directories it can get confusing.
When a reqest comes to IIS it can be distinguished by the combination of three factors:
The server versions of IIS let you create distinct Web Sites as long as each site is unambiguosly identified by these factors. For example, on Windows Server I can have four distinct web sites:
Site 1 will respond to all HTTP requests on its IP address (10.1.2.3)
Site 3 will respond to all site requests on its IP address and port number
Site 2 will accept any other requests. However, it will only respond to requests for the site names MyWebA.com and MyWebB.com
Site 4 will be the default bucket and catch any requests the others did not get.
IIS on Windows XP only allows one web site. However, it can have multiple virtual directories. This means that on XP you can't have the combination of IP/Port/Hostname route requests to a specific directory. Any valid combination of IP/Port/Hostname will always get routed to the single Site. On XP you can only route requests to distinct Virtual directories by specifying an Alias or directory name. So, on XP you cannot have www.MySiteA.com go to one virtual directory and www.MyStieB.com go to a different virtual directory (that requires a server version of IIS or some extra software). On XP you can have wwwMySiteA.com go to one Virtual directory and www.MySiteB.com/SiteB go to a different virtual directory because it has a distinct virtual directory alias on the second example.
So, on XP you have to distinguish your virtual directories by directory name. You get one default Root web directory, and then other requests are routed by the first driectory name. When setting up DNN you first need to make sure tht at least one IIS web site will accpet its requests. On XP that means your default web site should probably be like #4 and accept all requests.
Now DNN has its own mechanism for routing requests. Typically, DNN is installed in a single virtual directory (and normally in the default root virtual directory). You set up the DNN virtual directory to accept all requests that match the IP/Port/Hostname combinations you want to support. Typically you want DNN in a web site that is set up for something like IP all unassigned. Port 80. Hostname: any. This will catch any requests.
DNN then looks at the Hostname and port number in the requests to determine which of its Portals gets the request. It looks for an exact match. So, www.MyWebA.com is different from MyWebA.com which is different from MyWebA.com:8080. For every Hostname (and port number) that you want DNN to handle, you must have a properly defined Alias set of for a Portal (under site settings). Also, remember that if you want your Portal to respond by IP Address (http://10.1.2.3/) then you must register the IP address as an alias for the portal. DNN sees the IP address as another hostname.
If a request gets routed by IIS to your DNN install and DNN cannot find a matching Portal alias, DNN uses the default portal for your install which by default is the first portal that you installed. If your requests are being handled by the default portal that means that
1. IIS is routing the requests to your DNN install
2. You probably don't have a Portal with the proper Hostname and Port number set up in DNN so DNN is passing the request to its default portal.
You can set up distinct DNN installs in separate virtual directories or web sites, but you don’t normally do this just to have two portals. If all you want is multiple portals, use a single install and use the DNN portal alias mechanism. Sepearate DNN install and its extra complexity is mostly used for development, testing, or if you just want to keep two sites completely isolated, or if two sites could not share the same web.config (let’s say because one site required a different membership provider than the another, or a user…).
Are you ready to be heard? WildVoice Network
Equicast Media
Accidental Architect
ludis
Member
255 Points
51 Posts
Re: multiple portals on same IIS server
Dec 12, 2005 03:12 PM|LINK
Be careful with object qualifiers...some modules will break under object qualifiers.
Luis
djbaldwin
Participant
1025 Points
205 Posts
Re: multiple portals on same IIS server
Dec 12, 2005 03:44 PM|LINK
FYI, objectQualifiers are part of the DotNetNuke core. The real purpose of an objectQualifier is to separate the data in a shared SQL server environment where the user is given a single database, and does not have permissions to create additional databases. The objectQualifier prefixes the tables to allow multiple DotNetNuke installations along with other SQL applications which is very common with many hosting providers.
If a module does not support objectQualifiers, it should not be called a DotNetNuke module, period.