need help setting up server
Hello. This is my first time setting up network services. My setup is:
desktop 1 192.168.0.254 | DI-624 router 192.168.0.1 | VoIP device | Cable modem 70.177.173.196 | internet First, I'm trying to setup Apache. I enabled port forwarding of port 80 to desktop 1 on the router, but when I try to access a web page, I get a page saying This unit is password protected Please enter the correct password to access the web pages. I then wrote a simple java program that opens a server socket on port 80 on desktop 1 and waits to accept a request. Then I wrote another program which opens a socket on port 80 of 70.177.173.196, which connects, but not to the server socket, which probably means it is also getting that password page. Any ideas on what's wrong? I think it's a router configuration problem, but I don't see any place where you set a password for accessing web pages. |
Could your service provider block all incoming requests on port 80?
Try running apache on a non standard port (I use 8880) and see if you get a different situation. |
Right, I never thought that Cox would block port 80. I tried 8080, 90, and 105,
but now I get the message connection refused when I try that. Thanks anyways. |
portscan yourself to see if the ports are open. I have seen apache (with ssl support) act a bit "wonky" when stopping/restarting the service on occasion.
Also try opening 127.0.0.1:port# in your browser. If you can see the server from localhost, then your first idea about the router being to blame is likely. If you can't then it points to the server config. EDIT - silly smilieys. |
OK, I did a port scan of all 65535 ports with nmap, and I officially conclude Cox blocks every incoming port except for 23, 80, and 160 something. I knew that they would block certain ports, but I didn't know they would go that far. Damn Nazis. Guess I'll have to host my web stuff elsewhere. Thanks for the info.
|
Cox blocking all incoming requests on that many ports sounds unlikely.
Run nmap again as root and scan 127.0.0.1 - to see any ports blocked locally by a firewall and your external ip of the router. - to see ports block by Cox or the router itself. It really sounds like either you're running a firewall or you still have the ports blocked on the router. Not sure about Cox, but Verizon and Adelphia block 80, 8080, and 21 in Fairfax City (I'm from Virginia too ;) ) |
Well, nmap says that the modem and router has port 80 open. I temporarily mapped port 80 from the router to port 22 of the desktop which had my java server socket test program running on port 22, which still gives that password needed page. I still don't know where that page is comming from. Is it comming from Cox or the router itself?
----------------------------------nmap results--------------------------------------------- (for the desktop) yale@vaiolaptop:~/incoming$ nmap -p 0-65535 192.168.0.100 Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2005-05-19 18:31 GMT Interesting ports on necdesktop (192.168.0.100): (The 65525 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 9/tcp open discard 13/tcp open daytime 22/tcp open ssh 37/tcp open time 111/tcp open rpcbind 139/tcp open netbios-ssn 445/tcp open microsoft-ds 631/tcp open ipp 4662/tcp open unknown 6000/tcp open X11 20012/tcp open unknown (for the router) yale@vaiolaptop:~/incoming$ nmap -p 0-65535 192.168.0.1 Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2005-05-19 18:46 GMT Interesting ports on 192.168.0.1: (The 65534 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 80/tcp open http 5678/tcp open unknown (for the outside address) yale@vaiolaptop:~/incoming$ nmap 70.177.173.196 Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2005-05-19 18:50 GMT Interesting ports on ip70-177-173-196.dc.dc.cox.net (70.177.173.196): (The 1060 ports scanned but not shown below are in state: filtered) PORT STATE SERVICE 2/tcp closed compressnet 4/tcp closed unknown 6/tcp closed unknown 9/tcp closed discard 10/tcp closed unknown 16/tcp closed unknown 18/tcp closed msp 21/tcp closed ftp 22/tcp closed ssh 25/tcp closed smtp 26/tcp closed unknown 27/tcp closed nsw-fe 29/tcp closed msg-icp 31/tcp closed msg-auth 32/tcp closed unknown 35/tcp closed priv-print 36/tcp closed unknown 42/tcp closed nameserver 43/tcp closed whois 44/tcp closed mpm-flags 45/tcp closed mpm 46/tcp closed mpm-snd 47/tcp closed ni-ftp 48/tcp closed auditd 50/tcp closed re-mail-ck 52/tcp closed xns-time 53/tcp closed domain 56/tcp closed xns-auth 61/tcp closed ni-mail 70/tcp closed gopher 76/tcp closed deos 79/tcp closed finger 80/tcp open http 81/tcp closed hosts2-ns 83/tcp closed mit-ml-dev 85/tcp closed mit-ml-dev 87/tcp closed priv-term-l 88/tcp closed kerberos-sec 94/tcp closed objcall 95/tcp closed supdup 97/tcp closed swift-rvf 98/tcp closed linuxconf ... Nmap finished: 1 IP address (1 host up) scanned in 17.362 seconds |
Oops!
I assumed you were having troubles connecting from the outside. Maybe this info is more relevant and helpful Normal function for a home/small office broadband router -- If you hit port 80 from INSIDE the local network (the 192.168.xxx.xxx address) you get the router web-based admin page. Try it from firefox, type in 192.168.0.1 in the address bar. You'll probably get a login pop up asking for username/password. If you've never set up anything via this interface you can get the login from the router manual, or the manufacturers website. Once you log in you can set up the router's port forwarding. The interface is usually pretty simple, and I'm sure whatever brand you have there will be a website with a good faq/docs for it. Whatever you do make sure you change the password at least, since unsavory types might be reading this ;) Set it up so that external requests to the IP of your cable modem are routed through to the internal address of the box with your webserver. You can do the same for ftp requests (port 21) and ssh (22) IF YOU THINK YOU"LL NEED THESE SERVICES! Remember, networking between computers on the INSIDE network don't need open ports on the router, so you can xfer files from one pc to the next via scp or ftp with the ports still closed to the outside world. I hope this helps a bit more |
I just had the same problem. Google revealed on some other forum that this is actually VoIP device (Sunrocket in my case and in case of the guy from the other forum).
This gizmo does not seem to be processing loopbacks correctly. So using 127.0.0.1 works, by using DNS name does not. I just email question to Sunrocket customer support, so no resolution right now. The default password to enter is either welcome, or Welcome. And there're port forwarding settings in LAN section, however changing it didn't have any effect in my case. Cheers! PS Don't blame someone prematurely (like you blamed comcast). It's just not fare. |
All times are GMT -5. The time now is 02:49 AM. |