Here's a long version of the problem! I hope you can help us!
THANKS!
Marie_Jo
******************************************************
We have created a series of asp pages designed to provide clients with access to their information contained on our file server. The file server is PDC accessed by the webserver, BDC. We are using DHCP.

Previously, we had a great deal of difficulty accessing our databases over a mapped network drive. The problem seemed to be one of permisisons. Well, that now appears to be resolved, but a new problem has shown its ugly face. NOW WE CANNOT ACCESS TABLES CONTAINED WITHIN THE DATABASE.

All was tested, and worked fine, using PWS on a workstation. We were able to access the remote data without any problems. When we migrated to NT4 with IIS4 the problems began.

Here is the code from the global.asa:

Sub Application_OnStart() Application("strPo") ="Driver=Microsoft Visual FoxPro Driver;UID=;SourceType=DBC;SourceDB=\\Fileserver\applications\AppName\DataFolder\DataSubFolder\dbFolder\db1.dbc"

Application("strItem") ="Driver=Microsoft Visual FoxPro Driver;UID=;SourceType=DBC;SourceDB=\\Fileserver\applications\AppName\DataFolder\DataSubFolder\dbFolder\db2.dbc"

Application("strContact") ="Driver=Microsoft Visual FoxPro Driver;UID=;SourceType=DBC;SourceDB=\\Fileserver\Applications\Appname\DataFolder\DataSubFolder\dbFolder\db3.dbc" End Sub

NTFS permissions on \\Fileserver\Applications are - Everyone Full IUSR_NT-Fileserver (Internet Guest Account) Full IUSR_Webserver (Internet Guest Account) Full IWAM_MachineName Full

I am using System DSN and all appears to be fine with the setup.

The databases are being opened and when we pass information from a logon page to the verification page, which must open up a table in the database, we get the familiar error message 80004005, unable to open "\\path\file.dbf"

Any ideas as to what could be causing this? I don't think the problem is permissions, given that the .dbf files are contained within the same directory as the .dbc file.

This is part of the code for the access verification page

Dim cnnAr, rstAr, strSQL, strSQL2, strLogon, strpasswd, rstArName Dim strFlag, strFrench, strEnglish, strNumber, blnTrouve

blnTrouve = FALSE strFrench = "French" strEnglish = "English" strFlag = Session("strLangue") trim(strFlag)

strLogon = request.form("txtName") strPasswd = request.form("txtPassword") strPasswd = trim(strPasswd) strLogon = trim(strLogon)

' *** Verification of user & password ***

strSQL = "SELECT * FROM arcontmm WHERE Userid='"&strLogon&"' AND Password='"&strPasswd&"'" Set cnnAr = Server.CreateObject("ADODB.Connection") Set rstAr = Server.CreateObject("ADODB.Recordset") Set rstArName = Server.CreateObject("ADODB.Recordset") cnnAr.Open Application("strContactClient")

' *** The recordset rstAr contains the user/password pairing ***

rstAr.Open strSQL, cnnAr, 3, 1, 1 set rstAr = cnnAr.Execute(strSQL) Session("strNumber") = trim(Session("strNumber"))

' *** Verification of recordset ***

if rstAr.EOF then blnTrouve = FALSE Session("intChance")=Session("intChance")+1 else blntrouve = TRUE Session("strNumber") = rstAr("Number") strSQL2 = "Select Name FROM arcustmm WHERE Number='"&Session("strNumber")&"'" rstArName.Open strSQL2, cnnAr, 3, 1, 1 set rstArName = cnnAr.Execute(strSQL2) Session("strDescript") = rstArName("Name") end if

' *** Verification of page access ***

if blnTrouve then Session("strLogon")= strLogon if strFlag= strFrench then response.redirect("inventaire_f.asp") elseIf strFlag= strEnglish then response.redirect("inventaire_e.asp") end if

Automatic Password Synchronization was disabled from the start. This was one of the first issues I looked at.