Re: strange ODBC connection problems

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

We're using TCP for our connection, not named pipes.

Also, I should explain why we're trying to avoid using WINS. Everything I
read says that WINS is for backward compatibility. This is a new server, so
we're trying to go in "clean" so we don't have to worry about divorcing it
from WINS someday.

Thanks

Pat

"Terry" <ttrapp.spam.me.not@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7f3e9$42c0467d$45264c04$14491@xxxxxxxxxxxxxxx
> Do you have the netbios protocol installed on the SQL server? IIRC it is
> required when using named pipes as a connection method.
>
> --Terry
>
> "Patrick Peters" <patrick.peters@xxxxxxxxxxxxx> wrote in message
> news:%23jAd6C0eFHA.1328@xxxxxxxxxxxxxxxxxxxxxxx
> > We have a mysterious problem connecting to a SQL database with ODBC.
> Here's
> > a little background on our environment:
> > - We're connecting to a named instance of SQL 2000 on a Win 2003 Server
> > cluter. The virtual server name and the instance name are the same (so
> the
> > nomenclature to describe the instance would be something like
"FRED\FRED".
> > - The client is Windows XP, SP1.
> > - We're trying to set all this up without using WINS, so there are no
WINS
> > resolutions for for the server cluster or any of its virtual servers.
> >
> > So, we try to set up a System DSN with a connect string that looks like
> > "FRED.TEST.DOM\FRED" and ODBC can't connect. I can use nslookup to
> resolve
> > FRED.TEST.DOM without a problem. I can ping FRED.TEST.DOM. I can
> > substitute FRED's IP address in the server name field
("10.20.30.40\FRED")
> > and it works like a charm.
> >
> > I've set up a sniffer to see what's going on. When I specify
> > "FRED.TEST.DOM\FRED" the client is trying its best to resolve FRED using
> > WINS, broadcasting for name resolution, etc. It's completely ignoring
the
> > fact that I gave it a fully qualified domain name to work with. If I
> could
> > just beat ODBC into doing DNS resolution, I'd be in great shape.
> >
> > I've looked around for examples of how to connect to a named instance
> using
> > a DNS name, but I can't find an example of this anywhere.
> >
> > Does anyone have an idea?
> >
> > Thanks
> >
> > Pat
> > patrick.peters (AT) orametrix.com
> >
> >
>
>


.

Relevant Pages

  • Re: Windows Server 2003 and simple VPN pass thru
    ... If name resolution is the problem, would entries in the hosts file fix ... browsing (which is what you see in "My network Places") even harder. ... This was added in Server 2003 and might solve your problem. ... I have just managed to setup a very simple vpn pass thru connection to ...
    (microsoft.public.windows.server.networking)
  • RE: SQL Server Named Instance Active/Active Cluster IIS TCP/IP Con
    ... If I removed the named pipes Im not able to failover the nodes anymore. ... server, otherwise you may have different issues. ... > alias to configure the ports, or specify the port number in your connection ... We can connect to both instances of sql server ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL 2000, Named Pipes and Windows 2003 Standard
    ... to the SQL using named pipes i get a security audit log. ... fixed a SQL Connection timeout that happened every so often. ... seperated the Web server and SQL Server onto our new Dell Blade systems ... Windows 2003 is ...
    (microsoft.public.sqlserver.connect)
  • Connect fails to SQL Server 2005 using named pipes and IP address
    ... I have just installed SQL Server 2005 Standard Edition on a Windows ... pipes as the connection method and it works. ... many clients that connect to the older client using named pipes ...
    (microsoft.public.sqlserver.setup)
  • Re: VPN Problem
    ... hotfix & regedits of KB 292822 to the server? ... Name Resolution and Connectivity Issues on Windows 2000 Domain Controller ... but my VPN connection is being ... I have applied the hotfix per ...
    (microsoft.public.backoffice.smallbiz2000)