DHCP Shutdown? 2

[KZimmerman]

I'm in the MIS Dept for the American Red Cross

My current project is to set up a completely isolated network aside from our normal one, for the disaster command center. This separate network is not part of the domain, nor do we want it to be. The only thing in common with our network we want this one to have, is the firewall and internet connectivity. We have a separate server set up and configured as a DHCP for the DCC (disaster command center), but when we boot it up, the DHCP server sees our domain, and another DHCP server, tells us 'i'm not a part of this domain, and there's already a DHCP server running', and then shuts down.

Any ideas on why it would do this?

 

[Koonan]

You say isolated but how isolated? Is this "network" on a different subnet from the main network with Active Directory? Will this network have its own install of Active Directory?

Mike


=====================================
The good ole days weren't always good
and tomorrow ain't as bad as it seems
=====================================

 

[netometer]

Hi!
The easiest way to isolate the two DHCP servers is to configure the routing device between the two networks not to relay DHCP broadcasts.

NetoMeter

http://www.netometer.net

 

[KZimmerman]

net - looking into your solution. thanks....

 

[GlenJohnson]

'i'm not a part of this domain, and there's already a DHCP server running', and then shuts down.

Sounds like the new server is thinking it's a rogue server on the original network. When a dhcp server starts up, it tries to find if it's been authorized in active directory, and if it finds it's not authorized, it shuts itself off. The new server isn't as isolated as you think. Unplug the new server from the internet, or intranet, and start it up. Then do ipconfig /all and see what the server is thinking. Good luck.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.
TTinChicago
Johnson Computers

 

[KZimmerman]

Glen - i discovered that myself.... i do appreciate the assistance, we had to yank the thing completely out of the back of the 5509 and plug it directly into the DMZ on our firewall.... this has resolved the issue entirely
*does happy server dance*

 

[GlenJohnson]

Glad it worked out.
*Does happy server drink*



Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.
TTinChicago
Johnson Computers

 

[KZimmerman]

hahahha, oh man...

well here's an update on the final part of what has gone down regarding this whole 'isolated network'.

the story breaks down like this...
We originally were setting up this network, so anybody who would be working in the disaster recovery center this weekend (thanks alot francis) would be able to bring in any computer from anywhere, and jack in and be able to get onto the net, without putting our domain at risk. Now we've come to find out that we wont need the isolated network at all, because the command center is mostly going to be used as a call center. So myself and the entire MIS team have been busting our humps tryin to get this up, to get it up, only to learn that we have to basically undo everything.

Joy of joys eh?
*throws a rock @ hurricane francis for runing his Labor Day Weekend*

 

[GlenJohnson]

Let's hope francis doesn't throw it back. Good luck, you're gonna need it. Keep us informed.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.
TTinChicago
Johnson Computers