Results 1 to 3 of 3

Thread: Win2k domain gubbins...

  1. #1
    Senior Member
    Join Date
    Feb 2005
    5 times in 5 posts
    • Neo_VR's system
      • Motherboard:
      • DFI X48L2R
      • CPU:
      • QX9450@3.2gig
      • Memory:
      • 4gb Corsair
      • Storage:
      • 2x36gb raptors striped 640gb AAKS
      • Graphics card(s):
      • Gainward 8800gt
      • PSU:
      • Enermax Liberty 600
      • Case:
      • Antec P182
      • Operating System:
      • Vista Ultimate
      • Monitor(s):
      • Dell 22" wfp
      • Internet:
      • BT 8meg

    Win2k domain gubbins...

    Sorry to bother the windows server elite out here but ive got a few questions...

    1) when joining a XP machine to a win2k served domain... the machine always takes ages to logon(at least 2 minutes).... any reason why... any way round it?

    2) Is there some tickbox somewhere that blocks remote administration of the domain.. ive been trying to administer the group policys from my xp sp2 machine (logged onto domain with admin + GP edit rights) but it says it cant access the domain... also if i try to put a 2k3 server in as another domain controller/backup controller in the same domain, it also cannot connect.. so i think its a security setting somewhere... anyone got any ideas?

    thanks in advance

  2. #2
    Will work for beer... nichomach's Avatar
    Join Date
    Jul 2003
    Preston, Lancs
    138 times in 99 posts
    • nichomach's system
      • Motherboard:
      • Gigabyte GA-870A-UD3
      • CPU:
      • AMD Phenom II X6 1055T 95W
      • Memory:
      • 16GB DR3
      • Storage:
      • 1x250GB Maxtor SATAII, 1x 400GB Hitachi SATAII
      • Graphics card(s):
      • Zotac GTX 1060 3GB
      • PSU:
      • Coolermaster 500W
      • Case:
      • Coolermaster Elite 430
      • Operating System:
      • Windows 10
      • Monitor(s):
      • Dell 20" TFT
      • Internet:
      • Virgin Media Cable
    Sounds more like naffed up DNS to me; I take it your existing server is its own DNS server? i.e. It has the DNS server installed and the settings for at least its internal facing network adapter's TCP/IP settings are pointed at itself? Are you using DHCP, and if so, is the DHCP server set to use the domain controller as the DNS server for its clients?

    If you're administering from an XP workstation and the DNS isn't configured correctly, you will get messages like "a domain controller for X could not be contacted" and that sort of thing.

    DNS problems will also interfere with logons. The other common cause for long logons is bloated profiles.
    Last edited by nichomach; 11-03-2005 at 07:13 PM.

  3. #3
    Join Date
    Jan 2005
    0 times in 0 posts
    I agree with nichomach, sounds like dns to me. Active Directory requires a healthy dns to function right, so it would make sense that your administration would fail as well. Dns is where you should start your troubleshooting.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. ICS for a domain cleint, again
    By oshta in forum Networking and Broadband
    Replies: 3
    Last Post: 06-01-2005, 08:14 PM
  2. See one domain
    By Stringent in forum Software
    Replies: 0
    Last Post: 08-11-2004, 10:21 AM
  3. Domain Controllers and Win 2k3 SBS???
    By jo8t1 in forum Help! Quick Relief From Tech Headaches
    Replies: 20
    Last Post: 16-08-2004, 11:57 AM
  4. Replies: 10
    Last Post: 24-04-2004, 12:06 PM
  5. Newbie alert! How to point my 123reg domain to my home server?
    By Theo in forum Networking and Broadband
    Replies: 13
    Last Post: 06-12-2003, 03:27 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts