Quantcast
Channel: FileMaker Forum > Report an issue
Viewing all articles
Browse latest Browse all 3510

Access via NAT-forwardes ports destroys tables and data (6 Comments)

$
0
0

Issue report by Wolfgang Wunderlich1466

Product

FileMaker Pro

Version

14.0.1

Operating system version

OSX 10.10.4

Description of the issue

Opening a multiple-file solution with FM 14 via NAT destroys first table of first opened file.

When using FM14 the first file asks for login, login is accepted, start procedure is running and opens the other files to initialize. Then the first opened file (menu) access again for login - but login is not accepted. This repeats until the end of initializing procedure.
The first table of opened file then is corrupted (prefs).
This is stable to reproduce - but difficult to report.

The destroyed file/record is a one-record-table with > 200 stored fields with preference-values, grown over years.

The Layout behaves like a zero-record-found-set: Field are shown in entry-layout, fields values are empty, cursor can not be place in a field.
- This record can be deleted.
- Re-importing this record from a backup makes the solution work again.
- File-Restore with different option don't make a change.

There is no problem when using FM 13 with this configuration.

Steps to reproduce the problem

We use NAT to provide different servers on only one public IP.
NAT-configuration FireWall works fine with FM 13.
We have a multifile-solution (still 6 files)

This issue correlates with http://forums.filemaker.com/posts/0d4b705adf

Quite difficult to transport the problem. I can record a video to show the behavior.

I was also insecure, if my solution, grown over years, is part of the problem.
But it works fine with FM 13.....

Using script-debugger to find out a certain step of the initializing procedure which causes the problem did not give an hint. There was no certain script step that access some of the other files of the solution.

Expected result

same behavior when using FM 13 - normal startup of our solution.

Actual result

- opening the solution with FM 14 via NAT causes the problem

- opening the solution directly in local network or vie VPN works

- opening the solution with FM 13 works fine

Configuration information

We use NAT to provide different servers on only one public IP.
NAT-configuration FireWall works fine with FM 13.
We have a multifile-solution (still 6 files)


Opening th solution directly in local network or vie VPN works

This issue correlates with http://forums.filemaker.com/posts/0d4b705adf

Workaround

We don't deliver FM 14 to our customers - we still deliver FM 13.

Viewing all articles
Browse latest Browse all 3510

Trending Articles