VB6/SQL Server application runs locally, but not from server

[David C. Barber]

I have a VB6 SP6 MDAC 2.8 application talking to SQL Server 2000. Once I've
installed this application on my local machine I have been able to move the
..exe file to a file server and it runs just fine from there for all my local
users. This is very handy for updating the application without having to
reinstall it on each user's machine each time. They just use a shortcut
pointing to the file server .exe file

My problem has become that we have some users at remote locations that VPN
into our network who also want to use this application. When it's installed
locally on their machines, or even on file servers at their locations,
everything works fine. However, when they run the .exe off of my file
server the SQL Server connections times out on the initial connection open
after the default 30 seconds every time. Run from their own desktops or
file servers it connects within 2 seconds every time. This is on both
Windows 2000 and XP Pro machines. Even when I tell the shortcut to use
their local drive for the working directory the same problem happens.

This goes against everything I've seen with server-based files for 15 years.
Once a file is loaded in the computer for execution, why does it matter
where it came from? What "baggage" can an .exe file carry with it that will
cause it to not execute when hosted on one server, but run just fine from
the desktop or another, closer server? The only known difference is that
the connection speed is much better when I run it locally here to that file
server.

Help.

[Erland Sommarskog]

David C. Barber (da***@NOSPAMdb arber.com) writes:

My problem has become that we have some users at remote locations that
VPN into our network who also want to use this application. When it's
installed locally on their machines, or even on file servers at their
locations, everything works fine. However, when they run the .exe off
of my file server the SQL Server connections times out on the initial
connection open after the default 30 seconds every time. Run from their
own desktops or file servers it connects within 2 seconds every time.
This is on both Windows 2000 and XP Pro machines. Even when I tell the
shortcut to use their local drive for the working directory the same
problem happens.

Sounds indeed very strange, and I suspect that is is not really SQL
Server problem. But I don't really have a clue.

The one thing I can think off is that loading of the EXE across the
write uses up the network bandwidth. But for 30 seconds? I don't really
believe in that myself.

What does your connection string look like?

--
Erland Sommarskog, SQL Server MVP, es****@sommarsk og.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

[Brian Cryer]

"David C. Barber" <da***@NOSPAMdb arber.com> wrote in message
news:a8******** ************@co mcast.com...

I have a VB6 SP6 MDAC 2.8 application talking to SQL Server 2000. Once
I've
installed this application on my local machine I have been able to move
the
.exe file to a file server and it runs just fine from there for all my
local
users. This is very handy for updating the application without having to
reinstall it on each user's machine each time. They just use a shortcut
pointing to the file server .exe file

My problem has become that we have some users at remote locations that VPN
into our network who also want to use this application. When it's
installed
locally on their machines, or even on file servers at their locations,
everything works fine. However, when they run the .exe off of my file
server the SQL Server connections times out on the initial connection open
after the default 30 seconds every time. Run from their own desktops or
file servers it connects within 2 seconds every time. This is on both
Windows 2000 and XP Pro machines. Even when I tell the shortcut to use
their local drive for the working directory the same problem happens.

This goes against everything I've seen with server-based files for 15
years.
Once a file is loaded in the computer for execution, why does it matter
where it came from? What "baggage" can an .exe file carry with it that
will
cause it to not execute when hosted on one server, but run just fine from
the desktop or another, closer server? The only known difference is that
the connection speed is much better when I run it locally here to that
file
server.

Help.

Just a guess ... could it be an authentication problem? Do you specify the
username and account to use explicitly in the application or do you rely on
windows authentication. If you are using windows authentication then as a
test try explicitly using a username and password and see if that helps. If
that works then I'm not sure where you go from there but it may give you a
clue.

Brian

www.cryer.co.uk/brian