Hi!

I could not hep you much here because this is dependent on many things. I'm not Administration specialist to give you a list of all cases and indicate which one is the most probably is your case. I just know that IIS has limites access rights to the network as a guest only, because its process runs under local user accound. What resources it can access is configured in many places, and here I cannot help you much. You can make that special user for IIS process running to be a domain user, but this is a very big hole in security - imagine somebody breaks security of IIS - the entire network is redable then...

>>>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.
><<
>
>Well, would this not also apply in the development scenario? I can go to *any* machine on the network and navigate to my dev intranet and it works fine. Presumably, a similar special account is used in this case also which would have similar limited rights.
>
>Also, the SQL Server is accessed thru the LAN, and I am using machine name and native logon (via dsn-less connection string).
>
>Thanks for you input.
>
>Del