Solved

NTDS KCC Replication Errors in EventLog

Posted on 2009-04-08
14
3,310 Views
Last Modified: 2012-05-06
Hello I have a bunch of errors in event log on a DC that started on 3/16, actually it looks like 3/6 may have been the start, not sure how I didn't notice them till now, but it appears to also have recently been logging even more just the past couple days and it's got me worried.  I've been google searching and there is alot of info out there on it but would like somebody who maybe has been through this to help with a more direct approach.  Basically on our domain controller in our child domain it's logging these errors:

Here is the first one on 3/5:

EventID: 2088
Source: NTDS Replication
Category: DS RPC Client

Description: Active Directory could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.
 
Invalid DNS configuration may be affecting other essential operations on member computers, domain controllers or application servers in this Active Directory forest, including logon authentication or access to network resources.
 
You should immediately resolve this DNS configuration error so that this domain controller can resolve the IP address of the source domain controller using DNS.
 
Alternate server name:
 RADIUS1.npci.com
Failing DNS host name:
 210d126f-b8a0-4426-a076-a70b00a5d0c9._msdcs.npci.com
 
NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur.  To log all individual failure events, set the following diagnostics registry value to 1:
 
Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client
 
User Action:
 
 1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.
 
 2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>".
 
 3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns
 
  dcdiag /test:dns
 
 4) Verify that that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:
 
  dcdiag /test:dns
 
 5) For further analysis of DNS error failures see KB 824449:
   http://support.microsoft.com/?kbid=824449
 
Additional Data
Error value:
 11004 The requested name is valid, but no data of the requested type was found.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

------------------------------------------------------------------------------------------------------------------

I'm thinking this one may have been due to some random outtages we've had on our WAN circuit so that site with that DC actually has lost total network connectivity here and there so possibly that may have been from that.  Then on 3/16 is really when thing started getting logged alot and it was on a Monday night after 11PM so I know for a fact this didn't happen from anything that I changed because I wasn't doing anything on this network at that time and in fact I haven't been changing anything with the DC's, DNS, etc period anyway:

-------------------------------------------------------------------------------------------------------------------

EventID: 1232
Source: NTDS Replication
Category: DS RPC Client

Active Directory attempted to perform a remote procedure call (RPC) to the following server.  The call timed out and was cancelled.
 
Server:
210d126f-b8a0-4426-a076-a70b00a5d0c9._msdcs.npci.com
Call Timeout (Mins):
5
Thread ID:
328
 
Additional Data
Internal ID:
122adb0

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-----------------------------------------------------------------------------------------------------------------

EventID: 1308
Source: NTDS KCC
Category: Knowledge Consistency

The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following domain controller has consistently failed.
 
Attempts:
8
Domain controller:
CN=NTDS Settings,CN=RADIUS1,CN=Servers,CN=CoLocation,CN=Sites,CN=Configuration,DC=npci,DC=com
Period of time (minutes):
125
 
The Connection object for this domain controller will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this domain controller resumes, the temporary connection will be removed.
 
Additional Data
Error value:
1256 The remote system is not available. For information about network troubleshooting, see Windows Help.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-------------------------------------------------------------------------------------------------------------------

EventID: 1566
Source: NTDS KCC
Category: Knowledge Consistency

All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable.
 
Site:
CN=CoLocation,CN=Sites,CN=Configuration,DC=npci,DC=com
Directory partition:
DC=ForestDnsZones,DC=npci,DC=com
Transport:
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=npci,DC=com

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-------------------------------------------------------------------------------------------------------------------

EventID: 1311
Source: NTDS KC
Category: Knowledge Consistency

The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
 
Directory partition:
DC=ForestDnsZones,DC=npci,DC=com
 
There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.
 
User Action
Use Active Directory Sites and Services to perform one of the following actions:
- Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.
- Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site.
 
If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

EventID: 1865
Source: NTDS KCC
Category: Knowledge Consistency

The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.
 
Sites:
CN=CoLocation,CN=Sites,CN=Configuration,DC=npci,DC=com
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-------------------------------------------------------------------------------------------------------------------

So far I've noticed no ill effects of anything and no user complaints of users on that domain of anything being out of the ordinary, it's just these started being logged and it's worried me and I have to fix this.  I can ping all other DC's from that DC by dns name and vice versa.  It's DNS is pointing to itself as it is the DNS server as well.  NO other errors in system eventlog or otherwise pointing to any issues.  So what do you think is going on here and what do I need to do to fix this up?  

Any help greatly appreciated!
0
Comment
Question by:darkonex
  • 8
  • 6
14 Comments
 

Author Comment

by:darkonex
Comment Utility
Also I just ran a dnsdiag /test on that DC and here are the results.  What does that Dynamic DNS error at the top mean, how do I fix that maybe that's the cause?


Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Lenexa\KCSERV2K
      Starting test: Connectivity
         ......................... KCSERV2K passed test Connectivity

Doing primary tests
   
   Testing server: Lenexa\KCSERV2K

DNS Tests are running and not hung. Please wait a few minutes...
   
   Running partition tests on : DomainDnsZones
   
   Running partition tests on : ForestDnsZones
   
   Running partition tests on : lenexa
   
   Running partition tests on : Schema
   
   Running partition tests on : Configuration
   
   Running enterprise tests on : npci.com
      Starting test: DNS
         Test results for domain controllers:
           
            DC: kcserv2k.lenexa.npci.com
            Domain: lenexa.npci.com

                 
               TEST: Forwarders/Root hints (Forw)
                  Error: Forwarders list has invalid forwarder: 151.164.1.8 (<name unavailable>)
                  Error: Forwarders list has invalid forwarder: 206.13.28.12 (<name unavailable>)
                  Error: Root hints list has invalid root hint server: a.root-servers.net. (198.41.0.4)
                  Error: Root hints list has invalid root hint server: b.root-servers.net. (192.228.79.201)
                  Error: Root hints list has invalid root hint server: c.root-servers.net. (192.33.4.12)
                  Error: Root hints list has invalid root hint server: d.root-servers.net. (128.8.10.90)
                  Error: Root hints list has invalid root hint server: e.root-servers.net. (192.203.230.10)
                  Error: Root hints list has invalid root hint server: f.root-servers.net. (192.5.5.241)
                  Error: Root hints list has invalid root hint server: g.root-servers.net. (192.112.36.4)
                  Error: Root hints list has invalid root hint server: h.root-servers.net. (128.63.2.53)
                  Error: Root hints list has invalid root hint server: i.root-servers.net. (192.36.148.17)
                  Error: Root hints list has invalid root hint server: j.root-servers.net. (192.58.128.30)
                  Error: Root hints list has invalid root hint server: k.root-servers.net. (193.0.14.129)
                  Error: Root hints list has invalid root hint server: l.root-servers.net. (198.32.64.12)
                  Error: Root hints list has invalid root hint server: m.root-servers.net. (202.12.27.33)
                 
               TEST: Dynamic update (Dyn)
                  Warning: Dynamic update is enabled on the zone but not secure lenexa.npci.com.
         
         Summary of test results for DNS servers used by the above domain controllers:

            DNS server: 206.13.28.12 (<name unavailable>)
               1 test failure on this DNS server
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 206.13.28.12
               
            DNS server: 202.12.27.33 (m.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 202.12.27.33
               
            DNS server: 198.41.0.4 (a.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 198.41.0.4
               
            DNS server: 198.32.64.12 (l.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 198.32.64.12
               
            DNS server: 193.0.14.129 (k.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 193.0.14.129
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 193.0.14.129
               
            DNS server: 192.58.128.30 (j.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.58.128.30
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 192.58.128.30
               
            DNS server: 192.5.5.241 (f.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.5.5.241
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 192.5.5.241
               
            DNS server: 192.36.148.17 (i.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.36.148.17
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 192.36.148.17
               
            DNS server: 192.33.4.12 (c.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.33.4.12
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 192.33.4.12
               
            DNS server: 192.228.79.201 (b.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.228.79.201
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 192.228.79.201
               
            DNS server: 192.203.230.10 (e.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 192.203.230.10
               
            DNS server: 192.112.36.4 (g.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.112.36.4
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 192.112.36.4
               
            DNS server: 151.164.1.8 (<name unavailable>)
               1 test failure on this DNS server
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 151.164.1.8
               
            DNS server: 128.8.10.90 (d.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 128.8.10.90
               
            DNS server: 128.63.2.53 (h.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53
               Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 128.63.2.53
               
         Summary of DNS test results:
         
                                            Auth Basc Forw Del  Dyn  RReg Ext  
               ________________________________________________________________
            Domain: lenexa.npci.com
               kcserv2k                     PASS PASS FAIL PASS WARN PASS n/a  
         
         ......................... npci.com failed test DNS
0
 
LVL 15

Expert Comment

by:zelron22
Comment Utility
Are your DNS servers IP settings pointing to anything but themselves?  Active Directory DNS servers should point to themselves in the TCP/IP DNS settings.  Then you set the DNS server to forward non-internal requests on to external DNS servers.

0
 
LVL 15

Expert Comment

by:zelron22
Comment Utility
I'm sorry, AD DNS servers should point ONLY to themselves in the TCP/IP DNS settings.  They should not point to any other servers, especially not external servers (within the TCP/IP settings).  
0
 
LVL 15

Expert Comment

by:zelron22
Comment Utility
Whoops, just saw your comment in the last paragraph that they are pointing to theirselves.
0
 

Author Comment

by:darkonex
Comment Utility
Also noticed this in Active Directory Sites and Services.  KCServ2k is the DC logging these errors and notice in the 2nd picture how there's no domain listed next to it like all the others.  Also I noticed in DNS on KCServ2k it only has DNS entries for stuff on the child domain.  I do not see anything listed for the forest anywhere, shouldn't there be?

0
 

Author Comment

by:darkonex
Comment Utility
Here are the screenies
pic-1.jpg
2.jpg
0
 
LVL 15

Expert Comment

by:zelron22
Comment Utility
You see these entries in your DCDIAG log?  Your server is trying to perform LDAP lookups on external root servers.  Something is not correct with your DNS configuration.

>>Name resolution is not functional. _ldap._tcp.npci.com. failed on the DNS server 128.8.10.90
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 
LVL 15

Expert Comment

by:zelron22
Comment Utility
Do you have root servers set up in your internal DNS zone as name servers or something?  There must be service location (SRV) records for external DNS servers set up under _tcp.npci.com.  They will look like this:
Name                             type                               Data
_ldap                         Service Location(SRV)     [0][100][389]128.63.2.53
_ldap                         Service Location(SRV)     [0][100][389]202.12.27.33
_ldap                         Service Location(SRV)     [0][100][389]206.13.28.12

and they should look like this:
_ldap                         Service Location(SRV)     [0][100][389]KCSERV2K.npci.com
etc....
It also looks like you have the loopback address set for DNS instead of the server's actual IP.  I would change that so that TCP/IP DNS points to the actual IP address.  How many NICs are on this machine, how many are in use, and are the unused ones disabled?
0
 

Author Comment

by:darkonex
Comment Utility
I looked on DNS on the KCServ2k, the one with the errors, and nowhere do I see root SRV records anywhere.  I just see the ones for KCSERV2K.npci.com.  The IP address for DNS on that server is set to it's own IP 192.168.201.2 not the loopback.  There is 1 NIC in there.
0
 

Author Comment

by:darkonex
Comment Utility
Here is a screenshot of DNS on our parent domain DC and then one of the one giving errors in the child domain.  Not sure if that will be of any help but here they are.
dns-1.jpg
dns-2.jpg
0
 

Author Comment

by:darkonex
Comment Utility
I was doing more reading on how replication works etc and ran repadmin /showreps on the DC that was logging errors and it almost looks like it has been replicating recently:

Lenexa\KCSERV2K

DC Options: IS_GC

Site Options: (none)

DC object GUID: ddae2511-f6aa-4c89-a7f5-eb56e05a37e4

DC invocationID: 90031704-3c66-4a3c-8719-ea2ec85aae59



==== INBOUND NEIGHBORS ======================================



CN=Configuration,DC=npci,DC=com

    Lenexa\KCNEW via RPC

        DC object GUID: 2223dacf-8ef7-49ed-ac76-b117dfbacf65

        Last attempt @ 2009-04-08 15:30:12 was successful.

    CoLocation\RADIUS1 via RPC

        DC object GUID: 210d126f-b8a0-4426-a076-a70b00a5d0c9

        Last attempt @ 2009-04-08 15:40:17 was successful.

    Default-First-Site-Name\NPCCORP2K via RPC

        DC object GUID: 8fec1a7e-05bf-46b1-bb68-c17c154c12b2

        Last attempt @ 2009-04-08 15:40:18 was successful.



CN=Schema,CN=Configuration,DC=npci,DC=com

    Lenexa\KCNEW via RPC

        DC object GUID: 2223dacf-8ef7-49ed-ac76-b117dfbacf65

        Last attempt @ 2009-04-08 14:55:16 was successful.

    CoLocation\RADIUS1 via RPC

        DC object GUID: 210d126f-b8a0-4426-a076-a70b00a5d0c9

        Last attempt @ 2009-04-08 15:40:18 was successful.

    Default-First-Site-Name\NPCCORP2K via RPC

        DC object GUID: 8fec1a7e-05bf-46b1-bb68-c17c154c12b2

        Last attempt @ 2009-04-08 15:40:18 was successful.



DC=lenexa,DC=npci,DC=com

    Lenexa\KCNEW via RPC

        DC object GUID: 2223dacf-8ef7-49ed-ac76-b117dfbacf65

        Last attempt @ 2009-04-08 15:49:50 was successful.



DC=ForestDnsZones,DC=npci,DC=com

    CoLocation\RADIUS1 via RPC

        DC object GUID: 210d126f-b8a0-4426-a076-a70b00a5d0c9

        Last attempt @ 2009-04-08 15:40:18 was successful.

    Default-First-Site-Name\NPCCORP2K via RPC

        DC object GUID: 8fec1a7e-05bf-46b1-bb68-c17c154c12b2

        Last attempt @ 2009-04-08 15:40:19 was successful.



DC=npci,DC=com

    CoLocation\RADIUS1 via RPC

        DC object GUID: 210d126f-b8a0-4426-a076-a70b00a5d0c9

        Last attempt @ 2009-04-08 15:40:19 was successful.

    Default-First-Site-Name\NPCCORP2K via RPC

        DC object GUID: 8fec1a7e-05bf-46b1-bb68-c17c154c12b2

        Last attempt @ 2009-04-08 15:40:21 was successful.



DC=commcntr,DC=npci,DC=com

    CoLocation\RADIUS1 via RPC

        DC object GUID: 210d126f-b8a0-4426-a076-a70b00a5d0c9

        Last attempt @ 2009-04-08 15:40:21 was successful.

    Default-First-Site-Name\NPCCORP2K via RPC

        DC object GUID: 8fec1a7e-05bf-46b1-bb68-c17c154c12b2

        Last attempt @ 2009-04-08 15:40:21 was successful.

--------------------------------------------------------------------------------------------------------------------------

Also I will add that the errors that have gone on since 3/16 every 15 min when a replication was attempted actually stopped around 11AM today (maybe when I tried a couple things like netdiag /fix and dcdiag /fix) and the last things logged in the Directory Service eventlog now are these kind of informational messages that still don't sound very good to me.

To improve the replication load of Active Directory, a replication connection from the following source domain controller to the local domain controller was deleted.
 
Source domain controller:
CN=NTDS Settings,CN=COMMSQL,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=npci,DC=com
Local domain controller:
CN=NTDS Settings,CN=KCSERV2K,CN=Servers,CN=Lenexa,CN=Sites,CN=Configuration,DC=npci,DC=com
 
Additional Data
Reason Code:
0x60
Deletion Point Internal ID:
f0c08af


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

----------------------------------------------------------------------------------------------------------------------------

The following directory partition is no longer replicated from the source domain controller at the following network address because there is no Connection object for the domain controller.
 
Directory partition:
DC=commcntr,DC=npci,DC=com
Source domain controller:
CN=NTDS Settings,CN=RADIUS2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=npci,DC=com
Network address:
2bd01367-3fa7-454d-aae0-be0ed23e08d8._msdcs.npci.com

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 

Author Comment

by:darkonex
Comment Utility
Something else I noticed the errors actually started on 3/16 then stopped the next day, then didn't happen again until yesterday around noon (which would have been about the time we had a VPN router go down causing internet connectivity loss and possibly WAN connection to the parent DCs).  So I'm wondering if perhaps these are just all from that happening?
0
 
LVL 15

Accepted Solution

by:
zelron22 earned 500 total points
Comment Utility
That's probably the trigger, but I don't see why the server would be trying to replicate with root servers, unless you've got a host file or something else.  If the server can't find the other servers, replication would certainly fail, but it should show that it's failing with your actual servers, not with the root servers.

I think it would be best to figure it out and clean it up, but if everything is working when the VPN is up, then it probably won't hurt anything in the short term.

Off-topic, would you be located in The Caves in Lenexa?  I used to work for a company that owned a company that had a warehouse there.  Freaky.  I always thought the entrance there would be a great place for a donut shop.
0
 

Author Closing Comment

by:darkonex
Comment Utility
Thanks for the help, it hasn't happened again so it must have been the VPN being down which rarely happens so I'm not worried about it.  For your question about the caves, no I'm actually in a town 150 miles from there and our old network engineer though actually left here to go work there.
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

In this article, we will see the basic design consideration while designing a Multi-tenant web application in a simple manner. Though, many frameworks are available in the market to develop a multi - tenant application, but do they provide data, cod…
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now