Connecting to SQL Server 2005 remotely via windows authentication

Hi

I have installed SQL Server 2005 onto a server and then on my client machine I have installed SQL Server 2005 and the Server Management Studio.

When installing it on the server I chose all the defaults so have not setup an sql username or password to connect as I thought I could use Windows.

I go to the Server Management and registered servers, create a new one and enter the ip address of the server and choose Windows Authentication. The following error keeps appearing though and I am not sure what settings/where to check:

Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)

I have checked and think port 1443 is open on the server, tcpip is enabled but when I choose Windows authentication I cannot enter a username or password as it is greyed out. It has completed the username but no password and these are not the correct ones to connect to the server - I wish to wish the same one I use for RDC.

Or should I try SQL Authentication and if so how would I set this up? Cannot see on the server in SQL Configuration where I could set this?

Hope someone who knows a lot more than me on this can help!

Thanks for your time - this has been driving me mad for days now and everything I print off the internet is not help so any feed back or more useful links to loo up would be great.

Welcome :-) !

This error can have several causes. You have the login dialog to SQL Server authentication, but the server only accepts Windows authentication. YOu select Windows Authentication but no user token is passed to the server as the server and the client are not in the same domain .You cannot enter a password as the authentication is integrated, which means that the user was already authenticated and only the token is passed to the Server. For this case the authentication can only take place if the user has a (for the server) valid user token (User is in the same domain or any trusted domain)

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Hi

Thanks for the very helpful response. I am now going through Support for our externally hosted server which I have installed SQL Server 2005 onto. It appears I will need to set it up with SQL Authentication mode as I am of course on a different domain to the server I want to connect to so thank you for putting me on the right track with that one.

On a similar note - with SQL Authentication - setting up a new username & password I had read that it would need a username from the database. Is this only if you are directing it to a specific database? We will have lots of databases on our server once we have set it up and so only want to link direct to the SQL server and only then choose the database to work with.

No worries if you cannot help as you have been a great help so far.

Thanks for the welcome to this forum!

Sonia

|||User are created on a server level. These principals can be granted access to the server, which does not mean per se that they are able to access any database unless they are mapped to a specific (database)user or role (like the sysadmin role is mapped to the dbo automatically) in the database. YOu will only have to map him to a database if he needs access to it. No need to create a user for a login in a database if he does not need or is not allowed to retrieve any information from the db.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.d