Sign in or Create account

Your current IP is 38.107.191.97.

 

Support

K-12 Forums

Talk with other K-12 network administrators in your state.

Or see all states.

Categories

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

This discussion has been inactive for longer than 30 days, and is thus closed.

Domain Name System (DNS) troubles: Problem connecting to MSDE SQL server on local network

Bottom of Page

1 to 6 of 6

  1.  
    • CommentAuthorgbroiles
    • CommentTimeDec 22nd 2006
     permalink
    I've discovered that an application I use daily at work - TimeMatters 8.0 Enterprise, see <http://www.timematters.com> - is apparently incompatible with OpenDNS.

    More specifically, if I configure my router (which provides the DNS resolver addresses to the client machines via DHCP) to use OpenDNS, the client machines are unable to connect successfully to the database server, which is a Windows SBS 2003 running MSDE to provide database service to the clients. The application in question runs successfully on the server (e.g., it can connect via localhost, or otherwise doesn't have trouble resolving the name) but other machines on the local network can't connect.

    Curiously - (to me, anyway) the client machines can see the server from a TCP/IP perspective (e.g., ping) and Windows file sharing works fine - it's just the connection to the database server that fails.

    I can get a fair amount done with MySQL and Postgres on *nix boxes, but am weak with Windows/MS admin issues - so my fix for the problem has been to avoid using OpenDNS for this network.

    The problem is repeatable - I don't mind trying suggestions if anyone's got some, but I'll have to do it during non-business hours.
    • CommentAuthorbrjppru
    • CommentTimeDec 22nd 2006
     permalink
    Please, sorry me for my poor English.

    Problem consists in the fact that you all DNS querys send to opendns. This is not correct. In your local network necessary to deploy his own server DNS. I not to time did not work with SBS2003, but I can to assume that service DNS is there build it and it is already runned.

    All clients and all client machines must take DNS query from you DNS server. Let us allow your domain: enterprice.local all your computers have names of form host1.enterprice.local and inquire information about your local domain from your DNS server, who contains information about Active Directory, Exchange, SQL and other.

    You should include in your DNS server forward of query to DNS, besides query to your domain to servers OpenDNS. Then in you everything will work.

    For additional information you can read:

    http://en.wikipedia.org/wiki/Domain_Name_System
    http://support.microsoft.com/kb/291382

    And read my succes story, how to connect enterprice to opendns.

    http://brj.pp.ru/2006/12/09/domain-name-system/
    http://brj.pp.ru/2006/12/10/opendns-multihomed-dns/
    http://brj.pp.ru/2006/12/10/multihomed-dns-named-pdnsd/
    • CommentAuthorpencoyd
    • CommentTimeDec 22nd 2006
     permalink
    Are you using OpenDNS as a forwarder only?

    We have instructions here
    http://www.opendns.com/start/forwarding.php
    • CommentAuthorgbroiles
    • CommentTimeDec 23rd 2006
     permalink
    Thank you for the suggestions. I'll experiment and see if those ideas move me closer to success.

    To clarify, the current (working) configuration doesn't point to the SBS server for DNS - my router (a Netgear FVS318) gets DNS server information from my upstream router, acts as the DHCP host, and passes the DNS server information through to the clients.

    However, I can see that it might be useful to have the SBS system act as the local DNS resolver and DHCP host - I will investigate that approach. I had avoided it earler because I consider the FVS318 more reliable than a Windows server, but the Windows server reliability isn't too bad, all things considered.
    • CommentAuthorwforney
    • CommentTimeJan 1st 2007
     permalink
    You probably have your SBS misconfigured. It relies on DNS for its ActiveDirectory functions and if you just switch to using another box/router for DNS it will break things. It may not be noticable for a while, but it causes strange behavior on the network after a while unless you setup your other DNS server to have your local domain in it. Your local domain should be whateveryourcompanyis.local for activedirectory in your sbs dns, instead of .com. to use opendns properly hosted on SBS's DNS you simply open the DNS console and add the ip's to the Forwarders tab of the server's properties. Then in your DHCP, set the SBS as your primary DNS server. You might as well use SBS for DHCP too. There really isn't a reason to let a router do it if you have an SBS box. It's designed to handle all of that stuff.
  6.  permalink
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

1 to 6 of 6

  1.  

This discussion has been inactive for longer than 30 days, and is thus closed.