General discussion

Locked

ODBC System DSN problem

By kevcav ·
We have a web site that accesses data from many different data sources. All the data sources are set up as system DSN's. The problem is with one of the DSN's. The data is physically located on a NT server seperate of the IIS server. The data is all FoxPro free tables. All the DSN's point to data on a NT server except one. That one is the problem. That particular DSN points to data on a Win95 machine. The DSN keeps losing it's data path. The only way we have found to keep the DSN working is to run a macro on the server which constantly browses the data location. If this is not done, the ASP page that needs that data will error out because it can't find the data. The Win95 machine is on the same domain as then NT box. The NT box is mapped to the shared drive of the Win95 machine. We have tried using UNC with the same results. The macro we use to constantly browse the DSN path stops when we lock the server, so we need another alternative. Any Ideas?

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

ODBC System DSN problem

by artnweke In reply to ODBC System DSN problem

I think that if you set the default path of your FoxPro to the folder where your data is then when you ask for the data FoxPro will point to that folder automatically. I assume that you have FoxPro on that system and not a stand alone application. Ihope that this will be of help.

Collapse -

ODBC System DSN problem

by kevcav In reply to ODBC System DSN problem

FoxPro is my database, but I am using an ASP page to access the data. FoxPro is out of the picture except as the database. This is a web apoplication utilizing ASP pages to access foxpro data via ODBC's system DSN.

Collapse -

ODBC System DSN problem

by artnweke In reply to ODBC System DSN problem

I think that if you set the default path of your FoxPro to the folder where your data is then when you ask for the data FoxPro will point to that folder automatically. I assume that you have FoxPro on that system and not a stand alone application. Ihope that this will be of help.

Collapse -

ODBC System DSN problem

by kevcav In reply to ODBC System DSN problem

FoxPro is my database, but I am using an ASP page to access the data. FoxPro is out of the picture except as the database. This is a web apoplication utilizing ASP pages to access foxpro data via ODBC's system DSN.

Collapse -

ODBC System DSN problem

by bhostmeyer In reply to ODBC System DSN problem

The problem that your are being faced with is not a pathing issue but a security issue with your asp page. You need to add a statement to your asp page to refresh the connection and security to the nt server. If you enable ip forwarding to this other server it will help keep your path alive and will alow good security. Another option you may want to try is using Named pipes, The pipe will give access to the other database without giving access to any other part of the server.

I am guessing here but i amagin your odbc is set up like this

name = "thisdatabase"
Database name = "mydata.db"

if you are using pre set up odbc connection in the odbc manager your going to have problems going from one server to another it is best to setthese up at run time with your asp page. If you email me with more information I would be glade to show you how to do this with vbscript or xml.

Hope this Helps
Brooke Hostmeyer
Network Admin
Vijon labs Inc.

Collapse -

ODBC System DSN problem

by kevcav In reply to ODBC System DSN problem

Poster rated this answer

Collapse -

ODBC System DSN problem

by GNC In reply to ODBC System DSN problem

As Project Lead for Application Development, I noticed a few issues in your question that I would like to mention.
1. System DSN's - I have found that system DSNs can be a major problem. Assuming you are backing up your servers, system DSNs are saved in the registry. If your server goes down and requires a rebuild, you cannot ?restore? the old registry as the new install of NT will write its own. You would have to create 2 partitions on the new box, copy the old registry onto the second partition, and then repoint your boot INI to point to the second partition where your DSN are located. Strongly suggest you investigate UDLs: <http://msdn.microsoft.com/library/default.asp?URL=/library/techart/complus.htm>Use Universal Data Link (UDL) Files to Persist Connection Strings
2. You state ?The data is physically located on a NT server separate of the IIS server? with reference to the DSN causing you a problem. This seems to indicate your ?other? data is located ?on? the same server(s)as IIS. I would strongly urge you to put ALL of your data on a server(s) other than IIS. Not only that, your database servers should be on a different segment. This is a security issue, as a hacker breaking into you web site with a database on the same server could have access to your data.
3. You say the problem DSN points to data on a Win95 machine. This ?seems? to indicate the data is on an individual?s PC rather than a domain server. Have strong backup procedures been put into place for the PC?
4. You state ?The NT Box is mapped to the shared drive of the Win95 machine.? With reference to #2 above, our hacker now not only has access to your web site and data, they now can pass through a shared drive to your other Win95 machine ? and possibly your entire domain.

Collapse -

ODBC System DSN problem

by kevcav In reply to ODBC System DSN problem

I appreciate the help. We looked into UDL's and saved the connection string information from the UDL to a database. We now create our connections on the fly using that data. No more ODBC manager issues.

To respond to the other comments:

2)All data (except one region) is located on a seperate NT server. NO Data is stored on the IIS server.
3) The data on that PC is backed up nightly.
4) The one PC which contains data is accessed through a hidden share. The share is password protected and the connection to that machine is created on the fly via asp code.

Thanks again.

Collapse -

ODBC System DSN problem

by kevcav In reply to ODBC System DSN problem

This question was closed by the author

Back to Web Development Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums