• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 188
  • Last Modified:

Setting Up An Internal Webserver On LAN Client Behind Corporate Firewall

I want to set up a web server on one of my machines.  I have done this successfully with Apache.  I want to try to do the same with Abyss Web Server.  I have installed Abyss and it is running.  I can access my test page from the same machine using the localhost IP address.  I can also access the test page from the same machine using the machine's Ethernet IP address.  I cannot, however, access the page from another machine on the LAN using the Ethernet IP address.  I CAN ping the address from another client, so the connection and address are valid.  Abyss logs show no record of an attempted connection from another client.  Any suggestions?

Mike

0
shacho
Asked:
shacho
  • 5
  • 4
1 Solution
 
lkravenCommented:
What operating system are you running it under?  My guess is your local Windows firewall is blocking access.  Check and disable it?
0
 
shachoAuthor Commented:
XP Pro.  Have been trying to investigate the firewall config, but with limited success.  Looks like Windows firewall is disabled and McAfee Firewall (FireSvc.exe) is running.  I can't easily change the firewall settings as I am not logged in as admin.  That can be arranged, but at least I should be able to tell if that's causing the problem in the mean time, I would think.  Couldn't find any setting in the McAfee configuration utility and there is nothing in the McAfee logs (C:\Documents And Settings\All Users\Application Data\Host Intrusion Prevention) about blocking access.  Any ideas?



0
 
shachoAuthor Commented:
Disabled the firewall.  Still no go.

0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

 
lkravenCommented:
Are the two machines on the same subnet?

If there is a router, for instance, in between that is filtering, that may also explain it.  If they are on the same subnet, then there shouldn't be any interference from a router or firewall.

From one of the other LAN machines try this command:

telnet ip.of.your.server 80

You will be trying to telnet directly to the web server.  If it times out or is rejected something is blocking access to the service.  If you get some HTTP gibberish or a blank screen that closes when you hit enter, you have connected, and your problem is with the service itself.

If nothing is showing in the logs though, I strongly suspect McAfee is blocking port 80 access to your machine.  Most personal firewalls will block common services such as web (80, 443), mail (25, 110, 143) as a standard operating default.  You will need to configure any bypass it, but the easiest way to confirm is to shut it off temporarily and see if that resolves your problem.
0
 
shachoAuthor Commented:
I can connect via telnet and via ping.  So if the problem is with the service, why can I connect locally (from the host to the host), but not across the LAN?

0
 
lkravenCommented:
If you can telnet to the machine on port 80, but a web browser doesn't work, that is very strange.

Abyss itself can be configured to listen on certain IP addresses, but I'm not familiar enough with it to know whether or not it can be configured to only accept connections from certain IP addresses.

Am I correct in understanding that you are able to ping the machine from a remote machine, and that when you telnet to it (on port 80) you get a connection, but the web browser on a remote machine will not bring up a web page?

That is very strange indeed.  What is the behavior of the remote machine's web browser?  Does it take awhile and then report that the server timed out, is it a blank page, or some error?
0
 
shachoAuthor Commented:
>Am I correct in understanding...
Correct on all accounts.

>What is the behavior of the remote machine's web browser?
It times out after about 3 minutes.

Network Error (tcp_error)
A communication error occurred: ""
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.


0
 
lkravenCommented:
Are you using any proxy settings in the remote machine's web browser?  It is possible the proxy exists on a separate network that isn't local to your server's LAN IP address.  If you are, can you disable it and see if that works?
0
 
shachoAuthor Commented:
Ugh.  Somebody shoot me....
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now