logo
Apache Lounge
Webmasters

 

About Forum Index Downloads Search Register Log in RSS X


Keep Server Online

If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.

or

Bitcoin

A donation makes a contribution towards the costs, the time and effort that's going in this site and building.

Thank You! Steffen

Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
Post new topic   Forum Index -> Apache View previous topic :: View next topic
Reply to topic   Topic: Cannot connect to my server
Author
blackdust



Joined: 21 Sep 2006
Posts: 4

PostPosted: Thu 21 Sep '06 1:32    Post subject: Cannot connect to my server Reply with quote

I am running XAMPP on Win2K Pro inside a virtual machine. Everything was ok but now all the sudden I cannot connect to my server and event vwr is throwing up errors to do with Apache.

I was playing about with Filezilla but I don't think that would of caused Apache to stop working. The only other thing I had installed on my guest system apart from XAMPP was Webwall which is a web firewall application which may have caused some problem somewhere, I have since uninstalled it. I also installed Bit Torrent on my host machine but I doubt that would of caused any probs with the guest and Apache?

The error's are:

Quote:
The Apache service named reported the following error:
>>> Unable to open logs .

The Apache service named reported the following error:
>>> no listening sockets available, shutting down .

The Apache service named reported the following error:
>>> (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80.


Netstat -an shows the following:

Quote:
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:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1028 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1029 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1030 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1031 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1032 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1033 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1034 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1036 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1037 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1038 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1039 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1040 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1041 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1042 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1043 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1044 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1045 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1046 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1047 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1048 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1049 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1050 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1051 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1052 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1053 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1054 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1055 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1056 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1057 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1058 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1059 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1060 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1061 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1062 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1063 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1064 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1065 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1066 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1067 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1068 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1069 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1070 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:1071 127.0.0.1:3306 TIME_WAIT
TCP 127.0.0.1:3306 127.0.0.1:1027 TIME_WAIT
TCP 192.168.2.2:139 0.0.0.0:0 LISTENING
TCP 192.168.2.2:445 192.168.2.5:2582 ESTABLISHED
UDP 0.0.0.0:135 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:1026 *:*
UDP 192.168.2.2:137 *:*
UDP 192.168.2.2:138 *:*
UDP 192.168.2.2:500 *:*


XAMPP control panel is showing that Apache/MySQL are running but in the status page for XAMPP shows:

Quote:
MySQL database DEACTIVATED
PHP DEACTIVATED
HTTPS (SSL) ACTIVATED
Common Gateway Interface (CGI) DEACTIVATED
Server Side Includes (SSI) DEACTIVATED
SMTP Service DEACTIVATED
FTP Service DEACTIVATED <--- I turned it off for now


ETA: Apache is listening on 12.34.56.78:80, have tried both 0.0.0.0:80 & 127.0.0.1 but with no luck.
Back to top
James Blond
Moderator


Joined: 19 Jan 2006
Posts: 7373
Location: Germany, Next to Hamburg

PostPosted: Thu 21 Sep '06 9:09    Post subject: Reply with quote

Did you change something in the httpd.conf?
Which Virtual machine do you use?

To get the ip from the virtual machine type in the console (cmd) of the virtual machine ipconfig
Back to top
blackdust



Joined: 21 Sep 2006
Posts: 4

PostPosted: Thu 21 Sep '06 10:36    Post subject: Reply with quote

It's GSX Server & I already got my IP (if you mean LAN) which 192.168.2.2 - and no I haven't changed any settings in httpd.conf, also done a fresh reinstall and still no luck.
Back to top
James Blond
Moderator


Joined: 19 Jan 2006
Posts: 7373
Location: Germany, Next to Hamburg

PostPosted: Thu 21 Sep '06 11:07    Post subject: Reply with quote

Hm, ok GSX Server from VMWare!
Two things I know that can run wrong with that. Installed VMWare Tools on the virtual machine? Secondly you have to set the the network connection to NAT. I noticed that bridged does not allways run well under windows.

Hope that helps
Back to top
blackdust



Joined: 21 Sep 2006
Posts: 4

PostPosted: Thu 21 Sep '06 11:21    Post subject: Reply with quote

I had changed to NAT and I have VMtools installed.

I have since changed from using DynDNS to No-IP, I ping my no-ip address with a reply but I couldn't do that with dyndns after a few hours of use.

any way, it's still not connecting. i have tried changing ports to 8080 from in httpd.conf and still no joy.

By the way, yeserday my guest IP was 192.168.2.2 I get the following in ipconfig

Connection-specific DNS Suffix . : localdomain
IP Address. . . . . . . . . . . . : 192.168.139.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.139.2

I think thats the problem as I have open all the right ports on 192.168.2.2
Back to top
blackdust



Joined: 21 Sep 2006
Posts: 4

PostPosted: Thu 21 Sep '06 12:48    Post subject: Reply with quote

I've nailed it! When my IP address and gateway changed to one given by vmware I had to change my forwarded ports in my router from *.*.2.2 to my hosts lan IP.

Thanks for your help!
Back to top


Reply to topic   Topic: Cannot connect to my server View previous topic :: View next topic
Post new topic   Forum Index -> Apache