Thanks Tecman, but I should have spelt it out a little more clearly. here goes :
I have tried all the obvious options, namely :
1. Pinging : Successful : Both, with servername and FQDN.
2. Server network utility : Have all three installed and running (
Multiprotocol / Named pipes / TCP/IP ).
3. Multi protocol and named pipes are fine and I can connect.
It looks as though SQL Server is not listening on the TCP/IP port 1433 only. I have not tried changing the port, but I will. If there is a port conflict in that some other program may be using 1433 and starts before SQL Server.
Thanks again ... I was thinking of the DNS problem .. As a matter of fact, when I used IP to connect and it was succesful, I also initially thought it was a DNS problem .. But when I tried pinging both with just the server name and also with the fully qualified domain name, I was able to ping .. I tried from several boxes, on different subnets etc. Pinging is fine, and resolves with the correct IP address.
This would disqualify the DNS factor, would'nt you think ?
By the way, I also tried changing port numbers from 1433 to 1500 and restarted the SQL server .. then tried connecting using TCP/IP and the new port number - Client configuration.. I still cannot connect.
This leads me to believe that SQL Server has stopped listening on TCP/IP altogether ..I dont know why, though.
I have. I use the server network utility on the server to change port numbers that I want SQL server to listen to and then change the client settings on a client machine using the client network utility ....