QUESTION: Configuring AD within a Home Network topology

Tech-Archive recommends: Speed Up your PC by fixing your registry



Hello.

I have a domain (domain.local 192.168.2.102, static) running at home. I have
4 other computers using DHCP (192.168.2.x) from the Linksys router.

I can faneagle (sp?) with things to get a workgroup computer to joing the
domain by selecting domain and entering domain.local, and proceeding to
authenticate with a Domain Admin account. Most of the computers are wifi, so
logging on initially doesnt work. I typically have to log on as local admin
on each machine for the wifi to initialize, and then proceed to log off, and
then switch the dropdown to the domain.local, and then proceed.

I am unsure if the Wireless update rolloup MSFT rolled out in 2006 will
improve my authentication to the wifi network prior to log on/authentication.

I have had limited success using http://servername/connectcomputer to join
the domain as well, and was wondering how to finesse this technique, as it
appears to work ok.

My big thing is wanting to know how to nail down DNS setup, DHCP, etc.


I just want to use, and currently have it in use, server.domain.local,
192.168.2.102 running AD, and DNS.

So, each host is set to use the primary DNS of 192.168.2.102 and secondary
192.168.2.1... which is the router.

Also, for DNS, do I only setup forward lookup zones, since I can forward the
request to the router at 192.168.2.1, or where am I to go?

Within the router, do I change the configuration of the DNS, or do I point
the DNS to server.domain.local?

I have spent a few nights trying to search for a layout in terms of IP
addressing withing a home environment, which really isnt too different from a
business layout.

I feel that it is almost too simple, and I am making it difficult.

If anyone can begin to understand, please provide any feedback,

Thanks!
.



Relevant Pages

  • Re: Testing environment question
    ... For your domain members to function properly they must use the local DNS server. ... Turn off the DHCP function on the router. ... You can set up DHCP on the DC or you can just configure the machines manually to use the router for default gateway but use the DC for DNS. ...
    (microsoft.public.windows.server.general)
  • Re: Networking problems (again) tough one
    ... The problem *only* occurs on my Linux machines. ... DNS numbers, ... all systems start working again whether setup manually or with DHCP. ... If theu are shoing good, and yet things dont work, you may have a misconfigured router. ...
    (comp.os.linux.setup)
  • Re: Remote Site, DHCP Scope Issue
    ... user is going to call me tomorrow after they turn on the computers. ... When DHCP is disabled at the remote office, ... DNS) in that location. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Site, DHCP Scope Issue
    ... going to call me tomorrow after they turn on the computers. ... When DHCP is disabled at the remote office, ... Win2003 DC (running AD-integrated DNS) in that location. ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS Problem??
    ... In the DHCP field at the router, ... > DNS but it adds the 'public' side DNS automatically. ... Do you have another SERVER class machine with the clients? ...
    (microsoft.public.windows.server.dns)