DNS Error Removing Records

I just got a mac mini server and I've been fiddling around with the different services. My DNS wasn't working so I tried to remove the records, but it gave me an error and when I slick save it just puts my records back. Basically I can't remove my primary and reverse lookup. I get the following in my log when I try and start too…
16-Nov-2009 15:03:56.806 zone 1.0.10.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public: loading from master file db.1.0.10.in-addr.arpa. failed: file not found
16-Nov-2009 15:03:56.806 zone 0.0.127.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public: loaded serial 1997022700
16-Nov-2009 15:03:56.807 zone mododev.com/IN/com.apple.ServerAdmin.DNS.public: loading from master file db.mododev.com. failed: file not found
16-Nov-2009 15:03:56.807 zone localhost/IN/com.apple.ServerAdmin.DNS.public: loaded serial 42
16-Nov-2009 15:03:56.807 running
On a related note, when creating a primary zone, what do you put in the nameserver zone/hostname spaces? Apples documentation just says click to add a namespace, but I don't know what to put in there and it forces you to add one. I just want to be able to act as a local DNS for my network.
Message was edited by: ast3r3x

Can I at least get a reply saying that this isn't normal and I'm not just being dumb? If this is a legitimate error I'll just reinstall and chalk it up as a fluke, but if I have to worry about it happening again, there isn't much point in doing so.

Similar Messages

  • ISSUE: "This domain controller must register a DNS SRV resource record, which is required for replication to function correctly"

    so we currently have three domain controllers set up, two of them on 2012r2 and one of them on 2008r2. prior to any of these domain controllers being added to the domain there was only one, running on 2003r2. the 2003r2 server was up and running when the
    first 2012r2 was added and that's when running 'dcdiag /e /c /v' would yield an issue with "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local" in the DNS portion of the diagnostics, specifically:
    TEST: Records registration (RReg)
    Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
    Error:
    Missing SRV record at DNS server 192.168.22.4:
    _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
    after adding the second 2012r2 to the domain, this issue is still there... adding the 2008r2 server to the domain and running BPA it gives the following:
    Title:
    This domain controller must register a DNS SRV resource record, which is required for replication to function correctly
    Severity:
    Error
    Date:
    7/3/2014 11:24:48 AM
    Category:
    Configuration
    Issue:
    The "DcByGuid" DNS service (SRV) resource record that advertises this server as an available domain controller in the domain and ensures correct replication is not registered. All domain controllers (but not RODCs) in the domain must register this record.
    Impact:
    Other member computers and domain controllers in the domain or forest will not be able to locate this domain controller. This domain controller will not be able to provide a full suite of services.
    Resolution:
    Ensure that "DcByGuid" is not configured in the "DnsAvoidRegisteredRecords" list, either through Group Policy or through the registry. Restart the Netlogon service. Verify that the DNS service (SRV) resource record "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local", pointing to the local domain controller "CM-DC4-NY01.cmedia.local", is registered in DNS.
    More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=126968
    I've tried scanning and then re-scanning every single entry in DNS Manager and do not see any reference to this specific GUID mentioned, nor do I see any other domain controllers referenced that should not be in there. The two 2012r2 and the 2008r2 domain
    controllers are the only ones listed in DNS Manager... the 2003r2 mentioned earlier failed and was removed.

    Just to chime in, I noticed that you said you have one 2008 R2 DC, and two 2012 DCs.
    I also noticed in the ipconfig /all that all DCs are pointint to themselves for DNS. We usually like to see them point to a partner, then itslelf as the second entry, w hether loopback or by its own IP.
    Based on that, what I suggest to level the playing field by choosing the WIndows 2008 R2 DC as the first DNS on all DCs and only administer DNS using that DC. The reason I chose that is because of the least common denominator is what we rather use so we
    don't invoke any new features in the newer 2012 DNS console that 2008 R2 may not understand.  After that's done, on each DC run (and you can use a PowerShell window to run this):
    Rename the system32\config\netlogon.dns and netlogon.dnb files by suffixing ".old" to the file.
    ipconfig /registerdns
    net stop netlogon
    net start netlogon
    Then re-run the dcdiag /e /c /v.
    Post your results, please.
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.
    I thought the DNS entries were supposed to be the other way around? point to themselves first and a partner as secondary? regardless, as requested, I've changed it to what you've prescribed where they point to the 2008r2 server as the primary with themselves
    as the secondary. I've also followed the steps to what seems like refreshing the DNS? on each of the DCs. Here's the output from dcdiag /e /c /v
    Directory Server Diagnosis
    Performing initial setup:
    Trying to find home server...
    * Verifying that the local machine CM-DC1-NY01, is a Directory Server.
    Home Server = CM-DC1-NY01
    * Connecting to directory service on server CM-DC1-NY01.
    * Identified AD Forest.
    Collecting AD specific global data
    * Collecting site info.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory
    =ntDSSiteSettings),.......
    The previous call succeeded
    Iterating through the sites
    Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia
    ,DC=local
    Getting ISTG and options for the site
    * Identifying all servers.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=nt
    DSDsa),.......
    The previous call succeeded....
    The previous call succeeded
    Iterating through the list of servers
    Getting information for the server CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    * Identifying all NC cross-refs.
    * Found 3 DC(s). Testing 3 of them.
    Done gathering initial info.
    Doing initial required tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC1-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC3-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC4-NY01 passed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Advertising
    The DC CM-DC1-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC1-NY01 is advertising as an LDAP server
    The DC CM-DC1-NY01 is advertising as having a writeable directory
    The DC CM-DC1-NY01 is advertising as a Key Distribution Center
    The DC CM-DC1-NY01 is advertising as a time server
    The DS CM-DC1-NY01 is advertising as a GC.
    ......................... CM-DC1-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    [CM-DC1-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC1-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC1-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC1-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC1-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC1-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    ......................... CM-DC1-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC1-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC1-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC1-NY01\netlogon
    Verified share \\CM-DC1-NY01\sysvol
    ......................... CM-DC1-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC1-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC1-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC1-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC1-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 4609 to 5108
    * rIDPreviousAllocationPool is 4609 to 5108
    * rIDNextRID: 4629
    ......................... CM-DC1-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC1-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    A warning event occurred. EventID: 0x0000002F
    Time Generated: 07/08/2014 13:19:14
    Event String:
    Time Provider NtpClient: No valid response has been received from manually configured peer 0.ca.pool.ntp.org
    after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a n
    ew peer with this DNS name. The error was: The peer is unreachable.
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC1-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC1-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC1-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC1-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Advertising
    The DC CM-DC3-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC3-NY01 is advertising as an LDAP server
    The DC CM-DC3-NY01 is advertising as having a writeable directory
    The DC CM-DC3-NY01 is advertising as a Key Distribution Center
    The DC CM-DC3-NY01 is advertising as a time server
    The DS CM-DC3-NY01 is advertising as a GC.
    ......................... CM-DC3-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC3-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC3-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC3-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC3-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC3-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC3-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC3-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    ......................... CM-DC3-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC3-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC3-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC3-NY01\netlogon
    Verified share \\CM-DC3-NY01\sysvol
    ......................... CM-DC3-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC3-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC3-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC3-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC3-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15109 to 15608
    * rIDPreviousAllocationPool is 15109 to 15608
    * rIDNextRID: 15110
    ......................... CM-DC3-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC3-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC3-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC3-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC3-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC3-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Advertising
    The DC CM-DC4-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC4-NY01 is advertising as an LDAP server
    The DC CM-DC4-NY01 is advertising as having a writeable directory
    The DC CM-DC4-NY01 is advertising as a Key Distribution Center
    The DC CM-DC4-NY01 is advertising as a time server
    The DS CM-DC4-NY01 is advertising as a GC.
    ......................... CM-DC4-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC4-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC4-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC4-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC4-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC4-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC4-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC4-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    ......................... CM-DC4-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC4-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC4-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC4-NY01\netlogon
    Verified share \\CM-DC4-NY01\sysvol
    ......................... CM-DC4-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC4-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC4-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC4-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=DomainDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    CN=Configuration,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's
    no longer replicating this nc. 0 had no latency information (Win2K DC).
    ......................... CM-DC4-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15609 to 16108
    * rIDPreviousAllocationPool is 15609 to 16108
    * rIDNextRID: 15609
    ......................... CM-DC4-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC4-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC4-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC4-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC4-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC4-NY01 passed test VerifyReplicas

  • I can't connect to Internet anymore (WIFI or Ethernet). This was working perfectly before. I don't get a proper IP address from my ADSL box and it seems there is a DNS error when accessing the Internet.

    I have an issue with my MacBook pro (MAC OS X 10.8.3) when trying to access Internet. I am behind an ADSL box (Orange). I have a PC on the same LAN which accesses Internet perfectly via the same Box.
    On the MAC, I have tried WIFI and Ethernet. And have same issue on both. I have checked the IP address (the ADSL box is a DHCP server) but the MAC doesn't get a proper IP and network mask I tried a manual IP address setup and it doesn't get better. I have setup the DNS servers for my Internet provider, but I get DNS error. I have tried 2 Internet browsers (Chrome and Safari), both have the same issue.
    I tried to put my MAC on a different ADSL box (I have 2 acccesses with 2 providers at home) and get the same issue.
    I also noticed a havy CPU load on the mDNSResponder process (at least 30%). I have restarted it, but no improvement.
    Last, I have repared the permissions.
    From those trials, it seems that the problem is on the Mac side. But I am completelly without any new idea, so I need help
    Thanks

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, or by a peripheral device. 
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including Wi-Fi on certain iMacs. The next normal boot may also be somewhat slow.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • DNS error 404, 407,408 on Server 2008 R2

    Trying migrate an old Server 2003 DC to 2008 DC.  I ran adprep, forest etc on the old domain controller and everything was successful.
    On the first domain controller (Server 2003)  the 1<sup>st</sup> NIC card has an IP of 192.168.1.2 subnet of 255.255.255.0, gateway of 192.168.1.1 (Router) and DNS of 192.168.1.10. 
    On the 2<sup>nd</sup> card on the same server, the IP is 192.168.1.10, subnet of 255.255.255.0, gateway of 192.168.1.1 and DNS 192.168.1.10. 
    When I first tried to promote active directory I received an RPC error. 
    I noticed that RRAS was installed on the old domain controller and removed it since it is no longer needed. 
    After removing, Active directory successfully transferred and replicated. 
    I then went to Transfer the FSMO roles and it transferred successfully. 
    After rebooting the 2008 server I now get a DNS error “The DNS server could not open socket for address 192.168.1.9.”, “The DNS server could not bind a Transmission Control Protocol (TCP) socket
    to address 192.168.1.9”. “The DNS server could not bind a User Datagram Protocol (UDP) socket to 192.168.1.9.” 
    These errors are 404, 407 and 408.  On other programs are running on port 53. 
    On active directory I get an event error Event ID2092 ” This server is the owner of the following FSMO role, but does not consider it valid.”
    If I shut down the old 2003 domain controller active directory does not work. 
    I cannot connect to Active directory sites and services, users and computers etc. 
    The old domain controller resumed the primary FSMO roles. 
    What can I do to correct this problem? 

    Hi,
    Holding two NICs/IP address is not recommanded on DCs, Mr. Ace got a blog on this, see:
    Multihomed DCs with DNS, RRAS, and/or PPPoE adapters
    http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx
    If two IP addresses on the old DC are no longer needed, please try to configure into one IP address. We may consider to transfer the FSMO back and once the environment is clean, we can then have all the FSMOs on the new DC.
    Please run DCDiag, NetDiag and Repadmin to check the health of the DCs and the replication and
    Ipconfig /all for the two DCs, If possible, please upload the output into skydrive and post the link here.
    In addition, please check if the following articles could help:
    Event ID 408 — DNS Server Configuration
    Event ID 404 — DNS Server Service Status
    Best regards
    Michael
    If you have any feedback on our support, please click
    here.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • DNS Scavenging - Which Record are scavenged?

    I am about to enable scavenging in a domain that has never had scavenging enabled properly.  There are hundreds of records with old time stamps.  We have done our due diligence in researching records to disable deleting the old record if it has
    an old time stamp.  Previous admin's would let a server grab a DHCP server and then static IP the DHCP address.
    I know that Event ID 2501 will give me a summary of how many records were scavenged.  I seem to remember that (its been a while since I have been in a mess like this), there is a way to get a list/log of the records that were scavenged.  I hope
    we have all the records set, but I the first scavenging period may be painful.
    Is there a way to get a list of each record that was scavenged?

    You might want to setup DHCP credentials and add the DHCP server to the DnsUpdateProxy group. This way it will update the IP of the host instead of creating another one.
    And you really don't want to go below 24 hours with a lease, because technically scavenging is in multiple of days. And you must set the scavenging NOREFRESH and REFRESH values
    combined to be equal or greater than the DHCP Lease length.
    DHCP DNS Update summary:
    - Configure DHCP Credentials.
      The credentials only need to be a plain-Jane, non-administrator, user account.
      But give it a really strong password.
    - Set DHCP to update everything, whether the clients can or cannot.
    - Set the zone for Secure & Unsecure Updates. Do not leave it Unsecure Only.
    - Add the DHCP server(s) computer account to the Active Directory,  Built-In DnsUpdateProxy security group.
      Make sure ALL other non-DHCP servers are NOT in the DnsUpdateProxy group.
      For example, some folks believe that the DNS servers or other DCs not be
      running DHCP should be in it.
      They must be removed or it won't work.
      Make sure that NO user accounts are in that group, either.
      (I hope that's crystal clear - you would be surprised how many
      will respond asking if the DHCP credentials should be in this group.)
    - On Windows 2008 R2 or newer, DISABLE Name Protection.
    - If DHCP is co-located on a Windows 2008 R2, Windows 2012, Windows 2012 R2,
     or NEWER DC, you can and must secure the DnsUpdateProxy group by running
     the following command:
      dnscmd /config /OpenAclOnProxyUpdates 0
    - Configure Scavenging on ONLY one DNS server. What it scavenges will replicate to others anyway.
    - Set the scavenging NOREFRESH and REFRESH values combined to be equal or greater than the DHCP Lease length.
    More info:
    This blog covers the following:
    DHCP Service Configuration, Dynamic DNS Updates, Scavenging, Static Entries, Timestamps, DnsUpdateProxy Group, DHCP Credentials, prevent duplicate DNS records, DHCP has a "pen" icon, and more...
    Published by Ace Fekay, MCT, MVP DS on Aug 20, 2009 at 10:36 AM  3758  2 
    http://blogs.msmvps.com/acefekay/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group/
    I also recommend reviewing the discussion in the link below:
    Technet thread: "DNS Scavenging "
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/334973fd-52b4-49fc-b1d8-9403a9481392/dns-scavenging
    Some other things to keep in mind with registration and ownership to help eliminate duplicate DNS host records registered by DHCP:
    =====================================================
    1. By default, Windows 2000 and newer statically configured machines will
    register their own A record (hostname) and PTR (reverse entry) into DNS.
    2. If set to DHCP, a Windows 2000, 2003 or XP machine, will request DHCP to allow
    the machine itself to register its own A (forward entry) record, but DHCP will register its PTR
    (reverse entry) record.
    3. If Windows 2008/Vista, or newer, the DHCP server always registers and updates client information in DNS.
       Note: "This is a modified configuration supported for DHCP servers
             running Windows Server 2008 and DHCP clients. In this mode,
             the DHCP server always performs updates of the client's FQDN,
             leased IP address information, and both its host (A) and
             pointer (PTR) resource records, regardless of whether the
             client has requested to perform its own updates."
             Quoted from, and more info on this, see:
    http://technet.microsoft.com/en-us/library/dd145315(v=WS.10).aspx
    4. The entity that registers the record in DNS, owns the record.
       Note "With secure dynamic update, only the computers and users you specify
            in an ACL can create or modify dnsNode objects within the zone.
            By default, the ACL gives Create permission to all members of the
            Authenticated User group, the group of all authenticated computers
            and users in an Active Directory forest. This means that any
            authenticated user or computer can create a new object in the zone.
            Also by default, the creator owns the new object and is given full control of it."
            Quoted from, and more info on this:
    http://technet.microsoft.com/en-us/library/cc961412.aspx
    =====================================================
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

  • SNMP trap on OutOfMemory Error Log record

    I would like to implement SNMP trap on OutOfMemory Error Log record.
    In theory SNMP LogFilter with Severity Level "Error" and Message Substring "OutOfMemory" should do the trick.
    In reality it does not work (doh)(see explanations below), I wonder if someone managed to make it work.
    Log entry has following format:
    ----------- entry begin ----------
    ####<Nov 12, 2003 3:09:23 PM EST> <Error> <HTTP> <ustrwd2021> <local> <ExecuteThread: '14' for queue: 'default'> <> <> <101020> <[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>
    java.lang.OutOfMemoryError
         <<no stack trace available>>
    ------------ entry end ------------
    Notice that java.lang.... is NOT part of the log record, yep it seems that exception stack trace is not part of log record! Thus filter could be applied only to "<[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>" string, which is really useless.
    Here is fragment of trap data (i had to remove Message Substring in order to get Error trap to work)
    1.3.6.1.4.1.140.625.100.50: trapLogMessage: [WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception

    Andriy,
    I dont think you could do much here, since Outofmemory is not part of
    log record SNMP agent cannot filter on this. I would be curious to hear
    if anyone got it to work using SNMP.
    sorry,
    -satya
    Andriy Potapov wrote:
    I would like to implement SNMP trap on OutOfMemory Error Log record.
    In theory SNMP LogFilter with Severity Level "Error" and Message Substring "OutOfMemory" should do the trick.
    In reality it does not work (doh)(see explanations below), I wonder if someone managed to make it work.
    Log entry has following format:
    ----------- entry begin ----------
    ####<Nov 12, 2003 3:09:23 PM EST> <Error> <HTTP> <ustrwd2021> <local> <ExecuteThread: '14' for queue: 'default'> <> <> <101020> <[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>
    java.lang.OutOfMemoryError
         <<no stack trace available>>
    ------------ entry end ------------
    Notice that java.lang.... is NOT part of the log record, yep it seems that exception stack trace is not part of log record! Thus filter could be applied only to "<[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>" string, which is really useless.
    Here is fragment of trap data (i had to remove Message Substring in order to get Error trap to work)
    1.3.6.1.4.1.140.625.100.50: trapLogMessage: [WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception

  • Slicers Removed from Template: "Removed Records: Slicer Cache from /xl/slicerCaches/slicerCache3.xml part (Slicer Cache)"

    Product: Microsoft Office Professional Plus 2010
    I have created a template file with a data table, 2 pivot tables, and each of those 2 pivot tables has a pivotchart and 2 slicers.  I have some code that updates the pivot table ranges.  When that occurs the pivot tables, pivotcharts and slicers
    all update successfully.  
    The problem comes after saving the .xlsm file.  Upon opening the file I receive a message saying "Excel found unreadable content in 'myTemplate.xlsm'. Do you want to recover the contents of this workbook? If you trus the source of this workbook,
    click Yes."
    I then get a list or removed records and the repair that was done.
    Removed Records: Slicer Cache from /xl/slicerCaches/slicerCache3.xml part (Slicer Cache)
    Removed Records: Slicer Cache from /xl/slicerCaches/slicerCache4.xml part (Slicer Cache)
    Removed Records: Slicers from /xl/slicers/slicer2.xml part (Slicer)
    Removed Records: Drawing from /xl/drawings/drawing4.xml part (Drawing shape)
    Repaired Records: Named range from /xl/workbook.xml part (Workbook)
    Most of the file is OK with the exception of my last worksheet.  The pivot table and chart get updated, but the slicers are gone.  Any idea why this is happening?  Can something be done to prevent this?
    Thanks,
    Rich

    Hi Rich,
    Based on your description, my understanding is that slicers are removed after you get the error messages and repair it. You wonder to know why slicers are lost after repairing, it seems that the corrupted file caused the issue.
    Please try to update the  pivot table ranges manually without macros. According to my test, the slicers won’t be lost without macros. Please test this method in your own environment. If it
    works fine after disable macros, please check your code.
    If my understanding is incorrect, could you upload a sample via OneDrive and be at bit more precise explain your problem, so that we can get more accurate solutions to this problem. I am glad to help and forward to your reply.
    Hope it’s helpful.
    Regards,

  • Removed Records: PivotTable report from /xl/pivotTables/pivotTable1.xml part (PivotTable view)

    I keep getting an error in Excel 2013 when using PowerPivot. Can someone please explain to me what this error means? I can't see that there is anything wrong with the underlying data, and the list of "removed data" is empty too...
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>error085600_01.xml</logFileName><summary>Errors were detected in file 'E:\SkyDrive\Documents\Forex\Greenzone_Stats\Greenzone_2013_v2.xlsx'</summary><removedRecords summary="Following is a list of removed records:"><removedRecord>Removed Records: PivotTable report from /xl/pivotTables/pivotTable1.xml part (PivotTable view)</removedRecord></removedRecords></recoveryLog>
    TIA!
    Dennis

    Turns out it's a resource limitation in Excels chart rendering engine. If I filter the data model so that less rows are included in the PivotChart, the error goes away.
    Re
    Dennis

  • I keep getting a Yahoo DNS error handler page, and can't even access the add-ons page to disable it because it redirects me to the Yahoo DNS page immediately

    I have already seen some suggested solutions to the problem of this extremely annoying Yahoo DNS error solutions page, but they involve going to the add-ons page of firefox and disabling various add-ons. The issue is that even when I try to go to the add-ons page I get immediately redirected to the Yahoo DNS solutions page again.
    I have cleared my browser history and cache, hoping it would help, but nothing. Extremely annoying as I never installed anything - it simply started after a Firefox upgrade.
    Any help much appreciated.

    Open the Help menu and choose Restart Firefox with Add-ons Disabled. Remove any offending extensions. For details, see the "Uninstall from Firefox Safe Mode" section of the following article.
    * [[Cannot uninstall an add-on]]

  • Intermittent "Cannot find server or dns error"

    We are getting "Cannot find server or dns error" intermittently. It happens most frequently using internet explorer on https. Anyone else getting this or have any suggestions?
    (I have logged as TAR 1525537.999)
    null

    After many, many hours or research and corresponding with other
    Oracle resources, we resolved the issue. We still receive the
    "Cannot find server or DNS error" but with much, much less
    frequency.
    Here are the complete details:
    Environment:
    Windows NT 4.0 SP 6
    Oracle 9iAS 1.0.2.2
    Oracle 9iAS Portal 3.0.9.8.0
    Oracle 8i Database 8.1.7.0.0
    Apache HTTP Server: 1.3.19 (win32)
    mod_ssl: 2.8.1
    OpenSSL: 0.9.5a
    SSL port: 443
    Problem:
    We were running into the following error intermittently (but very
    frequently) when accessing pages in the Oracle Portal application
    with SSL enabled:
    "Cannot find server or DNS error" at the bottom of a "Page cannot
    be displayed" error page.
    Resolution:
    7 Applied patchset for Oracle8i 8.1.7.1.1 (to database client and
    server)
    7 Applied patchset for Oracle8i 8.1.7.1.5 (to database client and
    server)
    7 Applied patchset for Oracle Portal 3.0.9.8.1
    7 Implemented solution for Oracle Bug No. 1822053 (HTTP 404 Doing
    Portal Development) by changing (and un-commenting) the following
    line in our Apache http.conf file:
    From: #SetEnvIf User-Agent ".*MSIE.*" nokeepalive
    ssl-unclean-shutdown
    To: SetEnvIf User-Agent ".*MSIE.*" ssl-unclean-shutdown
    7 Implemented solution for Oracle Bug No. 1821195 (When uploading
    large file using modplsql & SSL error reading data from client)
    by replacing the existing ApacheModuleSSL.dll file with the
    patched file referenced in the bug details.
    Note: Bug No. 1821195 is for Oracle9iAS 1.0.2.2. It references
    Bug No. 1773627 for Oracle9iAS 1.0.2.1.
    I feel the biggest help was finding out about Bug No.
    1821195/1773627. We were provided the bug details by a local
    Oracle technical consultant, Dave McMarlin, referred to us by the
    Oracle Joint Staff Account Manager. That solved our problem with
    receiving the noted error message when we tried to add items to
    the content area. Applying the change to the http.conf file
    identified by Bug No. 1822053 (removing the nokeepalive entry) in
    combination with the Oracle8i and Oracle Portal upgrade seems to
    have solved our problems with the other intermittent occurrences
    of the noted error message.
    According to the details for the ApacheModuleSSL.dll patch, there
    was mention of a bug in the "select" function in Windows NT 4.0:
    "When checking a socket, if data can be read without blocking,
    select () returns yes, but when actually reading from the socket
    with recv(), that function returns WSAEWOULDBLOCK, which says
    that reading would block. It seems that this problem does not
    occur in usual operation, but only in an SSL enabled Apache
    (modssl or apache-ssl) with https. The code for WIN32, which
    handles writing to a socket, already contains a workaround for
    this. The code for reading from a socket did not have a
    workaround."
    Oracle Technical Assistance Report and Bug Information:
    TAR Number: 1727314.999
    BUG Reference: 1924408
    Open Date: 07/31/2001
    Abstract: Intermittent "Cannot find server or DNS error"

  • While Checking In " Cannot remove record because it has links"

    Hi All,
    We have an scenario while checking In MDM records in Data manager showing the following error " Cannot remove record because it has links".
    There are 2 main tables Table A and B, both are look up main to each other.
    Record 1 from Table A is linked with 5 records in Table B and one of the record from Table B is linked to Record 1 of Table A
    All the Records from Table B is checked In. Now am Check-out Record 1 from Table A and trying to Check-In back, while performing the same am getting the following error  " Cannot remove record because it has links".
    Is this work as per the Look up main design or am I missing anything. Help appreciated.
    thanks,
    <ar>

    Hi Alex,
    Before removing record you need to remove links for those records. By this I mean you must have a field in Table A which is lookup to Table B and vice-versa. So firstly delete this field value which is a sort of relationship between these two tables and afterward only try to delete/remove record.
    Regards,
    Mandeep Saini

  • Homework 3-4 Error finding record data

    Hi,
    I was stumped for a bit trying to access the data stored in the record store. RecordStore.getNumRecords() returns the correct number of stored records, 5, but when the code loops and tried RecordStore.getRecord(index), I got a RecordStoreException with the message "Error finding record data"
    The trouble was that I didn't read the documentation or look at the example closely enough to see that the store's recordId is a 1 based number, so 1..<=count, not 0..<count. Either that or use the RecordEnumeration and hasNextElement/nextRecord.

    I already made some tests connected with SUPERVISOR. Nothing changed.
    Finally, I removed ODI from this host and made a completely new installation and it works now. But don't ask me why !
    B.L.

  • Problem with wrt54gl Cannot find server or DNS Error

    Hello,
    I am having problem with wrt54gl roouter. I have windows 2K professional that connected trough the wire. The browser (and other tools) is periodically loosing connection for around 30-60 seconds showing "Cannot find server or DNS Error". after refreshes it comes back. If I connect PC directly to internet without router I never have a problem. I have put statical resolution of dns servers(3 of them) and ip does not help. I switch between ports on pc and router site, change the cable, remove antivirus, put latest windows updates, use different browsers. Disable anable 2d network card (2 on mother board).
    Any suggestions?
    Thanks

    Hi… Login to the setup page of the router and reduce the MTU to 1365. Upgrade or re-flash the firmware if needed.

  • Data length error in record 86.

    Data length error in record 86.
    Message no. FV147
    Diagnosis
    An error occurred in the processing of the data to be imported. It is highly probable that this is a data error.
    Contact your data provider.
    System Response
    Any account statement processing currently underway and any outstanding is being terminated.
    Procedure
    Check the structure of the supplied data. If the statement data you have obtained is error-free, you can simply restart the program. All those statements which have already been imported correctly will not be reimported.
    {1:F01SCBLINBBXXXX3446100003}{2:O9400634140719SCBLINBBXXXX34461000031407190634N}{3:{108:00000000000718}}{4:
    :20:14071905fr309439
    :25:52205785839
    :28C:611
    :60F:D140718INR792788,04
    :61:1407180718CR100000,00N169NONREF         
    :86:IN36701407187774 VIJBH14199069837
    IN36701407187774 VIJBH14199069837
    AGARWAL AGENCIES
    :61:1407180718CR150000,00N169NONREF         
    :86:IN36701407187251 SBIN414199017384
    IN36701407187251 SBIN414199017384
    EAGLE FOOTWERE
    :61:1407180718CR100000,00N169NONREF         
    :86:IN36701407187052 SAA96678573
    IN36701407187052 SAA96678573
    TANVEER TRADERS
    :61:1407180718CR98000,00N169NONREF         
    :86:IN36701407186828 SBIN314199982628
    IN36701407186828 SBIN314199982628
    MODERN AGENCY
    :61:1407180718CR179000,00N169NONREF         
    :86:IN36701407186029 SAA96670577
    IN36701407186029 SAA96670577
    BALAJI ENTERPRISES
    :61:1407180718CR60000,00N169NONREF         
    :86:IN36701407185397 367845438
    IN36701407185397 367845438
    SAKSHI ENTERPRISES
    :61:1407180718CR2000000,00N169NONREF         
    :86:IN3670140718H568 SBIN414199360804
    IN3670140718H568 SBIN414199360804
    RELAXO FOOTWEARS LIMITED
    :61:1407180718CR38000,00N169NONREF         
    :86:IN3670140718G554 CBINH14199566672
    IN3670140718G554 CBINH14199566672
    WONDER WALK AGENCIES
    :61:1407180718CR113000,00N169NONREF         
    :86:IN3670140718F851 JAKA140718621672
    IN3670140718F851 JAKA140718621672
    JYOTI SALES PROP MR AMIT VOHRA S
    :61:1407180718CR54200,00N169NONREF         
    :86:IN3670140718F006 BKIDN14199343033
    IN3670140718F006 BKIDN14199343033
    SHAH FOOT WEAR
    :61:1407180718CR64000,00N169NONREF         
    :86:IN3670140718F094 BKIDN14199343132
    IN3670140718F094 BKIDN14199343132
    MUSKAN TRADERS
    :61:1407180718CR114500,00N169NONREF         
    :86:IN3670140718F423 SBIN414199302946
    IN3670140718F423 SBIN414199302946
    GOUTAM DISTRIBUTORS
    :61:1407180718CR63000,00N169NONREF         
    :86:IN3670140718D651 SD1141261589
    IN3670140718D651 SD1141261589
    M K FOOTWEAR
    :61:1407180718CR67913,00N169NONREF         
    :86:IN3670140718D057 SBIN414199247753
    IN3670140718D057 SBIN414199247753
    SSS PG STORES
    :61:1407180718CR130000,00N169NONREF         
    :86:IN3670140718D183 UTBIN14199275937
    IN3670140718D183 UTBIN14199275937
    GOPAL SHOES
    :61:1407180718CR48000,00N169NONREF         
    :86:IN3670140718C628 CBINH14199546949
    IN3670140718C628 CBINH14199546949
    AGGARWAL FOOTWEAR
    :61:1407180718DR5000000,00N506PIRLXOIN01A00468
    PIRLXOIN01A00468                 
    :86:PIRLXOIN01A00468 SCBLR12014071800003757
    CASH SCBLR12014071800003757
    RELAXO FOOTWEARS LIMITED
    SIN09373C0000423 00001 PIRLXOIN01A0
    0468
    PIRLXOIN01A00468
    :61:1407180718DR4000000,00N506PIRLXOIN01A00469
    PIRLXOIN01A00469                 
    :86:PIRLXOIN01A00469 SIN09373Q0000468
    PIRLXOIN01A00469-SIN09373Q0000468
    SB3670140718HK96
    SIN09373C0000424-00001 PIRLXOIN01A0
    0469
    :61:1407180718DR1699195,25N699TRF            
    :86:316031790865 PAY001
    316031790865 PAY001
    GRAND WISE ENTERPRISES LIMITED
    AKMP037
    USD28,030.8 60.5755/INR743.76 1
    DEBIT IMEX CUSTOMER A/C
    :61:1407180718CR480000,00N195NONREF         
    :86:IL36701407182157 BARBR52014071800734481
    CASH BARBR52014071800734481
    APNA FOOT WEAR
    SENDER IFSCBARB0CHARMI
    IL36701407182157
    :61:1407180718CR235000,00N195NONREF         
    :86:IL36701407185517 SBINR52014071801147506
    CASH SBINR52014071801147506
    PRAKASH FOOT WEAR
    FUND TRF FRM 33174969142 TO52205785
    SENDER IFSCSBIN0016310
    IL36701407185517
    :61:1407180718CR500000,00N195NONREF         
    :86:IL36701407185083 SBINR12014071801142317
    CASH SBINR12014071801142317
    MODERN FOOTWEARS
    SENDER IFSCSBIN0001521
    IL36701407185083
    :61:1407180718CR800000,00N195NONREF         
    :86:IL36701407184746 HDFCR52014071851912408
    CASH HDFCR52014071851912408
    FASHION SQUARE
    SENDER IFSCHDFC0000412
    IL36701407184746
    :61:1407180718CR332000,00N195NONREF         
    :86:IL36701407184713 SBINR52014071801140001
    CASH SBINR52014071801140001
    WINGS POLYMERS
    SENDER IFSCSBIN0001581
    IL36701407184713
    :61:1407180718CR450000,00N195NONREF         
    :86:IL36701407184302 FDRLR52014071800031798
    CASH FDRLR52014071800031798
    ABHINAV ENTERPRISE
    SENDER IFSCFDRL0001492
    IL36701407184302
    :61:1407180718CR650000,00N195NONREF         
    :86:IL36701407183976 UCBAR32014071800058993
    CASH UCBAR32014071800058993
    GAYLORD SHOE AND CHAPPAL
    SENDER IFSCUCBA0000048
    IL36701407183976
    :61:1407180718CR700000,00N195NONREF         
    :86:IL36701407183860 SBINR52014071801134507
    CASH SBINR52014071801134507
    FOOTWEAR HOUSE
    RTGS TGH CHQ NO 172867
    SENDER IFSCSBIN0008602
    IL36701407183860
    :61:1407180718CR250000,00N195NONREF         
    :86:IL36701407183487 SBINR52014071801131379
    CASH SBINR52014071801131379
    PRATAP AGENCY PROP MRS SUNITA KUMRA
    SENDER IFSCSBIN0014152
    IL36701407183487
    :61:1407180718CR254740,00N195NONREF         
    :86:IL36701407182511 HDFCR52014071851915942
    CASH HDFCR52014071851915942
    HEPHZIBAH AGENCIES
    SENDER IFSCHDFC0001498
    IL36701407182511
    :61:1407180718CR398000,00N195NONREF         
    :86:IL36701407182496 BARBR52014071800726312
    CASH BARBR52014071800726312
    RAZA FOOT WEAR
    SENDER IFSCBARB0BASTIX
    IL36701407182496
    :61:1407180718CR300000,00N195NONREF         
    :86:IL36701407182349 KKBKR52014071800664337
    CASH KKBKR52014071800664337
    M M DISTRIBUTORS
    PAYMENT
    SENDER IFSCKKBK0000958
    IL36701407182349
    :61:1407180718CR61136,00N169NONREF         
    :86:IN3670140718C504 IOBAN14199026875
    IN3670140718C504 IOBAN14199026875
    M S CHINNS TRADERS
    :61:1407180718CR79995,00N169NONREF         
    :86:IN3670140718C142 SBIN414199219784
    IN3670140718C142 SBIN414199219784
    FRONTIER TRADING COMPANY
    :61:1407180718CR100000,00N169NONREF         
    :86:IN3670140718B731 SBIN414199200112
    IN3670140718B731 SBIN414199200112
    SHRI AMBEY TRADERS
    :61:1407180718CR125000,00N169NONREF         
    :86:IN3670140718B521 N199140025581074
    IN3670140718B521 N199140025581074
    SHYAM BROTHERS
    :61:1407180718CR68000,00N169NONREF         
    :86:IN3670140718A144 1205061871400003
    IN3670140718A144 1205061871400003
    POPULAR TRADERS PROP PISHORI LAL SETHI
    :61:1407180718CR41000,00N169NONREF         
    :86:IN3670140718A044 P14071849681718
    IN3670140718A044 P14071849681718
    AKSHAY FOOTWEARS
    :61:1407180718CR50000,00N169NONREF         
    :86:IN3670140718A099 BARBH14199284604
    IN3670140718A099 BARBH14199284604
    STAR ENTERPRISE
    :61:1407180718CR100000,00N169NONREF         
    :86:IN3670140718A002 SAA21370357
    IN3670140718A002 SAA21370357
    JAI OMKAR ENTERPRISES
    :61:1407180718CR120000,00N169NONREF         
    :86:IN36701407189725 UTBIN14199269504
    IN36701407189725 UTBIN14199269504
    SANTI STORES
    :61:1407180718CR100000,00N169NONREF         
    :86:IN36701407189538 SBIN414199107266
    IN36701407189538 SBIN414199107266
    VINAYAK TRADING
    :61:1407180718CR100000,00N169NONREF         
    :86:IN36701407189842 SAA3564919
    IN36701407189842 SAA3564919
    SKY STYLE MARKETING PROP.ABHISHEK S
    :61:1407180718CR120000,00N169NONREF         
    :86:IN36701407189384 MAHBH14199609866
    IN36701407189384 MAHBH14199609866
    ROYAL FOOT WEAR
    :62F:D140718INR1697499,29
    :64:C140718INR59273846,71
    -}{5:{CHK:CHECKSUM DISABLED}{MAC:MACCING DISABLED}}

    SAP REPLAY
    Regarding the incidence itself, kindly consider that The 86-record
    limitation is not a bug of the program, but the standard design.
    The error is coded as FV147, when the Note to Payee in Record 86
    exceeds 65 characters in Program RFEKA400.
    You will need to contact your Bank in order to obtain a correct file:
    I have attached some documentation on this message that will allow your
    bank to create it.
    Otherwise, you may use the following user-exit (SAP NOTE 494777):CMOD
    Enhancement Exit Name FEB00004 > EXIT_RFEKA400_001.
    This User Exit is called in RFEKA400 in the line: PERFORM
    PROCESS_RAW_DATA TABLES SWIFT. In Include ZXF01U06, you have
    the option to process the raw data.
    Hope this information is useful to you.

  • WRT54G2 DNS errors when connecting online to PS3... at a loss for ideas...

    Im having dns problems ever since PSN went back online and i cannot connect to the internet with my PS3 or log onto PSN. At first i would get dropped as soon i joined an online game, and it was running very slowly, but now it wont connect at all.
    Wired works perfectly. Wireless wont work.
    If i use automatic setup then the ip address fails.
    If i manually set everything then the ip address passes but the internet connection fails and i get a dns error.
    Signal strength is 100% and i have a Linksys WRT54G2 router. (worked perfect 2+ years until this week)
    I have Roadrunner cable modem.
    I did ipconfig/all and enetered all numbers from there and didnt work.
    I used standard dns like google and such and those didnt work.
    Im seriously at a loss for ideas. Is my router broken? Please can anyone help?

    I don't think it's necessarily your router. I've encountered the same problem on my WRT54GC and I used OpenDNS. But it gave me all sorts of problems with different websites so I had to take it out and use manual DNS. I used all sorts of combinations through until I got 4.2.2.2  to work.
    EDIT: also, try going in to your router's setup page and click Status. Take note of the DNS values and use those in setting up your PS3.

Maybe you are looking for