Page 1 of 1
installing apache 2.0.55 on xp - unable to bind to port 80
Posted: Sat Apr 29, 2006 7:02 am
by raghavan20
this is the error i get when i try to run msi installer for windows
Code: Select all
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not b
d to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
any clues related to the error?
Posted: Sat Apr 29, 2006 7:45 am
by timvw
You probably already have something that is bound to port 80... IIS perhaps?
You can:
- run apache or IIS on another port
- bind apache and iis to specific ip addresses (instead of default bind to all:0.0.0.0)
Posted: Sat Apr 29, 2006 7:49 am
by feyd
Skype may also be using the port.
Posted: Sat Apr 29, 2006 8:06 am
by raghavan20
I have skype installed. I do not windows XP professional so IIS cannot be running...but thanks for the hint, I will try to use 8080 and see what happens.
EDIT: my doubt is, why a chat application wants to use port allocated to Web servers?
Posted: Sat Apr 29, 2006 8:39 am
by raghavan20
I have successfully made the PHP 5 to work with apache. I have a doubt, how do I make the system to be accessible through global IP.
let me say that my ip is : 80.x.x.x
apache running at port: 8080
if i try, http://80.x.x.x:8080,,,it does not work...why...do I have to do some configuration somewhere to make it work???
Posted: Sat Apr 29, 2006 8:48 am
by nickvd
Assuming you are running a router on your network (to share your network for example). You will need to forward the needed ports to the system running apache... It would also allow you to use port 80 for the outside world, but have the router forward the traffic to apache at port 8080.
The configuration of this is highly dependant on your router, I point you to
http://www.portforward.com/
Hope this helps...
ps. If something on your system is already listening on port 80, and you dont know what could be, I STRONGLY suggest you run some anti spyware/virus software scans on your system to ensure you are clean. No software should need to bind to port 80 unless it's a web server, or you otherwise know about it...
also try 'netstat -a -n' from command prompt to see all the socket stuff listening on your system.
Posted: Sat Apr 29, 2006 8:54 am
by raghavan20
when I ran the netstat it is showing me as one of the entries, which I am worried about..
Code: Select all
TCP 192.168.0.101:4324 66.249.87.104:80 ESTABLISHED
EDIT: When I typed in the IP, it goes to google but what is the google doing with port 80?
EDIT: I have uninstalled a google player, but I come to understand that the recipient port was 80 at google but it was using another port in my system.
the entire list is....
Code: Select all
C:\www\Apache2\bin>netstat -a -n
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5051 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5101 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:38671 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1026 0.0.0.0:0 LISTENING
TCP 127.0.0.1:3950 127.0.0.1:3951 ESTABLISHED
TCP 127.0.0.1:3951 127.0.0.1:3950 ESTABLISHED
TCP 127.0.0.1:8080 127.0.0.1:4347 TIME_WAIT
TCP 127.0.0.1:8080 127.0.0.1:4348 TIME_WAIT
TCP 127.0.0.1:10025 0.0.0.0:0 LISTENING
TCP 127.0.0.1:10110 0.0.0.0:0 LISTENING
TCP 192.168.0.101:139 0.0.0.0:0 LISTENING
TCP 192.168.0.101:3817 85.131.97.59:6964 ESTABLISHED
TCP 192.168.0.101:3904 216.155.193.132:5050 ESTABLISHED
TCP 192.168.0.101:3909 68.142.233.182:5061 ESTABLISHED
TCP 192.168.0.101:4340 68.142.233.182:80 ESTABLISHED
TCP 192.168.0.101:4349 192.168.0.102:139 TIME_WAIT
TCP 192.168.0.101:4350 63.247.70.254:80 CLOSE_WAIT
TCP 192.168.0.101:4351 66.249.87.104:80 ESTABLISHED
TCP 192.168.0.101:4352 63.247.70.254:80 CLOSE_WAIT
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1056 *:*
UDP 0.0.0.0:1089 *:*
UDP 0.0.0.0:1244 *:*
UDP 0.0.0.0:1269 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5051 *:*
UDP 0.0.0.0:38671 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1080 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:2413 *:*
UDP 127.0.0.1:3818 *:*
UDP 192.168.0.101:123 *:*
UDP 192.168.0.101:137 *:*
UDP 192.168.0.101:138 *:*
UDP 192.168.0.101:1900 *:*
Posted: Sat Apr 29, 2006 9:09 am
by raghavan20
I have finally configured the router to redirect the requests from 80 to 8080 in local system and it works now.
My doubt is now, how to set up ftp connections from remote systems to my local server so that my friends can upload and edit the files on my system?
Posted: Sat Apr 29, 2006 10:05 am
by timvw
ftp is a bit harder because 'ftp is broken by design (tm)'.
Whenever someone connects to an ftp server (typically port 21) your ftp server will reply. When that person requests data, your ftpd will open a connection (originating port 20) to that person... When users start a 'passive' ftp session both commands and data will be send through the same connection... Or make them use something better like scp (winscp and filezilla are nice clients for win32).
Posted: Sat Apr 29, 2006 10:29 am
by raghavan20
I have installed filezilla, I have created an account dev with password, but when I first try to connect using
ftp://127.0.0.1 using the above account and password but is says that it is not able to find home directory. I know I have not still configured where to get the files from.
1. timvw, can you tell me how to point the ftp server where to get the files from or the ftp server always directly connects from the root itself like Desktop in Windows???
2. my second question is how to let the filezilla to accept connections from public ip say, 82.x.x.x on port 21?
Thanks for your answers.
Posted: Sat Apr 29, 2006 10:40 am
by timvw
raghavan20 wrote:can you tell me how to point the ftp server where to get the files from or the ftp server always directly connects from the root itself like Desktop in Windows???
With the FileZilla server management tool you connect to your server..
Choose Edit, Groups in the menu (i prefer to configure rights for a group, afterwards i add users to that group).
In the Shared Folders you can choose the folders (and an eventual alias).
There is also a button button "Set as home dir" that allows you choose a selected folder as homedir.
raghavan20 wrote:
my second question is how to let the filezilla to accept connections from public ip say, 82.x.x.x on port 21?
Via Edit->Settings in the General settings there is an option IP Filter which allows you to disallow/grant connections..
(I don't remember if there was a good manual.. I do remember that it took a while to get it right.. but that was because i forgot that windows firewall was instructed to block all connections..

)
Posted: Sat Apr 29, 2006 11:02 am
by raghavan20
I have created a group and allowed access to few directories on my local system and created a new user who was made to belong this group so the user can now access the directories allowed to access through group configuration. Thanks for that help
my second question was not so specific...I actually meant the following
I have a local ip: 192.168.0.101 and a public ip: 81.x.x.x
thus if some one wants to access my system through ftp, then they should be able to access through
ftp://81.x.x.x
and this does not happen now
I hope that you could now understand what my problem is.
Posted: Sat Apr 29, 2006 11:12 am
by timvw
Afaik FileZilla Server will bind to all interfaces (* / 0.0.0.0) by default.. What does netstat -an say for port 21?
You still have to configure your router to redirect requests to your (internal) pc...
If users configure their ftp client to make a 'passive' connection this should work...
Check if your ISP blocks some ports (Eg: overhere we had a couple of isps that used to block all ports < 1024)
Posted: Sat Apr 29, 2006 11:18 am
by raghavan20
thanks for the timvw, i have now set up the virtual ftp server using dlink wizard....thanks very much...