Hi All

Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.

It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.

I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.

Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:

Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?

Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?

Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?

Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?

Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?

Thanks

Is there a better way to do this very simple query(s)?
SQL HELP
INSTEAD OF INSERT TRIGGER AND NULL
readinf blob data in sql trigger
Trigger Help