Setting up DHCP

Hello,

I'm trying to get Win 2003 server to act as a DHCP server. I think I've got
things set up correctly, but am having problems. The server has 2 NICs. One
has a normal static IP and is connected to a T1 router. The other has
address 192.168.2.1, and is meant to be the Internal DHCP gateway. I
installed DHCP and enabled routing and remote access.

First of all, I'm not sure I have the TCP IP settings correct for the
"internal" NIC. What IP address do I use for its gateway? Currently I've
left it blank. If I use the T1 router or the "outward pointing" NIC for its
gateway, I get warning messages about disjoint networks. When I connect a
client computer to the internal NIC, and try to get it to automatically get
an IP address, it doesn't work.

Any help would be appreciated.

Thanks,

Brian

Based on Microsoft article: A computer running a Windows Server 2003
operating system can perform as a multihomed DHCP server
By default, the service bindings depend on whether the first network
connection is configured dynamically or statically for TCP/IP.
If the first network connection uses a manually specified IP address, the
connection is enabled in server bindings.

1. The internal NIC gateway should be blank.
2. Make sure you enable IP routing.
3. Also check the NAT settings. This post may help too.

Solved: Issues with multihomed serverSolved: Issues with multihomed server
.... No workstation receives IP from windows DHCP. 2. If assigning static IP
to those workstations, they can ping each ...
http://www.chicagotech.net/netforums...ic.php?=&p=356


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Ideas Live" <(E-Mail Removed)> wrote in message
news:129DD61B-0A0F-4502-B5BD-(E-Mail Removed)...
> Hello,
>
> I'm trying to get Win 2003 server to act as a DHCP server. I think I've
> got
> things set up correctly, but am having problems. The server has 2 NICs.
> One
> has a normal static IP and is connected to a T1 router. The other has
> address 192.168.2.1, and is meant to be the Internal DHCP gateway. I
> installed DHCP and enabled routing and remote access.
>
> First of all, I'm not sure I have the TCP IP settings correct for the
> "internal" NIC. What IP address do I use for its gateway? Currently I've
> left it blank. If I use the T1 router or the "outward pointing" NIC for
> its
> gateway, I get warning messages about disjoint networks. When I connect a
> client computer to the internal NIC, and try to get it to automatically
> get
> an IP address, it doesn't work.
>
> Any help would be appreciated.
>
> Thanks,
>
> Brian

MS DHCP needs a Domain with a Domain Controller,...and a Domain Controller
should be on a machine with only one nic (except for SBS).
The DHCP Service has to be "authorized" by the Domain.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Ideas Live" <(E-Mail Removed)> wrote in message
news:129DD61B-0A0F-4502-B5BD-(E-Mail Removed)...
> Hello,
>
> I'm trying to get Win 2003 server to act as a DHCP server. I think I've
> got
> things set up correctly, but am having problems. The server has 2 NICs.
> One
> has a normal static IP and is connected to a T1 router. The other has
> address 192.168.2.1, and is meant to be the Internal DHCP gateway. I
> installed DHCP and enabled routing and remote access.
>
> First of all, I'm not sure I have the TCP IP settings correct for the
> "internal" NIC. What IP address do I use for its gateway? Currently I've
> left it blank. If I use the T1 router or the "outward pointing" NIC for
> its
> gateway, I get warning messages about disjoint networks. When I connect a
> client computer to the internal NIC, and try to get it to automatically
> get
> an IP address, it doesn't work.
>
> Any help would be appreciated.
>
> Thanks,
>
> Brian

Thanks for the info, and sorry for my ignorance.

My machine has 2 NICs and is a domain controller. Why should it only have 1
NIC? If it only had an internal NIC, how would the domain controller talk to
the internet? Through routing?

I do have it working somewhat. The clients are able to automatically get an
IP address. But I'm having to specify a DNS server address on the clients.
How do I get them to automatically get a DNS server address as well as an IP
address?

Also, I'm using Kerio WinRoute Firewall software on the server. If I have
the firewall turned on, I cannot use a browser on the client. As far as I
know, I'm allowing all services for the internal NIC. As soon as I turn of
the firewall, I'm able to browse on the client. Any ideas?

Brian

"Phillip Windell" wrote:

> MS DHCP needs a Domain with a Domain Controller,...and a Domain Controller
> should be on a machine with only one nic (except for SBS).
> The DHCP Service has to be "authorized" by the Domain.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
> "Ideas Live" <(E-Mail Removed)> wrote in message
> news:129DD61B-0A0F-4502-B5BD-(E-Mail Removed)...
> > Hello,
> >
> > I'm trying to get Win 2003 server to act as a DHCP server. I think I've
> > got
> > things set up correctly, but am having problems. The server has 2 NICs.
> > One
> > has a normal static IP and is connected to a T1 router. The other has
> > address 192.168.2.1, and is meant to be the Internal DHCP gateway. I
> > installed DHCP and enabled routing and remote access.
> >
> > First of all, I'm not sure I have the TCP IP settings correct for the
> > "internal" NIC. What IP address do I use for its gateway? Currently I've
> > left it blank. If I use the T1 router or the "outward pointing" NIC for
> > its
> > gateway, I get warning messages about disjoint networks. When I connect a
> > client computer to the internal NIC, and try to get it to automatically
> > get
> > an IP address, it doesn't work.
> >
> > Any help would be appreciated.
> >
> > Thanks,
> >
> > Brian
>
>
>

"Ideas Live" <(E-Mail Removed)> wrote in message
news77896FC-FD67-4729-AA52-(E-Mail Removed)...
> Thanks for the info, and sorry for my ignorance.
>
> My machine has 2 NICs and is a domain controller. Why should it only have
> 1
> NIC?

272294 - Active Directory Communication Fails on Multihomed Domain
Controllers
http://support.microsoft.com/default...b;en-us;272294

191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default...b;EN-US;191611

>If it only had an internal NIC, how would the domain controller talk to
> the internet?

Domain Controllers are not supposed to talk directly to the Internet. They
are to be isolated from and protected at all costs *from* the Internet.

> Through routing?

Through Firewalls or Proxys. All the the "home user" Firewall device are
commonly (and very *incorrectly* called "routers"). When I say firewall, I
mean a real device, not some software that you load on a machine as a "host
based" firewall.

> I do have it working somewhat. The clients are able to automatically get
> an
> IP address. But I'm having to specify a DNS server address on the
> clients.
> How do I get them to automatically get a DNS server address as well as an
> IP
> address?

The DNS Servers and the WINS Servers need to be added either to the Server
Options or the Scope Options in the configuration of the DHCP Service. The
best thing is for them to be Server Options since they would rarely change
and are not effected by by subnet (hence Scope) that the Client is in. Once
done the Client needs their TCP/IP Config refreshed. You can force it with
IPConfig or just reboot the machine,...rebooting usually works.

> Also, I'm using Kerio WinRoute Firewall software on the server. If I have
> the firewall turned on, I cannot use a browser on the client. As far as I
> know, I'm allowing all services for the internal NIC. As soon as I turn
> of
> the firewall, I'm able to browse on the client. Any ideas?

Get rid of that. It has no place on a Domain Controller. If you want a
Firewall and want the LAN Topology to be something logical and
dependable,...buy a cheap $70 "home user" Firewall like a Linksys, D-Link,
or whatever. If you can spend a couple thousand, buy a real Firewall or
build an ISA Server. There are also some in the "middleground" for a few
hundred dollars.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------