asked on

Problems trying to create ODBC connection from client with pervasive database

I am trying to setup a DSN from a client and receive the above error. In running the Pervasive System Analyzer, there is a problem with the relational access. The relational service is active. I can setup a client DSN on the server with no problems, but when I try to do this from the client, I receive the error. What do I need to do?

Mirtheil

The error you are seeing could be related to a firewall. Make sure port 1583 is open on the server and client.
Is this the only client that gets the error? If so, what's different about this one?
Make sure you can ping the server by name from the client.

tlstimo

ASKER

The port is open and listening on the server, but not the client. How do I fix this on the client side? Also, this error is on all clients and I can ping the server from all clients.

Jim P.

You do have the Client ODBC software loaded?

tlstimo

ASKER

Yes, I do. I have the ability to setup a client using Pervasive ODBC Client Interface. Am I hearing your question correctly? The steps I take from the client are to navigate to ODBC Administrator through Control Panel. Select System DSN tab, click Add, select Pervasive ODBC Client Interface, create the name, enter my server name, click Get DSN list, pick the Pervasive Engine, then click Test. After a period of about 15 seconds or so, I receive this error: SQL connection manager may be inactive or using a different transport protocol from the client.

ASKER CERTIFIED SOLUTION

Mirtheil

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

tlstimo

ASKER

-OS: Windows SBS 2000, SP4
-TCP/IP Protocol
-Firewall is not blocking either port
-yes, I can create a client DSN on the server and connect ot the engine successfully

SOLUTION

Jim P.

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

tlstimo

ASKER

Thank you!!!! Setting the server to the IP instead of name did it! Is this caused by a problem with my DNS?

Mirtheil

When you ping the server by name from the client, does it show the same IP Address as what you entered? I've seen where DNS is returning the IP address of a different server.

tlstimo

ASKER

Yes, it does show the IP address of the server as I entered it. My knowledge of this is limited, but I always thought if you can see the IP address when you enter the name, then the DNS is working properly. Isn't this correct?

Jim P.

The way that DNS works, is that it looks to what is stored in memory (ipconfig /displaydns), then goes to the hosts file (On a windows machine c:\%systemroot%\system32\drivers\etc folder) then tries the DNS server for resolution. If a DNS resolution fails it will try broadcasting for the server, next it moves to the NetBIOS name, checks the LMhosts file, then looks for a WINS machine, then tries to find a master brwoser server.

Failing that it doesn't find the server.

So if the hosts file on the machine has a bad reference to the server, it will override what is coming from DNS. We've had individual workstations that were set up with a host file. We then replaced the server, but forgot about that PC's hosts file being edited, and it could never find the server.