I have installed DNN in my pc thru Microsoft Webmatirx. DNN Site works fantastically in my PC. I am starting the site thru webmatirx before accessing it thru browser. Webmatrix assigned address http://localhost:62856 for my DNN Site. After successfully installing DNN thru browser, my home page assigned as http://localhost:62856/home.aspx. It works nicely thru browser. I can access my admin as well as user accounts thru DNN Site. Now I want to share my DNN site to my collegues thru Local network in my office. 

I requested lot many people help to get thru it. But as of now, no one given the correct solution to configure my DNN settings to make it available thru local network. Hence I have written again for the help.

What are the steps I should carry to make my DNN Site available to my office collegues thru LAN. I tried by changing 'localhost' to 'IP address'  in my DNN site address. But I couldnt access it. I tried by mentioning portal alias with IP address in Host settings. That also failed. 

Actually I made this DNN site for our office internal Digital library. I am feeling bad not to share it with my collegues. Could anyone guide me how to share my DNN site which runs thru Webmatrix with all my colloegues in my office?

Thanks

As per your instruction, I have added my IP addrss (192.168.150.2:62856) in portal alias. There are 3 mode shown with radio button. None, Canonical and Redirect. I kept the default option of None. Is it correct? or need to select anyone else?

Is there any need to change the address assigned in Webmatrix (http://localhost:62856)? When I tried after correcting the information, I tried to access the site in the same PC with new alias. But I got HTTP 400 Bad request error (Page cannot be found). When I tried in other PC, I got the same HTTP 40o Error. Is there any more settings to be done for making the site available to other PC? Pls help.

I amended the IP address. Removed the port no. Now I have changed the 'localhost' with 'IP address' in webmatrix site setting. I got the following error.

DotNetNuke Error
--------------------------------------------------------------------------------

Domain Name 192.168.150.2:62856 Does Not Exist In The Database 

DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process: 

Web Server Processing

When a web server receives a Request from a client browser, it compares the file name extension on the target URL resource to its Application Extension Mappings defined in IIS. 
Based on the corresponding match, IIS then sends the Request to the defined Executable Path ( aspnet_asapi.dll in the case of ASP.NET Requests ). 
The aspnet_isapi.dll engine processes the Request in an ordered series of events beginning with Application_BeginRequest. 

HttpModule.URLRewrite OnBeginRequest ( UrlRewriteModule.vb )


The Request URL is parsed based on the "/" character 
A Domain Name is constructed using each of the relevant parsed URL segments. 


Examples: 


URL: http://www.domain.com/default.aspx = Domain Name: www.domain.com
URL: http://209.75.24.131/default.aspx = Domain Name: 209.75.24.131
URL: http://localhost/DotNetNuke/default.aspx = Domain Name: localhost/DotNetNuke
URL: http://www.domain.com/virtualdirectory/default.aspx = Domain Name: www.domain.com/virtualdirectory
URL: http://www.domain.com/directory/default.aspx = Domain Name: www.domain.com/directory

Using the Domain Name, the application queries the database ( Portals table - PortalAlias field ) to locate a matching record. 


Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list. 


Example: 


URL: http://localhost/DotNetNuke/default.aspx
URL: http://MACHINENAME/DotNetNuke/default.aspx
URL: http://209.32.134.65/DotNetNuke/default.aspx
PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,209.32.134.65/DotNetNuke 


Note: If you are installing the application to a remote server you must modify the PortalAlias field value for the default record in the Portals table according to the rules defined above. 
If I keep the same setting in Webmatrix, I am getting same HTTP 400 Error (Page cannot be found). What would be the problem? Where the problem still lies? Could you please help me to resolve?