Printable View
With apache you can configure the server to only listen on some address (i.e. 192.168.0.1). The webserver will then only serve pages if you talk to it on that specific ip address. This is usefull if you have a multi-homed host. But by specificly configuring it to listen on i.e. 192.168.0.1 the webserver will not listen to requests for 127.0.0.1 anymore. Your problem is probably similar.
I checked httpd.conf and its set to listen as default
However when I put KeyFocus Web server back in, and i try to access my localhost, then I examine my event logs for xp, I get this:Quote:
#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
#Listen 3000
#Listen 12.34.56.78:80
apache did not produce any such events other then one regarding an improper shutdown of the service, but that was because I hit the reboot.Quote:
The description for Event ID ( 5 ) in Source ( KFSensor ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: .
You're getting errors for a honeypot in regards to your apache install? Or is the Apache going to be part of the honeypot? Could the honeypot (assuming you have one installed) be interfering with the apache install?
For those not aware: kfsensor is a commercial honeypot for windows.
I had kfsensor installed but uninstalled it before installing keyfocus web server, and before apache. I must not have read the event log clearly enough, as I did not realize it was not relating to the Web Server.
the sensor was removed the other day, prior to installing any web servers.
Could their be any "leftovers" then? Or are you going to get a new EventLog notice for us? :D
that event was the only one pertaining to kfsensor, there are events that ocured afterwards but non relating to web servers or kfsensor.
EDIT: I just did a search of my computer to see if any traces of kfsensor were still in there, there was no findings. I also just finished uninstalling apache, as I had uninstalled keyfocus web server last night. There are no servers installed now, I even removed my ftp server. I took another look over my system events, and also checked my hosts table again, and am now going to install keyfocus web server again.
I will let you know how it goes.
Ok the results are everything works perfectly, I can access localhost and also access my admin page. I don't understand how, but I am happy. I thank you to everyone who helped.
I would like to know what the cause was, I dont understand how it could have been the honeypot, since that was uninstalled prior to installing a web server, but maybe a setting was changed elsewhere in my system.
Baffles me. The web server I am only useing for my lan, since it is against my ISP TOS to run a web server, I should be ok to block out internet access with my firewall corect?
What was running the FTP server?
As for your ISP's TOS, if you block port 80 that should deal with any little "issues" they have. I've been running my Apache (with ACID/Snort) for about a year now and no complaints yet from Rogers. *shrug*
Go figure.
I am on Rogers too, so if i run the server on say 8080 that should be ok? Ive done this before, remaping to other ports but I noticed rogers kept trying to conect and it freaked me out
The ftp server was running on the same machine, the xp (browse master on my network)
I realize it's on the same machine but what software was it? IIS? WU-FTP?
And I don't know about Rogers. I've had friends turn on an FTP for 5 min and get nailed by them. While people like myself... *shrug*
Hit and miss. I think you'll be ok because their scanner checks for standard stuff AFAIK.