Access to Remote Data Files with ASP VBScript
am 15.01.2005 14:57:13 von unknownPost removed (X-No-Archive: yes)
Post removed (X-No-Archive: yes)
I have not used FoxPro but to connect from a web server to a differnt
database server you need to have a domain level iuser account.
Create a domain level iuser account in which these computers are. Then
configure your IIS to run as this domain user account. Also makes sure that
the database has this domain user permission.
Alok Kumar
"Dr. Know" wrote:
>
> Greetings,
>
> I have an ASP/VBScript 'application' that accesses database files
> through OLE DB. It was developed on Win2k and Win2k server.
>
> The script basically opens a connection to a remote drive which is
> shared, and opens a recordset for reading and writing. The connection
> is made in free file mode - meaning that the databases are not in a
> container, but separate files within a directory.
>
> I am using the Visual FoxPro OLE DB provider - vfpoledb.dll v8.0.3117
>
> It works fine here, but when we put it on the customer's machines, it
> fails to work - I cannot get a connection to the remote share. I've
> used the 'wizard' to create a UDL to check the connection, tests OK.
>
> I have created and set permissions for the IUSR_MACHINENAME account to
> grant access to the files - and all the other things which work
> perfectly here on Windows 2000 setups. I've even tried creating a
> specific IUSR user just for this app, and given the other machine a
> matching user and password, and applied appropriate privileges to the
> proper directory. Still - no connection.
>
> They are using Win2003 Server as the IIS machine, and the remote data
> file is on a Win2000 server machine. That is the only difference
> between the two setups. There is no domain controller.
>
> Is there some hidden setting I have missed in WindowsServer2003?
> I have worked at this for two days, and I'm at my wits end.
>
> I've enabled security auditing and the security log shows successful
> anonymous connects, but I STILL cannot connect to the directory.
>
> A bonus was dependant on getting this working by today - and it
> doesn't look like we're going to make it... :-(
>
> PLEASE - does anyone know how to fix this blasted thing?
>
> Thanks,
>
> Bleary-eyed Greg
>
>
>
>
>
>
>
>
>
>
> Dr. Know
>
I have not used FoxPro but to connect from a web server to a differnt
database server you need to have a domain level iuser account.
Create a domain level iuser account in which these computers are. Then
configure your IIS to run as this domain user account. Also makes sure that
the database has this domain user permission.
Alok Kumar
"Dr. Know" wrote:
>
> Greetings,
>
> I have an ASP/VBScript 'application' that accesses database files
> through OLE DB. It was developed on Win2k and Win2k server.
>
> The script basically opens a connection to a remote drive which is
> shared, and opens a recordset for reading and writing. The connection
> is made in free file mode - meaning that the databases are not in a
> container, but separate files within a directory.
>
> I am using the Visual FoxPro OLE DB provider - vfpoledb.dll v8.0.3117
>
> It works fine here, but when we put it on the customer's machines, it
> fails to work - I cannot get a connection to the remote share. I've
> used the 'wizard' to create a UDL to check the connection, tests OK.
>
> I have created and set permissions for the IUSR_MACHINENAME account to
> grant access to the files - and all the other things which work
> perfectly here on Windows 2000 setups. I've even tried creating a
> specific IUSR user just for this app, and given the other machine a
> matching user and password, and applied appropriate privileges to the
> proper directory. Still - no connection.
>
> They are using Win2003 Server as the IIS machine, and the remote data
> file is on a Win2000 server machine. That is the only difference
> between the two setups. There is no domain controller.
>
> Is there some hidden setting I have missed in WindowsServer2003?
> I have worked at this for two days, and I'm at my wits end.
>
> I've enabled security auditing and the security log shows successful
> anonymous connects, but I STILL cannot connect to the directory.
>
> A bonus was dependant on getting this working by today - and it
> doesn't look like we're going to make it... :-(
>
> PLEASE - does anyone know how to fix this blasted thing?
>
> Thanks,
>
> Bleary-eyed Greg
>
>
>
>
>
>
>
>
>
>
> Dr. Know
>