October 7, 2008 at 7:23 am
OK, first off, I am not a Database guy, I am a network guy. I do consulting for small businesses. I have a client using a medical records program called MicroMD. It has a client software that connects to a database on a server. This company has 2 office's that had a site to site VPN between them.
I had a PC that had this software installed on a system in the main office where the server is, this program worked good, no issues. This user moved to the second office, which has a different subnet, but the VPN connects them. Now when I attempt to launch the program, I get the following problems.
1. When I first launch, it thinks for a minute and then I get a window pop up with connection properties. The title of the window is "Connect to Adaptive Server Anywehre". It has a Login Tab, and ODBC tab, a database tab, network tab, and Advanced Tab. As far as I can tell, these settings are all correct, nothing should have changed.
2. If I click "Cancel" on that properties window, I get an error message that says:
Error [100]
Unable to connect transaction using DSN entry 'MEDICAL'; No data was found to satisfy the request.
I click the OK button and everything closes.
3. If I click "OK" on the properties window instead of cancel, I get this error message:
Error [-100]
Unable to connect transaction using DSN entry 'MEDICAL'; SQLSTATE = 08001 [SYBASE][ODBC Driver][Adaptive Server Anywhere]Database server not found.
IF I take this PC back to the original office, it works fine. In second office with different IP subnet, i get the problems. Anyone have any ideas?
I have verified that I am able to access all the shares on the server the same from the second office as from the main office.
If I did not provide enough info, please let me know, I have not done alot with databases before, so this has me somewhat lost. I was not around when this program was originally installed, the company who makes it charges a crazy yearly support fee that my client does not want to pay, since they dont use this program anymore for new data, they just keep it around for accessing previous data.
Any help would be very much appreciated.
October 7, 2008 at 7:34 am
Is the user swapping pcs when they move to the second office, or moving their pc?
It looks like it cannot find the ODBC data source, is this setup on the second pc?
October 7, 2008 at 7:38 am
Just so you are aware "Adaptive Server Anywhere" is a Sybase product. What are the ODBC settings? Is there a firewall involved on either side of the VPN?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
October 7, 2008 at 7:41 am
Ultimately this is an ODBC configuration issue with the link being to Sybase. So, open control panel, administrative tools, Data Sources. Find the data source associated with the error and then walk through the configuration of that. There must be something in that configuration (most likely in the network communication layer piece) that is configured incorrectly and is now limited due to the new network topology where it lies. I blelieve that will take care of your problem. Post back with issues if you still have them.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
October 7, 2008 at 7:56 am
Thanks for the quick replies, i will check the data source settings. Do you mean on the server or on the PC?
It is the same PC, I am taking the PC from main office, unplugging it, bring it to the second office, plugging it in there. The only thing that changes is the local subnet, it still logs onto the domain.
The two locations are connected via hardware Site to Site VPN. I have a sonicwall on both sides of the VPN and am not blocking any traffic. I also attempted to create a NAT rule to make the server think the PC that was moved it on the local subnet, but that did not help at all.
October 7, 2008 at 7:58 am
ODBC datasource on the PC, check the configuration in there and you should be able to get this working.
Control Panel --> Admin tools --> Data sources (ODBC)
October 7, 2008 at 8:04 am
configuration looks ok to me, its all the same as on another PC in the main office that is able to connect OK. Is there some setting that needs to change since its now going over a VPN instead of being local?
October 7, 2008 at 8:12 am
So when you walk through the ODBC configuration for that DSN and you get to the end what happens when you hit the TEST button? Curious.
Not familiar with Sybase (thank you!!! 🙂 ) but I am also wondering if there is something at the server end that is configured to allow specific IP's through the VPN. Hopefully you will understand that better than I since you are the network guy. 🙂
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
October 7, 2008 at 10:26 am
Hi Jeff
I would check the firewall settings for the SQL server IP,i had a problem like this earlier and it was a firewall issue
🙂
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply