Re: Still trying to get my site up!
On Mon, 27 Jun 2005 21:43:08 -0700 Garrett Cooper [EMAIL PROTECTED] wrote: I say get rid of the ISP and find a better one. Any ISP that actively blocks port 80-a port which should be allowed as a backup port for programs-isn't really setup correctly and I doubt that they have all of your best interests in mind when making decisions. -Garrett ** Reply Separator ** Tuesday, June 28, 2005 7:12:05 AM Getting a new ISP is not really an option. They are my local cable company. Ipso facto, they have a de facto monopoly on cable in this region. I cannot simply shop for another service. Actually, they are a pretty good company. Their service is good, and they are willing to work with me on most issues. They will even sell me a static IP is I am willing to fork over $25 additional each month. In addition to port 80, they also block port 25. This sort of behavior is becoming an industrial standard now with cable companies. The blocking of port 25 has to do with the 'worm' problem a few years ago. The port 80 blocking is more attuned to greed I believe, but that is pure speculation. -- Gerard E. Seibert [EMAIL PROTECTED] Q. What is the definition of irreconcilable differences? A. When she is melting down her wedding ring to cast it into a bullet. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Still trying to get my site up!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gerard Seibert Sent: Tuesday, June 28, 2005 4:26 AM To: freebsd-questions@freebsd.org Cc: Garrett Cooper Subject: Re: Still trying to get my site up! On Mon, 27 Jun 2005 21:43:08 -0700 Garrett Cooper [EMAIL PROTECTED] wrote: I say get rid of the ISP and find a better one. Any ISP that actively blocks port 80-a port which should be allowed as a backup port for programs-isn't really setup correctly and I doubt that they have all of your best interests in mind when making decisions. -Garrett ** Reply Separator ** Tuesday, June 28, 2005 7:12:05 AM Getting a new ISP is not really an option. They are my local cable company. Ipso facto, they have a de facto monopoly on cable in this region. I cannot simply shop for another service. Do you have DSL in your area? Also you can get an offsite webhost for about $10 a month. Actually, they are a pretty good company. Their service is good, and they are willing to work with me on most issues. They will even sell me a static IP is I am willing to fork over $25 additional each month. In addition to port 80, they also block port 25. This sort of behavior is becoming an industrial standard now with cable companies. Yes that is true and with the recent US Supreme Court ruling it is going to get worse. But you also probably don't understand the politics behind it, either. The US Supreme Court lawsuit was funded primariarly by Verizon, behind the scenes, with assistance from some of the other telephone companies. While on the surface it appears to have failed, in actuality like many Supreme Court rulings it helps both sides. For the cable companies they get, obviously, the ability to do whatever the hell they want without having to open their networks. However the telecommunications companies get something too, and that is the ability to federally regulate the cable companies. Previously to the ruling, regulation of the cable companies was on a state by state and county by county basis. With lots of money, the cable companies could easily quash any local attempts at regulation of Internet services by the local cable franchise granters. Now with the ruling, regulatory control of the cable companies has been effectively turned over to the FCC. (If you don't understand why this is, read the decision) Thus all that is necessary is for the telecommunications lobby to get cable regulation bills pushed through Congress, which they could, based on the level playing field premise. The FCC will probably try to prevent this from happening by preemptively issuing their own regulations, but don't forget that the FCC got regulatory control over the telephone companies though an Act of Congress. The same thing is now in the future for the cable companies. Now, the cable companies know all this too, and they of course don't want it to happen. So what they are doing now is making absolutely sure that their price and service structure is equal or slightly higher than the DSL providers. As a result of this you do not have situations where a telecommunications company dumps 5 million bucks into a metropolitian area to put in DSLAMS and gets no subscribers, because everyone is using cable since it's $10 cheaper a month for Internet service, or because everyone who wants a server gets a cable connection and uses dydns. Doing this then gets the market split between cable and DSL, which removes the impetus for the telephone companies to heavily fund regulation legislation in the US congress. Every broadband supplier in the industry, both Cable and DSL, knows that the biggest obstacle to growth of broadband is that there is no killer app that forces users to switch to it. A decade ago, the killer app was e-mail and web surfing, that literally forced every computer user to get an ISP and dialup account. But today, the existence of the cut-rate $10-a-month dialup providers has created a situation where the majority of home Internet users are still on dialup modems. So, while it may seem on the surface that if either the cable company or the telecommunications companies could get a lot of market share by undercutting each other, the effect would be that the other would run to Congress with a pocketful of money to do nasty things. And the market gain would be only transient because most users have shown that when it comes to broadband they don't give a shit about quality of service, all they care about is what is cheaper. The second the company that was doing the $10 undercut ran out of money, and put their rates back, all the users they gained would go back to the other provider. It's kind of a mutually assured destruction sort of thing. The DSL providers in most areas have one thing that hampers them that the cable companys don't - they are distance-limited from the CO. So in any given metro area you have holes in DSL coverage, where the cable company
Re: Still trying to get my site up!
--On June 26, 2005 7:06:34 PM -0400 Gerard Seibert [EMAIL PROTECTED] wrote: The 'beerstud.us' redirects to 'www2.beerstud.us:9545' bash-2.05b# dig www.beerstud.us ; DiG 8.3 www.beerstud.us ;; res options: init recurs defnam dnsrch ;; got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 54693 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 5 ;; QUERY SECTION: ;; www.beerstud.us, type = A, class = IN ;; ANSWER SECTION: www.beerstud.us.12H IN CNAMEbeerstud.us. beerstud.us.5h59m37s IN A 63.208.196.110 ;; AUTHORITY SECTION: beerstud.us.23h59m37s IN NS ns2.mydyndns.org. bash-2.05b# ping beerstud.us PING beerstud.us (63.208.196.110): 56 data bytes 64 bytes from 63.208.196.110: icmp_seq=0 ttl=243 time=50.902 ms 64 bytes from 63.208.196.110: icmp_seq=1 ttl=243 time=49.316 ms 64 bytes from 63.208.196.110: icmp_seq=2 ttl=243 time=50.472 ms 64 bytes from 63.208.196.110: icmp_seq=3 ttl=243 time=49.538 ms 64 bytes from 63.208.196.110: icmp_seq=4 ttl=243 time=50.056 ms 64 bytes from 63.208.196.110: icmp_seq=5 ttl=243 time=50.229 ms 64 bytes from 63.208.196.110: icmp_seq=6 ttl=243 time=49.012 ms bash-2.05b# traceroute www.beerstud.us traceroute to beerstud.us (63.208.196.110), 64 hops max, 44 byte packets 1 66.221.96.1 (66.221.96.1) 0.339 ms 0.195 ms 0.189 ms 2 f1-g1-c1.propagation.net (66.34.255.1) 0.651 ms 0.825 ms 0.594 ms 3 g0-8.na21.b000385-1.dfw01.atlas.cogentco.com (38.112.17.77) 2.164 ms 2.168 ms 2.615 ms 4 g6-1.core01.core02.dfw01.atlas.cogentco.com (66.28.6.205) 2.108 ms 1.775 ms 1.878 ms 5 p10-0.core01.dfw03.atlas.cogentco.com (154.54.1.58) 2.819 ms 2.679 ms 2.547 ms 6 so-3-2-0.edge2.Dallas1.Level3.net (4.68.127.13) 2.366 ms 2.901 ms 2.820 ms 7 so-7-0-0.bbr2.Dallas1.Level3.net (4.68.96.121) 2.877 ms 3.095 ms 2.895 ms 8 so-3-0-0.mp1.Boston1.Level3.net (209.247.9.125) 49.159 ms so-2-0-0.mp2.Boston1.Level3.net (64.159.4.181) 48.916 ms so-3-0-0.mp1.Boston1.Level3.net (209.247.9.125) 49.986 ms 9 ge-11-1.hsa1.Boston1.Level3.net (4.68.100.100) 49.963 ms ge-11-0.hsa1.Boston1.Level3.net (4.68.100.36) 48.582 ms ge-10-2.hsa1.Boston1.Level3.net (4.68.100.132) 49.108 ms 10 fe-0-0-0.router1.bos.dyndns.org (63.211.169.134) 48.787 ms 49.373 ms 49.485 ms 11 firewall1.bos.dyndns.org (63.208.196.57) 48.381 ms !X 49.319 ms !X 49.009 ms !X bash-2.05b# dig www2.beerstud.us ; DiG 8.3 www2.beerstud.us ;; res options: init recurs defnam dnsrch ;; got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 13620 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5 ;; QUERY SECTION: ;; www2.beerstud.us, type = A, class = IN ;; ANSWER SECTION: www2.beerstud.us. 1M IN A 216.45.232.47 ;; AUTHORITY SECTION: beerstud.us.23h57m1s IN NS ns2.mydyndns.org. bash-2.05b# ping www2.beerstud.us PING www2.beerstud.us (216.45.232.47): 56 data bytes 36 bytes from ip2.159.45.216.susc.suscom.net (216.45.159.2): Destination Host Unreachable Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 cb03 0 35 01 5173 66.221.101.248 216.45.232.47 bash-2.05b# traceroute www2.beerstud.us traceroute to www2.beerstud.us (216.45.232.47), 64 hops max, 44 byte packets 1 66.221.96.1 (66.221.96.1) 0.262 ms 0.205 ms 0.309 ms 2 f1-g1-c1.propagation.net (66.34.255.1) 0.901 ms 0.997 ms 1.139 ms 3 gige-g6-0-601.gsr12012.dal.he.net (216.218.217.181) 2.120 ms 1.831 ms 2.193 ms 4 sp0-2-DLLSTXRI.broadwing.com (206.223.118.72) 2.992 ms 2.937 ms 2.871 ms 5 216.140.5.65 (216.140.5.65) 3.366 ms 3.562 ms 3.369 ms 6 p2-1.c0.ftwo.broadwing.net (216.140.4.225) 3.956 ms 216.140.5.41 (216.140.5.41) 4.190 ms 4.163 ms 7 p4-0.c0.atln.broadwing.net (216.140.17.114) 47.602 ms s7-3-0.c1.atln.broadwing.net (216.140.17.110) 47.033 ms p4-0.c0.atln.broadwing.net (216.140.17.114) 47.114 ms 8 so7-1-0.C1.wash.broadwing.net (216.140.8.21) 48.129 ms p3-0.c0.wash.broadwing.net (216.140.8.109) 47.970 ms so7-1-0.C1.wash.broadwing.net (216.140.8.21) 46.314 ms 9 p6-0.c0.nwyk.broadwing.net (216.140.17.122) 54.416 ms 68.527 ms so-5-0-0.c1.nwyk.broadwing.net (216.140.17.118) 60.054 ms 10 p1-0-0.a1.nwyk.broadwing.net (216.140.10.14) 53.376 ms s2-0-0.a1.nwyk.broadwing.net (216.140.10.222) 51.697 ms 50.859 ms 11 65.90.201.102 (65.90.201.102) 49.940 ms 50.784 ms 50.264 ms 12 * * * 13 * ip2.159.45.216.susc.suscom.net (216.45.159.2) 49.181 ms !H * 14 * * * 15 * * * If you can't reach the host, then port 9545 is irrelevant. Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still trying to get my site up!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gerard Seibert wrote: On Sunday, June 26, 2005 8:47:41 PM John Brooks [EMAIL PROTECTED] wrote: $do you have any kind of firewall? from the outside world port 9545 $is closed. so either it is being blocked, you are not actually $listening on it, or there is no port forwarding on your gateway. $ $run this on the box itself and post the output: $ netstat -na | grep LISTEN $ $try to connect from another host on your network: $ http://192.168.0.4:9545 $ $then try: $ http://192.168.0.4:80 $ $-- $John Brooks $[EMAIL PROTECTED] $ $ -Original Message- $ From: [EMAIL PROTECTED] $ [mailto:[EMAIL PROTECTED] Behalf Of Gerard Seibert $ Sent: Sunday, June 26, 2005 6:07 PM $ To: freebsd-questions $ Subject: Still trying to get my site up! $ $ $ Thanks to several individuals, I have almost gotten my Apache2 server $ working. Almost, but not quite. $ $ My ISP blocks port 80; therefore I am using a redirect from DynDNS.org to $ redirect to an alias using port 9545. $ $ The 'beerstud.us' redirects to 'www2.beerstud.us:9545' $ $ From my FreeBSD box, if I type: lynx http://beerstud.us, I see the $ following message: Using http://www2.beerstud.us:9545/. The connection is $ made and the index.htm file is displayed. $ $ However, I am unable to reach this site from any other computer. $ Eventually, the request will time out and I receive an error message $ telling me that the site is not available. $ $ I am not sure what I am doing wrong at this point. I have posted the $ following files if anyone feels ambitious enough to look them over for me. $ $ httpd.conf = http://www.seibercom.us/FreeBSD/httpd.conf $ $ hosts = http://www.seibercom.us/FreeBSD/hosts $ $ This is the output from ifconfig -a $ net-card.txt = http://www.seibercom.us/FreeBSD/net-card.txt $ $ resolv.conf = http://www.seibercom.us/FreeBSD/resolv.conf $ $ The 'hosts' file has a pretty good description of my network in it. I $ double checked my router, and I believe it is configured $ correctly to pass $ port 9545 through. $ $ -- $ Thanks! $ $ Gerard Seibert $ [EMAIL PROTECTED] $ ** Reply Separator ** Monday, June 27, 2005 6:48:35 AM The netstat -na | grep LISTEN command produces this output: tcp40 0 *.139 *.* LISTEN tcp40 0 *.445 *.* LISTEN tcp40 0 *.901 *.* LISTEN tcp46 0 0 *.9545 *.* LISTEN tcp40 0 127.0.0.1.25 *.* LISTEN Both http://192,168.0.4:9545 goes to my site. The http://192.168.0.4:80 produces this error: Looking up 192.168.0.4 Making HTTP connection to 192.168.0.4 Alert!: Unable to connect to remote host. lynx: Can't access startfile http://192.168.0.4/ Dear Gerard looks like there is no server running on port 80, may we have a look into your httpd.conf file? Greetings Oliver Leitner Technical Staff http://www.shells.at -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCv91tWvEVE8MtwbgRAqETAJ9aFtJ8QCJhhrFCgADkaKK8PrAkywCgnprt U1jTSUmErKIfj+JG0MxL7nM= =VhmQ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still trying to get my site up!
-Original Message- From: Garrett Cooper [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 9:23 PM To: Ted Mittelstaedt Subject: Re: Still trying to get my site up! Ted Mittelstaedt wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gerard Seibert Sent: Monday, June 27, 2005 6:15 AM To: Oliver Leitner Cc: John Brooks; FreeBSD Question Subject: Re[2]: Still trying to get my site up! My new problem is how do I do an FTP into the site. Well, you first have to FTP into www2.beerstud.us as the FTP protocol does not have any way to create a redirect the way that dydns is doing for you with their web server. Second, if your ISP is so stupid as to block incoming port 80 yet allow people to run web servers on any other port number, then it is quite likely that they are stupid enough to block incoming port 21 (the FTP port) yet allow incoming FTP on any other port. In which case you just run your ftp daemon and your command line ftp client program with the -P option and choose some convenient port number. I just tried using WS~Pro from a WixXP machine, but that failed. Don't know about that one however the WS_FTP that is the freeware one has a Advanced tab on the site config that allows you to specify the remote port. Ted Ted's advise is really good considering that more ftpd's run on non-standard ports than httpd's, or at least what I've seen so far. Besides, if you have to serve via FTP then just use an ftpd instead of obfuscating transfers via httpd; ftpd is much better at helping people get files than http anyhow ;). I say get rid of the ISP and find a better one. Any ISP that actively blocks port 80-a port which should be allowed as a backup port for programs-isn't really setup correctly and I doubt that they have all of your best interests in mind when making decisions. -Garrett Drat. Did it again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still trying to get my site up!
Gerard Seibert wrote: Thanks to several individuals, I have almost gotten my Apache2 server working. Almost, but not quite. My ISP blocks port 80; therefore I am using a redirect from DynDNS.org to redirect to an alias using port 9545. The 'beerstud.us' redirects to 'www2.beerstud.us:9545' From my FreeBSD box, if I type: lynx http://beerstud.us, I see the following message: Using http://www2.beerstud.us:9545/. The connection is made and the index.htm file is displayed. However, I am unable to reach this site from any other computer. Eventually, the request will time out and I receive an error message telling me that the site is not available. I am not sure what I am doing wrong at this point. I have posted the following files if anyone feels ambitious enough to look them over for me. httpd.conf =http://www.seibercom.us/FreeBSD/httpd.conf hosts=http://www.seibercom.us/FreeBSD/hosts This is the output from ifconfig -a net-card.txt=http://www.seibercom.us/FreeBSD/net-card.txt resolv.conf=http://www.seibercom.us/FreeBSD/resolv.conf The 'hosts' file has a pretty good description of my network in it. I double checked my router, and I believe it is configured correctly to pass port 9545 through. Hi, Just checked www2.beerstud.us:9545, the connection fails.. Are you sure that you have enabled port forwarding in the router? - Sarath ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still trying to get my site up!
Sarath ER wrote: Gerard Seibert wrote: Thanks to several individuals, I have almost gotten my Apache2 server working. Almost, but not quite. My ISP blocks port 80; therefore I am using a redirect from DynDNS.org to redirect to an alias using port 9545. The 'beerstud.us' redirects to 'www2.beerstud.us:9545' From my FreeBSD box, if I type: lynx http://beerstud.us, I see the following message: Using http://www2.beerstud.us:9545/. The connection is made and the index.htm file is displayed. However, I am unable to reach this site from any other computer. Eventually, the request will time out and I receive an error message telling me that the site is not available. I am not sure what I am doing wrong at this point. I have posted the following files if anyone feels ambitious enough to look them over for me. Sarath, I will see if I can rephrase some of this, and at least help *MY* understanding. If your ISP is blocking port 80, then the fix absolutely must fall into one of two categories: either you can find out how your ISP is blocking it, and do a workaround of that, or you must have someone else perform a service for you, having the required URL changed to be the correct base port (not 80, and I would myself choose 8080, if your ISP didn't block that also). Nice thing about that, your friendly apache-friend isn't going to lose any bigtime bandwidth, because it's still being served from your machine, your friend is merely serving to redirect the port, not actually serve it. Now, I will make the assumption here that the above paragraph is mostly right. You could use ethereal very simply to check and make sure of it. One screwup would be to have the redirect be close, but not actually what it should be, and it's really, really easy to read and check this. I'd bet it as either a very likely thing to be, OR while you do it, you are pretty likely to spot the real problem. Go give it a try. Ethereal is such a great tool that you can't really lose here, learning how to use it, you're looking at a win-win situation. httpd.conf =http://www.seibercom.us/FreeBSD/httpd.conf hosts=http://www.seibercom.us/FreeBSD/hosts This is the output from ifconfig -a net-card.txt=http://www.seibercom.us/FreeBSD/net-card.txt resolv.conf=http://www.seibercom.us/FreeBSD/resolv.conf The 'hosts' file has a pretty good description of my network in it. I double checked my router, and I believe it is configured correctly to pass port 9545 through. Hi, Just checked www2.beerstud.us:9545, the connection fails.. Are you sure that you have enabled port forwarding in the router? - Sarath ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Still trying to get my site up!
do you have any kind of firewall? from the outside world port 9545 is closed. so either it is being blocked, you are not actually listening on it, or there is no port forwarding on your gateway. run this on the box itself and post the output: netstat -na | grep LISTEN try to connect from another host on your network: http://192.168.0.4:9545 then try: http://192.168.0.4:80 -- John Brooks [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gerard Seibert Sent: Sunday, June 26, 2005 6:07 PM To: freebsd-questions Subject: Still trying to get my site up! Thanks to several individuals, I have almost gotten my Apache2 server working. Almost, but not quite. My ISP blocks port 80; therefore I am using a redirect from DynDNS.org to redirect to an alias using port 9545. The 'beerstud.us' redirects to 'www2.beerstud.us:9545' From my FreeBSD box, if I type: lynx http://beerstud.us, I see the following message: Using http://www2.beerstud.us:9545/. The connection is made and the index.htm file is displayed. However, I am unable to reach this site from any other computer. Eventually, the request will time out and I receive an error message telling me that the site is not available. I am not sure what I am doing wrong at this point. I have posted the following files if anyone feels ambitious enough to look them over for me. httpd.conf = http://www.seibercom.us/FreeBSD/httpd.conf hosts = http://www.seibercom.us/FreeBSD/hosts This is the output from ifconfig -a net-card.txt = http://www.seibercom.us/FreeBSD/net-card.txt resolv.conf = http://www.seibercom.us/FreeBSD/resolv.conf The 'hosts' file has a pretty good description of my network in it. I double checked my router, and I believe it is configured correctly to pass port 9545 through. -- Thanks! Gerard Seibert [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Still trying to get my site up!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gerard Seibert Sent: Sunday, June 26, 2005 4:07 PM To: freebsd-questions Subject: Still trying to get my site up! Thanks to several individuals, I have almost gotten my Apache2 server working. Almost, but not quite. My ISP blocks port 80; therefore I am using a redirect from DynDNS.org to redirect to an alias using port 9545. No, you are not. You cannot redirect to a specific port using the DNS system. Currently dydns.org has beerstud.us pointing to IP address 63.208.196.110 If that is your IP address then hosts on the Internet that query www.beerstud.us will go to port 80 on that IP address. If that isn't your IP number then it must be an IP address of a webhost that will issue a HTTP redirect when it gets a query to port 80 on your beerstud.us URL. The 'beerstud.us' redirects to 'www2.beerstud.us:9545' From my FreeBSD box, if I type: lynx http://beerstud.us, I see the following message: Using http://www2.beerstud.us:9545/. The connection is made and the index.htm file is displayed. However, I am unable to reach this site from any other computer. Eventually, the request will time out and I receive an error message telling me that the site is not available. I am not sure what I am doing wrong at this point. You need to contact the support department of your ISP. I don't understand why you think that your ISP is just blocking port 80 and not any other port. There are firewalls out there nowadays smart enough to see an incoming HTTP request and block it no matter what port it's coming in on. If your ISP is blocking port 80 that probably means you haven't paid for an enhanced account that will allow you to run a server. If that is the case and your ISP is making money off allowing ports to be open for customers, then I would think that they probably have one of those firewalls setup that blocks incoming HTTP get requests no matter what port they come in on. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
