Weird Slow Connectivity Problem

Question

Hi guys
We are facing a slow connection problem and we cant seem to find an answer
as to whats happening.
Our application has
1. An app server hosting EJBs , datasources etc
2. A webserver on different box hosting servlets and command classes.
3.A Sql server 7 database on a different box.
All these boxes are on a secured network ; which means that access to them
is given on a requirement basis.
We have JSPs on the web box which get a datasource connection from the app
box to run queries against the database server.Our problem is that even to
run a very simple query ; it takes a long long time (in order of minutes)
and the same query runs lightening fast in the test environment where all
the boxes are on the same network.
We use type 4 SQL driver.We initially thought that this could be a network
problem as it doesnt make sense that the same query runs very fast on the
test boxes.But the network settings seem ok.
The network settings are this way :
Appserver box has access to database server box.
Webserver box has access to Appserver box.
So you can see that webserver doesnt have direct access to database
server.Is it needed to run queries ; since I am taking a connection from the
appserver.How does the whole business of running queries work when I take a
connection from a datasource on an app server.
I had this question posted to the BEA weblogic customer support ; but they
really couldnt help me.
Any ideas would be appreciated.
Thanks
Pankaj Vij

Answer 1

This has many possible troubleshooting paths. You don't mention if this is a workgroup or domain based Windows network. Checking the "Directory Access" settings as appropriate may yield the solution.
If this is a domain/active directory network the issue may lay with the machine account on the domain server.
Create a new user account on the Mac and see if the problem follows when you log in to that account and try to access the SMB share.
If the problem goes away, then you should look at the original user's startup items to see what might be launching at startup or simply move all files to the new user and delete the old account (not the preferred method).
If the problem persists with a second user on the same machine, then I'd take another Mac, boot it to target disk mode (laptop is good for this), using a firewire cable, boot the troublesome mac to the target mac and try to replicate the issue.
If issue persists, this is a network permissions issue on the server, if it goes away it is a local software issue on the Mac and a clean install of the OS may be needed if you can't locate the meddlesome settings/software.