can ping but can't access web server

March 4, 2010 at 13:50:22
Specs: Linux, 2.4 P4/1GB
We recently had to put our helpdesk sever on a public IP address. We can access it on the local IP address within our network. But the only computers outside our network that can access it is networks with the same ip subnet as ours. We are on say, "aaa.bbb.ddd.1" gateway. Anybody outside that number can ping the web address (helpdesk.blahblah.blah) but can't access it via the web. We have several accounts that all have (aaa.bbb.ddd.1) gateway and they can access it. But if you had (aaa.bbb.eee.1) You can ping it but don't have web access. Any thoughts on why this is. Is it firewall? DNS? We are running ClearOS for our gateway. Content filter turned off. We put it on a public IP because nobody could access it via web externally or locally with it behind our gateway.
Anything would be appreciated.

See More: can ping but cant access web server

Report •

March 4, 2010 at 14:49:15
We recently had to put our helpdesk sever on a public IP address.

If you don't mind me asking......why?

I don't know your setup but lets take a look at a simple one:

Internet >> SOHO Router >> switch(es) >> Clients/Servers

Now lets say you want to be able to allow remote access from external sites to an internal server located within your LAN.

A typical SOHO router, as well as proving DHCP and NAT will also provid firewall protection. Most, if not all SOHO Router's also allow you to do what's called a port forward which allows you to direct external access to an internal resource. Alternatively, you could also put the server in the DMZ in order to allow external access to it.

So now, with a simple SOHO Router, you can have two different methods for accessing an internal server without hanging it out on the internet with an external IP address.

So I guess what I'm wondering is, why you haven't done something like this (ie: either a port forward to an internal resource or, move the internal resource into the DMZ)?

Report •

March 5, 2010 at 07:36:49
We have tried this. We had serious trouble with our gateway the other day. We spent two days trying to get it back up and running correctly. It was one of the strangest things i've ever seen. We installed the gateway on three different computers 4 or 5 times. And every time we did it something new would go wrong. From painfully slow boot times to server and internet access problems. If we could get two of our servers on the internet, three more wouldn't work at all. Internet access would just quit out of the blue. NOTHING would work at the same time. We finally got everything but the helpdesk to work. No matter what we did on the gateway, Port forward, DMZ, 1 to 1 Nat, Host list, disable firewall, it didn't matter. We could ping the web address but could not access from the web externally.

What we have setup is Cable Modem >>External Switch >>Gateway >>Internal Switch >> Clients/Servers. The external switch is for devices that need one of our public ip's like a linksys router that runs a connection to our postoffice/bookstore via Fiber. And now our helpdesk server.

Report •
Related Solutions

Ask Question