Re: SQL and DNS

anonymous_at_discussions.microsoft.com
Date: 02/24/04


Date: Tue, 24 Feb 2004 10:19:28 -0800

sql server primary runs on tcpip, and you can configure it
to listen to multiple protocols at the same time. Client
specifies what protocol to use when initiating connection.

you should use client network utility to configure tcpip
as the first network protocol to be used to establish
connection to sql server. if you still have problems then
define an alias.

>-----Original Message-----
>Is there a way that you know of that I can do this
globally for my sites
>using a registry entry or something? Is there a parameter
that would
>tell NetBIOS to resolve to DNS instead?
>
>Thanks again,
>
>John Jakus
>
>Jim Young wrote:
>> Your welcome. The problem is not with SQL Server but
with applications that
>> need to be able to resolve a netbios name to an IP
address. In a pure DNS
>> environment and without a WINS server on your network
you will need to
>> create aliases on the client machines.
>>
>> Jim
>>
>> "John Jakus" <John.Jakus.DieSpammerDie@Valence.com>
wrote in message
>> news:ubs13lq%23DHA.2484@TK2MSFTNGP12.phx.gbl...
>>
>>>Jim,
>>>
>>>Thank you so much for that answer. I configured an
Alias with the server
>>>name as TCP/IP and it worked. Now can you explain why I
had to do that?
>>>Why doesn't SQL just resolve this using DNS? Is there a
place in the
>>>registry that I can just tell machines to use TCP
instead of other
>>>protocols for resolution to SQL?
>>>
>>>Thank You Again,
>>>
>>>John Jakus
>>>
>>>Jim Young wrote:
>>>
>>>>You will probably need to use the Client Network
Utility to create
>>
>> aliases
>>
>>>>to the IP address of your server.
>>>>
>>>>Jim
>>>>
>>>>"John Jakus" <John.Jakus.DieSpammerDie@Valence.com>
wrote in message
>>>>news:%23VkSc5o%23DHA.3820@TK2MSFTNGP09.phx.gbl...
>>>>
>>>>
>>>>>I have just setup a new SQL environment. The Server
is a Win2K SP4 with
>>>>>SQL Server 2000 and SP3a. Our site does not have an
MS domain, AD or
>>>>>WINS server. We do have DHCP and DNS running for IP
managment and name
>>>>>resolution. I have setup a DNS name for the SQL
server. I can resolve
>>>>>the name forward and backward. No problem. I am
having problems
>>>>>resolving to this server with applicatoins.
>>>>>
>>>>>I can setup application connections using IP address
but DNS resolution
>>>>>does not work with all products.
>>>>>
>>>>>SQL Enterprise Managment Server will connect using IP
or full DNS name.
>>>>>If I try to use just host name, it fails to connect
with a access denied
>>>>>or server not found error.
>>>>>
>>>>>Now from a command prompt I can resolve using both
hostname.domain.com
>>>>>and hostname. If I try using both of these from some
SQL applications
>>>>>they fail.
>>>>>
>>>>>Does SQL rely on NetBIOS names?
>>>>>
>>>>>Any information would be appreciated.
>>>>>
>>>>>Thank You,
>>>>>
>>>>>John Jakus
>>>>
>>>>
>>>>
>>
>>
>.
>



Relevant Pages

  • Re: SQL and DNS
    ... cliconfig.exe is already on the client machine, with MDAC. ... Tibor Karaszi, SQL Server MVP ... In a pure DNS ...
    (microsoft.public.sqlserver.server)
  • Re: request/response style profiling
    ... Not having a public protocol certainly does NOT mean that there's no way to ... parse the binary data. ... some client access libraries such as ADO ... SQL Server MVP ...
    (microsoft.public.sqlserver.tools)
  • Re: Cant access linked server, except from
    ... You do this by opening up SQL Server Configuration Manager from the ... Underneath the SQL Native Client Configuration you find the Client ... Protocols - here the Named Pipes protocol have to be enabled... ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 7.0 on Windows 2000
    ... File shares and SQL Server services are two different issues. ... including DNS records and Client aliases. ...
    (microsoft.public.sqlserver.clustering)
  • Re: MS Tabular Data Stream (TDS)
    ... SQL Server itself uses TDS as an application level protocol ... SQL Server, the SQL Server ODBC driver, or the DB-Library ... The TDS packets are then passed to a SQL Server client ...
    (microsoft.public.sqlserver.clients)