Ok

I've tried to stay away, but I need help.

[twinrecords]

ok, I am running Fedora 14, behind a WNDR3700 Netgear router, have been working on getting this server up and running, of course everything is fine inside my local network, but outside, nada...here's what I can tell you about what I have done and what I know.

I have thepc-doctor.net for a domain, the domain is hosted with domain.com and is supposed to be pointed to my server, but it doesn't work..

I created an A name for the domain to point to my EXTERNAL ip(not sure if this is right)

opened port 82 because my isp has 80 on stealth, 82 is open.

Configured the http.conf file to show VirtualHost 172.16.0.92 (servers ip address)

I have the listen directive on port 82

I have configured the hosts file to contain all of the ip addresses, I read somewhere that I should do that, so it has 127.0.0.1, 206.217.12.51 and 172.16.0.92.

I have turned the NAT layers off on the router, I even set the DMZ to the same as the servers ip, and configured my firewall to accept incoming connections for port 82

So as I said, internally I can access everything, and I understand that the dns never actually gets resolved because it's all internal, but I just get the "browser cannot open web page" from an external computer.

[wheel]

opened port 82 because my isp has 80 on stealth, 82 is open.

Right there. I gather by 'stealth' you mean it's blocked?

You're all fired up and listening on port 82.

But MY browser will call your server on port 80, not 82.

You can test this by visiting your website but adding :82 on the end, like:
http://www.example.com:82
You should see your site.

You have four choices.
1) your isp redirects 80 to port 82.
2) your isp opens port 80
3) you move your site somewhere else
4) you get a new Isp that isn't stuck in 1998

#4 and #2 are the realistic options.

[twinrecords]

that's funny, cause my wife and I were just talking about how the local isp is outdated, refusing to upgrade and blaming all the users for draining the bandwidth

[g1smd]

Some ISPs specifically ban their customers from serving websites from their home or office location. The traffic pattern they design for is the reverse of what happens when you start serving a website from your end. Your http://206.217.nnn.nnn:82/ URL is world visible.

[Leosghost]

Some where in the T&C's on your ISP website it will probably tell you that you can't host websites from the domestic package ..which from your posts is what I assume you have.

As g1smd says ..many don't even let you host from business packages..why would they, would let every customer turn into a potential bandwidth hog ..and who knows what they might be hosting ..most ISP's just do not need the potential for that kind of grief ..nor for every other line user on the dslam to be burning up their help desk because someone is using all the pipe.

Btw ..mine is Ok about me hosting from here , if I wanted to and the pipe to me is big enough..but I don't need the grief of doing that either.

[twinrecords]

I have a business package actually, and it doesn't say anywhere that I can't do it, i'll talk to them tomorrow

[g1smd]

In any case it's a good learning exercise to set up a server and configure it. Keep the server for testing future site designs on.

Reliable hosting is fairly cheap these days if your ISP tells you that you can't serve your own site.

[twinrecords]

I have 3 domains, I have a fairly large one for an online business which I host with a company, but my 2 other ones are really small, so I would have no problem being able to host them. I called the only other ISP in my area and they don't block ports, so that's cool.

thanks for your help guys, i appreciate it. I saw so many posts on the internet about how to switch incoming requests to a different port, but I guess with this ISP it's not possible. Thanks again, not to mention, browsers look to prt 80

[Leosghost]

just a thought ..is your IP static or dynamic ( if the latter, you'll need to allow for that and set something up ) ? either way you might also want to look into DNS failover services or similar ..else if you had a power cut and went off line at home you might be unlucky and have it coincide with a crawl..out for too long can hit your rankings.

nicely arcane subject ..hours of fun ahead of you there ..if not days ..Good luck :)

[twinrecords]

I have a static IP, and I have already setp a DNS failover.

I'm glad to see that with my first attempt at this, I did in fact have it all setup properly, it was the port 80 that got me in the end, people like you guys are a great resource, and I appreciate it greatly.

This has definitely been alot of work to setup so far, I'm sure there will be alot more work ahead, days...if not weeks.

[Leosghost]

I just realised ..we all forgot our manners ..Welcome to WebmasterWorld twinrecords :-)

[twinrecords]

thank you