I'd suggest you add a static route to the W2k clients just to see if that corrects the problem... try this command:

route ADD ddd.ddd.ddd.ddd MASK mmm.mmm.mmm.mmm ggg.ggg.ggg.ggg

d = destination (the mysql DB server)
m = subnet mask (255.255.255.0 or whatever your route happens to be)
g = gateway (I guess this would be the switch, not quite sure, suggestions anyone???)


If this solves the problem, you should make the route persistent by adding '-p' to the above command.

Hope this helps.


Mauricio Pellegrini wrote:
Hi,

This seems to be a strange situation.

I have a server ( Sun fire v65x ) running SuSE 8.2 and My-Sql 4.1.1alpha-max.

I've detected that when our adsl internet connection is down
the querys on our local network turns to be unusually slow.

But this situation occurs only when querys are executed from  PC's
 running W2k.

Other machines running Linux, on the same local net, doesn't seem to be
affected by this. Those machines performs the exact same querys in a
fraction of time compared to the ones running W2k.

All the PC's and the server are phisically connected to the same Switch.

There's a gateway which provides the internet connection.

Querys are performed from within EMS MySQl manager on the W2k boxes and
from  MySql Control Center on Linux.

There's also one more thing, the same query executed from the MySQl
CLIENT ( the text based application ) returns normal execution times on
the W2k boxes.

Soon as the ADSL service is restored execution times return to normal
on w2k and remains unchanged on Linux.

I can't figure why this happens.. any ideas are especially welcome

Thanks Mauricio


-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to