DHCP - how to disble on server

We assign IP addresses to our client computers manually. We do not want
DHCP running on our Windows 2003 server std edition. We are getting IP
address conflicts. When we delete the DHCP server in the DHCP console,
it eventually begins to run again or if we reboot it is reactivated.

I assume we disable the DHCP Server service in the Services...

Thank you!

Hi!

You can remove DHCP server through Manage Your Server tool or Add/Remove
programs, Add/Remove Windows Components, Network Services. Or you can just
set up DHCP correct scope which will not cause IP conflicts.

HTH

Toni


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> We assign IP addresses to our client computers manually. We do not want
> DHCP running on our Windows 2003 server std edition. We are getting IP
> address conflicts. When we delete the DHCP server in the DHCP console,
> it eventually begins to run again or if we reboot it is reactivated.
>
> I assume we disable the DHCP Server service in the Services...
>
> Thank you!
>

I tried through the manage your server tool but must be doing something
wrong as it shows DHCP running. I deleted the server/scope here to get
to this point and there is no scope address showing like before. I
would define a scope however having a problem with DHCP and gateway
assignments. DHCP assigns the proper gateway & DNS (Server's internal
NIC) but clients cannot get to Internet unless I manually assign IP,
DG, and DNS int he TCP/IP properties. I only have 4 client computers so
no big deal but would liket o figure it out.

Anyway, I'll try the add/remove programs;however, right now I have no
conflicts popping up. Thanks


T. Uranjek wrote:
> Hi!
>
> You can remove DHCP server through Manage Your Server tool or Add/Remove
> programs, Add/Remove Windows Components, Network Services. Or you can just
> set up DHCP correct scope which will not cause IP conflicts.
>
> HTH
>
> Toni
>
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) oups.com...
> > We assign IP addresses to our client computers manually. We do not want
> > DHCP running on our Windows 2003 server std edition. We are getting IP
> > address conflicts. When we delete the DHCP server in the DHCP console,
> > it eventually begins to run again or if we reboot it is reactivated.
> >
> > I assume we disable the DHCP Server service in the Services...
> >
> > Thank you!
> >

In news:(E-Mail Removed) oups.com,
(E-Mail Removed) <(E-Mail Removed)> typed:
> We assign IP addresses to our client computers manually. We do not
> want DHCP running on our Windows 2003 server std edition. We are
> getting IP address conflicts. When we delete the DHCP server in the
> DHCP console, it eventually begins to run again or if we reboot it is
> reactivated.
>
> I assume we disable the DHCP Server service in the Services...
>
> Thank you!

Yes, you can disable the DHCP server service, and this will work.
That said, why would you want to use static IPs for clients? What's the
value in that? I haven't done that since I was using Netware 3x!

When I used DHCP for clients, the clients could not connect to the
Internet even though the correct DNS & Gateway IPs were showing on the
clients when I did IPconfig /all. So I manually assigned this
information and everything was ok.
Also, I like knowing the IP addresses for troubleshooting over the
phone and for RDC connections. This is a small network so easy to take
care of.

Thanks,


Lanwench [MVP - Exchange] wrote:
> In news:(E-Mail Removed) oups.com,
> (E-Mail Removed) <(E-Mail Removed)> typed:
> > We assign IP addresses to our client computers manually. We do not
> > want DHCP running on our Windows 2003 server std edition. We are
> > getting IP address conflicts. When we delete the DHCP server in the
> > DHCP console, it eventually begins to run again or if we reboot it is
> > reactivated.
> >
> > I assume we disable the DHCP Server service in the Services...
> >
> > Thank you!
>
> Yes, you can disable the DHCP server service, and this will work.
> That said, why would you want to use static IPs for clients? What's the
> value in that? I haven't done that since I was using Netware 3x!

In news:(E-Mail Removed) ups.com,
(E-Mail Removed) <(E-Mail Removed)> typed:
> When I used DHCP for clients, the clients could not connect to the
> Internet even though the correct DNS & Gateway IPs were showing on the
> clients when I did IPconfig /all. So I manually assigned this
> information and everything was ok.
> Also, I like knowing the IP addresses for troubleshooting over the
> phone and for RDC connections. This is a small network so easy to take
> care of.

I would've done some troubleshooting to fix the DHCP errors - I can't
imagine they would've been that tough to work out. I like central management
of this stuff, even on small networks, but if this works for you, it's your
network!


>
> Thanks,
>
>
> Lanwench [MVP - Exchange] wrote:
>> In news:(E-Mail Removed) oups.com,
>> (E-Mail Removed) <(E-Mail Removed)> typed:
>>> We assign IP addresses to our client computers manually. We do not
>>> want DHCP running on our Windows 2003 server std edition. We are
>>> getting IP address conflicts. When we delete the DHCP server in the
>>> DHCP console, it eventually begins to run again or if we reboot it
>>> is reactivated.
>>>
>>> I assume we disable the DHCP Server service in the Services...
>>>
>>> Thank you!
>>
>> Yes, you can disable the DHCP server service, and this will work.
>> That said, why would you want to use static IPs for clients? What's
>> the value in that? I haven't done that since I was using Netware 3x!