Connecting to MSDE via client

Hope someone can explain why this happened.
I installed MSDE on a Winxp workstation.
I then setup clients to access MSDE via TCP/IP using the (Static) IP Address
address of the workstation.
Connection successful
I then removed MSDE2000 and installed MSDE2000 sp3a
Went I to connect to MSDE via TCP/IP and could not connect using the IP
When I changed to The machine name I could connect to MSDE2000
Anyone with any idea.
Server was winXP and workstations Win98 and Win08se.
Regards
Jeff
--
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003Jeff Williams wrote:
> Hope someone can explain why this happened.
> I installed MSDE on a Winxp workstation.
> I then setup clients to access MSDE via TCP/IP using the (Static) IP
> Address address of the workstation.
> Connection successful
> I then removed MSDE2000 and installed MSDE2000 sp3a
> Went I to connect to MSDE via TCP/IP and could not connect using the
> IP When I changed to The machine name I could connect to MSDE2000
> Anyone with any idea.
> Server was winXP and workstations Win98 and Win08se.
> Regards
> Jeff
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003
Check that the Server (via sql server network utility) is configured to
use TCP/IP. Also check your client is configured like this too (client
network utility).
Br,
Mark Broadbent
mcdba , mcse+i
=============

connecting to database error

Hi there

i have a problem connecting creating a data source to SQL server express.

I am running winXP with service pack2

My machine is APOLLO\SQLEXPRESS

i AM USING AN ODBC CONNECTION.

i GET THE FOLLOWING ERRORS:

SQL SERVER ERROR 1231

AND

SQL SERVER ERROR 17.

Having done a google search and looked at the local security settings i am not sure what to add to the object names.

Can anybody please help.Gino

Gino,

You need to add authentication to your connection string. An application has it's own identity that SQL Server will not recognize.

Adamus

|||

Hi there again

Could you please state step by step procedure to perform this authentication. Is this authentication code based or windows based as i have mentioned previously? If this is code based could you please give some hints.

Gino

Connecting is slow on just one machine, iSQLW, EM

We have one WinXP Client machine here that is having some issues connecting
to Any SQL Server...
We have tried with both TCP/IP-1433 and with NamedPipes with the same
results. in CNU we forced the connection with an Alias and had the same
results.
If we open EM, it takes about a minute to expand a server, and a bit more
then a minute to expand the Databases folder.
if I open iSQLw it takes for ever to connect to the DB, When I click the
drop down to select a DB, it takes 40+ seconds. Doing a Query on a Table
took 5 minutes...
On another machine sitting next to this one, we did the same tests.
Expanding the server took 2 seconds, DB same. iSQLw connected immediately
and the drop down did just that. The Query took 1 second....
If we look at the Data packets in a protocol analyzer it looks like the
machine thatis requesting the data from the SQL Server is requesting info
over and over and over and over... Where the one that work asks for it and
boom it all comes back.
We have a Custom App Written to use OLEDB and it works great on the machine.
Any suggestions?
Thanks,
Scott<-
Scott,
Could be an MDAC issue. You might want to reinstall MDAC 2.8 (I believe the
latest version for XP).
Steve
"Scott Townsend" <scott-i@..-N0-SPAMplease.enm.com> wrote in message
news:%23y7WbbYCFHA.4020@.TK2MSFTNGP15.phx.gbl...
> We have one WinXP Client machine here that is having some issues
connecting
> to Any SQL Server...
> We have tried with both TCP/IP-1433 and with NamedPipes with the same
> results. in CNU we forced the connection with an Alias and had the same
> results.
> If we open EM, it takes about a minute to expand a server, and a bit more
> then a minute to expand the Databases folder.
> if I open iSQLw it takes for ever to connect to the DB, When I click the
> drop down to select a DB, it takes 40+ seconds. Doing a Query on a Table
> took 5 minutes...
> On another machine sitting next to this one, we did the same tests.
> Expanding the server took 2 seconds, DB same. iSQLw connected immediately
> and the drop down did just that. The Query took 1 second....
>
> If we look at the Data packets in a protocol analyzer it looks like the
> machine thatis requesting the data from the SQL Server is requesting info
> over and over and over and over... Where the one that work asks for it
and
> boom it all comes back.
>
> We have a Custom App Written to use OLEDB and it works great on the
machine.
> Any suggestions?
> Thanks,
> Scott<-
>

Connecting Clients

What are the prerequisites for Win2K and WinXP Clients to
connect to a MSDE server?
I have installed MDAC2.8, is there anything else they need?
Hi
Nothing else. XP has MDAC 2.8 already in it. All low level connectivity is
there once MDAC is installed.
Regards
Mike
"Kon" wrote:

> What are the prerequisites for Win2K and WinXP Clients to
> connect to a MSDE server?
> I have installed MDAC2.8, is there anything else they need?
>