How do I stop separate DHCP service offering IPs to the wrong clients ?

Bit of a bizarre one this so here goes:

Main network in the office has a DHCP server offering IP's etc to all clients. No problem.

We have a Norton Ghost server that is connected to the office LAN on the first NIC card and gets its IP address from the Office address space.  

The Ghost server also has a secondary NIC card which is connected to a hub, and the prospective ghost clients are also connected to that hub, to create a separate LAN.

Now, the Ghost Server is running DHCP on a different IP range, so that any ghost clients connected to the hub automatically receive an IP address from the Ghost Server, so we can multicast images etc..

The problem is, when office clients ask for a new IP address, occasionally the Ghost Server is quickest to respond and so the office client ends up with an IP address which is in the wrong range and therefore breaks... SO...

How can I configure the Ghost Server DHCP, to only give out IP addresses to clients that have requested them on the second NIC card ?  -- Is is possible to bind the DHCP client to a particular NIC card ?

Any suggestions gratefully received!
grayp1Asked:
Who is Participating?
 
mikecrConnect With a Mentor Commented:
Since it is showing a local area connection and not an IP address, this is probably why. Assign a static IP to the NIC on the setup network for the same subnet that you are passing DHCP on. It sounds like what is happening is that both NICs in this box are set up for DHCP. They are getting an IP address from your regular network on both of them. Since these IP's are in the same subnet, the DHCP broadcasts are making it to your server and it is servicing the requests. By changing the IP address of the NIC on the setup network, you can bind to that subnet the DHCP traffic and not send it out over the whole network.
0
 
JconleyMCSECommented:
Listening....
0
 
SysExpertCommented:
I think that you need to disable the DHCP  server stuff on the first NIC and leave it on the second only.

You may need to switch the order of the NICs since ghost may default to using the first.

I would also check the symantec site's knowledge base !

I hope this helps !
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
vsamtaniCommented:
Why is the ghost server machine connected to the main office LAN at all?

If it's only so it can get an IP address, you would be better off setting a static IP address on the ghost server and then disconnecting it from the office lan completely.

I suspect that I'm missing something, though. More detail would help.

Vijay
0
 
grayp1Author Commented:
Thanks to all who've replied so far!

To fill in the gaps:
The first NIC card is connected to the Office Lan so we can access the Internet for drivers and the like, plus copy files from the servers to the newly ghosted machines.

At the moment we're just disconnecting the Office lan from the 1st NIC card, which obviously solves the problem, but if there is a way of having the two networks joined without DHCP problems, then thats what i'd prefer.. (lazy..;))
0
 
mikecrCommented:
Your basically screwed. I believe you will not be able to get around this. DHCP runs as a service on NT and binds to all network adapters located in it. If you were running Windows 2K you can go into the properties of the scope and bind it to the IP of a specific interface but you cannot do that on an NT machine as it is not supported. The only way I can think of to do this would be to put some type of router in between it and the network and have it drop the DHCP acks that it passes.
0
 
grayp1Author Commented:

Thanks Mikecr.. It is running Windows2k (sorry for not mentioning earlier)

I checked the Properties for the Scope and its binding to Local Connection 2, which is correct.. so why is it servicing requests for Local Connection 1 ??

0
 
mikecrCommented:
Are both of the boxes checked currently in there or just for the IP of your set up network?
0
 
grayp1Author Commented:

just the one box, with the IP address of the network.
0
 
grayp1Author Commented:
Thanks Mikecr.
0
 
mikecrCommented:
No problem....
0
All Courses

From novice to tech pro — start learning today.