SQL 2000 Developer - Login Failed using SQLOLEDB, QA and EM have no problem connecting

Hi all,

SETUP
-----
I've installed the following on my staging server (pretty fresh
installs):
- Windows XP SP1
- SQL 2000 Developer Edition
- Server MYSERVER
- Uses TCP/IP in standard port and Named Pipes in standard folder.

Security is set to:
- Service account: System Account
- Authentication: SQL Server and Windows
- SA has a password assigned



I created the following database, with no tables (other than system,
of course) for login testing purposes:
- Database: MYDATABASE

Misc. info:
- Server has two IPs assigned, 192.168.0.2 and 192.168.0.11. One of
them runs a proxy, the other a mail server.


PROBLEM
-------

- Trying to connect to the database from within my ASP and VB
applications returns "Login failed for user 'sa'.".
- Connection string is as follows: 
  "Provider=sqloledb; Data Source=192.168.0.2; Network
Library=DBMSSOCN; Initial Catalog=MYDATABASE; User ID=sa;
Password=mypassword;"


FACTS
-----

- I can connect with no problems with both Query Analyzer and
Enterprise Manager using MYSERVER as data source.
- That very same connection string works perfectly when connecting to
the production server (running SQL 7.0 on XP) on another IP.
- SQL Server 7.0 was working just fine on this very same machine prior
to a complete format and reinstall.

Failed workarounds:
- I've also tried using 192.168.0.11 and MYSERVER as Data Source.
- I've created a new user and login with ownership over MYDATABASE.
Same problem arises.
- I've updated to MDAC 2.8.


LIMITATIONS
-----------

- Server must be running under XP.
- SQL Server must use it's own login (Windows Authentication is not
acceptable).





I'll apreciate any help you can provide on solving the problem. Hope
you like the report-style format.

Thanks in advance.

When you connect using QA are you using the stand SQL login sa with your
password , or using a trusted connection... because it looks like the error
is simply telling you that the sa password is incorrect...

-- 
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), C{*filter*}te, NC
www.computeredservices.com
(Please respond only to the newsgroups.)

I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org

I use sa, and can connect with every other user I create for the
database as well (from QA, that is). Actually, I figure the trusted
connection shouldn't even work as the server is configured right now.

Thank you for your interest.

Update: The line "Network Library=DBMSSOCN" was causing the problem.
What I've got to figure out now is a) Why it worked with the previous
XP installation - SQL7 and not with this one, and b) Why the
connection works with the production server and not with the local
staging server. That's an issue that belongs to some other group
though.