MSDE/NT Connection problem across domains


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: MSDE/NT Connection problem across domains

  1. #1
    Will Rickards Guest

    MSDE/NT Connection problem across domains

    Greetings,

    MSDE (SQL Server 7) SP3 has been setup on an NT4 Server (SP6a).
    This resides on one NT domain.
    It has been setup with mixed mode authentication.
    There are clients, NT4 Workstation SP4-SP6a, trying to connect to it which
    are on separate domains.
    I've tried using the TCP/IP library to connect but it was unable to connect.
    I've installed MDAC 2.5.
    I'm trying to use sql server authentication.

    Here is the connection string that I pass to an ADO Connection object.
    Provider=SQLOLEDB;
    Data Source=Collaboration Data Source;
    Initial Catalog=Database Name;
    Trusted_Connection=No;
    User ID=sa;
    Password=;
    Network Address=1.2.3.4,1433;
    Network Library=DBMSSOCN;
    Application Name=Application Name

    Do I need to setup a trust between NT domains to use the TCP/IP library?
    I've read several faqs and they seem to say the following:
    'With 7.0 all net-libs require NT authentication.' but they also say a bit
    later
    'Or, you could use a net-lib that does not need authentication - e.g. tcp-ip
    sockets.'
    So which is it?

    What is the best way to connect these clients to the server?

    ---
    Will Rickards

    -----------------------------------------------------
    More info below:

    Here are some test results using the SQLOLEDB Provider

    1. net view \\server: works from both test workstations
    Output then -> The command completed successfully.
    2. UDL test results, by UDL file.
    *** Named Pipes with SQL Authentication:
    TestA: "Test connection failed because of an error in initializing provider.
    Login failed for user 'sa'. Reason: Not associated with a trusted SQL
    Server connection."
    TestB: "Test connection failed because of an error in initializing provider.
    Login failed for user DOMAIN\UserName"
    *** Named Pipes with NT authentication:
    TestA: Succeeded
    TestB: "Test connection failed because of an error in initializing provider.
    Login failed for user DOMAIN\UserName"
    *** TCP/IP with Computer Name:
    (using SQLServerAuth)
    TestA: "Test connection failed because of an error in initializing provider.
    Login failed for user 'sa'. Reason: Not associated with a trusted SQL
    Server connection."
    TestB: Failed with same error message.
    (using NT auth)
    TestA: Succeeded
    TestB: "Test connection failed because of an error in initializing provider.
    Login failed for user DOMAIN\UserName"
    *** TCP/IP with IP address:
    (using SQLServerAuth)
    TestA: "Test connection failed because of an error in initializing provider.
    Login failed for user 'sa'. Reason: Not associated with a trusted SQL
    Server connection.
    TestB: Failed with same error message.
    (using NT auth):
    TestA: Succeeded
    TestB: "Test connection failed because of an error in initializing provider.
    Login failed for user DOMAIN\UserName"

    Note that the error messages for TestB that specified "Login failed for user
    DOMAIN\UserName" occur even after I added him to the Users group on the
    server.

    Anybody have any clue why I can't connect to this server from TestB?



  2. #2
    Jason Langston Guest

    Re: MSDE/NT Connection problem across domains

    Will,
    Comments inline :
    "Will Rickards" <rickards@sensemaking.nospam.com> wrote :
    <snip>
    > Here is the connection string that I pass to an ADO Connection object.
    > Provider=SQLOLEDB;
    > Data Source=Collaboration Data Source;
    > Initial Catalog=Database Name;
    > Trusted_Connection=No;
    > User ID=sa;
    > Password=;
    > Network Address=1.2.3.4,1433;
    > Network Library=DBMSSOCN;
    > Application Name=Application Name


    Try this ADO Connection string instead :
    "Provider=SQLOLEDB;" & _
    "Data Source=1.2.3.4,1433;" & _
    "Network Library=DBMSSOCN;" & _
    "Initial Catalog=Database Name;" & _
    "User ID=sa;" & _
    "Password=;"

    > Do I need to setup a trust between NT domains to use the TCP/IP library?


    Nope, try the above. Post if it doesn't work. It should, I use it all the
    time.

    HTH,

    JasonL



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center