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.
Can Ping But Can’t Access Web Server
Share
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)?