Solved

Failing to make remote connection to Pervasive database

Posted on 2015-01-26
4
281 Views
Last Modified: 2015-01-26
I'm trying to make a remote connection to a remote Pervasive database (both systems are on a local LAN) with a .NET application we have developed. I know that it works fine on all other PCs' (4 in total) but on one of them I get this

Error in connection. -3496: Server name not found by Pervasive Network Services Layer

When I do a network packet capture on the remote server I see the request coming in

Is there anyone on here who could help me out?
0
Comment
Question by:Gerhardpet
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 28

Accepted Solution

by:
Bill Bach earned 500 total points
ID: 40571382
Server Name Not Found is usually a client-side issue, often caused by smaller environments with no internal DNS server -- the client is unable to PING the server by name, and thus name resolution is failing, and the client returns this error.

This could also be caused by a firewall issue on the server side.  If the Windows Firewall (or other third-party firewall) is enabled on the server, try turning it off.  Similarly, turn off the firewall on the client computer as a test.  You can also use the Windows TELNET command like this:   TELNET <servername> 3351
This should return a black screen, with no errors.  Try port 1583, in addition to 3351, if you are using the SQL /ODBC interface.

If you can post the excerpt from your packet capture showing the connection and about 10 packets on either side, this might also yield some other things to try...
0
 
LVL 1

Author Comment

by:Gerhardpet
ID: 40571546
Thanks Bill. You pointed me in the right direction! It was a DNS issue. The IP address of the client was pointing to a different PC on their SBS 2011. I created an entry in the host file

The network is a mess.
0
 
LVL 28

Expert Comment

by:Bill Bach
ID: 40571566
A Hosts file is a great workaround, but be sure to document it.  Some time in the future, you're going to be troubleshooting the same site (after DNS gets fixed), and this one computer will be failing, and you won't know why.
0
 
LVL 1

Author Comment

by:Gerhardpet
ID: 40571765
You are right. I deleted the wrong DNS entry and remove the line from the host file. Now it works.

Still a lot more to clean up. Thanks again for your help!
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
A Stored Procedure in Microsoft SQL Server is a powerful feature that it can be used to execute the Data Manipulation Language (DML) or Data Definition Language (DDL). Depending on business requirements, a single Stored Procedure can return differe…
In this fourth video of the Xpdf series, we discuss and demonstrate the PDFinfo utility, which retrieves the contents of a PDF's Info Dictionary, as well as some other information, including the page count. We show how to isolate the page count in a…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question