Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Problem with certificates and DNS

Posted on 2007-11-22
5
Medium Priority
?
350 Views
Last Modified: 2010-04-19
We have a SBS 2003 for our small office.  The original problem was that the computers were loading slowly so I changed the DNS configs to point to the SBS (DNS server).  Now the computers load quickly. Welllllll, when I try to access the company website from the office, I am prompted for a Username and Password, which is not needed.  I Viewed the certificate from the error message and saw that it was using our OWA certificate.  When I remove the DNS settings, the computers go back to loading slowly but they can access the company site with no problem.  For example, company domain "Thanks.org", OWA is mail.thanks.org and website is thanks.org.

I went to redo the certificates and saw that the CA wasn't installed but there is a Microsoft Certificate for the OWA.  I installed a certificate for thanks.org but it still did not work.
0
Comment
Question by:imy2000
[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
  • 2
5 Comments
 
LVL 70

Expert Comment

by:KCTS
ID: 20334280
All of your clients MUST point to your windows SBS server for their DNS, otherwise you will run into numerous problems.
0
 

Author Comment

by:imy2000
ID: 20335191
When all 6 of the clients are pointed to the DNS server, we have no logon problems but we are unable to access the company website.   That's the gist of the post; trying to find the solution as to why the clients cannot access the company website when the DNS is pointed to the SBS server.
0
 

Author Comment

by:imy2000
ID: 20339615
I figured it out this morning.  All clients were pointed to the DNS server, logged on Quickly but could not get to the company website.  The wrong IP address was in the Forward Zone record for www.  It was  the IP for the ISP and should be the IP of the website hoster.  Once this change was made, the problem was fixed.
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 22413838
PAQed with points refunded (125)

Computer101
EE Admin
0

Featured Post

Looking for the Wi-Fi vendor that's right for you?

We know how difficult it can be to evaluate Wi-Fi vendors, so we created this helpful Wi-Fi Buyer's Guide to help you find the Wi-Fi vendor that's right for your business! Download the guide and get started on our checklist today!

Question has a verified solution.

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

I wrote this article to explain some important DNS concepts that should be known to avoid some typical configuration errors I often see in forums. I assume that what is described here is the typical behavior of Microsoft DNS client. I don't know …
Resolve DNS query failed errors for Exchange
This tutorial will teach you the special effect of super speed similar to the fictional character Wally West aka "The Flash" After Shake : http://www.videocopilot.net/presets/after_shake/ All lightning effects with instructions : http://www.mediaf…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…

618 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