>Kile;
>
>Sned a copy of your code for your DSN connection and I will take a look at it.
>
>Tom


Tom -

Thanks for your response, and offer! I would be happy to send the code, but I really don't think it's a matter of incorrect code. Like I said in the original message, I get the same result regardless of whether I use the code for a DSNless connection, or if I set up a System DSN on the WebServer.

I think the problem lies somewhere in an incorrect NT or IIS configuration.

I have also pinned down the following:

If I set up a System DSN on the WebServer, pointing to a database on the DBServer, when setting it up for the first time I have the same problem. After selecting the server (DBServer) it tests the connection and times out. If I make it test the connection again, it succeeds and I can continue with the DSN setup. Perhaps it is a lookup problem? Could it be that the WebServer is not looking up the IP of the DBServer fast enough so the connection times out. But when you try it again, the DBServer IP has already been looked up and the connection succeeds... I just installed the new NTServer (WebServer) and I could very well have some DNS (not DSN) problems that need to be resolved....


Hrmmm.....