Re: Logon Win2000

From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 07/05/04

  • Next message: Mojon: "The policy software restriction policies" 
    Date: Mon, 05 Jul 2004 19:27:12 GMT

    First make sure your dns is configured correctly for the domain. Your domain
    controller must point to itself as it's preferred dns server in tcp/ip properties and
    the XP Pro computers must point only to the AD domain controller for dns. Never list
    any ISP dns servers as a preferred dns server on any W2K/XP Pro domain computers.
    Since you are having problems it would be a good idea to run first netdiag and then
    dcdiag on your domain controller and then netdiag on one of your XP Pro computers
    looking for failed tests/errors/fatal warnings.

    http://support.microsoft.com/default.aspx?scid=kb;en-us;301423 --- how to install
    netdiag and dcdiag

    If all that checks out, then go to your Domain Controller Security Policy and under
    security settings/local policies/security options find the option for "digitally sign
    communications always" for client and server and set them both to disabled. Then do
    the same for Domain Security Policy. Rune secedit /refreshpolicy machine_policy
    enforce on the domain controller and reboot an XP Pro computer to see if it helps.
    There are known issues where smb signing is used in a W2K domain with XP Pro SP1
    clients. --- Steve

    "Cristiano Parisotto" <CristianoParisotto@discussions.microsoft.com> wrote in message
    news:60642084-1734-440A-AC85-A3AC6ABA38AB@microsoft.com...
    > Dear Friends,
    >
    > I have a problem login in my Domain server.
    >
    > I have 1 server win 2000 with basic configuration like AD, DNS, DHCP, and IIS.
    >
    > In My Xp clients I configure the clients to log on in the AD server. Everything
    work normally, but is so much slowly.
    >
    > In the Active Directory and don't configure anything my clients in win98 work
    normally and is faster.
    >
    > This occour only in the clients with WinXP
    >
    > I have read and want to know if anyone can helpme, I see that I can configure the
    policy settings of the AD, can this is the problem?
    >
    > There are any configuration in the client or in the server that make the logon more
    faster ?
    >
    > If anyone can help me.
    >
    > Thanks so much
    >
    > Cristiano
    >
    >

  • Next message: Mojon: "The policy software restriction policies"

    Relevant Pages

    • Re: Network connections gets disconnected
      ... I have tried different brand firewall router also yesterday. ... server IP as the DNS Server but still having same problem.... ... AD clients MUST point to the DNS ... Do not put your ISP's DNS server *anywhere* on an AD client. ...
      (microsoft.public.win2000.networking)
    • Re: Can Internet Computers see my private address DNS server?
      ... I have not placed any of our computers in the NAT router's DMZ. ... It is my intent, eventually, to turn the client with the Win Server 2003 ... and there are 6 clients. ... address is entered in the Alternate DNS server: ...
      (microsoft.public.windows.server.dns)
    • Re: setup/configure internal domain dns server?
      ... the ISP provided dns servers and not the main domain controller but I ... AD must have a DNS server setup for the AD domain. ... DNS server to itself for DNS, use the actual IP address not 127.0.0.1. ... Point all AD clients to the DNS server setup for the AD domain ONLY (Servers ...
      (microsoft.public.windows.server.dns)
    • Re: Can Internet Computers see my private address DNS server?
      ... To let your DNS server resolve these external names I typically just ... I would recommend using your 2003 server to perform your DHCP. ... and there are 6 clients. ... In the DNS server dialog box, I have entered my Internet Service ...
      (microsoft.public.windows.server.dns)
    • Re: setup/configure internal domain dns server?
      ... the ISP provided dns servers and not the main domain controller but I ... AD must have a DNS server setup for the AD domain. ... DNS server to itself for DNS, use the actual IP address not 127.0.0.1. ... Point all AD clients to the DNS server setup for the AD domain ONLY (Servers ...
      (microsoft.public.windows.server.dns)