Copyright: Copyright © 1996 Borland International, Inc. All rights reserved.


Communication Diagnostic Tool overview
Communication Diagnostic Tool

The InterBase Communication Diagnostic Tool (ComDg32) lets you troubleshoot your communications setup by testing for existing or potential network problems.

To run a test, click the tab that represents the type of connection you want to diagnose, enter the required information on the property sheet, then click Test.

Choose an item below for property sheet details.

DB Connection

NetBEUI

Winsock


Winsock TCP/IP connection
Winsock

Use this property sheet to test your Winsock TCP/IP connectivity.

To run a test:

1. Enter the name of an InterBase server in the Host field.

2. Choose a service name or number from the dropdown Service list.

3. Click Test, then review the output in the Results window.

Sample results:

Path Name 	= C:\WINDOWS\SYSTEM\wsock32.dll

Size      	= 66560 Bytes

File Time 	= 09:50:00

File Date 	= 07/11/1995

Version   	= 4.0.0.950

This module has passed the version check.

Initialized Winsock.

Attempting connection to: 100.100.99.99.

Socket for connection obtained.

Connected to host "myhost", port 21

Closed socket and deinitialized Winsock

Test complete -- no errors

Possible error messages and corresponding actions:

If the error message is...	Then check...
Failed to find named port	your SERVICES file to be sure there is an entry for gds_db in the form: gds_db 3050/tcp
Failed to connect to host	hostname, port nn the InterBase Server to make sure it is installed properly, is running and is configured for TCP/IP.
Failed to resolve hostname	hostname your HOSTS file or DNS to be sure it has an entry for the server.


InterBase DB Connection
DB Connection

This test lets you connect to an InterBase database using the InterBase client libraries. It is the most basic test of InterBase operation, and is generally needed only after confirmation that the underlying network is working correctly.

To run a DB Connection test:

1. Choose a server type -- Local or Remote --  to which you want to connect. If you choose Remote, you have to enter the name of the Server and the Network Protocol (choose from the dropdown listbox). If you choose Local, server and protocol aren't needed, so the fields are grayed. Note: InterBase Server must be running on your machine before you can connect to a local database.

2. In the Database Info group, enter the name of a Database on the selected server, along with the required User Name and Password. Notes: Include the full drive and directory path to the database. If you're connecting to a database on a NetWare server, include the disk volume name. NT share names or mapped drive letters are not allowed.

3. Click Test, then review the output in the Results window.

Sample output (local connection):

    Path Name 	= C:\INTERBAS\BIN\gds32.dll

    Size      	= 348160 Bytes

    File Time 	= 17:40:00

    File Date 	= 12/04/1995

    Version   	= 4.1.0.5

    This module has passed the version check.

    Attempting to attach to c:\interbas\examples\employee.gdb

         Attaching	 ...Passed!

         Detaching	 ...Passed!

    InterBase versions for this connection:

    InterBase/Windows NT (access method), version "WI-B4.1.0"

    on disk structure version 8.0

    InterBase Communication Test Passed!

Possible error messages and corresponding actions:

If the error message is...	Then check...
Unavailable database	if the InterBase server is running (the server must be running before attempting a database connection).


NetBEUI/Named Pipes Connection
NetBEUI

Use this property sheet to test NetBEUI connectivity. It does not use the client libraries.

To run the test, enter the name of a Windows NT server on which InterBase has been installed, then click Test and review the output in the Results window.

Notes:

NetBEUI is supported on Windows NT, Windows 95, Windows for Workgroups 3.11 and on machines running Lan Manager Enhanced. It requires the NETAPI.DLL driver supplied with those environments.

This connection may fail if a Microsoft Windows network is not the default network for the client. One way to check this is to run the Network Setup program that is in the Network program group. Check that Microsoft Windows Network is the first item on the Networks list. You should also be logged into the MS Windows network with a valid NT user name and password.