Well I have to give a big thank you to Mike Weideli & Sally Rankin for their efforts.

Mike sent me the information below and it does seemed to have worked. Now I have the firewall on and I can log a workstation into R6.

Possible Remedies:
•    Enabled Named Pipes and TCP/IP protocols on the database server.
i.    Start → All Programs → Microsoft SQL Server 2005 → SQL Server Configuration Manager
ii.    In the left hand pane, expand "SQL Server Configuration Manager (Local) → SQL Server 2005 Network Configuration"
iii.    In the left hand pane, highlight "Protocols for SQLEXPRESS"
iv.    In the right hand pane, right click "Named Pipes" and select "Enable"
v.    In the right hand pane, right click "TCP/IP", select "Enable" and then select "Properties"
vi.    On the "IP Addresses" tab ensure that "Enabled" is set to "Yes" for each network adapter listed.
vii.    Click [OK] to close the TCP/IP Properties dialog.
viii.    In the left hand pane select "SQL Server 2005 Services"
ix.    Right click "SQL Server (SQL EXPRESS)" and select "Restart"
Whilst it is not required for this process, it can make the task of configuring remote access to SQL Server Express easier if you also start the process "SQL Server Browser". You may need to open the properties and on the "Service" tab change the Start Mode from Disabled to Automatic, before you can start the process.

•    Add SQL Server 2005 Express as an exception to the windows firewall.
You will need to add SQL Server 2005 Express as an exception to any firewall software that is running locally. The following sequence assumes the Windows XP Firewall:
i.    Start → Control Panel (classic view) → Windows Firewall
ii.    On the Exceptions tab, click "Add Program..."
iii.    Browse to "sqlserver.exe" and click [OK]. This is normally located in the folder "Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn"
iv.    Repeat for "sqlbrowser.exe" if you have set the "SQL Server Browser" service to run. This is normally located in the folder "Program Files\Microsoft SQL Server\90\Shared"
v.    Click [OK] to close the Windows Firewall dialog.
If you still find that you cannot connect, then try opening TCP Port 1666 in the Windows Firewall:
vi.    Start → Control Panel (classic view) → Windows Firewall
vii.    On the Exceptions tab, click "Add Port..."
viii.    The "Name" can be anything, but I suggest something like "TCP Port 1666 for SQL Server". For the "Port number" enter 1666, and ensure that TCP is selected. Click [OK]
ix.    Click [OK] to close the Windows Firewall dialog.
For those that are interested, the port number 1666 comes from the "TCP Dynamic Ports" displayed on the "IP Addresses" tab of the "TCP/IP Properties" of the TCP/IP Protocol listed by SQLServer Configuration Manager.
If you get this error when trying to connect using Microsoft SQL Server Management Studio then try opening UDP port 1434.

•    Ensure that the SQL Server 2005 Express server process is running.
Check this by:
i.    Start → Control Panel (classic view) → Administrative Tools → Services
ii.    Scroll down and check that "SQL Server (SQLEXPRESS)" has the status of "Started". Start it if it is not already started.
________________________________________
These notes have been tested against SQL Server Express 2005 running under Vista and Windows XP

Of note perhaps is that although I had Named Pipes and TCP/IP both enabled the IP address setting is not enabled by default. Setting the exception was obvious but not knowing which .exe to set the exception for was my problem.

Thanks

Hi Keith,
Odd that it should work once, but not the second time. There is some information on the message, including pertaining to firewall setup here: http://support.microsoft.com/kb/328306.
Regards

Sorry about that, though I suspect that you analysis of the firewall log would make my head spin! Anyway, if you search for port 1434 you will see that it is required by the SQL Browser service (see http://www.sql-server-performance.com/a … ns_p1.aspx). It sounds like it is quite a common thing to need to do, but for maximum security it should be left closed and the client configured to avoid the need to use the SQL Browser service. I must admit I am not 100% sure about how to do that!