So you were getting Error 18456 rather than the 18452 stated ?

>Ok, I don't understand it - but it now connects.
>
>I found this http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx
>
>I checked the state in the error log and it was 8 - I went in and reset the password to 'test', then logged in with 'Kevin' and 'test' and it connected.
>
>Now, the thing is, I removed and readded myself multiple times. My password was correct.
>
>I don't know... strange.
>
>
>>What type of authentication are you using in this case?
>>
>>>I have SQL 2005 running on Win 2003 Server box. I have a Win 7 Pro box that can connect to the server just fine. My laptop running XP Pro also connects fine. I just bought another PC running Win 7 Home Premium. I put SSMS on it and when I try to connect to the server I get:
>>>
>>>

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

>>>
>>>One thing to note: I have only been able to connect to SQL from my older PC and my laptop via the IP address. There's an issue with my domain controller on the server. I'm working on it, but like I said, I have been able to connect to SQL via IP.