New server registration error

Hi, I've just installed MSDE 2000 Release A on a Windows NT Server 4.0 w/SP6. I'm on a WinXP machine and I've installed the Enterprise Manager, and am trying to register a new server registration. However, I'm getting the error: Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection. I've made sure that both the client and server are using TCP/IP for the protocol list, and I've tried using the physical server's name and it's IP address to register, but keep getting the same error. Thanks for the help.How are you authentacating? Try a search before posting.
http://www.dbforums.com/t525129.html
or

http://search.msn.com/pass/results.asp?RS=CHECKED&FORM=MSNH&v=1&&q=Login+failed+for+user+%27sa%27.+&cp=1252|||I was trying to authenticate via SQL Authentication. I did try searching, and nothing I found seemed to pertain to my situation. But I fixed the problem, so if anyone wants to know, I used Windows authentication to register the server, then I right-clicked on the server, chose properties, and went to the security tab. In there, it was checked to use "Windows only" under the Authentication section. I changed it to "SQL Server and Windows", restarted the SQL service, deleted my Windows SQL registration. Then I was able to successfully register my SQL server using SQL Authentication!

New Installation - Can Not Connet to Server On My PC

I have just installed SQL Express and Server Management Studio on my PC. I also have IIS 5.0 on WinXP. When I open Management Studio and try to connect the sI get the following error message:- Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider) .

This happens if I change the server, change the authentication method or try my user name or the 'sa ' user. To make things even more frustrating I did the same installation on my laptop earlier this year with no problems.

Has anyone any answers to my problem?

Thanks

hi,

having modified the authentication property (and restarted the service), did you enable the sa login?.. verify in the Instance->Security->Logins->sa Properties (Status tab) the login is enabled..

regards