Through server administration utility I can access our server database fine.  When I try the database system utility -and click connection type Remote, it says that it is not available.   Options remote tab, remote setup settings is the same as setup in administration utility.  Any ideas?  

On 3/26/2014 2:44 PM, Owen wrote:
> Through server administration utility I can access our server database fine.  When I try the database system utility -and click connection type Remote, it says that it is not available.   Options remote tab, remote setup settings is the same as setup in administration utility.  Any ideas?


Setting should not be same - dbsys needs to use the main port (default
12005) while admin uses admin port (default 12006).

If that's was not the issue i'd say main port (12005) is blocked by
firewall.

Raul

Thanks Raul, I tried 12005, same result.  The server is inside the network, no firewall involved.  

I don't know if it is related or not, this problem was discovered when I first tried to do a remote session in my applications and got a ESocketError.  My first thought was, can I get to a table through the utility?   So, I tried the I started messing with the utility and found it would not connect remote.   

On 3/26/2014 3:02 PM, Owen wrote:
> I don't know if it is related or not, this problem was discovered when I first tried to do a remote session in my applications and got a ESocketError.  My first thought was, can I get to a table through the utility?   So, I tried the I started messing with the utility and found it would not connect remote.
>

ESocketError is a winsock error simply surfaced by DBISAM. There is
usually a message as well that provides more info.


Is problem from one machine or generally not accessible (if you have
more than 1 pc around to try on) ?

Can you confirm the db server is still running on 12005?

For example using netstat or TCPView
(http://technet.microsoft.com/en-us/sysinternals/bb897437) on the server
and look for 12005.

How about shutting down dbsrv and restarting it to see if that affects
anything ?

Raul

Raul wrote:

On 3/26/2014 3:02 PM, Owen wrote:
> I don't know if it is related or not, this problem was discovered when I first tried to do a remote session in my applications and got a ESocketError.  My first thought was, can I get to a table through the utility?   So, I tried the I started messing with the utility and found it would not connect remote.
>

ESocketError is a winsock error simply surfaced by DBISAM. There is
usually a message as well that provides more info.


Is problem from one machine or generally not accessible (if you have
more than 1 pc around to try on) ?

Can you confirm the db server is still running on 12005?

For example using netstat or TCPView
(http://technet.microsoft.com/en-us/sysinternals/bb897437) on the server
and look for 12005.

How about shutting down dbsrv and restarting it to see if that affects
anything ?

Raul


Raul,
You are pretty smart.  Actually that solved both my problems.  I did a netstat -a on the server and discovered that ports 12010 was running as well as 2009.  I had been trying to do 12005 or 12009.  So, when I tried the utility with port 2009, it worked.  Now for the Socket error.  Again, I was using 12009, so I switched the port to 2009 and it let me in.  

Thanks,
Owen