Member Avatar for bondi007

i set up the domain
and the ip address
and the subnet mask

so
the computers will be


and so on

and the subnet mask will be automaticly configured

and the domain i set up on the main windows server 2003
is

so all my computers are pluged into the hub/switch
and all my ip addresses are assigned

ive got 4 xp machines and one server 2003 machine
all i do is right click on my computer and click change name and add it to

and my users that i set up in active directory on the windows server 2003 machine would work on the xp machines

Hope your still awake


Is that right
cheers

soz about all the threads ive made

  • 3 Contributors
  • 4 Replies
  • 109 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by TheNNS

Dani AI

Generated

Short, practical notes for with follow-ups to and : the basic domain setup is fine, but a few often-missed items will stop domain joins or logons. Verify these before adding XP machines.

  • DNS: clients must resolve the domain controller. Point each client�s primary DNS to the server running Active Directory and set the DNS suffix/search suffix. Use ipconfig /all and nslookup on a client to confirm the server is being used and SRV records are visible.
  • Time sync: Kerberos authentication requires clocks to be close. Make sure client time matches the DC (otherwise logons fail).
  • Addressing: if you use static IPs, set gateway and DNS manually. For easier administration, consider running DHCP on the server or a router and ensure option 003 (gateway) and 006 (DNS) are correct.
  • Firewalls/ports: disable or allow AD-related traffic while joining (DNS 53, Kerberos 88, LDAP 389, RPC 135, SMB 139/445, NetBIOS 137-138). Third-party firewalls on clients commonly block joins.
  • Permissions and computer accounts: join using an account with rights to create computer objects (or pre-create the computer account in AD). By default, non-admins can join a limited number of machines unless changed.
  • Client updates: keep XP at latest service pack/patches for best compatibility.

As mentioned, if internet access is needed there are two simple options: let a dedicated router do NAT/gateway (easiest), or enable NAT on the server (RRAS/ICS) if you need the server to handle routing. �s offer of guides is useful for step-by-step screenshots.

Quick troubleshooting checklist: from a client run ipconfig /all, nslookup <domain>, and ping <dc-hostname>; if join fails note the exact error and check the client and DC event logs. If DNS lookup of the DC fails, fix DNS first — almost all domain problems trace back to name resolution.

Recommended Answers

All 4 Replies

Member Avatar for Spriggan

seems right, but im far from an MCSE.
I can however email you some PDFs that may help if you PM me.

Member Avatar for TheNNS

if you have internet connection, don't forget to configure your server with routing services so the computers can get internet access.

Member Avatar for bondi007

i havnt got internete but will the stuff i told you work?

Member Avatar for TheNNS

yes it should.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.