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:
Quote:
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:
START>CONTROL PANEL>USER ACCOUNTS
ADVANCED TAB...MANAGE PASSWORDS...
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!
Re: Solution to non-domain Windows Authentication
You should send a PM to si_the_geek and ask him to make this a part of the Tutorials And Tips sticky thread at the top of the forum.
This isn't something that should get lost in the thread shuffle. :thumb:
Re: Solution to non-domain Windows Authentication
Thanks a lot for sharing... :thumb:
1 Attachment(s)
Re: Solution to non-domain Windows Authentication
sorry..where did i get Advanced Tab?
Re: Solution to non-domain Windows Authentication
Quote:
Originally Posted by erickwidya
sorry..where did i get Advanced Tab?
Is that PC currently in a domain, or simply a workgroup? You can find that out by right-clicking on MY COMPUTER and going to the COMPUTER NAME tab. Does it list a DOMAIN there?
Did you switch to classic view in the CONTROL PANEL? You do have XP PROFESSIONAL - right?
Re: Solution to non-domain Windows Authentication
Quote:
s that PC currently in a domain, or simply a workgroup? You can find that out by right-clicking on MY COMPUTER and going to the COMPUTER NAME tab. Does it list a DOMAIN there?
Did you switch to classic view in the CONTROL PANEL? You do have XP PROFESSIONAL - right?
yes..i have XP Proffesional SP1..the PC is in Workgroup not using domain..
i think i switched it to Classic but can't find to restore it :(
Re: Solution to non-domain Windows Authentication
I don't have a non-domain computer, but MSDN says...
Quote:
How to Manage Stored User Names and Passwords
To manage stored user names and passwords, follow these steps:
1. Log on to the computer as the user whose account you want to change.
2. Click Start, and then click Control Panel.
3. In Control Panel, click User Accounts under Pick a category to open the User Accounts dialog box.
4. Open the Stored User Names and Passwords dialog box; to do so, use the appropriate method:• If you log on with a limited account:a. Under Related Tasks, click Manage my network passwords.
• If you log on with an account with administrative privileges:a. Under or pick an account to change, click your user account to open the What do you want to change about your account? dialog box.
b. Under Related Tasks, click the Manage my network passwords.
A list of stored user names and passwords similar to the following example is displayed:
*.Microsoft.com
Passport.Net\*(Passport)
Does that work for you?
1 Attachment(s)
Re: Solution to non-domain Windows Authentication
Quote:
Does that work for you?
yes i found one that simillar to this with some different :
Quote:
A list of stored user names and passwords similar to the following example is displayed:
my_user_name@hotmail.com.com
Passport.Net\*(Passport)
i guess i need to add UserName and Password at Selected Window right?
thx szlamany
Re: Solution to non-domain Windows Authentication
Yes - that is it...
I was on a windows 2003 terminal server system today and saw "Stored Usernames and Passwords" - that is the same dialog box that WinXP Pro has...
Re: Solution to non-domain Windows Authentication
What about this on a Windows 2000 Professional workstation thats not logged on to the domain?
ta
kai :wave:
Re: Solution to non-domain Windows Authentication
Quote:
Originally Posted by kaihirst
What about this on a Windows 2000 Professional workstation thats not logged on to the domain?
ta
kai :wave:
I am not 100% sure, but I believe all this came about with XP and 2003.
I did some google searches and MSDN searches and could not find anything.
Re: Solution to non-domain Windows Authentication
ok cheers.
will give it a go next time ive got the opportunity and let you know.
cheers
kai :wave:
Re: Solution to non-domain Windows Authentication
I am trying to get this working on Sql 2005 Standard using a Vista non domain workstation.
I can get this working on XP professional using these instructions. I am unable to get it working with VISTA. I have tried VISTA Business Edition.
Anyone get this working?
Re: Solution to non-domain Windows Authentication
Welcome to the forum!
I've not got Vista installed yet on any of our development machines.
I'll PM someone who does and see if they can help.
Re: Solution to non-domain Windows Authentication
Hi,
sorry to bump such an old post, but I'm having the exact same problem using Vista Business as jon.vickers posted before me and was wondering if someone found a solution yet :ehh:
Re: Solution to non-domain Windows Authentication
Welcome to the forum!
I still don't have Vista installed on any workstations here - let's see who jumps into this thread with an answer.
Re: Solution to non-domain Windows Authentication
What I've found/done so far:
I've used the runas.exe to run the application as my domain user
I've entered the server IP in "control userpasswords2" so it should always use those credentials connecting to the SQL server
What I can't do:
Enter the ODBC connector using the correct setting because Vista checks the current NT logon credentials against the SQL server and won't save the DSN unless it succeeds.
I'm now trying to figure out how to manually edit the registry to add the DSN connection, in other words circumventing the check performed by the ODBC GUI.