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.
>