Hi all.

Before I get into this post, I want to state that I usually do all that I can think of to solve a problem on my own. In fact, this is my very first post to a DNN forum of any kind. I am sure that many of you will think my problem is so basic that it is laughable, but I don't care as long as it gets solved. :)

I have "successfully" installed DNN 3.2.2 on a virtual machine (VMWare Server) that has Windows 2000 Server SP4, SQL Server 2000 SP3, and .Net Framework 1.1 and 2.0. I say successfully in quotes because I can do all that I need to do with the modules, even adding a purchased module, when I access the portal locally on the VM; that is, I am on the VM itself using IE 6 to administer the portal. Here's the problem: I go to my client computer (Windows XP Pro - yes, IIS is enabled) and type in the IP address of the VM and ... 404. Actually, I get the default website of my local IIS! Btw, I can ping the IP address.

In my efforts to make sure I can "see" the site, I created a test.htm file with "hello world" between starting and ending html tags. That's it. In IE on my client computer I am able to see that file, so something is happening when IIS and DNN are processing aspx files, because I created a test.aspx with the same "hello world" content as in test.htm and I get a 404. Obviously, I am missing something. I can administer the portal if I am on the VM itself, but it can't connect to it (the aspx files) from a client.

So, what's the laughable solution? :)  Why are .aspx files somehow being re-directed or something to result in a "page cannot be displayed" message on my client computer? I looked at the web.config file, dnncore.js, etc. to try and figure it out, but I can't.

Thanks for your help,

Dan