Client cant connect to server

We have installed a SQL 2000 server on a windows xp-pro machine and succesfully installed DotNetNuke. Now is the problem that there is no way we can manage to get a client connected. We have tried everything, changing tcp port, setting permissions, changing registry according to document 307197 in the microsoft database and nothing helps.
The only thing we can see is that in the serverlog we get a message stating that "SuperSocket Info : Bind failed on TCP port 1433". Can anyone help?
Regards Ulla & TomI assume you mean MSDE since SQL Server itself won't run on XP Pro. Have you looked at these yet:
http://support.microsoft.com/kb/293107/EN-US/
http://support.microsoft.com/kb/312935/
Have you checked to see if anything else is listening on port 1433? Have you tried using SQL on another port?
Jeff|||first thanx for yor reply - but no - I do mean Microsoft SQL Server 2000 Enterprise (evaluation version) - and it does run on an XP pro SP2 machine...
I am able to connect to the server locally by eg running my DotNetNuke portal and access it via http, but I cant access the portal from other computers in my home network.
I did have a look at the docs you mention. Regarding doc 293107 I have shot down all other software running on the server and it dosnt help. I checked the TCP ports with TCPVIEW and found nothing utilizing port 1433. I also changed the default TCP port for the server.
Regarding doc 312935: this does not refer to the same error message that I receive, however in lack of other good ideas I will try to get hold of the file from MS containing the fix fo that problem....
I hope you have other good ideas to fix my problem......|||

ujep wrote:

I do mean Microsoft SQL Server 2000 Enterprise(evaluation version) - and it does run on an XP pro SP2machine...

Are you 100% certain about that? Do you have a reference? Anything I have ever seen (e.g.Choosing an Edition of SQL Server 2000 andA Comparison of SQL Server 2000 with Access 2000) indicates that Windows XP can only run these versions of SQL Server 2000: Personal, Developer, and Desktop.
|||I downloaded the server from MS herehttp://www.microsoft.com/downloads/details.aspx?FamilyID=d20ba6e1-f44c-4781-a6bb-f60e02dc1335&DisplayLang=en , the documentation states that it can run on XP...
the welcome picture in setup states that this is a Windows 2000 server Enterprise edition....
I still havent found a fix for the problem, hope someone can help|||

ujep wrote:

I am able to connect to the server locally by eg running my DotNetNuke portal and access it via http, but I cant access the portal from other computers in my home network.

Most likely a firewall or security policy issue then. Though I wouldn't think you'd get the SQL port error, since DNN doesn't need to cross the network to reach a local SQL server and the clinet systems don't access SQL directly. Try a simple Hello World HTMP and ASPX page from the clients.
Jeff|||I am able to open html and aspx pages from the cliens - the only thing I can't do is open DNN - so if the problem is a security policy issue then it should then be within the server (or DNN) -|||

Yeah, but DNN works on the server itself, so it isn't a DNN or server problem either. When you opne DNN on the server, can you use the FQDN name justa s you would on the client, or are you just able to use "localhost"?

Jeff