MSDE access over network slow for XP workstations, not Win2K

I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
application on multiple workstations.
These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
All workstations can access and ping the server under 1MS.
When the client application opens and reads data from the database server,
it takes a short time for this to be performed on the Win2000 Pro machines,
but all the XP machines take an abnormally long time to connect and to
retrieve the data.
The XP's do connect, but the retrieval is very slow, sometimes it timesout
during a retrieval.
This occurs even when nobody is connected to the database, so I've ruled out
the governer.
I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
The install process only installed MDAC 2.7 if the current version is before
that.
Anybody have an idea what might be the problem?
All responses are welcome.
TIA
Jim K
Hi Jim,
Name resolution problems perhaps? Try connecting to the IP address instead
of the server name to find out.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
> I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
> application on multiple workstations.
> These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
> All workstations can access and ping the server under 1MS.
> When the client application opens and reads data from the database server,
> it takes a short time for this to be performed on the Win2000 Pro
> machines,
> but all the XP machines take an abnormally long time to connect and to
> retrieve the data.
> The XP's do connect, but the retrieval is very slow, sometimes it timesout
> during a retrieval.
> This occurs even when nobody is connected to the database, so I've ruled
> out
> the governer.
> I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
> The install process only installed MDAC 2.7 if the current version is
> before
> that.
> Anybody have an idea what might be the problem?
> All responses are welcome.
> TIA
> Jim K
>
|||Thanks, I didn't think of that.
I have connected using the IP in other apps, but that was to the default
instance.
Since I have a named instance in this case, how would I format the IP and
instance?
Ex: default instance installed on server SERVER1, I can substitute the IP
for SERVER1
for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
Thanks!
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Hi Jim,
> Name resolution problems perhaps? Try connecting to the IP address instead
> of the server name to find out.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Jim K" <krusej@.megsinet.net> wrote in message
> news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
SP2).[vbcol=seagreen]
server,[vbcol=seagreen]
timesout
>
|||Hi Jim,
I'd suggest setting a fixed port for the named instance, then just connect
to that port. Even set up an alias on the client boxes that knows about the
port. It would completely avoid the sql browser function that essentially
just maps your instance name to a port anyway. To do that:
1. Open svrnetcn.exe and for the named instance, uncheck the "dynamic port"
box and select your own port (ie 38474 or something).
2. Restart the instance.
3. On the client, run cliconfg.exe and set up an alias pointing to that port
on the server.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:u6vH8Mo7EHA.2196@.TK2MSFTNGP11.phx.gbl...
> Thanks, I didn't think of that.
> I have connected using the IP in other apps, but that was to the default
> instance.
> Since I have a named instance in this case, how would I format the IP and
> instance?
> Ex: default instance installed on server SERVER1, I can substitute the
> IP
> for SERVER1
> for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
> Thanks!
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...
> SP2).
> server,
> timesout
>
sql

MSDE - Just Stops!

Hi:
I have a Win2000 server that has been running MSDE for about five months.
Suddenly today it just stopped running.
There were no entries in the event viewer or anything. I stopped and
restarted the service and it still did not respond.
Finally I rebooted the computer and it's working once again. I rebooted the
machine last night so it had only been running about 12 hours and was
functional this morning.
Does anyone have any suggestions on how to determine what happened - and
prevent it from happening in the future?
Thanks for your help!
Fred
Hi,
Verify the SQL Server Logs as well for any errors. It is always recommented
to check the logs atleast once a day.
Check if there is any memory leak 3rd paqrt programs in ur server.
Thanks
Hari
SQL Server MVP
"Fred Nelson" <fred@.smartybird.com> wrote in message
news:umZDRJNUFHA.2664@.TK2MSFTNGP15.phx.gbl...
> Hi:
> I have a Win2000 server that has been running MSDE for about five months.
> Suddenly today it just stopped running.
> There were no entries in the event viewer or anything. I stopped and
> restarted the service and it still did not respond.
> Finally I rebooted the computer and it's working once again. I rebooted
the
> machine last night so it had only been running about 12 hours and was
> functional this morning.
> Does anyone have any suggestions on how to determine what happened - and
> prevent it from happening in the future?
> Thanks for your help!
> Fred
>