Hi,

Its also worth checking that the Network Configuration is set on the SQL Server. Check out Properties of the instance and Network Configuration, make sure TCP/IP and Named Pipes (depending on your Network Configuration) are enabled protocols.

I think when you install MSDE it defaults to not set these up.

This may be mentioned in the article Sergey has pointed you at, but just my thoughts.

HTH

Jon



>To all,
>
>I've got a desktop box and a laptop, both with MSDE and Enterprise Manager/Query Analyzer, etc. For a couple of years now I've been developing n-tier apps with FoxPro and VB.NET against SQL Server MSDE (with MSDE on the same machine). I've just recently decided to do the obvious thing and run my apps on one machine against the SQL Server on the other machine.
>
>I can't get either of the boxes to recognize the SQL Server on the other box. I can create ODBC data sources on the "other" box for every viable data source except SQL Server.
>
>I've tried creating a login account through a variety of mechanisms (ODBC, SQL Server wizards, etc.) but the SQL Server on one box absolutely will not recognize the SQL Server on the other box. eg. Using the SQL Server Create Login Wizard, when I "finish", I get the SQL-DMO error "Error 15401: Windows NT user or group '[computer]\[account]' not found. Check the name again."
>
>It ain't supposed to be this hard. Clearly I'm missing something basic. Is there any documentation on the UT for doing this "trivial" task that is intelligable by mere mortals?
>
>Regards,
>Thom C.