I am running a web server on a computer I have, I currently have Comcast Cable internet installed, plus am using a Addtron ADR E200P Router, my problem is this:
when I put my outward IP in the http address in my browser it says this DNS Error or whatever, page cannot be displayed, but I can get to the website inside my network, so my question is:
A. Can I not go to the site with my external IP Address because of the way Comcast is set up?
or
B. Is it something to do with the Router Model I am using, that does not support it,
or
C. Am I being really stupid, and should know something, and everyone else is like that.
Problem with IP??
-
Alex_Select
- Member
- Posts: 84
- Joined: Fri Oct 12, 2001 1:23 pm
- Location: Washington, D.C.
Question
Who is resloving the DNS querey? Your machine behind the router or the router itself?
I know that some areas that were formerly serviced by @home would block commonly used ports - http, ftp, smtp - so that members would not run servers. Check your AUP - it is probably a violation and could get you disconnected.
DNS shouldn't matter since you are trying an IP address rather than URL/Hostname - right?
Are you using port forwarding/DMZ to allow http requests to your server? Most routers require that you use static addressing on the LAN side of the router to do this. That means you would have to set the dns, gateway, and ip address manually on all machines behind the router.
Do be careful about running servers, tho. I have friends that have received nasty threatening letters from comcast - besides 128k is REALLY slow fo a server (which is why they cap upload so low in the first place, probably). Given that your upload queue is so small (if it is 128k) you will notice the effect on your downloads if someone is accessing your webiste at the same time...
If you are really bent on doing this, bind your http server to a non standard port (>1024) and have people use that to access. You'll still probably get caught eventually anyway...
Example: bind to tcp port 65230 and have your clients use xxx.xxx.xxx.xxx:65230 to get to your site (where the x's are your public ip address)
Have fun,
Skye
DNS shouldn't matter since you are trying an IP address rather than URL/Hostname - right?
Are you using port forwarding/DMZ to allow http requests to your server? Most routers require that you use static addressing on the LAN side of the router to do this. That means you would have to set the dns, gateway, and ip address manually on all machines behind the router.
Do be careful about running servers, tho. I have friends that have received nasty threatening letters from comcast - besides 128k is REALLY slow fo a server (which is why they cap upload so low in the first place, probably). Given that your upload queue is so small (if it is 128k) you will notice the effect on your downloads if someone is accessing your webiste at the same time...
If you are really bent on doing this, bind your http server to a non standard port (>1024) and have people use that to access. You'll still probably get caught eventually anyway...
Example: bind to tcp port 65230 and have your clients use xxx.xxx.xxx.xxx:65230 to get to your site (where the x's are your public ip address)
Have fun,
Skye
anything is possible - nothing is free
Blisster wrote:It *would* be brokeback bay if I in fact went and hung out with Skye and co (did I mention he is teh hotness?)
Well, that does not really solve the problem, other people can already connect to my server from the outside using the external IP, but I can't connect to it from inside the network, I have all the DMZ, everything set up already though, so I do not know what the problem is? since people inside the network are the only ones who cannot access it.
-
BlackSword
- Advanced Member
- Posts: 700
- Joined: Thu Apr 19, 2001 12:00 am
- Location: Ontario, Canada
Have you tried specifying the internal IP?Originally posted by Gamewiz
Well, that does not really solve the problem, other people can already connect to my server from the outside using the external IP, but I can't connect to it from inside the network, I have all the DMZ, everything set up already though, so I do not know what the problem is? since people inside the network are the only ones who cannot access it.
I haven't setup a web server but for any game server I always connect to it using the internal IP address of the game server. Basically why tie up the router when anyone internal can go straight to the server.
P4 2.4ghz 512ram XP pro ATI 9600pro
P4 2.0ghz 256ram Win2000 Geforce2 MX 400
P4 1.6ghz 512ram XP Home Geforce4 Ti4200
P3 866mhz 320ram ME & XP pro TNT2
All thru HotBrick 600
P3 1.1ghz 260ram Win2000 laptop
P4 2.0ghz 256ram Win2000 Geforce2 MX 400
P4 1.6ghz 512ram XP Home Geforce4 Ti4200
P3 866mhz 320ram ME & XP pro TNT2
All thru HotBrick 600
P3 1.1ghz 260ram Win2000 laptop
Try just forwarding the specific port (usually 80) to the server vs using the DMZ feature. DMZ just forwards all ports. I think you are confusing your router as it's reply would be forwarded to itself?
You get hairy palms and go blind that way, my friend
Skye
You get hairy palms and go blind that way, my friend
Skye
anything is possible - nothing is free
Blisster wrote:It *would* be brokeback bay if I in fact went and hung out with Skye and co (did I mention he is teh hotness?)
I have DMZ set up, the server computer's ports(80,81etc,) is already released to the public, but that is not the problem, the public can see my web server, I can't but no matter, maybe I just can't anyway, thanks for all you alls help though, I will just use the internal server IP to get there from now, on,
Cheers!
Stevie Minter
anyway, thanks for all you alls help though, I will just use the internal server IP to get there from now, on, Cheers!
Stevie Minter