Hi

We have an issue with running DBISAM with Windows Server 2012 Direct Access. If you simply do the following:

1. Install Windows Server 2012 R2
2. Run DBISAM and test with DbSys, everything works fine.
3. Install Direct Access on server 2012.
4. Run DBISAM and test with DbSys, can no longer connect to the database server.

Now if you run Dbsys and set it up to run connecting via 127.0.0.1 it works, but if you use the internal IP .e.g. 192.168.0.1 it wont connect.

has anyone come across this before?

On 2/26/2015 9:47 PM, ClockOn wrote:
> We have an issue with running DBISAM with Windows Server 2012 Direct Access. If you simply do the following:
> 1. Install Windows Server 2012 R2
> 2. Run DBISAM and test with DbSys, everything works fine.
> 3. Install Direct Access on server 2012.
> 4. Run DBISAM and test with DbSys, can no longer connect to the database server.
> Now if you run Dbsys and set it up to run connecting via 127.0.0.1 it works, but if you use the internal IP .e.g. 192.168.0.1 it wont connect.
> has anyone come across this before?

Step 3 is not that simple - you're reconfiguring much of the host
networking and routing.

I have not specifically used this but as with any VPN solution my
suspicion is routing and/or firewall issues.

Since you can connect using local loopback we know DBISAM itself is
operational.

Based on these tests i assume assume you're connecting from local
clients (not DirectAccess clients in which case IPv6 comes into play as
well).

DBSRVR is a straightforward TCP server so normal TCP server
troubleshooting tips would all apply.

Raul

Hi

This is strange it fails on local machine and LAN clients without even try to connect via direct access. I can ping etc all fine turned off firewall. New server with direct access thats it easily repeatable. Ive tried connecting via hostname with no luck as well.

Oh also i found if you turn off direct access and run the command like 'netstat' you can see the DBISAM ports are available but as soon as its turned on they're gone. Cannot see anything to allow the ports through etc

so problem seems to be that direct access forces the use of IPv6 which DBISAM is not able to use. So will have to work out some middleware for our application to get around this.