appache webserver, dyndns.org

Okay, im trying to make a small webserver for my own personal use. (and for the hell of it)

However, im having some issues. With the main ones cleared up, heres me delema:
It doesnt work.

Now, heres what ive got:
Appache webserver, installed and running set to port 8080 (i think)
verizon DSL (which sucks and blocks port 80 (gr) )
router, with ports 80, 21, 8080-8085, and that funny pcanywhere one forwarded to my servers ip

router firewall on, but anonymous internet requests allowed.

Okay.
i CAN ping netman86.homelinux.net from another internet source.
i CAN NOT goto http://netman86.homelinux.net on another internet source
i CAN goto http://netman86.homelinux.net on my LAN

i CAN connect to my pcanywhere server with the hostname set to netman86.homelinux.net instead of my IP

i CAN NOT goto http://netman86.homelinux.net:8080/ from another internet source OR my lan, but i CAN go to http://netman86.homelinux.net:XXXX/ on BOTH LAN and other internet source. (and it works)
(where XXXX is the remote management port on my router)


also, if you happen to know where im supposed to put the files for my website so that i dont get the apache setup complete webpage, that would be nice...if not ill have to lift a finger and find out myself.



so...what am i missing?

Is the line that tells what port apache to listen on, double check this.

aha, it was set to 8082, from a previous experiment...i guess unintslling it and reinstalling it is of no use.

after changing it to 8080, and restarting the apache server, the results seem the same.

I'm reading your port 8080 as closed, so most likely your ISP isn't blocking it, and your router is forwarding it properly.

So it's something wrong with your webserver configuration. Try getting rid of the
Listen 80
line in your configuration, leaving only the Listen 8080 line.

If that doesn't work, what errors do you get in your apache logs (if any?)

listen 9=9= is hte only line in the conf file.

only think in the log files is in the error one, when i started and stopped the server a few times.

There's an error in the log file? What is it?

Try using the following to see what port apache is listening:


***NOTE: the apache process might be named httpd or something else, check and replace accordingly. ***

It should output something similar to this:

In my example my server is listening on 80 and 443.

untill i get my linux drivers down pat, im using apache on windows 2000...

according to the file its listening on 8080

and the error log only says that i stoped and restarted the server...several times.

also, the appache server was down for about 5 hours today, but my internet was still up...

anyways, during the install i chose port 8080...
the config file agrees

netstat -a -p
Then check with taskmanager for the current PID of apache and see which ports it has open

in task manager, after running netstat -a -p, there was apache.exe PID 564, and apache.exe pid 812.

no idea how to check ports...

playing with netstat i found nothing.

netstat -a -p jsut had the headers, no data.
netstat lited lots of stuff, i hadto ctrl+break the process so i wouldnt fall asleep...same iwht netstat-a

is there a way t ouse it to check the ports on a ceartian PID?

Windows netstat doesn't provide the pid, but, TCPView does. (and its free)

cool program. i had like 200 javaw's, ended one and they all turned red and went away. woo.

all it says is apache is listening... on http?

apache.exe 564 tcp portacomo:http portacomo:0 listening...

woo, i dont know what it means but i just crashed javaw and something ive never seen before with it!

That means its listening on port 80, where is the conf file located? Is there multiple conf files?

i honestly do not know, i goto apache http server on the start menu, and theres a configure folder...says "edit appache httpd.conf"

i am now running a sucessfull FTP server from this computer, so its definatley a port issue for the apache...help?

ftp://netman86.homelinux.net - whoot.
(now i just gotta gather all my freeware and put it there!)

After you edit your HTTPD.conf file, do you restart Apache? The changes don't go into effect until the Apache service is stoped and restarted, which may explain why your config changes aren't occuring.

JigPu