I discovered the problem. IIS would not work on port 80, so following the advice of a "brand x" forum, I changed my IIS port to 81 and didn't look much further to find what was using port 80 in the first place. Doing a netstat -o from the command prompt didn't tell me anything about another program using port 80 so I stopped there and just told IIS to use port 81.
Well, last night I did more detective work and all of a sudden realized I had installed Apache webserver software a couple months back but didn't go any further at that point.
Long story short......I uninstalled Apache and not it's working. IIS is once again pointed at port 80. Now if I can get my static IP routing pointed to my web server, I'll be in business.
I think what I need to do is document all the steps I am taking to go from a simple asp.net website with a sql server backend to hosting that website on my own server at home while also building a home network and turn it into an article to post somewhere. I have been using so many different resources, forums, and step by step guides, it's not funny. I've never had any network classes, but I have learned a ton during this process. Not just about networks, but also more that I need to know about how my software interacts with that software.
At my job, I just write code and check it in.
Building a network from the ground up, using the network to develop, deploy, and operate what I write gives me a very complete understanding of just what I'm really doing.
Thanks to everyone who has helped me along the way so far. Just by asking me the questions about different scenarios like above, I am led to discover the problems on my own. That's the best way to learn.
Thanks