pinging is 15ms on local!!!!

    General discussion

  • my windows server started acting funny and giving me 15ms ping time when I ping from a workstation but after many 15ms I will get few <1 ms..

    It's causing a real problem with my database application!! and it's making users crazy!!

    I found this in the event log of the server but not sure if it's the reason..

    please help

    The security of this directory server can be significantly enhanced by configuring the server to reject SASL (Negotiate,  Kerberos, NTLM, or Digest) LDAP binds that do not request signing (integrity verification) and LDAP simple binds that  are performed on a cleartext (non-SSL/TLS-encrypted) connection.  Even if no clients are using such binds, configuring the server to reject them will improve the security of this server.
    Some clients may currently be relying on unsigned SASL binds or LDAP simple binds over a non-SSL/TLS connection, and will stop working if this configuration change is made.  To assist in identifying these clients, if such binds occur this  directory server will log a summary event once every 24 hours indicating how many such binds  occurred.  You are encouraged to configure those clients to not use such binds.  Once no such events are observed  for an extended period, it is recommended that you configure the server to reject such binds.
    For more details and information on how to make this configuration change to the server, please see http://go.microsoft.com/fwlink/?LinkID=87923.
    You can enable additional logging to log an event each time a client makes such a bind, including information on which client made the bind.  To do so, please raise the setting for the "LDAP Interface Events" event logging category to level 2 or higher.

    The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

    Jassim Rahma
    Saturday, February 06, 2010 7:52 AM

All replies

  • I dont think the two events listed above are related. To figure out why you are seeing 15ms results, I would recommend that you take a packet capture on the workstation and the server to take a look at the traffic that is occuring on each of their local segments. 

    It is difficult to troubleshoot why you are seeing the 15ms response times, until you take a look at the traffic.  First, ICMP is generally treated with low priority on the network by switches and routers so you cannot always use this as a determination of an issue at the application layer.  In addition, I have not come accross any applications that would be affected by 15ms.  As a matter of fact most VoIP implementations can handle 40, 50 ms.  So, I am not convinced that your db problems are related to congenstion on the network.

    You can get a free copy of Wireshark which is pretty easy to use.  Once you capture the traffic, you will definatley see what is going on between the nodes.
    Visit my blog: anITKB.com, an IT Knowledge Base.
    Saturday, February 06, 2010 5:03 PM
  • i never tried it before but I am downloading it now and will let you know...

    Just for your infor.. this is the error I am getting on my .net application..


    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.
    ************** Exception Text **************
    System.InvalidOperationException: Internal connection fatal error.
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlDataReader.CloseInternal(Boolean closeReader)
       at System.Data.SqlClient.SqlDataReader.Close()
       at System.Data.Common.DbDataReader.Dispose(Boolean disposing)
       at System.Data.Common.DbDataReader.Dispose()
       at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
       at shefa.frmFindPatient.txtFind_KeyDown(Object sender, KeyEventArgs e)
       at System.Windows.Forms.Control.OnKeyDown(KeyEventArgs e)
       at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
       at System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
       at System.Windows.Forms.Control.WmKeyChar(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.TextBoxBase.WndProc(Message& m)
       at System.Windows.Forms.TextBox.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
        Assembly Version:
        Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
        CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
        Assembly Version:
        Win32 Version:
        CodeBase: file:///C:/Program%20Files/shefa/shefa.exe
        Assembly Version:
        Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/
        Assembly Version:
        Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/
        Assembly Version:
        Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/
        Assembly Version:
        Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/
        Assembly Version:
        Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/
        Assembly Version:
        Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/
        Assembly Version:
        Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/
        Assembly Version:
        Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
        CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    For example:
        <system.windows.forms jitDebugging="true" />
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Jassim Rahma
    Saturday, February 06, 2010 10:37 PM
  • Hi,

    Please try to collect the following information:

    Download Microsoft Network Monitor.

    1. Run Network Monitor and start capturing.
    2. Try to ping the server.
    3. Stop the capturing, save the result and upload the file to Windows Live SkyDrive (http://www.skydrive.live.com/). If you would like other community member to analyze the report, you can paste the link here, if not, you can send the link to tfwst@microsoft.com.

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, February 09, 2010 2:07 PM
  • this is the result of my network monitor... it's really getting slow but when user keep trying then it will pass







    Jassim Rahma
    Monday, April 12, 2010 3:14 PM
  • I get the impression that you have IIS, Active Directory, and File sharing all enabled on the same server.  Exactly what services are running on this machine?  How many users does this server support?  It's quite possible that the server is simply overwhelmed.  Check your CPU, RAM, and HDD utilization.  What type of RAID array are you using?  Many times, people underallocate for a machine on the hard disk spindles.  The errors you posted are all related to Active Directory issues.  The first error is one you should receive only during boot, and it states that DNS won't start until after all of AD replicates due to the fact some DNS zones would begin hosting inaccurate information if it starts too soon.  The other issues deal with server/client communications.  Are you running legacy clients in your environment, IE Windows 98/NT?
    Monday, April 12, 2010 3:38 PM