Re: Win 2K Server setup

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

From: Richard G. Harper (rgharper_at_email.com)
Date: 10/09/04 

Date: Sat, 9 Oct 2004 06:36:56 -0400

In broad strokes, here's how I would proceed:

1. Set up the Windows 2000 Server in a workgroup. Don't install anything
except the default Windows components (well, perhaps add things like the
monitoring tools, but certainly don't install DNS, DHCP, etc. right now).
Give the server a fixed IP address in the range you want to use for your
network - given the size of your network I'd use whatever IP address range
the router is using right now.

2. Install Active Directory and let the AD Wizard set up a DNS zone when it
discovers that you have no DNS server active now. Be sure your domain name
is one that cannot be duplicated outside the network (like using
MyDomain.local instead of MyDomain.com).

3. Once things have had a bit to settle out, install DHCP on your server.
You'll need to authorize the server in Active Directory. Be sure you set
the DHCP server options for DNS server so that it points to your AD DNS
server and set the default gateway to the IP address of your router.

4. Create user accounts on the domain controller.

5. Disable DHCP on the router.

6. Reboot each client PC and make sure it gets the correct settings via
DHCP. If the client doesn't have the right DNS server the next step won't
work.

7. Join the client PCs to the domain.

You can fill in the details on AD, DNS, DHCP, etc at
http://www.microsoft.com/technet or http://msdn.microsoft.com/; basic
networking at sites like http://www.wown.com/ and
http://www.practicallynetworked.com/ 

-- 
Richard G. Harper [MVP Win9x]  rgharper@gmail.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all.  Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
"Suezy" <Suezy@discussions.microsoft.com> wrote in message 
news:0EF23AE7-2456-4464-8356-59448D68501A@microsoft.com...
>I would appreciate any advice in setting up a Internal soho domain with win
> 2k server, 4 win xp clients and a wireless router/firewall (Netgear 
> WTG624).
>
> I have enough understanding to manage something when it is setup, but not 
> to
> configure the dns, dhcp, ad etc.. so this is my first attempt.
>
> The router currently gets the IP from the cable and is then a dhcp server 
> to
> my clients. (I have the server 2k machine just running as a dhcp client at
> the moment).
> The router is configurable to not be a dhcp server and to reserve IP's 
> etc.
>
> I would like suggestions please on how to setup and configure the server 
> so
> it becomes the dhcp server for the clients, yet gets the benefit of the
> router/firewall and provides ICS for the clients also without having to
> register an external domain name.
> What IP addresses should I use etc ?
>
> Also if there is any very basic setup info websites that would help me I
> would appreciate it. I get lost in too much technical stuff like I have 
> been
> trying to read sofar, most is talking big scale stuff, rather than 
> something
> small like I want to do.
>
> Thanks to all in anticipation of some good help :-)
>
> Suezy

Relevant Pages

  • RE: RPC Service unavailable
    ... Below are settings with fixed and DHCP settings on one op the clients: ... DNS Suffix search list: maddogs.local ... also when setting things on DHCP I can still access the client woth RDP ... is that the dhcp server is assigning some options incorrectly, ...
    (microsoft.public.windows.server.dns)
  • Re: RRAS and FQDN (connection-specific dns suffix is blank)
    ... domain within the DNS tab of TCP/IP properties so that names are resolved properly but this doesn't solve the issue with the server not being able to hand out the domain suffix to the vpn client when the clien logs in. ... this would be done via DHCP but I'm using a static set of IP addresses for vpn clients. ... The client does not get its network config directly from DHCP even if you use the DHCP option. ...
    (microsoft.public.windows.server.networking)
  • Re: Application Hang
    ... If the workstation ip is expired, the lease time is exceeded, delete the ip on the DHCP server "address leases" and run ipconfig /renew on the workstation. ... The forwarders ip is only used form the DNS server, all domain members will ask the domain DNS server for the www.whatever.com address, if the server doesn't know it, it will automatically forward ther request to the ip addresses under the forwarders tab. ... When I do a "ipconfig /all" on the client, ...
    (microsoft.public.windows.server.networking)
  • Re: Internet Speed
    ... I think what we are trying to say is to use the DHCP from the SBS and NOT ... DNS and WINS point to the SBS. ... as the server IP address. ... it is recommend to configure all SBS client computers' IP and DNS ...
    (microsoft.public.windows.server.sbs)
  • RE: Understanding ISA Server System Policy
    ... for dhcp and dns the system policies do able isa to be dhcp and dns CLIENT ... I know it is best having ISA on another server but that is what the primary ... Client for Microsoft Windows, QoS, File and Printer sharing, TCP/IP. ...
    (microsoft.public.isa.configuration)