It looks like the name lookup is very slow, you may need to increase the connection timeout in ADO or whatever you're using. Try using the TCP/IP address instead of the computer name. You can also set up a TCP/IP alias from client computers to SQL Server (run "cliconfg" from the command prompt and map a name to an IP address).

Roman


>Hi, I just installed an SQL server 2000 on a server that is connected in our intranet. When I try to connect to it via another computer, it first always gives me a timeout error, but if I retry right after that, it connects without problems. This is a major problem because I have plenty of application that requires this server to run now that the development stage of my applications are almost all finished. Does anybody have an idea of what could be causing this problem. Note, no matter how long it waits for the timeout, the second time it always work.