win2003 server and dhcp

Im in a school network and we get our IP's from a other remote location, we
use their ip's/dns servers. Now what we wanna do is setup a new domain and
add all our PC's to this new domain. But what happens when we enable dhcl on
the 2003 server it crashes the network. Is there a way to get the domain
running without enabling DHCP on the win2003 server?

Well, a Windows DHCP server will not function properly if there is an
unauthorized DHCP server already on the network. But, I wouldn't expect it
to crash the network, so maybe there is something else going on here. In
any event:

1. You do not 'need' DHCP as long as you are willing to statically
configure all the client machines.

2. It sounds like you have a router or Windows Server which is relaying
DHCP requests to a remote DHCP server. If you can turn off the relay, then
you could enable the Windows 2003 DHCP server.

3. If you can persuade the people controlling the remote DHCP server to
change the DNS scope option to point to the IP of the new Windows 2003
Server, this may be the only necessary change.

Obviously, we don't have enough information to be sure of #2 and #3.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Bigshow" <u16638@uwe> wrote in message news:58c6e5e18d85e@uwe...
> Im in a school network and we get our IP's from a other remote location,
we
> use their ip's/dns servers. Now what we wanna do is setup a new domain and
> add all our PC's to this new domain. But what happens when we enable dhcl
on
> the 2003 server it crashes the network. Is there a way to get the domain
> running without enabling DHCP on the win2003 server?

ya I thought of hard coding the ip's but when I try to join the domain it
says :Error occurred when attempting to join the domain. Network path was not
found. and it is excessible, through current our current workgroup.

2. the main connection comes in then all the pc's are networked by a bunch of
hubs/switches
, how would ya turn off relaying in the 2003 server?.....in services prolly??

3. I would have to talk to them and find out, well the main tech here would
have to talk to them.


any other suggestions would be cool. thanks for the help so far.


Doug Sherman [MVP] wrote:
>Well, a Windows DHCP server will not function properly if there is an
>unauthorized DHCP server already on the network. But, I wouldn't expect it
>to crash the network, so maybe there is something else going on here. In
>any event:
>
>1. You do not 'need' DHCP as long as you are willing to statically
>configure all the client machines.
>
>2. It sounds like you have a router or Windows Server which is relaying
>DHCP requests to a remote DHCP server. If you can turn off the relay, then
>you could enable the Windows 2003 DHCP server.
>
>3. If you can persuade the people controlling the remote DHCP server to
>change the DNS scope option to point to the IP of the new Windows 2003
>Server, this may be the only necessary change.
>
>Obviously, we don't have enough information to be sure of #2 and #3.
>
>Doug Sherman
>MCSE, MCSA, MCP+I, MVP
>
>> Im in a school network and we get our IP's from a other remote location, we
>> use their ip's/dns servers. Now what we wanna do is setup a new domain and
>> add all our PC's to this new domain. But what happens when we enable dhcl on
>> the 2003 server it crashes the network. Is there a way to get the domain
>> running without enabling DHCP on the win2003 server?

The most common problems when joining a domain are DNS related. Make sure
the server has a fixed compatible IP; make sure it points only to itself for
DNS; make sure the various DNS subdomains exist - if not restart the
Netlogon service; check Event Viewer for errors. Make sure the clients
point only to the server IP for DNS.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Barry S" <u16638@uwe> wrote in message news:58c7d5f4fee2e@uwe...
> ya I thought of hard coding the ip's but when I try to join the domain it
> says :Error occurred when attempting to join the domain. Network path was
not
> found. and it is excessible, through current our current workgroup.
>
> 2. the main connection comes in then all the pc's are networked by a bunch
of
> hubs/switches
> , how would ya turn off relaying in the 2003 server?.....in services
prolly??
>
> 3. I would have to talk to them and find out, well the main tech here
would
> have to talk to them.
>
>
> any other suggestions would be cool. thanks for the help so far.
>
>
> Doug Sherman [MVP] wrote:
> >Well, a Windows DHCP server will not function properly if there is an
> >unauthorized DHCP server already on the network. But, I wouldn't expect
it
> >to crash the network, so maybe there is something else going on here. In
> >any event:
> >
> >1. You do not 'need' DHCP as long as you are willing to statically
> >configure all the client machines.
> >
> >2. It sounds like you have a router or Windows Server which is relaying
> >DHCP requests to a remote DHCP server. If you can turn off the relay,
then
> >you could enable the Windows 2003 DHCP server.
> >
> >3. If you can persuade the people controlling the remote DHCP server to
> >change the DNS scope option to point to the IP of the new Windows 2003
> >Server, this may be the only necessary change.
> >
> >Obviously, we don't have enough information to be sure of #2 and #3.
> >
> >Doug Sherman
> >MCSE, MCSA, MCP+I, MVP
> >
> >> Im in a school network and we get our IP's from a other remote
location, we
> >> use their ip's/dns servers. Now what we wanna do is setup a new domain
and
> >> add all our PC's to this new domain. But what happens when we enable
dhcl on
> >> the 2003 server it crashes the network. Is there a way to get the
domain
> >> running without enabling DHCP on the win2003 server?