Swade,

it is quite easy. If you use the same database, then you have to choose a different object qualifier, otherwise (if you have a seperate database on the same SQL Server instance), it's the same as installing the first instance.

You don't need a second IP address, and you don't need a second SQL Server instance (but if you have this, no problem - if the server is powerful enough).

Take care about the host header values in IIS, and the App Pool user (if you're using IIS 7+).

Are you installing DNN manually or do you use the web installer?

Best wishes
Michael

---

Swade,

afaik the machine key is used to encrypt the passwords. That means: you can use the same machine key, but when you change it on one portal, the passwords for all users get invalid.

If you have the same users on the second portal, it should be possible to copy their password-hashes from the database in the first portal (where the passwords are still valid).

The object qualifier does not make any difficulties for reaching the site. It is used for the scenario that you have different instances of DNN running against the same database (and I mean: the same database in the same instance of SQL Server).
Example: You have a single installation of DNN in a folder caled C:\DNN, and a database called DotNetNuke. If you don't use an object qualifier, you have tables like "Modules", "Tabs" etc. in this database. Assume you have two installations in folders called C:\DNN1 and C:\DNN2, but only one database. Then you have to use different object qualifiers, can be "dnn1" for the first and "dnn2" for the second DNN instance. You will get tables named "dnn1_Modules", "dnn2_Modules", "dnn1_Tabs", "dnn2_Tabs" etc. You can also use no object qualifier on the first installation, but on every other installation you need an object qualifier.

Best wishes
Michael

---