Networking Forums

Networking Forums > Computer Networking > Windows Networking > DHCP won't bind to NIC team w/ static IP

Reply
Thread Tools Display Modes

DHCP won't bind to NIC team w/ static IP

 
 
andrew@technodevil.com
Guest
Posts: n/a

 
      09-06-2007, 04:22 PM
I'm in the middle of transferring server roles from a Windows Server
2003 box to a Server 2003 R2 box, and the last thing I have to
transfer over at the moment is DHCP. However, no matter what I try
the new DHCP server absolutely will not bind to the onboard NIC (DHCP
Server properties -> Advanced -> Bindings)--it's actually a team of
NICs on a Dell server, though. The team most definitely has a static
IP. Is there a problem with Server 2003 R2 and Broadcom NIC teams,
maybe? The current DHCP server is bound to an Intel NIC team on a
Dell server without problem.

I had originally transferred the scope from one server to another by
exporting the scope to a text file and then importing it, but when I
couldn't bind to the NIC I recreated it manually to see if that might
be the culprit. No dice. I also thought that it might be something
with not able to bind while another server was authorized, so I
deauthorized the old server and then tried to bind the new one to the
team. No dice, either.

I'm stumped. Any thoughts? Thanks.

 
Reply With Quote
 
 
 
 
Mathieu CHATEAU
Guest
Posts: n/a

 
      09-06-2007, 05:18 PM
Hello,

is your R2 SP2 ? There is currently network issue.
So on the dhcp console, you don't see any ip to bind to ?


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> I'm in the middle of transferring server roles from a Windows Server
> 2003 box to a Server 2003 R2 box, and the last thing I have to
> transfer over at the moment is DHCP. However, no matter what I try
> the new DHCP server absolutely will not bind to the onboard NIC (DHCP
> Server properties -> Advanced -> Bindings)--it's actually a team of
> NICs on a Dell server, though. The team most definitely has a static
> IP. Is there a problem with Server 2003 R2 and Broadcom NIC teams,
> maybe? The current DHCP server is bound to an Intel NIC team on a
> Dell server without problem.
>
> I had originally transferred the scope from one server to another by
> exporting the scope to a text file and then importing it, but when I
> couldn't bind to the NIC I recreated it manually to see if that might
> be the culprit. No dice. I also thought that it might be something
> with not able to bind while another server was authorized, so I
> deauthorized the old server and then tried to bind the new one to the
> team. No dice, either.
>
> I'm stumped. Any thoughts? Thanks.
>


 
Reply With Quote
 
andrew@technodevil.com
Guest
Posts: n/a

 
      09-06-2007, 05:29 PM
Yes, it's 2003 R2 SP2.

When I go into the Bindings section, I see the adapter listed there,
but it's unchecked and unbound. If I check it to bind it, click OK,
then click OK to get out of the DHCP server properties, it's unchecked
if I go back in there.

On Sep 6, 10:18 am, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
> Hello,
>
> is your R2 SP2 ? There is currently network issue.
> So on the dhcp console, you don't see any ip to bind to ?
>
> --
> Cordialement,
> Mathieu CHATEAUhttp://lordoftheping.blogspot.com
>
> <and...@technodevil.com> wrote in message
>
> news:(E-Mail Removed) oups.com...
>
> > I'm in the middle of transferring server roles from a Windows Server
> > 2003 box to a Server 2003 R2 box, and the last thing I have to
> > transfer over at the moment is DHCP. However, no matter what I try
> > the new DHCP server absolutely will not bind to the onboard NIC (DHCP
> > Server properties -> Advanced -> Bindings)--it's actually a team of
> > NICs on a Dell server, though. The team most definitely has a static
> > IP. Is there a problem with Server 2003 R2 and Broadcom NIC teams,
> > maybe? The current DHCP server is bound to an Intel NIC team on a
> > Dell server without problem.

>
> > I had originally transferred the scope from one server to another by
> > exporting the scope to a text file and then importing it, but when I
> > couldn't bind to the NIC I recreated it manually to see if that might
> > be the culprit. No dice. I also thought that it might be something
> > with not able to bind while another server was authorized, so I
> > deauthorized the old server and then tried to bind the new one to the
> > team. No dice, either.

>
> > I'm stumped. Any thoughts? Thanks.


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Setting the bind and dhcp for use as dns/ddns alike Linux Networking 4 01-02-2012 12:10 PM
BIND not being updated by ISC DHCP Alexander Burke Linux Networking 0 03-13-2006 11:44 AM
DHCP Error 64 - No static IP bound to this DHCP Server DHCP Firewall Windows Networking 0 02-02-2006 04:04 PM
radvd, BIND and DHCP Mark Hackett Linux Networking 4 05-21-2004 07:47 AM
DHCP server will not bind to Network Interface. Bob H. Windows Networking 1 02-13-2004 02:44 AM



1 2 3 4 5 6 7 8 9 10 11