[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 277
  • Last Modified:

How to configure router windows 2003(SBS) DHCP, DNS for internet connection on client computers

hello friends,

i have windows 2k3(sbs) having 3 network cards, with one netgear switch is connected and to the switch 12 client pcs win xp and win 2k with latest service packs. win 2k3 sbs is running as domain controller, DHCP activated, WINS running.
I have DSL Connection - modem connected to NetGear FVS 318 router.
DSL connection is with dynamic ip.

Windows 2003 SBS (192.168.100.1, 255.255.255.0) - Switch - Client computers

i dont want to use RRAS, but simply want to share internet through router, but want to run DHCP from Windows 2k3 SBS.
I have diabled DHCP on router.
Added Router ip address (192.168.100.201,255.255.255.0)     now i dont know what would be the DNS address of router. Gateway of router.

can some body tell me how i connect these things using 1 and/or 2 Network cards of server that local network and internet sharing both can work.

please write me what addresses should i give as ip, subnet, dns, gateway, dhcp fields in server/router where ever needed and DNS forwarding in server to which address?

little confused ...
0
bhattmilan
Asked:
bhattmilan
  • 2
1 Solution
 
Fatal_ExceptionCommented:
I would disable one of your NICs and only use one to connect to the switch.

You need to use the built-in DNS server on the DC for name resolution, so configure it and use Forwarders  (Forwarder Tab) for name resolution on the internet.  Also make sure your clients are using it for DNS or you will have real trouble with your Clients logging onto the Domain.

You can configure your router with any address as long as it is in the same subnet, and is not in the DHCP configured Scope on your server.  But I prefer either using the first or last IP addresss, so your Router and (Default Gateway on all clients/server) address would be 192.168.100.254.  This should be either statically set on the systems, or can be pushed out by your DHCP server.

Your DNS server on your DC will be the same address as the static IP address of your server.  (192.168.100.1)

Subnet is all class C, and Classful, so your configs are correct there.

Actually, this is a pretty simple setup.  Just make sure that your server has the IP address hard coded (static) and your DNS is working properly.

FE
0
 
Fatal_ExceptionCommented:
Thanks..

FE
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now