Results 1 to 3 of 3
  1. #1
    Join Date
    Nov 2004
    Location
    Dundee, Scotland
    Posts
    45

    Unanswered: Problem using Client Tools to Remotely Connect to a SQL Server Instance on Another PC

    Someone please help me before I loose all of my hair !!!

    I have two machines, a Windows Server 2003 machine running an SQL Server Standard Edition database instance and client tools (Enterprize Manager etc.), and a workstation PC running Windows XP SP2 which has just the SQL Server client tools (not an actual DB instance).

    I'm trying to use the Enterprize Manager client tool on my WinXP machine to remotely connect to the server instance on the server PC (via 'New SQL Server Registration' option). Everytime I do this I get the following error message:

    Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server Connection.
    Now I've tried using different usernames and passwords. I have login details for my SQL Server set to use Windows Login rather then SQL Server login, so I tried remotely connecting with the username and password for the server PC, tried 'sa' with server password, even tried setting up a new user on the server and logging in from the client with that, no luck. I've opened up correct ports 1433 on both PCs, even disabled the windows firewalls algother. Both server and client have SP3a installed, WinServer2003 has SP1 and XP SP2.

    So I'm at a loss to how to remotely connect to my SQL Server. FYI I know the server itself is working fine because I can connect to it using Enterprize Manager/Query Analyser on the local machine. Any ideas? Many thanks for your help!
    Sunday Ironfoot

    SQL Server 2000 n00b

  2. #2
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    If the client and the server are on the same domain, or if the client account belongs to the tree where domain belongs to, then you can use Windows authentication. But if you already tried this, can you do a TELNET from the client with 1433 successfully?
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  3. #3
    Join Date
    Nov 2004
    Location
    Dundee, Scotland
    Posts
    45
    I've not setup a Domain Controller. Anyway I've solved it, I had SQL Server running in Windows Authentification Mode, so I switched to mixed mode and all is well now
    Sunday Ironfoot

    SQL Server 2000 n00b

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •