Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just installed a new server for replacing a Windows XP in a small office, the clients are windows pcs and the new CentOs 5.5 is running a LAMPP setup.

The clients are unable to connect to the server for using a WebApp (http://newserver)

The WebApp is working perfectly locally, so what did I miss? iptables? firewall?


share|improve this question
Can users access the server via IP address? i.e – Brian Mar 21 '11 at 19:21
@Brian, yes, they can.. – gustyaquino Mar 21 '11 at 19:51
up vote 2 down vote accepted

Just guessing - a DNS entry? You don't say you did that. /edit - no longer a guess. If you didn't edit DNS (or every HOSTS file), then of course the clients can't resolve the Domain Name to the IP address.

share|improve this answer
Is really necesary to specify a DNS entry in a isolated network? In the previous windows server wasn't. – gustyaquino Mar 21 '11 at 19:15
Yes. Something is required to translate names to IP addresses. You were using something to identify the old server previously. Either DNS and you didn't know it, or possibly NetBIOS or WINS. – mfinni Mar 21 '11 at 19:24
mfinni, how can I do that? – gustyaquino Mar 21 '11 at 19:37
What server(s) are your client machines using for DNS now? Add the entry there. – mfinni Mar 21 '11 at 19:57
@mfinni, thanks, I found a quick the solution here: – gustyaquino Mar 21 '11 at 22:56

A few things to get you started:

  • What type of error you do mean when you say "unable to connect"? The type of error you get here may help narrow in on the source of the issue. If it is a DNS error then your "newserver" host name is not being resolved. If it is a connection timeout type of error then it may be a server connectivity or Ethernet setup issue. An immediate "connection denied" type may be a misconfigured firewall. Any sort of Apache error page is likely a server misconfiguration.
  • Double-check the server's Ethernet configuration (ifconfig).
  • Try to ping/telnet/ssh/ftp into the server from a client machine (depending what services you have available on the server and network). If this doesn't work troubleshoot this issue in more detail until you find the cause and fix it.
share|improve this answer
The server name "newserver" cannot be resolved. I try with the IP address and is working just fine. I already changed the configuration in the file '/etc/sysconfig/network' and in the file '/etc/hosts'. Well, I renamed the local.localdomain to 'newserver'. Is that correct? – gustyaquino Mar 21 '11 at 18:56
Assuming you mean '/etc/hosts' on the server then this only will let the server access itself with the "newserver" name. Ideally you want whatever intranet DNS to correctly resolve the "newserver" host name. Temporarily you can also use the hosts file on the Windows clients (\Windows\system32\drivers\etc\hosts). – uesp Mar 21 '11 at 19:01
The alternative solution will work just great, the name 'oldserver' is correctly resolved by the network DNS and points to the old server wich is still operating. This let me believe that there's is something else to do with the new server. – gustyaquino Mar 21 '11 at 19:09

Check to ensure that you have allowed traffic on port 80 in your firewall config (/etc/sysconfig/iptables).

Also check your logs for httpd, message, security.

share|improve this answer
Mike, thanks, the server is allowing any client to connect by using the ip address. The issue seems to be related to the server's name: It cannot be resolved. – gustyaquino Mar 21 '11 at 19:13

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.