Solved

Setting up Domain with DNS and DHCP

Posted on 2011-03-24
9
747 Views
Last Modified: 2012-05-11
Hey Everyone -

Just recently setup a new Server wtih Server 2008 Standard as a sole server (DC). Normally I setup Server 2003 SBS servers which I find a little more easy (probably biased). However, setting up a domain was a bit different.

The client currently had a single laptop on his network which is owned by the landlord. Before i setup the Server in the office, I provided a static IP for the router to interface with the landlords connection, the internal router address as 192.168.1.1 and DCHP from the Server starting at 192.168.1.100. This allowed all users to connect to the web in the mean time. One thing to note: there are only two laptops connecting to the server and they are connecting wirelessly on the network.

However, I then setup the domain via DCPROMO and enabled the DNS Server and DHCP Server. I gave the server a static IP of 192.168.1.5 and started DCHP Server to give out addresses after 192.168.1.99. DNS was setup as well. I then removed DHCP from the router.

However, the wireless clients were unable to be added to the domain without changing the DNS entry in the TCP/IP settings to 192.168.1.5. I then removed that entry after joining the domain, but then they are unable to get to the internet.

These laptops are regularly taken home and need fully dynamic TCP/IP settings.

Anything I'm missing?
0
Comment
Question by:tecpub
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
9 Comments
 
LVL 11

Expert Comment

by:JoeNuvo
ID: 35212578
you have to diag to see why it can't go over internet.
possible reasons

1. IP Configuration obtain is incorrect.  got ex : wrong gateway IP
    base on your given data.  IP Config which client obtain should be as following
    IP  : 192.168.1.99 and over
    Sub : 255.255.255.0
    Gateway : 192.168.1.1
    DNS : 192.168.1.5

2. DNS service on DC can't resolve the name
    either on the client on or the DC, try nslookup
    you might need to set Forwarders in the DNS to 192.168.1.1

access to DC and access to Internet is 2 different issues.
0
 

Author Comment

by:tecpub
ID: 35212582
Currently, I have them setup with Static IP Settings exactly like you said and they are able to access the web and network. However, when it's dynamic, they lose connection...
    IP  : 192.168.1.99 and over
    Sub : 255.255.255.0
    Gateway : 192.168.1.1
    DNS : 192.168.1.5

Looks like the forwarding (or lack of) is my problem?
0
 
LVL 14

Accepted Solution

by:
Justin Yeung earned 500 total points
ID: 35212644
it sounds like your dhcp is not setup correctly.

make sure you have option "router" = 192.168.1.1 and "dns server should be 006" with 192.168.1.5

anyway when you get the ip address from your dhcp, do you get the same configuration as your type in staticly?
0
Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

 

Author Comment

by:tecpub
ID: 35212654
This is under "Server Options" correct?

Currently, I have "003 Router" Unchecked and "006 DNS Server" with 127.0.0.1 as the IP address. I'll change those right now.
0
 

Author Comment

by:tecpub
ID: 35212667
justinyeung: what's the difference between setting the IP for "003 Router" to the IP of the server compared to the physical router of 192.168.1.1?

Should I keep the DHCP service running on the router when it's set to 192.168.1.1?
0
 
LVL 14

Expert Comment

by:Justin Yeung
ID: 35212710
the router under dhcp 003 is the gateway option and your gateway is your router in this senario.
0
 

Author Comment

by:tecpub
ID: 35212715
Great. So I can leave the DHCP service off on the router... correct?
0
 
LVL 14

Expert Comment

by:Justin Yeung
ID: 35212717
you should disable your router dhcp to avoid getting incorrect set of ip.

cause your router will give out the address like this

192.168.1.x (the scope of your router)
255.255.255.0
192.168.1.1
and here is the problem dns will be 192.168.1.1 which you will not able to authenicate to your DC.
0
 

Author Comment

by:tecpub
ID: 35212719
Perfect, that's already done. So the problem it looks like was the forwarding.

Thanks justinyeung!
0

Featured Post

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

One of the most often confused topics in the area DNS is the idea of GLUE records. Specifically, what they are, when they are needed, when they are provided, and how they are created. First, WHAT IS GLUE? To understand GLUE, you must first under…
Occasionally you run into the website or two that will not resolve properly using your own DNS servers.  Some people simply set up global forwarders for their DNS server.  I don’t recommend doing this because it can cause problems resolving addresse…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question