Connecting to a database

Hi,

We are hosting a webserver for a client, and have a connection to our foxpro
software via a dll. If we put the software on the drive that has also the
website, it works ok. If we move the software to an external networkdrive,
it gives an error that it can't connect to the database. Probably this is
because of security reasons. Does anybody know how to resolve this problem ?

thanks in advance
Xavier

Eric
Mon May 24 04:31:38 CDT 2004

Hello, Nuyttens!
You wrote on Mon, 24 May 2004 08:40:22 GMT:

NX> We are hosting a webserver for a client, and have a connection to our
NX> foxpro software via a dll. If we put the software on the drive that has
NX> also the website, it works ok. If we move the software to an external
NX> networkdrive, it gives an error that it can't connect to the database.
NX> Probably this is because of security reasons. Does anybody know how to
NX> resolve this problem ?

You are correct. This is a security issue. Your web application is probably
running under the local IWAM_machine-name account. This account does not
exist on the remote file server. Therefore, you can't access the database.
There are different ways to resolve this problem. For example, you can
lower/change the NTFS security on the remote folder/share. You can also
setup your IIS to use a different account to run your web app. If you do
that, make sure you specify an account that exists on the entire network.
Ask your network admin to help because he's responsible for network
security.
--
Eric den Doop
www.foxite.com - The Home Of The Visual FoxPro Experts - Powered By VFP8

Sietse
Mon May 24 05:05:35 CDT 2004

Hi Xavier,

A few assumptions:
Website is running in IIS
User access is using the IUSR

With no modifications the DLL is instanciated using the IUSR's credentials.
The IUSR (ofcourse) doesn't have the access rights for the network drive by
default. You can set the rights for the IUSR for that network drive, but my
opinion for that is that it's a bad solution. A better solution is using
COM+. COM+ components can use impersonation, so the dll gets started using
user credentials other than the IUSR, while the IUSR still can access the
functionality of the DLL.

Look at the help of Component Services on how to add a VFP-COM component to
the COM+ services

The using of the dll in ASP is not affected by using Component Services.
Additional advantage is the easy shutting down of the dll at run time for
updating purposes.

In NT4 Comnponent Services were called Transaction Server (MTS)

HTH,
Sietse Wijnker



"Nuyttens Xavier" <xavier@cpsit.be> wrote in message
news:Wxisc.127165$rz5.6725759@phobos.telenet-ops.be...
> Hi,
>
> We are hosting a webserver for a client, and have a connection to our
foxpro
> software via a dll. If we put the software on the drive that has also the
> website, it works ok. If we move the software to an external networkdrive,
> it gives an error that it can't connect to the database. Probably this is
> because of security reasons. Does anybody know how to resolve this problem
?
>
> thanks in advance
> Xavier
>
>

Nuyttens
Tue May 25 01:08:07 CDT 2004

thanks for the help !!

"Nuyttens Xavier" <xavier@cpsit.be> schreef in bericht
news:Wxisc.127165$rz5.6725759@phobos.telenet-ops.be...
> Hi,
>
> We are hosting a webserver for a client, and have a connection to our
foxpro
> software via a dll. If we put the software on the drive that has also the
> website, it works ok. If we move the software to an external networkdrive,
> it gives an error that it can't connect to the database. Probably this is
> because of security reasons. Does anybody know how to resolve this problem
?
>
> thanks in advance
> Xavier
>
>