Hi!

This is a security issue. IIS is running under its own process. This process logs on on the machine using special local machine account. This account have no rights to access network as a usual domain network user, so probably it has no rights to access internet, for example. If your SQL Server is accessed through LAN, access it using machine name and SQL Server native logon or trusted connection.

HTH.

>Hi all:
>
>I've created a simple ASP which uses a VFP COM object a la Rick Strahl's article showing how to do this. My page renders beautifully on my development server (when accessed from any workstation on the network). My development "server" is actually my laptop, which is running XP Professional and IIS 5.1. However, the production server is running Windows 2000 Server, which runs IIS 5.0. When I navigate to my page on the production server, the page does not render and I have narrowed it down to the fact that it cannot successfully make a connection to SQL Server. I'm using a DSN-less connection method, so it has nothing to do with the connection setup.
>
>I thought it might have something to do with security, but if it did, then how could it work on the development "server?"
>
>So, it would seem there is some difference between IIS 5.0 and 5.1. I see that 5.1 only runs under XP, so I cannot upgrade the IIS on the production server.
>
>It would be really cool to get this working. If anyone has any ideas I'd love to hear them.
>
>Del