NLB is loaded by default in Windows 2003. Have you ensured NLB is not checked under network properties?
Dennis -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al Sent: Monday, December 22, 2003 9:54 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] After upgrading to Windows 2003 You didn't say why you have NLB loaded. What's it's purpose? -----Original Message----- From: Irwan Hadi [mailto:[EMAIL PROTECTED] Sent: Monday, December 22, 2003 2:38 AM To: [EMAIL PROTECTED] Subject: [ActiveDir] After upgrading to Windows 2003 I just upgraded my active directory infrastructure from Windows 2000 to Windows 2003. For a background, we have two servers working as domain controller and file server, and one server working as Exchange Server 2000 for about 70 users. The upgrade from Windows 2000 to Windows 2003 went pretty smoothly, and here is how I did that. First, I moved all FSMO roles from the first server to the second server, moved all the data from the first server to the second server, demoted the first server, rebuilt it with Windows 2003 Standard edition so that I have clean install. After that I promoted the first server, transfered the FSMO roles that the first one originally had, transfered back the data to the first server, and recreated the shared drives. Both of the domain controllers have the same specs, where basically both of them have two network cards, one is Intel 100/S, and the other Intel 1000/XT. I needed to put both network cards on originally, because we have two different subnets in the same network. By having the server to listens on the two subnets, besides getting better throughput, I can make the local traffic to stay within the local network, instead of going to the router and coming back again. After I upgraded the system to Windows 2003, I disabled the second network card on the domain controller that handles the RID, PDC, Infrastructure roles, because when they were running Windows 2000, I always get warning on the event log which after I checked at Microsoft site I found that Domain Controller that handles PDC should not be multi-homed. Moreover, I noticed after I promoted the servers back as domain controller, everytime I restart both servers, I got a popup message saying that a service could not be started, and I should check the event log. After I checked the event log, I noticed this popup is caused by the following: --------------- EventId: 7000 Source: Service Control Manager The Network Load Balancing service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. -------------- So I went to Microsoft site, and found the following: http://support.microsoft.com/?kbid=268437 But the problem is the KB above only applies for Windows 2000 Advanced server. Furthermore, I also noticed that the registry key that this KB tells I should delete also exists on my other Windows 2003 box that only has one network card. My question is have any of you ever got the same problem like I'm having above, why it seems only after I promote the server as a domain controller, I'm starting to have the popup above. Is there anyway to fix the popup above? I know that it is not harmful, but I just don't like the DC to give popup like that everytime I restart it. Thanks List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
