All,

I spent 2 days troubleshooting the site and I am having trouble getting it to DNN 3.2.2 site to pull up on the WAN (internet).  I can pull up the website on the LAN (intranet), but I have not been able to get the site working on the internet. 

For example, let's suppose that this site has a domain name called www.aaa.com.  In the local area network (intranet), I can pull up the site without a problem using the domain name www.aaa.com.  However, if some John Doe types in www.aaa.com on the other end of the globe, the site does not pull up.  From the outside (internet), I am able to come up with the correct internet IP address by pinging www.aaa.com.  I can also ping HTTP port 80 and get a response back as an open port.  From there, I'm not sure what the problem is with the DNN site.  Most of my testing has been done on www.internetsupervision.com.

For your info: I've checked the following:

• The box (the Network Settings, TCP/IP settings are ok).
• The firewall (opened HTTP/HTTPS ports, mapped static LAN address to static WAN address).
• The domain registration company (pointed to the correct static IP address where the box resides). 

All three checked out ok.  I've pointed it out to the right static IP address but the URL info does not seem to pass through or trigger the loading of the site over the internet.  I have included the portal alias: www.aaa.com and aaa.com in the PORTAL ALIAS under HOST>PORTALS.

I am beginning to suspect that it is some simple setting under my nose and I think it has something to do with the ODBC settings, the MS .NET v2.0, OR the file sharing settings.  I'm not sure but my gut tells me that one of those settings are the culprit.  I've googled the problem but was not able to find a solution that works just yet.

Box Specs:
MS Server 2000
SQL Server 2000
IIS 5.0
DNN 3.2.2

Any help would be greatly appreciated.  This appears to be a simple problem where something has to be tied together for it to work... but I have not gotten there despite the high levels of fustration trying to get it to work.

Thanks,

Eric

Interesting - I guess you could refer to the internet as a WAN, but that technically is wrong BTW.  Your problem sounds like either:

1.  your internal DNS not properly set up (do you have a proxy or other device handling traffic like ISA server, etc.?)
2. your firewall is not configured properly - your external IP is replying (not a good thing BTW replying to ping requests)
3. Your NAT is not working properly (similar to #2 or part of the same problem and is not translating the address correctly)

If you can get to the site internally, via IP or name resolution, and DNN works, then it has nothing to do with IIS, ODBC, File permissions, etc.  You should focus on the firewall as it sounds like the culprit.  I'd trace the traffic on that IP that you expect to be assigned and look at the routing statements in the firewall config.  What kind of firewall is it?  Hardware (CISCO PIX, etc.) or software?