On 4/8/2010 1:57 PM, David Lemcoe wrote:
> Hello all. I'm in the process of making a small server farm based mostly
> on Windows Server 2003. For simplicity's sake, the only non-2003 server
> will be a CentOS 5.4 server running only vsftpd, httpd, and mysqld. My
> plan is to have this server in a 2003 Server's network receiving a DHCP
> address from the Domain Controller.
>
> Currently, I have two other (non-DC) servers running with no issues on
> the domain. NAT works as it should, and internet access is just fine.
> The CentOS box on the same network will not receive an IP address (only
> through static configuration, the non-DC 2003 boxes have no problem
> receiving an IP and DNS settings with auto settings) or get online. Even
> when defining a static IP on the CentOS box, there is no Internet
> access, unlike to the other clients. My question is, what could be
> restricting the DHCP and DNS information to the CentOS host, and why
> can't I access the internet/NAT forward a web server?
>
> To summarize, I have four machines involved, all located on the same
> network:
>
> * Machine 1 - Windows Server 2003 Enterprise - Domain Controller,
> DHCP server, DNS server, NAT server.
> * Machine 2 - Windows Server 2003 Enterprise - Domain member,
> Exchange server.
> o Receives DHCP and DNS information with automatic network
> settings.
> o Has internet access through NAT.
> o NAT forwards ports to this host.
> * Machine 3 - Windows Server 2003 Enterprise - Domain member,
> Sharepoint Server.
> o Receives DHCP and DNS information with automatic network
> settings.
> o Has internet access through NAT.
> o NAT forwards ports to this host.
> * *Machine 4* - CentOS 5.4 - On same network as other clients, hosts
> web server.
> o Does *NOT *receive DHCP address or DNS information.
> o Has *no *internet access
> o NAT does *NOT *forward correctly.
>
> I am looking for a solution to get the CentOS server on the network like
> the other clients.
Centos works normally with standard DHCP servers and obviously would
know nothing about upstream NAT handling. There must be some sort of
restriction imposed by the Windows server in this scenario.
--
Les Mikesell
lesmikesell at gmail.com