As MS Sharepoint administrators will know; MS Sharepoint installs a named instance of <servername>OFFICESERVERS on SQL Server 2005 Express, if no existing server is specified. I was recently tasked with upgrading this version to SQL Server 2005 Standard Edition. I noticed during this process that this Express instance was only visible from client connections localy on the server. I implemented the upgrade successfully and applied Service Pack 3. All of this has been successful without any errors and Sharepoint itself (which runs via IIS localy) is running correctly. However, I am still only able to connect to the instance localy. Any remote client connections get the "[SQL server driver][DBNETLIB]SQL server does not exist or access denied" message. The instance does not appear in the browser list of remote management tools. Connection attempts using IP address instead of instance name also fail. Both SQL logins and Windows Authentication logins fail. The server is configured to allow both. I have already investigated the usual suspects; Surface Area Configuration is set to allow local and remote connections. SQL Server Browser service is running. Names Pipes and TCP/IP has been Enabled in Network Configuration. Dynamic ports is enabled, in additon to the default port of 1433. Other network related functions are running without problem. The server can be 'pinged', Remote Desktop is working, file explorer etc. What else could I be missing here ?