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<-
>