Some clients not finding the server ?

Hi Folks,
 
                 I am activating DCHP on Windows Server 2012 R2.

Seems faily straightforward -

1) Install the DCHP role
2) Configure the address range
3) Deactivate DCHP on the router

I guess thats it for the server.

One question - how do the domain attached clients find the  (DCHP) server.

I am thinking that I will put a primary and Secondary DNS in the router -

        1.  The DNS of the server (xxx.local)
and 2.  A DNS for the WWW (eg. Googles 8.8.8.8)..

The reason I'm doing this is that we occasionally seem to have a client looses the server, eg. Cannot even ping the server although it will contact the WWW, so my idea is to let the server control both DCHP and DNS.

If I let the network adapters on the DOMAIN PCs take the default settings (ie. no manual settings) will they be able to contact the server, or should I put the servers IP address as the default DNS?

Thanks.
Chris ColemanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
Some clients not finding the server ?

Since clients were getting DHCP from the router before, I would run a TCP/IP Reset, DNS Flush on these machines.

      
Open cmd.exe with Run as Administrator
Then: netsh int ip reset c:\resetlog.txt
Then: ipconfig /flushdns

Restart these computers.

I am thinking that I will put a primary and Secondary DNS in the router -

Let your Server do all this.
LearnctxEngineerCommented:
One question - how do the domain attached clients find the  (DCHP) server.

If they are not on the same subnet, then via a DHCP helper configured on your routers to forward DHCP requests from clients to the DHCP server.

I am thinking that I will put a primary and Secondary DNS in the router -

        1.  The DNS of the server (xxx.local)
and 2.  A DNS for the WWW (eg. Googles 8.8.8.8)..

Why have a secondary to Google? Active Directory requires a healthy DNS environment. Having the potential for clients to resolve externally will break Active Directory. If AD acts as your DNS server, I would recommend it, then AD can handle lookups externally for the clients via root hints. Better still, set your proxy servers up to perform external DNS resolution for clients and let AD handle internal DNS resolution. Conditional forwarders to the proxy server can handle external lookups for applications that do not support proxy servers.

1) Install the DCHP role
2) Configure the address range
3) Deactivate DCHP on the router

I guess thats it for the server.

I assume you have authorised the DHCP server? Just checking, wouldn't be the first time someone installed DHCP and didn't authorise the server.
Chris ColemanAuthor Commented:
Hi -

Well I don't have a proxy server (as such) ..

I could, I think in the DHCP config.  specify the router as a gateway, then point the domain clients at the domain server's DNS, which should take care of domain requests and pass the others onto the NAT ??

Chris.
Check Out How Miercom Evaluates Wi-Fi Security!

It's not just about Wi-Fi connectivity anymore. A wireless security breach can cost your business large amounts of time, trouble, and expense. Plus, hear first-hand from Miercom on how WatchGuard's Wi-Fi security stacks up against the competition plus a LIVE demo!

JohnBusiness Consultant (Owner)Commented:
You should really use your server for both DHCP and for DNS.  Trying to keep the router in the mix will just confuse things.

Set up a separate VLAN if you want different access for guests.
Wayne88Commented:
"The reason I'm doing this is that we occasionally seem to have a client looses the server, eg. Cannot even ping the server although it will contact the WWW, so my idea is to let the server control both DCHP and DNS."

How are you pinging the client?  If you are pinging using IP address then it should always work internally unless if PING is blocked/dropped by the server firewall.  Solve this first.

If you are pinging by machine name and it's failing but it worked when using IP address then it's the machine name resolution that's failing.

Providing that you have troubleshot the items mentioned above by the others then I would check the TCP/IP NetBIOS Helper service is running on the problematic clients because that will explain why only some clients are failing to connect to the server.  Start the TCP/IP NetBIOS Helper service if not running already (reboot the pc just to be safe) then retest.
Shaun VermaakTechnical SpecialistCommented:
After disabling the old DHCP and starting the new DHCP you can do this on one device to test, you do not need to do this on all
ipconfig /release && ipconfig /renew

Open in new window


One question - how do the domain attached clients find the  (DCHP) server.
When their lease expires they will broadcast and DHCP server will respond (assuming the same subnet)

I am thinking that I will put a primary and Secondary DNS in the router -
        1.  The DNS of the server (xxx.local)
and 2.  A DNS for the WWW (eg. Googles 8.8.8.8)..
No, add external DNS addresses on the DNS Servers as forwarders and only give out AD DNS addresses via DHCP
dnsforwarders.jpg

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris ColemanAuthor Commented:
Hi,

       On Sunday I started the process of installing the DCHP on my server, but I did not complete it, there were other things to do.

I really did not get much further than checking the DNS was complete.

On the clients that were loosing contact with the server I temporarily installed a static IP, Gateway and DNS address.

Anyway I have found the above discourse to be extremely helpful and very useful in other ways, I am pretty sure I will be able to make it work now, or at least when I'm able to access the server again - we're also relocating to another building.

Many Thanks.
JohnBusiness Consultant (Owner)Commented:
Thanks for the update.
Chris ColemanAuthor Commented:
Hi - I would share out the points more equally if I can find a way ?
Wayne88Commented:
Thanks for the update.  Cheers!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.