Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
I did a migrate from 2000 sp4 to 2008, but !!

Answered I did a migrate from 2000 sp4 to 2008, but !!

  • Thursday, June 14, 2012 8:57 AM
     
     
    Sign In to Vote
    0

    I did a migration from windows server 2000 sp4 to a windows server 2008 R2 , then I made the 2008 r2 server the FSMO holder for the five roles ,

    Now both servers is a domain controllers ,all things goes very good, accept when I unplug the 2000 server  it makes the logon too slow, I don't know why.

    I think if a domain controller goes down ,the other will do the job .

    any ideas plz .

     

All Replies

  • Thursday, June 14, 2012 9:34 AM
     
     
    Sign In to Vote
    0

    Hello,

    is the new DC also DNS server and are clients configured to use iton the NIC as preferred and the old one as secondary? Assure also that NO other DNS servers are used, ISPs DNS server for example.

    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

     
  • Thursday, June 14, 2012 6:01 PM
     
     
    Sign In to Vote
    0

    Hello,

    is the new DC also DNS server and are clients configured to use iton the NIC as preferred and the old one as secondary? Assure also that NO other DNS servers are used, ISPs DNS server for example.

    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Thanks Meinolf Weber 

    yes ,the new dc is DNS server ,and it is configured as preferred DNS .

    I also configured some clients with the new DC as the only DNS server ,but no change .

     
  • Thursday, June 14, 2012 7:24 PM
     
     
    Sign In to Vote
    0

    Hello,

    please post an unedited ipconfig /all from the DC/DNS servers and a client with problems.

    For machine higher then Windows 2000, which i assume all are please implement fast logon optimization with disabling "Always wait for the network at computer startup and logon." as described in http://technet.microsoft.com/en-us/library/cc780527(v=ws.10).aspx

    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

     
  • Saturday, June 16, 2012 8:14 AM
     
     
    Sign In to Vote
    0

    2008 DC

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : DCSERVER
       Primary Dns Suffix  . . . . . . . : egh.gov
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : egh.gov

    Ethernet adapter Local Area Connection 4:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
     VBD Client) #4
       Physical Address. . . . . . . . . : B8-AC-6F-95-31-97
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::7037:bf55:72c2:c28%16(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.20.40.22(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.0.0.0
       IPv4 Address. . . . . . . . . . . : 192.168.3.22(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.20.40.1
       DHCPv6 IAID . . . . . . . . . . . : 448310383
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-21-D9-A2-B8-AC-6F-95-31-99

       DNS Servers . . . . . . . . . . . : 192.168.3.22
                                           192.168.3.18
                                           10.20.40.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection 3:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
     VBD Client) #3
       Physical Address. . . . . . . . . : B8-AC-6F-95-31-95
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection 2:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
     VBD Client) #2
       Physical Address. . . . . . . . . : B8-AC-6F-95-31-9B
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
     VBD Client)
       Physical Address. . . . . . . . . : B8-AC-6F-95-31-99
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{F4A67BA2-A53C-4159-8F44-6E056F54F4F4}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{F8162758-58A8-4FD5-9FF5-955A6144EC03}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{D33BD0DA-142E-42D7-901C-4F407403159F}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{C24771B0-EB9B-4F14-B2C3-9C1A5F459271}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    2000 DC

    Windows 2000 IP Configuration

            Host Name . . . . . . . . . . . . : carebk
            Primary DNS Suffix  . . . . . . . : egh.gov
            Node Type . . . . . . . . . . . . : Broadcast
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
            DNS Suffix Search List. . . . . . : egh.gov

    Ethernet adapter Broadcom NetXtreme Gigabit Ethernet Adapter - PCI slot 3:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
            Physical Address. . . . . . . . . : 00-10-18-02-0A-47
            DHCP Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 10.20.40.18
            Subnet Mask . . . . . . . . . . . : 255.0.0.0
            IP Address. . . . . . . . . . . . : 192.168.3.18
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . :
            DNS Servers . . . . . . . . . . . : 192.168.3.22
                                                192.168.3.18

    Ethernet adapter Intel Fast Ethernet LAN Controller - onboard:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapt
    er (10/100)
            Physical Address. . . . . . . . . : 00-B0-D0-FC-07-90
            DHCP Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.5.62
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.5.1
            DNS Servers . . . . . . . . . . . : 192.168.5.1

    win 7 client

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : MOH-PC
       Primary Dns Suffix  . . . . . . . : egh.gov
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : egh.gov

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Netwo
    tion
       Physical Address. . . . . . . . . : B8-AC-6F-48-16-39
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::ecfa:3b24:d112:6490%11(Pre
       IPv4 Address. . . . . . . . . . . : 10.20.40.107(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.0.0.0
       IPv4 Address. . . . . . . . . . . : 192.168.3.107(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.20.40.1
       DHCPv6 IAID . . . . . . . . . . . : 246983791
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-33-E7-92-B8-AC-6F

       DNS Servers . . . . . . . . . . . : 192.168.3.22
                                           192.168.3.18
                                           10.20.40.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{F17CC21A-31D4-4083-9A97-011DE075321F}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    win xp client

    Windows IP Configuration

            Host Name . . . . . . . . . . . . : atabaz
            Primary Dns Suffix  . . . . . . . : egh.gov
            Node Type . . . . . . . . . . . . : Hybrid
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
            DNS Suffix Search List. . . . . . : egh.gov

    Ethernet adapter VMware Network Adapter VMnet8:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for
    VMnet8
            Physical Address. . . . . . . . . : 00-50-56-C0-00-08
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 192.168.217.1
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . :
            DHCP Server . . . . . . . . . . . : 192.168.217.254
            Primary WINS Server . . . . . . . : 192.168.217.2
            Lease Obtained. . . . . . . . . . : Saturday, June 16, 2012 10:07:26 AM
            Lease Expires . . . . . . . . . . : Saturday, June 16, 2012 10:37:26 AM

    Ethernet adapter VMware Network Adapter VMnet1:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for
    VMnet1
            Physical Address. . . . . . . . . : 00-50-56-C0-00-01
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 192.168.59.1
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . :
            DHCP Server . . . . . . . . . . . : 192.168.59.254
            Lease Obtained. . . . . . . . . . : Saturday, June 16, 2012 10:08:03 AM
            Lease Expires . . . . . . . . . . : Saturday, June 16, 2012 10:38:03 AM

    Ethernet adapter Local Area Connection:

            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network C
    onnection
            Physical Address. . . . . . . . . : BC-30-5B-A1-D4-48
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 10.20.40.108
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            IP Address. . . . . . . . . . . . : 192.168.3.108
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 10.20.40.1
            DNS Servers . . . . . . . . . . . : 192.168.3.22
                                                192.168.3.18

     
  • Sunday, June 17, 2012 4:48 PM
     
     Answered
    Sign In to Vote
    0

    Hello,

    do NOT use more then one ip address or NICs on DCs, why have you configured this kind of crappy network setup? Also this is done on all other machines? Multi-homing DCs is bad practice and result in problems with name resolution, slow logons, GPOs applied not correct and some more.

    In the DNS zones you have registered multiple A records for each NIC, so of course clients may get wrong information back.

    So in your case use ONLY the 10.x.x.x or 192.168.x.x subnet and NOT more. Additional reconfigure all machines to ONE ip address only. After the change, that you should start with the DCs, run ipconfig /flsuhdns and ipconfig /registerdns and restart the netlogon service on DCs and reboot all other machines.

    Additional assure that all not longer required ip address records are removed within the DNS zones. After the change please post again an unedited ipconfig /all from the machines, so we can verify it again, if the slow logon still exist, which i assume will NOT.

    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

     
  • Wednesday, June 20, 2012 3:40 PM
     
     
    Sign In to Vote
    0

    Multihoming the DC is not recommended as it relates to numerous issues which can result into the communication, dns name resolution, replication etc. Configure each DC working with one working live NIC. I presume the reason is due to multihoming of the DC. Refer the links posted into the below discussion.

    http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/a1583d7f-fa59-4497-89de-666d683e53a0/

    Awinish Vishwakarma - MVP - Directory Services

    My Blog: awinish.wordpress.com

    Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.

     
  • Friday, June 22, 2012 6:46 AM
     
     
    Sign In to Vote
    0

    Hello ,

    Well ,that make sense ,I am working on it 

    thanks :)