I know the easy solution to this is to scrap IIS, SQL Server and Windows,
but as any of you who work with established clients know, sometimes those
aren't an option.
 
Here's the problem I'm facing.  I'm writing a PHP application for a local
business.  The application is being hosting on a Windows 2003 server.  PHP
is installed as a CGI plugin to IIS, and we have SQL Server 2005 setup on
another Server.
 
Last we we finally got the webserver working as it should and talking to the
database.  When I am on the web server box itself I have no problems
connecting.  

However if I go to another PC and bring up the web application, the
connection to the database server cannot be established.
 
Has anyone had any experience with this or know some good ways to
troubleshoot the problem?  I suspect it may have to do with authentication,
but I'm don't have any idea what IIS uses to authenticate with SQL Server.
 
The statement where it initially dies is mssql_connect(Server, Username,
Password) - although it appears that the variables for user name and
password are never actually used.  
 
What has me baffled is that it should be the same whether I'm running it
from localhost/webapp/index.php or webserver/webapp/index.php.
 
Anyone have any suggestions?
 
Thanks
 
Mike

_______________________________________________

UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net

Reply via email to