ID: 38965 Updated by: [EMAIL PROTECTED] Reported By: aren at cambre dot biz -Status: Assigned +Status: Bogus Bug Type: MSSQL related Operating System: Windows 2003 (for both servers) PHP Version: 4.4.4 Assigned To: fmk New Comment:
No PHP uses ntwdblib and if you install the Client tools from MSSQL server you can define the default protocol. Older versions of ntwdblib (or combinations of other MS tools installed) uses named pipes as the default. The best way is to install the Client Tools and us the Clinet Network utility to set default protocol as well as create aliases for different servers. Each alias can be defined with the prefered protocol. Previous Comments: ------------------------------------------------------------------------ [2006-09-26 17:25:21] [EMAIL PROTECTED] Frank, is this really a PHP problem? ------------------------------------------------------------------------ [2006-09-26 17:16:54] aren at cambre dot biz Description: ------------ When using mssql_connect to connect to a SQL Server database on a remote server, PHP attemtps to connect using named pipes. This is a terribly outdated behavior; SQL Server connections these days are almost always done with TCP 1433. I figured this out with a difficult phpBB installation and using Wireshark (formerly Ethereal) to watch network traffic. There is a registry hack that can force the SQL Server Client program to use TCP 1433, but this hack's effects on other software is unknown. For more info, see http://people.smu.edu/acambre/blog/2006/09/22/Buggy+PHP.aspx and http://www.phpbb.com/phpBB/viewtopic.php?t=446662&postdays=0&postorder=asc&start=0 Reproduce code: --------------- Just use mssql_connect to connect to an external database. Expected result: ---------------- The database should open just as if the database is on localhost. Actual result: -------------- Usually a cannot connect error. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=38965&edit=1
