Charm: No Domain Controller for SB5

Hi,
I configured Charm in solution Manager 4.0, created a satellite system SB5 in smsy and run the batch to get the info to charm. now i have it in /tmwflow/cmsconf but when i synchronize the project in solar_admin_project we get the error No Domain Controller for SB5.
The STMS is configured correctly in SB5
The RFC dests are OK also from SMSY i can see the dommain controller without any problem and distribution routes also.
Any advise
Thanks
Ahmed

Thanks Pascal,
I was able to fix the problen but adding a domain link between solution manager and satellite systems.
Ahmed

Similar Messages

  • ACL migration Error : 1210 could not find a domain controller for domain "Test Domain" (Old Domain)

    Hi
    We are migrating from old domain to new domain. Before live migration, we are trying to check the ACE/ACL migration through SubInACL. We are running the SubInACL on a cluster, which is a member of the Old Domain (Test Domain). We are able to resolve and
    ping both Old Domain and the New domain from this cluster machine. We have created a network share on this cluster, which is accessible to all Domain Users of the Old Domain. Both Domains have two way forest level trust. we are trying to migrate
    the ACL of this share (\\ClusterMachine\testshare$) to the new domain using SubInACL. We are trying to run the below command to get it done.  
    subinacl /outputlog=C:\Users\Administrator\Desktop\Migrationlog.txt /subdirectories
    \\ClusterMachine\testshare$\*.* /migratetodomain=OldDomain=NewDomain=mappingfile.txt
    Mapping file contains : Domain Users=NewDomain_Users
    But we are geeting the Error that "1210 could not find a domain controller for domain "Test Domain". Error finding domain name : 1210 the format of the specified computer name is invalid. Current Object "\\ClusterMachine\testshare$"
    will not be processed."

    Hello,
    how in detail is DNS set up in each domain?
    Any problems when using nslookup to verify?
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://blogs.msmvps.com/MWeber
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    Twitter:  

  • Unable to find domain controller for the specified domain. Please explicitly specify the domain controller.

    Im getting error "Unable to find domain controller for the specified domain. Please explicitly specify the domain controller."   when I try to create an AD connection for my User Profile Service.  The entire sharepoint environment is installed
    on one server.  That server has everyting on it, AD, SQL, Sharepoint, and its the domain controller. I cant figure out why this will not identify?Trevor Fielder

    Hi,
    Did you get this error when clicking on the Populate Containers button?
    If yes, please make sure that you have provide the domain credentials in the account name and password
    boxes below when entering the domain information. The account must be granted the replicating directory changes permission on the domain.
    You can refer to this blog:
    http://www.harbar.net/articles/sp2010ups.aspx
    Xue-Mei Chang

  • Pricing for VM running WS 2012 E R2 primarily as domain controller for ~5 clients

    Hi
    I am starting a small medical clinic, with only about 6 client PCs.  However, I  would like a domain network structure for security purposes moving forward rather than a workgroup.
    I'm looking at either purchasing a modest server (ie HP Proliant ml310) with windows server 2012 essentials r2 and using it locally (total cost ~$1500) or using a Windows Azure virtual machine to run the domain controller over a VPN.  We already use
    office 365 e3, so don't really need a local server for email, storage etc. I already have an old synology NAS that could be used for disk images etc that we would lose out on with the hosted server solution.
    Can someone verify my calculations for monthly cost estimate I tried using the calculator --1 small VM + 225 GB storage for the OS came to $65/month
    Would I be able to run it on the small virtual machine or would I need to go up to medium just for the OS?  If the later is the case it would definitely not be cost effective.
    Thanks for the help
    TM

    hi tdiddy,
    Thanks for posting!
    About VM and azure storage pricing , I suggest you could refer to this pricing details page and calculations fee:
    http://azure.microsoft.com/en-us/pricing/details/virtual-machines/
    http://azure.microsoft.com/en-us/pricing/details/storage/
    Also, for this billing question Please contact azure billing support team via
    http://www.windowsazure.com/en-us/support/contact/
    Hope it helps.
    Regards,
    Will
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Best pracices for setting up Domain controller for our remote European offices

    Hi,,
    We have about 17 remote site across Europe (HQ in UK), I want to start revoking the offices local DC's and host them in a couple of Cloud servers in Germany with local NAS boxes for file storage. I will have MPLS network between the offices to the Cloud
    DC.
    Now what would be the best practices and tips for this situation in respect to the DC's. How can I prioritize the remote offices to use the Cloud DC/DNS and not our DC at our HQ in the UK. Would it be better to have a sub-domain created (europe.company.co.uk)
    for the other offices.
    Any suggestions on this setup for the DC

    Hiya,
    on the conceptual level. The reason for having local DC's, is that if the local sites internet line is offline, people are still able to authenticate and access local resources. From that point of view, you might as well just run with your HQ DC's only. Note:
    the cloud does offer availability on their services, that might not be matched by your HQ in terms of double internet lines.
    That said.
    The DNS server of the clients as well as the sites & services of Active Directory. Your clients will use the nearest domain controller available from sites and services information.
    Managing Intersite Replication
    http://technet.microsoft.com/en-us/library/cc794799%28v=ws.10%29.aspx

  • [Forum FAQ] How to sync time with a Domain Controller for a standalone server

    As we all known, if a computer belongs to an Active Directory domain, it will sync the time automatically by using the Windows Time service that is available on Domain Controllers.
    While a standalone server will synchronize with its local hardware time and Windows time server. (Figure 1)
    Figure 1.
    Under some circumstances, a standalone server is necessary in a product environment. We can sync the time of this standalone server with the Domain Controller using
    the steps below:
    1. Modified the value of the AnnounceFlags:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
    Under this entry we can see the default value of AnnounceFlags is 10 (Decimal), we configure the value as 5 (Decimal). (Figure 2)
    Figure 2.
    2. Confirm the value of the registry key below is set to 0:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer 
    Figure 3.
    3. Configure the standalone server to synchronize with a specific time source (Domain Controller).
    In our test, we configured our Domain Controller (192.168.10.200) as the time source. Used the following commands:
    w32tm /config /syncfromflags:manual /manualpeerlist:192.168.10.200
    4. Sync the time with the Domain Controller using the command below:
    w32tm /config /update
    From the figure below (Figure 4), you can see the after we did all the steps above, the time on the standalone server was synced with the Domain Controller.
    Figure 4.
    (Note: Peerlist is a separated list of DNS servers, or IP Addresses for the time servers)
    More information:
    Windows Time Service Tools and Settings
    http://technet.microsoft.com/en-us/library/cc773263(WS.10).aspx#w2k3tr_times_tools_dyax
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Thank you for the instruction! I am sure it is one of the scenarios that majority of administrators will run into. So I suggest to write a wiki about it and publish it for this month's TechNet Guru in Windows Server section. This month's TechNet Guru can
    be found here:
    Calling All Wise Men! Windows
    Server Gurus Needed! Apply Within! No One Turned Away!
    Thanks for your informative post. :)
    Regards.
    Mahdi Tehrani   |  
      |  
    www.mahditehrani.ir
    Please click on Propose As Answer or to mark this post as
    and helpful for other people.
    This posting is provided AS-IS with no warranties, and confers no rights.
    How to query members of 'Local Administrators' group in all computers?

  • Replace WS2003 domain controller for WS2012 domain controller

    Hi, I think that is a common problem but I haven't found anythink exactly like this, only something similar, but I have a lot of doubts yet.
    The thing is that I have a network with two domain controllers:
    WS2003     - 192.168.0.1, who is the first domain controller I created and is also a file sharing server
    WS2008R2 - 192.168.0.8, who is a  new domain controller I added one year ago.
    Now, I want to replace the first one, keeping the second. One.
    I thinking of removing the first one and replace it with a new machine (WS2012) with the same IP and name host. I need the same host because clients are pointing to it to get the shared files.
    My main fear is that clients get some error related with trust relationship and I will have to rejoin them one by one to the domain.
    As I have another domain controller, Will the global catalog of the new machine be synchronized automaticly with the WS2008R2 domain controller?
    Do I need to demote the old domain controller before add the new one?
    Thanks a lot

    Hi Tomas,
    As pointed by Burakm you should have an additional file server and should avoid using a Domain controller which has priviledged access, to share files. This puts you at a security risk.
    Regarding the requirement of old host name:
    Here is something that would let you keep a different servername and IP, yet allow your users to connect to the old hostname and access the share. Use CNAME records of old server to point it to the new hostname.
    How to Configure Windows Machine to Allow File Sharing with DNS Alias
    You might also look for Distributed File System Shares.
    http://blogs.technet.com/b/josebda/archive/2009/06/26/how-many-dfs-n-namespaces-servers-do-you-need.aspx
    NOTE- You can't run in-place upgrade of a 2003 to 2012 DC.
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Changing Domain Controller for Exchange 2013

    Folks
    I have an Exchange 2013 running on Server 2012.
    Old DC on Server 2008.
    I want to decommission the 2008 server. I have build a 2012 DC and for the life of can not work out how to change the DC that my exchange box uses????
    Using Set-ADServerSettings cmdlet only seems to change the server for that current session?? reboot and back to the old DC...
    When I use the Se-ExchangeServer cmdlet, I get domain controller cant be found. I have set the execution policy on the dc to unrestricted and still Domain controlleer cant be found..
    New dc is a GC..
    Any ideas would be good.
    -graham

    First, the behavior observed for the cmdlet Set-ADServerSettings is normal. The values for the domain controllers
    designated are " per session". For example:
    The PreferredServer parameter
    specifies the FQDN of the domain controller to be used for this session.
    http://technet.microsoft.com/en-us/library/dd298063(v=exchg.150).aspx
    +++
    What parameters, exactly, did you use for Set-ExchangeServer? What was the entire command?
    If the domain controller(s) were found for "Set-ADServerSettings"
    and... if Exchange is functioning OK in general, the domain controllers should be accessible.
    +++
    Are you in a position where you could shut down the older server (during off hours for example) and see if Exchange can
    find - and use - the newer DC?
    Will you only have one DC after decommission of the old one?
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • AD account logging to a remote domain controller for authentication

    Hi,
    I have a weird issue with an AD account using a different logonserver when authenticating to AD.  A domain admin account uses the local site domain controller but another account is using a remote domain controller as logonserver. I'm using both account
    to logon to the same server (CRM 2011). But when I issue the command "set l' from the command line, they shows different logonserver value. 
    My issue is the crm account is pointing to a remote domain controller (windows 2012 R2) which I don't want and should use the local site domain controller (windows 2008 R2). The reason being is that the CRM server is on a  test network (isolated) and
    when we test an upgrade of CRM addon product called Experlogix, the upgrade requires to get authenticated by AD but it fails and I think the logonserver is the issue. When the crm account is used on the test server it points not to the local site domain controller
    but to the remote dc which is not in the test server.
    Thanks for your help!!!
    AA

    Start by checking that your are sites and subnets are well configured.
    Use dssite.msc and make sure that:
    You have AD sites that represent your physical sites
    All the subnets in use are created and moved to the correct AD site
    Your DCs belong to the correct AD site
    You can read more about the DC Locator process here: http://social.technet.microsoft.com/wiki/contents/articles/24457.how-domain-controllers-are-located-in-windows.aspx
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Preparing virtual domain controller for cloning fails because DC not in cloneable domain controllers group

    Hi I am running a virtulized server 2012R2 DC DC02TL.test.local in a lab environment. I want to clone the DC. I am following this tutorial.
    http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12-metablogapi/0020.clone3_5F00_49D67345.png
    I put the DC into the Group of clonable Dcs but somehow the CMDLet
    New-ADDCCloneConfigFile
    does not seem to recognize that the DC is in that group and fails. I tried to reboot the DC, but no luck.

    https://support.microsoft.com/kb/2745013?wa=wsignin1.0
    This link may help you.
    Darshana Jayathilake

  • Central Domain Controller in Solution manager

    Hi All,
    We have configured ChaRM successfully for ECC and BI system landscapes, by creating domain links between Solution Manager domain controller and individual domain controllers for ECC and BI systems. Now, we are planning to go for a central domain controller (Solman Domain Controller) for all the satellite systems. So basically, we plan to move the individual domain controllers from ECC and BI to solman domain controller and i guess there will not be domain links required anymore.
    With regards to above scenario, please help me with below queries:
    1 - Will the above strategy work with chaRM or not
    2 - If yes, what are the activities that would be required to be redone in satellite system and solman system
    3- Any critical pre-requisites that needs to be checked before we can start this exercise
    Please help me with the above queries. Appreciate your time and effort.
    Thanks in advance.
    Regards,
    Imran

    HI,
    Yes, you could use solman to be set as the main domain controller; either way with domain links, please kindly have a look
    at this expert blog by our Charm expert;
    /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
    On transport group matters , you may want to visit this blog, on point no. 3
    https://weblogs.sdn.sap.com/cs/junior/view/wlg/15116
    Hope this helps.
    Cheers
    SH

  • Lack of Connectivty to Domain Controller - Domain Controller Access Issues Requires Repeated Reauthentication

    Sorry if my attempt to be thorough in my description may result in excessive and unnecessary information. 
    I'm running into some problems with a single server running WS 2012 R2 as a domain controller (AD and DNS) and I’m trying to figure out what the cause is. 
    The network has ~10 computers on it connected through a cable business gateway (running DHCP) which feeds 2 switches and a wireless router acting as a switch. (I also turned on remote services, but the end users aren’t using that until I get certificates
    setup.)
    For 6+ months everyone had access to the shared files and databases on each workstation without issue. 
    In the last month users would occasionally have to re-enter their credentials to get access to shared server folders despite being on a domain account already. 
    Last week one of the computers intermittently cannot gain access to the shared folders– entering the correct credentials just results in the credentials being requested again and again: There’s an error icon at the bottom saying that “there are currently
    no logon servers available to service the logon request”.  While access is rejected I’m still able to ping the DC both via its name and IPV4 address. 
    (Pinging via its name results in an IPv6 address in the response.) 
    Other network connectivity appears intact (able to browse the web, perform network discovery.)
    Things that ‘seem’ to allow access on this computer until the next failure:
    Entering a different domain username and password into the windows credentials request has allowed access a couple of times.
    Disconnecting and reconnecting the network cable allowed the original username to be used to log on (at least once.)
    After removing it from and then rejoining it to the domain (a few hours ago) it experienced the problem once more. Also, logging on with domain credentials created a TEMP user folder instead of the folder with the domain username. 
    Looking at the event logs, I notice there are quite a few warnings and errors reported regarding DC access on many of the computers; maybe this is normal?
    Most Problematic Computer:
    Event ID 8016:  System failed to register host A or AAAA resource records. (With an unknown Ipv6 and the server’s ipv4 address in the DNS server list.) 
    Event ID 131:  NtpClient unable to set a domain peer to use as a time source because of DNS resolution error on ‘Server.domain.local’ 
    ‘No such host is known.”
    Event ID 5719:  NETLOGON. This computer was not able to setup a secure session with a domain controller in the domain due …..: there are currently no logon servers available to service the logon request.
    And then pairs of: Event 1500: The Group Policy settings for the computer were processed successfully. There were no changes detected since the last successful processing of Group Policy. & Event 1054:
     The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
    Event 1030:  The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation
    at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.
    On the server I’ve run DCDIAG and DCDIAG /test:DNS and those all appeared to pass.
    Ipconfig/all from the server:
       Connection-specific DNS Suffix 
       Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
       Physical Address. . . . . . . . . : FC-4D-D4-F2-A1-83
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2601:8:a182:1100:b155:a0b0:892d:9ed5(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::b155:a0b0:892d:9ed5%13(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.1.10.42(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : fe80::abd:43ff:fe9a:ab47%13
     10.1.10.1
       DHCPv6 IAID . . . . . . . . . . . : 234638804
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-3F-7D-B9-68-05-CA-24-31-C4
       DNS Servers . . . . . . . . . . . : ::1
    127.0.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ipconfig/all from the problematic computer:
    Wireless LAN adapter Wi-Fi:
       Connection-specific DNS Suffix 
    . : wp.comcast.net
       Description . . . . . . . . . . . : Intel(R) Centrino(R) Wireless-N 6150
       Physical Address. . . . . . . . . : 40-25-C2-63-C2-B8
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2601:8:a182:1100:8f5:1606:d0a8:6b25(Prefe
    rred)
       Temporary IPv6 Address. . . . . . : 2601:8:a182:1100:283e:f9e8:4841:6c50(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::8f5:1606:d0a8:6b25%3(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.1.10.31(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Tuesday, March 10, 2015 9:19:02 AM
       Lease Expires . . . . . . . . . . : Tuesday, March 17, 2015 1:23:15 PM
       Default Gateway . . . . . . . . . : fe80::abd:43ff:fe9a:ab47%3
    10.1.10.1
       DHCP Server . . . . . . . . . . . : 10.1.10.1
       DHCPv6 IAID . . . . . . . . . . . : 54535618
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-15-6B-AA-F0-DE-F1-9C-07-D4
       DNS Servers . . . . . . . . . . . : 2001:558:feed::1
    2001:558:feed::2
                    10.1.10.42
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Any thoughts? I was assuming it was a Domain Controller/DNS error, but I don't know where to check next.  Could a failing piece of hardware be the culprit? 
    Thanks,
     -JT

    Hi,
    According to the error you have posted.
    A Netlogon 5719 event indicates that the client component of Netlogon was unable to locate a DC for the domain it was trying to perform an operation against.
    Most of the time this is caused by network issues or name resolution (DNS/WINS) issues, you could refer to:
    Netlogon 5719 and the Disappearing Domain [Controller]
    http://blogs.technet.com/b/instan/archive/2008/09/18/netlogon-5719-and-the-disappearing-domain.aspx
    Did you refer to this KB article?
    Event ID 5719 is logged when you start a Domain Member
    http://support.microsoft.com/kb/938449
    Regards.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Windows Server 2008 R2: Server unable to authenticate with Domain Controller

    Hello, I was wondering what could be the reason for this error if it is certain that there was no other computer on the network using the same name:
    This computer could not authenticate with<Domain-controller>, a Windows domain controller for domain <Domain-name>, and therefore this computer might deny logon requests. This
    inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. 
    What would cause the machine account pw to be 'not recognized'?

    You can track changes in AD by enabling AD Auditing: https://technet.microsoft.com/en-us/library/cc731764%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
    As reading the logs is usually a complicated and time consuming task, it is recommended to use a third party tool for auditing. The one I usually recommend is Lepide Auditor - Active Directory: http://www.lepide.com/lepideauditor/active-directory.html
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Server 2008 Hyper-V Failover Cluster Error on Domain Controller Reboot

    I am pretty new to Hyper-V virtual but I have 2 Hyper-V Clusters, each with 2 Nodes and a SAN, 1 Physical Domain Controller for failover cluster management and 1 virtual domain controller as backup.  All is running well, no issues.  I installed
    windows updates on the physical DC and upon reboot, got an error 5120 on cluster 2 that says "Cluster Shared Volume 'Volume1' ('Cluster Disk 1') is no longer available on this node because of 'STATUS_CONNECTION_DISCONNECTED(c000020c)'.  All I/O will
    temporarily be queued until a path to the volume is reestablished.  It pointed to the 2nd node in that cluster as being the issue but when I look at it, it is online and all healthy so I don't understand why the error was triggered and if the DC would
    go down for a failure, would that node not be able to access the CSV permanently.
    Appreciate any help anyone can provide.

    Hi mtnbikediver,
    In theory, if you has the correct configuration of cluster the DC restart will not cause the CSV down, does your shared storage installed on your DC? Did you run
    the cluster validation before you install the cluster? We strongly recommend you run the cluster validation before you build the cluster, same time please install the recommend update of 2008 cluster first.
    Recommended hotfixes for Windows Server 2008-based server clusters
    http://support.microsoft.com/kb/957311
    I found a similar scenario issue the DC restart will effect the cluster network name resource offline, but it is for 2008R2.
    Cluster network name resource cannot be brought online when one of the domain controllers is partly down in Windows Server 2008 R2
    http://support2.microsoft.com/?id=2860142
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Active Directory domain controller could not be contacted

    Hello
    Help please.
    I am trying to add a new server (2008) to domain 'bridgelimited.local' - only one DC (2003) doing everything at the moment. The plan is to add the new server, then move everything over from the old machine, then retire/upgrade the old machine and use as a backup.
    I am currently trying to dcpromo on the new machine but I get the following error:
    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller for domain bridgelimited.local:
    The error was: "DNS name does not exist."
    (error code 0x0000232B RCODE_NAME_ERROR)
    The query was for the SRV record for _ldap._tcp.dc._msdcs.bridgelimited.local
    Common causes of this error include the following:
    - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
    212.50.160.100
    196.168.16.2
    - One or more of the following zones do not include delegation to its child zone:
    bridgelimited.local
    local
    . (the root zone)
    For information about correcting this problem, click Help.
    192.168.16.2 is IP address for the DC.
    Any help would be grately appreciated.
    Kind Regards
    Richard

    Managed to get the DCDIAG
    Here goes (I know my harddisk is failing - that's why I am desperate to get everything shifted to the new server).
    Domain Controller Diagnosis
    Performing initial setup:
       * Verifying that the local machine bridgeserver, is a DC.
       * Connecting to directory service on server bridgeserver.
       * Collecting site info.
       * Identifying all servers.
       * Identifying all NC cross-refs.
       * Found 1 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\BRIDGESERVER
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             * Active Directory RPC Services Check
             ......................... BRIDGESERVER passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\BRIDGESERVER
          Starting test: Replications
             * Replications Check
             * Replication Latency Check
                DC=ForestDnsZones,DC=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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). 
             * Replication Site Latency Check
             ......................... BRIDGESERVER passed test Replications
          Starting test: Topology
             * Configuration Topology Integrity Check
             * Analyzing the connection topology for DC=ForestDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for DC=DomainDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             ......................... BRIDGESERVER passed test Topology
          Starting test: CutoffServers
             * Configuration Topology Aliveness Check
             * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             ......................... BRIDGESERVER passed test CutoffServers
          Starting test: NCSecDesc
             * Security Permissions Check for
               DC=ForestDnsZones,DC=BridgeLimited,DC=local
                (NDNC,Version 2)
             * Security Permissions Check for
               DC=DomainDnsZones,DC=BridgeLimited,DC=local
                (NDNC,Version 2)
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local
                (Schema,Version 2)
             * Security Permissions Check for
               CN=Configuration,DC=BridgeLimited,DC=local
                (Configuration,Version 2)
             * Security Permissions Check for
               DC=BridgeLimited,DC=local
                (Domain,Version 2)
             ......................... BRIDGESERVER passed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             ......................... BRIDGESERVER passed test NetLogons
          Starting test: Advertising
             The DC BRIDGESERVER is advertising itself as a DC and having a DS.
             The DC BRIDGESERVER is advertising as an LDAP server
             The DC BRIDGESERVER is advertising as having a writeable directory
             The DC BRIDGESERVER is advertising as a Key Distribution Center
             The DC BRIDGESERVER is advertising as a time server
             The DS BRIDGESERVER is advertising as a GC.
             ......................... BRIDGESERVER passed test Advertising
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role Domain Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role PDC Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role Rid Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             ......................... BRIDGESERVER passed test KnowsOfRoleHolders
          Starting test: RidManager
             * Available RID Pool for the Domain is 2609 to 1073741823
             * bridgeserver.BridgeLimited.local is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 2109 to 2608
             * rIDPreviousAllocationPool is 2109 to 2608
             * rIDNextRID: 2121
             ......................... BRIDGESERVER passed test RidManager
          Starting test: MachineAccount
             * SPN found :LDAP/bridgeserver.BridgeLimited.local/BridgeLimited.local
             * SPN found :LDAP/bridgeserver.BridgeLimited.local
             * SPN found :LDAP/BRIDGESERVER
             * SPN found :LDAP/bridgeserver.BridgeLimited.local/BRIDGELIMITED
             * SPN found :LDAP/96d36b0b-a148-4c2f-b3d3-8c2ac83fcaf9._msdcs.BridgeLimited.local
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/96d36b0b-a148-4c2f-b3d3-8c2ac83fcaf9/BridgeLimited.local
             * SPN found :HOST/bridgeserver.BridgeLimited.local/BridgeLimited.local
             * SPN found :HOST/bridgeserver.BridgeLimited.local
             * SPN found :HOST/BRIDGESERVER
             * SPN found :HOST/bridgeserver.BridgeLimited.local/BRIDGELIMITED
             * SPN found :GC/bridgeserver.BridgeLimited.local/BridgeLimited.local
             ......................... BRIDGESERVER passed test MachineAccount
          Starting test: Services
             * Checking Service: Dnscache
             * Checking Service: NtFrs
             * Checking Service: IsmServ
                IsmServ Service is stopped on [BRIDGESERVER]
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: RpcSs
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... BRIDGESERVER failed test Services
          Starting test: OutboundSecureChannels
             * The Outbound Secure Channels test
             ** Did not run Outbound Secure Channels test
             because /testdomain: was not entered
             ......................... BRIDGESERVER passed test OutboundSecureChannels
          Starting test: ObjectsReplicated
             BRIDGESERVER is in domain DC=BridgeLimited,DC=local
             Checking for CN=BRIDGESERVER,OU=Domain Controllers,DC=BridgeLimited,DC=local in domain DC=BridgeLimited,DC=local on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local in domain CN=Configuration,DC=BridgeLimited,DC=local on 1 servers
                Object is up-to-date on all servers.
             ......................... BRIDGESERVER passed test ObjectsReplicated
          Starting test: frssysvol
             * The File Replication Service SYSVOL ready test
             File Replication Service's SYSVOL is ready
             ......................... BRIDGESERVER passed test frssysvol
          Starting test: frsevent
             * The File Replication Service Event log test
             ......................... BRIDGESERVER passed test frsevent
          Starting test: kccevent
             * The KCC Event log test
             Found no KCC errors in Directory Service Event log in the last 15 minutes.
             ......................... BRIDGESERVER passed test kccevent
          Starting test: systemlog
             * The System Event log test
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:47:27
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:47:41
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:47:55
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:09
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:23
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:38
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:52
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:49:06
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:49:20
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:49:54
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:50:08
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:50:22
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:51:33
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:51:53
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:07
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:21
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:35
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:49
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:03
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:17
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:31
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:45
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:12:23
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:12:37
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:12:51
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:05
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:19
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:33
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:47
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:14:01
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:14:15
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:15:24
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:15:38
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:15:53
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:07
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:21
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:35
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:49
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:17:03
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:17:17
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             ......................... BRIDGESERVER failed test systemlog
          Starting test: VerifyReplicas
             ......................... BRIDGESERVER passed test VerifyReplicas
          Starting test: VerifyReferences
             The system object reference (serverReference)
             CN=BRIDGESERVER,OU=Domain Controllers,DC=BridgeLimited,DC=local and
             backlink on
             CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             are correct.
             The system object reference (frsComputerReferenceBL)
             CN=BRIDGESERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=BridgeLimited,DC=local
             and backlink on
             CN=BRIDGESERVER,OU=Domain Controllers,DC=BridgeLimited,DC=local are
             correct.
             The system object reference (serverReferenceBL)
             CN=BRIDGESERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=BridgeLimited,DC=local
             and backlink on
             CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             are correct.
             ......................... BRIDGESERVER passed test VerifyReferences
          Starting test: VerifyEnterpriseReferences
             ......................... BRIDGESERVER passed test VerifyEnterpriseReferences
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
       Running partition tests on : BridgeLimited
          Starting test: CrossRefValidation
             ......................... BridgeLimited passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... BridgeLimited passed test CheckSDRefDom
       Running enterprise tests on : BridgeLimited.local
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope
             provided by the command line arguments provided.
             ......................... BridgeLimited.local passed test Intersite
          Starting test: FsmoCheck
             GC Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             PDC Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             Time Server Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             Preferred Time Server Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             KDC Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             ......................... BridgeLimited.local passed test FsmoCheck
    The only thing I can see (other then the HDD) is the
    IsmServ Service is stopped on [BRIDGESERVER]
    Hope you can help. Pretty please.
    Kind Regards
    Richard

Maybe you are looking for