Announcement

Collapse
No announcement yet.

Taking Long Time in Preparing Networking Connections...

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Taking Long Time in Preparing Networking Connections...

    Hi All,

    I have a Windows Server 2003 as a DC. From last two weeks I am experiencing a problem that when I start the server it took a lot of time( Some 15 to 20 minutes) in the phase " Preparing Network Connections...".Previously it was not the case. to get around the issue I changed the NIC card of the machine but to no use. Can anyone please figure out what can be the real issue there...

    thanks in advance!
    Always Curious!

  • #2
    Re: Taking Long Time in Preparing Networking Connections...

    What are the hardware specs? -- this can slow the system down
    Have you checked the event viewer for errors?
    What changed between "previously this was not the case" and now?

    Basically tell us a lot more, and you will get some useful advice rather than speculation
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Taking Long Time in Preparing Networking Connections...

      Originally posted by Ossian View Post
      What are the hardware specs? -- this can slow the system down
      Have you checked the event viewer for errors?
      What changed between "previously this was not the case" and now?

      Basically tell us a lot more, and you will get some useful advice rather than speculation
      thanks for your consideration.
      Hardware specs:
      Intel Xeon CPU 2.80 GHz
      RAM: 512 MB
      RAID Drives
      NIC Card: 3COM EthernetLink XL 10/100 PCI TX NIC(3C9058-TX)

      Software Specs:
      Windows Server 2003 SP2
      WSUS
      Antivirus:McAfee Virus Scan Enterprise 8.0.0


      and there has been not a single change between the time it was working and now...
      Always Curious!

      Comment


      • #4
        Re: Taking Long Time in Preparing Networking Connections...

        If you have only one domain controller this problem is almost always dns related.

        The domain controller should point it's dns settings to it's own local ip address.
        In the dns server you have to configure forwarders to resolve external (internet) host names.

        Maybe you can post an ipconfig /all of your server?

        Comment


        • #5
          Re: Taking Long Time in Preparing Networking Connections...

          Originally posted by Geertm View Post
          If you have only one domain controller this problem is almost always dns related.

          The domain controller should point it's dns settings to it's own local ip address.
          In the dns server you have to configure forwarders to resolve external (internet) host names.

          Maybe you can post an ipconfig /all of your server?
          thanks for the care!
          Yes it could be.... When I changed the NIC card the system restarted after installing its drivers. At that time the system did not have any IP address assigned. When the system restarted (without the IP address) it was very fast. After login I assigned the IP address to the system and it again prompt me to restart the system and when I restarted the system this time( after assigning the IP) it then took the long time. So how do I go next.
          The ipconfig/all is here.
          Always Curious!

          Comment


          • #6
            Re: Taking Long Time in Preparing Networking Connections...

            Could you also post then dns config of your server please.
            Is this the only domain controller/dns server in the domain?

            Comment


            • #7
              Re: Taking Long Time in Preparing Networking Connections...

              512Mb RAM isn't doing too much good either!
              Do consider going to 2Gb -- its very cheap these days
              Tom Jones
              MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
              PhD, MSc, FIAP, MIITT
              IT Trainer / Consultant
              Ossian Ltd
              Scotland

              ** Remember to give credit where credit is due and leave reputation points where appropriate **

              Comment


              • #8
                Re: Taking Long Time in Preparing Networking Connections...

                Originally posted by Geertm View Post
                Could you also post then dns config of your server please.
                Is this the only domain controller/dns server in the domain?
                yes this the only DC and dns server in my LAN... How can I post the DNS details....


                thanks
                Always Curious!

                Comment


                • #9
                  Re: Taking Long Time in Preparing Networking Connections...

                  Originally posted by Ossian View Post
                  512Mb RAM isn't doing too much good either!
                  Do consider going to 2Gb -- its very cheap these days
                  I think it is not a RAM issue as previously it was working fine. This problem has popped up suddenly....
                  Always Curious!

                  Comment


                  • #10
                    Re: Taking Long Time in Preparing Networking Connections...

                    Originally posted by Curious View Post
                    How can I post the DNS details....
                    Maybe some screenshots?

                    you can also post a "dcdiag /q"

                    Comment


                    • #11
                      Re: Taking Long Time in Preparing Networking Connections...

                      Originally posted by Geertm View Post
                      Maybe some screenshots?

                      you can also post a "dcdiag /q"
                      The Following is the result of dcdiag/q. Note that BACKUP was a computer with Win 2K3 in our domain which has been now removed from the LAN long long ago and NETSERVER is computer in our domain with Win 2K3 installed acting as a proxy server.

                      C:\>dcdiag/q
                      [Replications Check,SERVER] A recent replication attempt failed:
                      From BACKUP to SERVER
                      Naming Context: DC=ForestDnsZones,DC=pdcc,DC=edu,DC=pk
                      The replication generated an error (1256):
                      The remote system is not available. For information about network tr
                      oubleshooting, see Windows Help.
                      The failure occurred at 2008-02-02 15:51:15.
                      The last success occurred at 2007-05-01 10:52:23.
                      2307 failures have occurred since the last success.
                      [BACKUP] DsBindWithSpnEx() failed with error 1722,
                      The RPC server is unavailable..
                      [Replications Check,SERVER] A recent replication attempt failed:
                      From BACKUP to SERVER
                      Naming Context: DC=DomainDnsZones,DC=pdcc,DC=edu,DC=pk
                      The replication generated an error (1256):
                      The remote system is not available. For information about network tr
                      oubleshooting, see Windows Help.
                      The failure occurred at 2008-02-02 15:51:15.
                      The last success occurred at 2007-05-01 10:52:23.
                      2315 failures have occurred since the last success.
                      [Replications Check,SERVER] A recent replication attempt failed:
                      From BACKUP to SERVER
                      Naming Context: CN=Schema,CN=Configuration,DC=pdcc,DC=edu,DC=pk
                      The replication generated an error (8524):
                      The DSA operation is unable to proceed because of a DNS lookup failu
                      re.
                      The failure occurred at 2008-02-02 15:51:23.
                      The last success occurred at 2007-05-01 10:52:23.
                      2604 failures have occurred since the last success.
                      The guid-based DNS name 8b38b6cc-5d40-4684-821e-44ef38e7f10f._msdcs.
                      pdcc.edu.pk
                      is not registered on one or more DNS servers.
                      [Replications Check,SERVER] A recent replication attempt failed:
                      From NETSERVER to SERVER
                      Naming Context: CN=Schema,CN=Configuration,DC=pdcc,DC=edu,DC=pk
                      The replication generated an error (8524):
                      The DSA operation is unable to proceed because of a DNS lookup failu
                      re.
                      The failure occurred at 2008-02-02 15:51:31.
                      The last success occurred at 2007-03-02 14:46:55.
                      3245 failures have occurred since the last success.
                      The guid-based DNS name 1baeaeb7-0a69-45f1-8227-784f33ba5a8d._msdcs.
                      pdcc.edu.pk
                      is not registered on one or more DNS servers.
                      [NETSERVER] DsBindWithSpnEx() failed with error 1722,
                      The RPC server is unavailable..
                      [Replications Check,SERVER] A recent replication attempt failed:
                      From NETSERVER to SERVER
                      Naming Context: CN=Configuration,DC=pdcc,DC=edu,DC=pk
                      The replication generated an error (8524):
                      The DSA operation is unable to proceed because of a DNS lookup failu
                      re.
                      The failure occurred at 2008-02-02 15:51:08.
                      The last success occurred at 2007-03-02 15:13:36.
                      3337 failures have occurred since the last success.
                      The guid-based DNS name 1baeaeb7-0a69-45f1-8227-784f33ba5a8d._msdcs.
                      pdcc.edu.pk
                      is not registered on one or more DNS servers.
                      [Replications Check,SERVER] A recent replication attempt failed:
                      From BACKUP to SERVER
                      Naming Context: CN=Configuration,DC=pdcc,DC=edu,DC=pk
                      The replication generated an error (8524):
                      The DSA operation is unable to proceed because of a DNS lookup failu
                      re.
                      The failure occurred at 2008-02-02 15:51:15.
                      The last success occurred at 2007-05-01 10:52:22.
                      2608 failures have occurred since the last success.
                      The guid-based DNS name 8b38b6cc-5d40-4684-821e-44ef38e7f10f._msdcs.
                      pdcc.edu.pk
                      is not registered on one or more DNS servers.
                      [Replications Check,SERVER] A recent replication attempt failed:
                      From NETSERVER to SERVER
                      Naming Context: DC=pdcc,DC=edu,DC=pk
                      The replication generated an error (8524):
                      The DSA operation is unable to proceed because of a DNS lookup failu
                      re.
                      The failure occurred at 2008-02-02 15:51:38.
                      The last success occurred at 2007-03-02 14:59:33.
                      3300 failures have occurred since the last success.
                      The guid-based DNS name 1baeaeb7-0a69-45f1-8227-784f33ba5a8d._msdcs.
                      pdcc.edu.pk
                      is not registered on one or more DNS servers.
                      [Replications Check,SERVER] A recent replication attempt failed:
                      From BACKUP to SERVER
                      Naming Context: DC=pdcc,DC=edu,DC=pk
                      The replication generated an error (8524):
                      The DSA operation is unable to proceed because of a DNS lookup failu
                      re.
                      The failure occurred at 2008-02-02 15:51:46.
                      The last success occurred at 2007-05-01 10:52:23.
                      2605 failures have occurred since the last success.
                      The guid-based DNS name 8b38b6cc-5d40-4684-821e-44ef38e7f10f._msdcs.
                      pdcc.edu.pk
                      is not registered on one or more DNS servers.
                      REPLICATION-RECEIVED LATENCY WARNING
                      SERVER: Current time is 2008-02-02 16:37:33.
                      DC=ForestDnsZones,DC=pdcc,DC=edu,DC=pk
                      Last replication recieved from BACKUP at 2007-05-01 10:52:23.
                      WARNING: This latency is over the Tombstone Lifetime of 60 days!

                      DC=DomainDnsZones,DC=pdcc,DC=edu,DC=pk
                      Last replication recieved from BACKUP at 2007-05-01 10:52:23.
                      WARNING: This latency is over the Tombstone Lifetime of 60 days!

                      CN=Schema,CN=Configuration,DC=pdcc,DC=edu,DC=pk
                      Last replication recieved from NETSERVER at 2007-03-02 14:46:55.
                      WARNING: This latency is over the Tombstone Lifetime of 60 days!

                      Last replication recieved from BACKUP at 2007-05-01 10:52:23.
                      WARNING: This latency is over the Tombstone Lifetime of 60 days!

                      CN=Configuration,DC=pdcc,DC=edu,DC=pk
                      Last replication recieved from NETSERVER at 2007-03-02 15:13:36.
                      WARNING: This latency is over the Tombstone Lifetime of 60 days!

                      Last replication recieved from BACKUP at 2007-05-01 10:52:22.
                      WARNING: This latency is over the Tombstone Lifetime of 60 days!

                      DC=pdcc,DC=edu,DC=pk
                      Last replication recieved from NETSERVER at 2007-03-02 14:59:33.
                      WARNING: This latency is over the Tombstone Lifetime of 60 days!

                      Last replication recieved from BACKUP at 2007-05-01 10:52:23.
                      WARNING: This latency is over the Tombstone Lifetime of 60 days!

                      There are warning or error events within the last 24 hours after the
                      SYSVOL has been shared. Failing SYSVOL replication problems may cause
                      Group Policy problems.
                      ......................... SERVER failed test frsevent
                      Always Curious!

                      Comment


                      • #12
                        Re: Taking Long Time in Preparing Networking Connections...

                        The "dcdiag /q" only displays the errors, so normally there should be no output

                        My gues is that your old domain controllers are still registered in active directory and in DNS.

                        The "still registered in DNS" is most likely causing the waiting for network connections problem.

                        Comment


                        • #13
                          Re: Taking Long Time in Preparing Networking Connections...

                          Originally posted by Curious View Post
                          I think it is not a RAM issue as previously it was working fine. This problem has popped up suddenly....
                          I agree it is probably not a RAM issue, but 512Mb far too little for a server these days.
                          Tom Jones
                          MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
                          PhD, MSc, FIAP, MIITT
                          IT Trainer / Consultant
                          Ossian Ltd
                          Scotland

                          ** Remember to give credit where credit is due and leave reputation points where appropriate **

                          Comment

                          Working...
                          X