ODBC connection paramaters

[t1950]

i'm trying to connect an XP 32bit laptop over a WAN to an ASA11 db. the pc sees shared folders on the db server via explorer.

i'm using the Windows ODBC manager to set up the connection. because it's on a different sub net than the server, on the network tab in ODBC setup , i'm specifying host=172.68.18.18 with different tries at specifying a port and DoBroadcast=Direct.

examples of what i've tried are host=...:port=2638, host=...;port=2638, host=...:2638;DoBroadcast=Direct (all lower, mixed case, and all upper).

i've tried the DoBr at the beginning of the line (DoBr..;host-...) with and without a port specified.

when the laptop is on the LAN in the main office, it connects.

any help would be appreciated.

[graeme_perrow]

If the port number that the server is using is 2638 (the default), you don't need to specify port= at all. If you're specifying a host IP address, the default is DoBroadcast=direct so you don't need to specify that either. In the network tab, make sure the TCP/IP box is checked and specify host=172.68.18.18 in the text box next to it. You also need to make sure you have the correct server name on the Database tab.

[t1950]

something has changed on the laptop or with the ISP, because host=172... worked in Oct 2012 for about 4 weeks. we can't figure out what has changed.

the tech i was working with on the other end and i thought it was something to do with a firewall or something the ISP provider was blocking.

a further test, using telnet (telnet 172.16.30.5 2638) came back successfully.

the message we get is dbserver not found. if the company hit its connection limit while we were trying to connect, would we get a different message?

[MCMartin]

yes, you would get a license exceeded message

[MCMartin]

the telnet IP is different than the IP you mentioned in your question above?

[t1950]

the ip address i used in my example was a number i made up because i couldn't remember the actual addr. the one in the telnet is the one we used for host= on the network tab.

[t1950]

Thanks for the suggestions.

The client was able to connect with host=172.16.30.5, which what was originally in his setup that STOPPED working.

AFAIK, no other changes were made to their VPN, firewall, network, etc.

[MCMartin]

In this case don't trust the statement that nothing else was changed 😉