Skip to main content

My (limited) experience with Filemaker Pro

A friend has a retail location which uses Filemaker Pro on 2 computers - I'll refer to them as Main and Satellite.  Filemaker will have a primary instance running on the Main computer and the Satellite will connect to it.  It turns out that Filemaker has it's own network "stack" known as the Filemaker Network (aka fmn://)

Firewall:
You need to ensure that the Windows Firewall allows communication for Filemaker Pro.
Click Start and type "firewall" in the search box.  Then click Allow A Program Through Windows Firewall.  Find the Filemaker pro in the list and make sure the check box is selected for the type of network your interface was designated as.  In his case: public.

Allow Sharing (Filemaker):

On the Main Computer, open Filemaker and click on :
File
  Sharing
    Filemaker Network (this page will show you the IP)
      Network Sharing (click "On")

Connect to Remote Filemaker Share:

On the Satellite Computer, click on:
File
  Open Favorite
     Manage Favorites
  Click +
  Click Remote
  Click Add 
  Insert the IP from the Main system (from the Allow Sharing section above)

Comments

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...