I apologise in advance if this has been covered in the standard documentation or in a previous thread as I do not know what to search or where to look.

The problem I have is that I cannot access my Dot Net Nuke website remotely; that is, I can access the website locally (http://localhost/dotnetnuke), however, when I jump on another machine on the network and try to access the dot net nuke website (http://<computer name / local IP address>/dotnetnuke), I get a number of error messages.

To provide more information:
I have successfully deployed Dot Net Nuke v4.3.2 website application on my local machine.
My operating system is Windows XP Pro, hence IIS is version 5.1.
My computer is patched with all the latest service packs.
I have installed the latest dot net framework v2.0.50727.
The dot net nuke database is MS SQL Server Express.
MS SQL Server Express was installed using Windows Authentication - The default installation was used.
The internet browsers I am using are IE6.0.2900 and Mozilla Firefox 1.5.0.4.

The first error message I get on the remote machine is "The page cannot be displayed" (IE6) and "Firefox can't establish a connection to the server at localhost" (Firefox).  I have ruled out that the remote machine is having problems connecting to my local iis web server as I have created a simple website with one htm page that outputs "Hello World".  That page loads fine from the remote pc.  For some reason firefox is redirecting the url I have entered to http://localhost/dotnetnuke even though I have used the computer name and internal IP address in place of localhost.
At first I thought that the remote pc's IIS service maybe causing the problem so I stopped the remote pc's IIS services.  I still get the error messages on both browsers.

Seeing that I can access the dot net nuke website locally and that I can access other websites remotely (the hello world website) makes me believe that it is not the local IIS web server, but the dot net nuke website application.  Perhaps it is a permissions / authentication thing.

Any assistance in this matter is much appreciated.

Kevin.

I have reviewed the forum you have suggested;  I have tested it in my own local Dot Net Nuke web application but have been unsuccessful.

I followed the instructions set out in the suggested forum.
I have created new portal aliases:

<computer name>/dotnetnuke
<internal IP address>/dotnetnuke

The result of the computer name (remote - client access) alias (browser - Mozilla) is that it looks to search google and finds the closest match then redirects the user to the closest possible match.  In my case, my computer name is "grand" hence the alias I have used is grand/dotnetnuke.  I get redirected to http://www.nps.gov/grca/ (Arizona USA Grand Canyon official website). 
The same alias on IE6 produces a different result - "Page cannot be displayed".

The result of the internal IP address alias (browser - Mozilla) shows a browser error message "The connection has timed out - The server at <internal IP address> is taking too long to respond."
The same alias on IE6 produces a different result - "Page cannot be displayed".

I have managed to resolve the problem myself.

It was a file permissions problem.  I added the user account <computer name>\users with read and write permissions to the dotnetnuke folder.  That is it.

I came across this by accident when a user on another computer tried to copy some files from my computer; A permission dialog box popped up indicating the lack of permission for the other user.  I checked difference of some files that were able to be copied and it turned out to be <my computer name>\users account.  I thought to myself, perhaps this was the case with the dot net nuke website too.

In addition, the http alias is required too when others are trying to access the local dotnetnuke website.  You will need to add
1. <computer name>\dotnetnuke (or whatever you called your dotnetnuke website)
2. <internal ip address>\dotnetnuke (or whatever you called your dotnetnuke website)

I hope this thread is beneficial to others in future.  It took my 2 full days of trial and error testing and countless searching through forums.  My last resort was trying to get help from this forum.  Suprisingly, there was little help.

Cheers.