Computing.Net > Forums > Windows Server 2003 > Setting up server based LAN

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Click here to start participating now! Also, check out the New User Guide.

Setting up server based LAN

Reply to Message Icon

Name: uncommon21
Date: July 17, 2006 at 12:35:39 Pacific
OS: win xp
CPU/Ram: 512
Product: compaq
Comment:

Using Microsoft's Server 2003, I know you have to setup a domain controller. Now within setting up the domain controller can you set up the DNS server? Or do you need to setup the DNS server before the domain controller?

After all that is said and done, then do you go in and setup the DHCP server?

Is the 3 main parts for setting up a domain: domain controller, DNS, DHCP....and then going ahead and creating user accounts in active directory?




Sponsored Link
Ads by Google

Response Number 1
Name: rmartin74
Date: July 17, 2006 at 13:05:54 Pacific
Reply:

In my experience, once you have configured the DC, it doesnt matter which you set up next, DNS or DHCP. You should be able to go into Manage Server from the start menu and select Add Role, then select either DHCP or DNS. You can also add it from add/remove windows components. For info on DNS you maight try this link:

http://support.microsoft.com/default.aspx?
scid=kb;en-us;814591

Once you have DNS, DHCP (if needed) and a DC, you have the basics for a Domain and can move forward with your user account creation. Depending on your router, it can also hand out DHCP addresses. There are a few security risk for having a DHCP server on your DC ....according to MS.


0

Response Number 2
Name: uncommon21
Date: July 17, 2006 at 13:54:45 Pacific
Reply:

Now then, what steps would I take on setting up the LAN with Internet. I have a DSL router, would i just plug that into the switch? Is there any configuration on the server i need to do? thanks


0

Response Number 3
Name: heropsycho2177
Date: July 17, 2006 at 18:35:40 Pacific
Reply:

If you don't have DNS setup upon DCpromo'ing, you will be prompted to set DNS up. If you don't know DNS, allow DCPromo to setup your DNS for you.

Security risks are more associated with NOT using Windows as the DHCP server, as Windows DHCP can do secure DNS updates, and has some checks against rogue DHCP servers. That is if you believe Microsoft over others.

In reality, it is also a security risk since DHCP is another vector for attack on the server.
Please help survivors of Hurricane Katrina!

www.redcross.org


0

Response Number 4
Name: uncommon21
Date: July 18, 2006 at 08:30:50 Pacific
Reply:

Now then, what steps would I take on setting up the LAN with Internet. I have a DSL router, would i just plug that into the switch? Is there any configuration on the server i need to do with DNS? thanks


0

Response Number 5
Name: Kirk Obenschain
Date: July 18, 2006 at 10:43:00 Pacific
Reply:

uncommon21, You need to list the router's IP address as the default gateway in your NIC's TCP/IP properties. The router's IP address has to be on the same network. The router I installed had an IP address of 192.168.1.1, and by typing that address into IE's address bar I was taken to the setup page for the router. When prompted, I could enter anything for user but had to enter "admin" for the password. On this page, I was able to change the IP address if I needed to for the router to match the network's address. I would not have had to do this had my network had an address of 192.168.1.x/24. Hope this helps.


0

Related Posts

See More



Response Number 6
Name: uncommon21
Date: July 21, 2006 at 13:30:14 Pacific
Reply:

So, by enterning my routers IP address as my default gateway in TCP/IP properties, this will setup the LAN with internet? All i would have to do is plug into switch and set up machines to obtain IP address automatically and I am online?


0

Response Number 7
Name: Kirk Obenschain
Date: July 24, 2006 at 07:43:24 Pacific
Reply:

That's all there was to it for me because my router came with DHCP enabled. Good luck.


0

Response Number 8
Name: wanderer
Date: July 25, 2006 at 11:54:40 Pacific
Reply:

Incorrect.

With server you DO NOT want your router doing dhcp. You want your SERVER doing dhcp since it auto updates DNS server.

DO NOT point your server to the internet for DNS during install but to ITSELF. You can corrupt Active Directory by doing so since the ISP's dns server will not allow writes which are required for AD install.

MS DNS works like this:
wkst makes a request for google.com. The wkst dns settings say go to the MS servers DNS to resolve. MS DNS doesn't know about google.com so it looks at its FORWARDERS TAB for the ISPs DNS server(s) you entered. It forwards the request to the ISP's DNS which returnes the answer to MS DNS with in turn gives it to the wkst.

Otherwise you end up with major name resolution/can't find server issues.

Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.


0

Response Number 9
Name: wanderer
Date: July 25, 2006 at 11:57:42 Pacific
Reply:

Forgot to add that 2003 server can be a standalone server which means no Active Directory. Might be a easier setup to maintain for you.

Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.


0

Sponsored Link
Ads by Google
Reply to Message Icon

Win 2003 Server Stand. R2... Sharing file permissions ...



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Setting up server based LAN

Setting up Server 2003 www.computing.net/answers/windows-2003/setting-up-server-2003/8265.html

VPN ip WAN PPP error www.computing.net/answers/windows-2003/vpn-ip-wan-ppp-error/5899.html

Help setting up terminal server www.computing.net/answers/windows-2003/help-setting-up-terminal-server/7192.html