Results 1 to 17 of 17

Threaded View

  1. #1

    Thread Starter
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004

    Exclamation Solution to non-domain Windows Authentication

    If any of you have ever tried to access a SQL box on a network, from a laptop for instance, that is not part of the domain.

    You will remember getting an error:

    Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
    This problem also happens when you VPN connect to an outside network - and attempt access to the remote network through the VPN.

    You can get around this error, on WINDOWS XP PROFESSIONAL machines by:



    Click Add and then load the SERVER NAME of the SQL BOX on the other network and the WINDOWS AUTHENTICATION username and password that would give you authentication on that network!

    From that point on you have credentials to access that server without actually logging in to that domain.

    I was very impressed!
    Last edited by szlamany; Oct 14th, 2005 at 01:07 PM.

    *** Read the sticky in the DB forum about how to get your question answered quickly!! ***

    Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".

    Some Informative Links:
    [ SQL Rules to Live By ] [ Reserved SQL keywords ] [ When to use INDEX HINTS! ] [ Passing Multi-item Parameters to STORED PROCEDURES ]
    [ Solution to non-domain Windows Authentication ] [ Crazy things we do to shrink log files ] [ SQL 2005 Features ] [ Loading Pictures from DB ]

    MS MVP 2006, 2007, 2008

Posting Permissions

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


Click Here to Expand Forum to Full Width

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.