Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 11 to 15 of 15 total |
Unable to connect to database |
Sat, Jul 28 2012 7:59 PM | Permanent Link |
Raul Team Elevate | Ping at least ensures your name resolution works (if you connect to
hostname) but it's ICMP so doing telnet would actually test end-to-end TCP connectivity. Raul On 7/28/2012 7:52 PM, Blake wrote: > They have been able to ping the server. I haven't tried telnet, but I will. > |
Sat, Jul 28 2012 8:30 PM | Permanent Link |
Fernando Dias Team Elevate | Blake,
You haven't yet tell us, what DBISAM version are you using? -- Fernando Dias [Team Elevate] |
Sun, Jul 29 2012 3:01 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Blake
>Just to clarify--the issue I'd REALLY like to solve is this one where my app connects to the remote server sometimes but then not others. I think it's something wonky with the network since it only happens at the client site, never on my test network. That's usually a good indication its not your fault The problem is that the effect can be caused by hardware or software. For the client sites reporting it can they say it its all workstations connecting or just specific ones. If they can't ask them to record by workstation. If a specific one you've found your culprit. Also ask for a full software audit - then you have a guessing game, but at least you should be able to isolate the differences between their setup and yours. Roy Lambert [Team Elevate] |
Thu, Aug 2 2012 2:25 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Blake,
<< That is, I start it. It works. I exit. The users start it up, and it works for them. They exit. A few hours or days later, they go to start it up and it fails to connect. >> Try to get the exact error message from them. That will help a lot in determining what the issue is - if it's a proper DBISAM engine error, then that's a DBISAM problem. If it's a DBISAM error that is just wrapping a Winsock error (code), then it is external to DBISAM and an environmental issue (firewall setting, most likely). If you have any other questions, please let me know. Tim Young Elevate Software www.elevatesoft.com |
Sat, Aug 18 2012 6:19 PM | Permanent Link |
Blake | Thanks for everybody's help.
I've had the situation occur a couple of times where the app stops working--but now I've had it where it STARTS working again, even though I've changed nothing. So, I consider myself off the hook. I'm still curious, but it's an academic curiosity at this point. Everything they use is secondhand, bargain-basement hardware (and I suspect unlicensed software), and I didn't sign on to debug their network. Just as an FYI, I'm using DBISAM 4.3. Thanks again. |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |