A colleague and I are working with an organization to enable remote 
access via the internet. The client has a DSL connection using a 
NetGear router. We can share ebase locally, so apparently the LAN, 
Windows network configuration and Filemaker's net protocol are 
working. We can open ports on the router for other applications and 
successfully get access to the machine in the office that runs ebase, 
so apparently the router configuration procedure is valid. But 
accessing FileMaker through port 5003 doesn't work. That is, I get no 
files available in the open dialog when selecting the correct IP 
address as host.

There is a FileMaker tech note (106727) that might point to the 
problem, suggesting that the router needs to be configured to 
selectively block UDP packet routing but allow TCP/IP traffic.

This problem is obviously erratic - I've set systems up for Internet 
file sharing before without encountering this problem. Anyone have 
this happen or have experience with the router configuration 
mentioned?  

------------------ 
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support  and enter the email address 
you used to subscribe to the ebase support list:: [email protected]

To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
 ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------

Reply via email to