Solved

DNS ISSUES

Posted on 2014-04-29
15
179 Views
Last Modified: 2014-09-18
Hi All,

Our client machines keep losing connections to printers, outlook and sharepoint.
Outlook cannot find exchange, share point - page not displayed.
Printers - users print, nothing happens, we have to manually remove and re-add printers

The resolution we found is clear dns cache and then stop and start dns cache. The problem is widespread and we cannot find a solution. Thanks in advance for you help.
0
Comment
Question by:jaya31
  • 4
  • 4
  • 4
  • +3
15 Comments
 
LVL 12

Expert Comment

by:Imtiaz Hasham
ID: 40030122
Is there any error?
0
 
LVL 10

Expert Comment

by:Korbus
ID: 40030134
Can you let us know a bit about your DNS setup?  
Do your workstations have a secondary DNS configured?  (if so, what does it point at)
Does your DNS server use your ISP's DNS server's as forwarders?

When the issue next occurs:  try to ping a problematic device by name.  What address is this name resolving to WHEN the problem occurs?  Does this IP address exist ANYWHERE in your DNS server?  Or, if the name FAILS to resolve, even though it usually works, this would indicate some kind of problem with your DNS server or it's connection.
0
 
LVL 25

Expert Comment

by:Fred Marshall
ID: 40030309
Don't use DNS because it adds complexity which appears to be the issue.
Use static IP addresses for the printers and address them accordingly on the client machines.
Subject to how you have things set up but this is most typical.
0
 
LVL 12

Expert Comment

by:Imtiaz Hasham
ID: 40030338
Frmarshall - In a domain environment, you need DNS to work.

One more thing - please ensure your windows updates are all installed.
0
 

Author Comment

by:jaya31
ID: 40030376
The errors are Outlook cannot connect to exchange, sharepoint - page not displayed and for printers user prints but nothing happens.

When we ping the dns server from a machine that is having the issue, we get a response to both name and IP, the DNS server name is an entry on the dns server as well as the client machine. However the next time it happens, I will double check those points.
0
 
LVL 45

Expert Comment

by:Craig Beck
ID: 40030381
DNS is a requirement here, especially for Domain and Exchange connectivity.  You need to authenticate to DCs, etc, so you HAVE to have DNS.

Where is DNS on your network?  Is it running on a DC?  If so, can you check the logs to see if there are any errors or warnings?
0
 
LVL 25

Expert Comment

by:Fred Marshall
ID: 40030383
In a domain environment, IP addresses still work.  Why use DNS when you don't have to?  Just because it's there isn't a good enough reason.  Yes, some will claim that it makes their lives easier.  But that's dependent on the size of the network, how many people are involved in messing with it, etc. etc.
0
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 12

Expert Comment

by:Imtiaz Hasham
ID: 40030398
FMarshall - DNS resolves the internal hostnames to IPs like WINS used to do a couple of years ago, however, WINS is much slower and DNS has it's own resilience hence Microsoft made it a necessity since Windows Server 2000.
0
 
LVL 45

Expert Comment

by:Craig Beck
ID: 40030444
@fmarshall - you need DNS in a domain environment for a whole load of reasons.  Active Directory won't even install on a server without DNS being present.

Exchange relies on DNS.  It's mandatory in a domain environment even if Exchange is installed on a Domain Controller.

Clients NEED DNS in order to authenticate to a Domain Controller.  Without DNS a client wouldn't be able to locate SRV records, etc.

Sure, IP addresses still work for static devices such as printers, but I think you miss the point here.  The fact is that DNS is failing somewhere and in an AD environment that's catastrophic.  So, instead of bypassing the issue by using IP addresses we have to fix the DNS problem.  In any case, if the printer is shared from a server or client PC on the network users won't be able to authenticate to the host to actually print unless the print-server is a DC.  That's even more reason to fix the DNS issue.
0
 
LVL 25

Expert Comment

by:Fred Marshall
ID: 40030586
craigbeck and Imtiaz:  I had narrowed the question down to just printers and now see that it's broader than that.  I stick with what I said about network (IP addressed) printers.  You don't need DNS for them to work.  How you implement them is a matter of preference.  But you may well need DNS to work for other things like Outlook, shared printers, printers on a server, etc.
0
 
LVL 45

Expert Comment

by:Craig Beck
ID: 40030850
If the printer is standalone (not shared from a PC or server) using an IP to reference it is fine, but if AD security permissions govern printer access DNS is required.
0
 
LVL 12

Expert Comment

by:Imtiaz Hasham
ID: 40030867
I agree to preference of using IP addresses for printers, however, the issue here is Outlook and sharepoint losing connectivity - Hence my concern.
0
 
LVL 25

Expert Comment

by:Fred Marshall
ID: 40031111
We agree it appears.  Y'all know better than I about those things.
Why would one want to have AD security permissions governing printers?  To save paper?
0
 
LVL 45

Expert Comment

by:Craig Beck
ID: 40031297
Oh fmarshall...

Some documents are sensitive. We control how they are distributed and reproduced using security permissions on drives, printers, etc...

We use permissions on shared printers to determine who can print to departmental printers (to manage printing costs, etc) and to ensure only authorised people can manage the printer or print queue.

There are lots of reasons why permissions are used.
0
 
LVL 7

Accepted Solution

by:
Scobber earned 500 total points
ID: 40034426
In your DNS Mmc snap in right click properties your server and find the option multibyte utf change it to strict rfc. On every DNS server in the forest.

Restart your DNS server and go again, is your domain xxx.local and your sharepoint say intranet.xxx.com

In your DNS server add a domain of intranet.xxx.com and set an a record for the root  domain to be your internal sharepoint ip.
0

Featured Post

Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

Join & Write a Comment

I've written instructions for one router type, but this principle may be useful for others of the same brand and even other brands of router. Problem: I had an issue especially with mobile devices that refused to use DNS information supplied via…
SSL is a very common protocol used these days when browsing the web.  The purpose is to provide security to communication, but how does it do it?  There are several pieces at work that have to be setup before SSL will even work and it requires both …
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

759 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

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now