dbTalk Databases Forums  

Open remote:..

comp.databases.filemaker comp.databases.filemaker


Discuss Open remote:.. in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Joseph Sanders
 
Posts: n/a

Default Open remote:.. - 12-05-2005 , 05:27 PM






I know this has been delt with before. I've been reading every post I
can find on the subject but I'm still having problems. Any help you can
give me would be appriciated.

I'm hosting file on my machine at work (WIN2K PRO) which is connected
to the LAN and in turn the internet via action tec DSL router.

I have Network Sharing ON in the sharing menu it shows my IP: as
192.168.0.3 I know this is a private IP.

Quote:
From www.whatismyip.com i've got: 71.34.xxx.xxx for a "public" IP.
I've setup port forwarding on my router to forward port:5003 to
192.168.0.3

I've verified that this port is open by probing it from
https://www.grc.com/x/ne.dll?bh0bkyd2

I've tried to connect to the open file (history.fp7) on a machine
across the room by:

open: remote: Add Host: IP 71.34.xxx.xxx ("public" IP)

Select ( 71.34.xxx.xxx) from list of hosts (no available files show up
even though I have "don't display in open remote file dialog UNchecked)

network file path: fmnet:/71.34.xxx.xxx/

to which I add the file name "history" so it looks like this:

network file path: fmnet:/71.34.xxx.xxx/history

Click OPEN

I get:

history.fp7 could not be opened. Either the host is not available or
the file is not available on the host.

I CAN connect to this file by using the LAN IP address (private?)
192.168.0.3/history



Any ideas?

-JOE



Reply With Quote
  #2  
Old   
42
 
Posts: n/a

Default Re: Open remote:.. - 12-05-2005 , 06:46 PM






1) Firewall software on the pc itself? e.g. McAffee / Norton? Its
possible (indeed its normal) to allow inbound connections originating
from the LAN (192.168.0.*) while blocking everything else.

2) Verify your public IP address by actually looking at the router
status page. www.whatismyip.com is not infallible - e.g. proxy servers
may confuse it.

3) Multiple NAT? Are you sure your NAT router isn't itself behind a NAT
router. Some corporate networks and even some ISPs will do this.

FWIW Usually this sort of thing will end up being related to firewall
software.


-Dave


In article <1133825257.264246.158860 (AT) g43g2000cwa (DOT) googlegroups.com>,
joseph.sanders (AT) gmail (DOT) com says...
Quote:
I know this has been delt with before. I've been reading every post I
can find on the subject but I'm still having problems. Any help you can
give me would be appriciated.

I'm hosting file on my machine at work (WIN2K PRO) which is connected
to the LAN and in turn the internet via action tec DSL router.

I have Network Sharing ON in the sharing menu it shows my IP: as
192.168.0.3 I know this is a private IP.

From www.whatismyip.com i've got: 71.34.xxx.xxx for a "public" IP.

I've setup port forwarding on my router to forward port:5003 to
192.168.0.3

I've verified that this port is open by probing it from
https://www.grc.com/x/ne.dll?bh0bkyd2

I've tried to connect to the open file (history.fp7) on a machine
across the room by:

open: remote: Add Host: IP 71.34.xxx.xxx ("public" IP)

Select ( 71.34.xxx.xxx) from list of hosts (no available files show up
even though I have "don't display in open remote file dialog UNchecked)

network file path: fmnet:/71.34.xxx.xxx/

to which I add the file name "history" so it looks like this:

network file path: fmnet:/71.34.xxx.xxx/history

Click OPEN

I get:

history.fp7 could not be opened. Either the host is not available or
the file is not available on the host.

I CAN connect to this file by using the LAN IP address (private?)
192.168.0.3/history



Any ideas?

-JOE



Reply With Quote
  #3  
Old   
Aladino
 
Posts: n/a

Default Re: Open remote:.. - 12-06-2005 , 02:02 AM



I'll append my experience and problems here.
I can connect to my office server with filemaker pro with Open Remote ->
fmnet:/85.xxx.xxx.xxx/. To do this I've made a NAT rule and configurede
firewall to turn TCP port 5003 from our public IP on router to our
Server. And It works like it should.
The problem is with filemaker server admin. In the same way described
before, I've made other two NAT rules and configured firewall to turn
TCP ports 50003 and 50006 to the same Server, but this didn't give me
the result I'm awaiting: there's no way to connect FileMaker Server with
Admin Tool. :-(
I can't understand way, it seems me it should work... Is there any thing
I must configure on my Server (other then accept remote admin)?

P.S. Our office Server is a G5 with Mac OS X 10.3.9 Server, and my
computer is a Mac too, with Mac OS X 10.4.3.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.