>Hi,
>
>I visited a client's site yesterday to do a test of my app that uses a SQL Server database. They wanted to see the installation of SQL Server so we went through that, installing on a Windows XP Pro system. Upon completion of the install I ran the surface area configuration manager to allow remote TCP/IP connections. I also checked the firewall to ensure port 1433 was allowed (the firewall was actually switched off).
>
>They had a small network setup just for this test and had it configured as a workgroup. The remote PCs could access shared folders on the PC with SQL Server on it, but they could not see SQL Server at all. We tried connecting with my app which uses the Windows API to enumerate all available servers and databases, it found none. We checked using the ODBC applet and still couldn't find any servers.
>
>Has anybody any ideas what could have caused this problem and how to fix it?

Check event log to see if SQL server is really started listening on TCP/IP port. Do not trust default 1433. If you find the entry listening on ... then enable that port on firewall (you said it's off though).
Cetin