Remote Connect to SQL Server 2000

Roy, Are your settings exactly the same? The connection tab and its details is one part of the settings but you also have the connection properties and then specifically the Driver Properties. I see in the Database URL that you are using the namedPipe=true driver property. The only thing (if all your settings match) is that the use of namedPipe may cause the problem. I have no experience with this setting and reading the documentation for it reveals no hints (this is copied from http://jtds.sourceforge.net/faq.html): "namedPipe (default - false): When set to true, named pipe communication is used to connect to the database instead of TCP/IP sockets. When the os.name system property starts with "windows" (case-insensitive), named pipes (both local and remote) are accessed through the Windows filesystem by opening a RandomAccessFile to the path. When the SQL Server and the client are on the same machine, a named pipe will usually have better performance than TCP/IP sockets since the network layer is eliminated. Otherwise the JCIFS library is used. JCIFS provides a pure Java named pipe implementation and uses NTLM authentication, so the domain parameter is required. This feature supports the instance parameter (which changes the named pipe URL), but it does not currently support the named pipe at a location other than /sql/query on the server. The port parameter is ignored if set." Does any of the above make any sense moving forward? Regards Roger