FM Server Ports/Airport

doxx · 05-13-2003, 05:22 PM

Hi, I'm running a FileMaker Server on an Ethernet Connection... I want to access the database wireless from an iBook via Airport (with DHCP)... Internet access works perfectly (ibook>airport>hub>router>dsl) and I already have some airport experience with portmapping and stuff...

This one drives me crazy... does anybody know the ports FMPro Server uses (for portmapping). I did a port scan and it said 80 and 5003 are open and in use on the FM server machine. I did the portmapping for the iBook/airport... still no luck... any ideas??

grrl_geek · 05-13-2003, 06:29 PM

I know you don't have a Netopia router, but here's Netopia's instructions on how to get Filemaker to work on their setup.

http://www.netopia.com/en-us/support...e/NQG_038.html

The gist of it is that you have to add Filemaker as a server in your router (TCP port 5003), but block UDP traffic to the 5003 port. for some reason this screws Filemaker up.

Good luck!

eagle_eyes · 05-13-2003, 06:59 PM

You may also need to supply the ip address of the server to access it. It would help if more info on the server was provided. Is it on your network is the biggest thing.

It does work though, I run a fm pro server at work. I can access it from behind a basestation, from at home, from anywhere. I run another one at home for kicks, and I can also access that one from anywhere. I just had to tell the basestation to open port 5003 to the fm pro server machine.

doxx · 05-13-2003, 09:00 PM

eagle_eyes: my setup at home with an airport bs works just fine... I opened port 5003 and that was it...

grrrl_geek: I will figure out tomorrow how to block this particular UDP port and see if it works...

some more info though...

at work I have the following problem: we're running a network with fixed IPs (192.168.100.xxx) on two Hubs...
The basestation (Extreme btw.) is hooked up to one of the hubs, where 192.168.100.1 is the router/gateway to the internet.
FM Server is running on the hub (192.168.100.232)
The wireless clients get their IPs via DHCP from the airport bs.
The wireless FM client gets the ip 10.0.1.3 - I did a portmapping in the bs for that ip (port 5003-5003).
I guess the problem is somewhere in the address translation from the hubs to the airport?...
Internet access (client>airport>hub>router) works fine w/o any tweaks...
Also I can access the wireless clients from computers of the wired network and vice versa...

hschickel · 05-14-2003, 05:57 AM

doxx,

This sounds like a wiring problem. There are a couple of workarounds...

1. Airport Clients behind NAT - AEBS should be hooked to the the hub via a crossover cable or uplink port to the WAN port on the AEBS. The WAN ip address of the AEBS should be 192.168.100.xxx and the router address should be 192.168.100.1. The distribute IP addresses box should be checked along with the radio button for NAT and DHCP. No port forwarding should be necessary with this setup. Air clients will get NAT protected addresses in 10.0.1.0/24 and your router should send them automatically to addresses in 192.168.100.0/24.

NOTE - this setup is quite insecure. It protects the airport clients from the wired clients when the protection should be going the other way if you need it at all. If you don't need security proceed to option 2.

NOTE2 - under this setup, which I believe is what you're going for, the wired clients should not have easy access to the wireless clients. This is why I thnk you have a wiring problem.

2. Air Clients on the 192.168.100.0/24 network - AEBS should be hooked to the the hub via a crossover cable or uplink port to the WAN port on the AEBS. The WAN ip address of the AEBS should be 192.168.100.xxx and the router address should be 192.168.100.1. The distribute IP addresses box should not be checked. IP addresses for the clients should be assigned manually from 192.168.100.0/24. The air client gateways should be set to the address of the AEBS - 192.168.100.xxx. No port forwarding is necessary with this setup.

(Alternatively this should work if you check the distribute IP addresses box and the share a range of IP addresses button and then use an unused range within 192.168.100.0/24. I have not tested this approach.)

NOTE - this setup is also quite insecure. Everyone is on 192.168.100.0/24 with no separation of air and wired. If you don't need security this is the best solution. Everyone will have equal access to everything.

Hugh

ps - a secure setup would place the air clients and the wireless clients on their own subnets with a vpn gateway connecting them. The air clients should not be able to connect to anything without going through the gateway.

EDITS:
pps - the fact that you're running this whole setup on hubs makes this extra dangerous. Anyone who can get access to your air network can sniff and capture packets from your entire network very easily. This is especially true of option 2.

ppps - http://www.oreilly.com/catalog/80211security/ - is a great book on the subject of wireless security.

doxx · 05-14-2003, 10:06 AM

hschickel - the uplink port did the trick... thank you so much

05-13-2003, 05:22 PM	#1
doxx Triple-A Player Join Date: Nov 2002 Location: Hell's Kitchen Posts: 84	FM Server Ports/Airport Hi, I'm running a FileMaker Server on an Ethernet Connection... I want to access the database wireless from an iBook via Airport (with DHCP)... Internet access works perfectly (ibook>airport>hub>router>dsl) and I already have some airport experience with portmapping and stuff... This one drives me crazy... does anybody know the ports FMPro Server uses (for portmapping). I did a port scan and it said 80 and 5003 are open and in use on the FM server machine. I did the portmapping for the iBook/airport... still no luck... any ideas?? __________________ ------------------------------------- never touch a running system -------------------------------------

05-13-2003, 06:29 PM	#2
grrl_geek Major Leaguer Join Date: Feb 2003 Location: Berkeley, CA Posts: 270	Similiar problem I know you don't have a Netopia router, but here's Netopia's instructions on how to get Filemaker to work on their setup. http://www.netopia.com/en-us/support...e/NQG_038.html The gist of it is that you have to add Filemaker as a server in your router (TCP port 5003), but block UDP traffic to the 5003 port. for some reason this screws Filemaker up. Good luck!

05-13-2003, 06:59 PM	#3
eagle_eyes Triple-A Player Join Date: Jan 2002 Posts: 116	You may also need to supply the ip address of the server to access it. It would help if more info on the server was provided. Is it on your network is the biggest thing. It does work though, I run a fm pro server at work. I can access it from behind a basestation, from at home, from anywhere. I run another one at home for kicks, and I can also access that one from anywhere. I just had to tell the basestation to open port 5003 to the fm pro server machine. __________________ Eagle Eyes eagleeyes@mac.com --------------------------------------- MacOSXHints has an irc channel now. Come check it out! Free software to connect: http://www.freefallsoftware.com/files/xhintschat/XHintsChat.dmg

05-13-2003, 09:00 PM	#4
doxx Triple-A Player Join Date: Nov 2002 Location: Hell's Kitchen Posts: 84	eagle_eyes: my setup at home with an airport bs works just fine... I opened port 5003 and that was it... grrrl_geek: I will figure out tomorrow how to block this particular UDP port and see if it works... some more info though... at work I have the following problem: we're running a network with fixed IPs (192.168.100.xxx) on two Hubs... The basestation (Extreme btw.) is hooked up to one of the hubs, where 192.168.100.1 is the router/gateway to the internet. FM Server is running on the hub (192.168.100.232) The wireless clients get their IPs via DHCP from the airport bs. The wireless FM client gets the ip 10.0.1.3 - I did a portmapping in the bs for that ip (port 5003-5003). I guess the problem is somewhere in the address translation from the hubs to the airport?... Internet access (client>airport>hub>router) works fine w/o any tweaks... Also I can access the wireless clients from computers of the wired network and vice versa... __________________ ------------------------------------- never touch a running system -------------------------------------

05-14-2003, 05:57 AM	#5
hschickel All Star Join Date: Jan 2002 Location: NY, NY Posts: 776	doxx, This sounds like a wiring problem. There are a couple of workarounds... 1. Airport Clients behind NAT - AEBS should be hooked to the the hub via a crossover cable or uplink port to the WAN port on the AEBS. The WAN ip address of the AEBS should be 192.168.100.xxx and the router address should be 192.168.100.1. The distribute IP addresses box should be checked along with the radio button for NAT and DHCP. No port forwarding should be necessary with this setup. Air clients will get NAT protected addresses in 10.0.1.0/24 and your router should send them automatically to addresses in 192.168.100.0/24. NOTE - this setup is quite insecure. It protects the airport clients from the wired clients when the protection should be going the other way if you need it at all. If you don't need security proceed to option 2. NOTE2 - under this setup, which I believe is what you're going for, the wired clients should not have easy access to the wireless clients. This is why I thnk you have a wiring problem. 2. Air Clients on the 192.168.100.0/24 network - AEBS should be hooked to the the hub via a crossover cable or uplink port to the WAN port on the AEBS. The WAN ip address of the AEBS should be 192.168.100.xxx and the router address should be 192.168.100.1. The distribute IP addresses box should not be checked. IP addresses for the clients should be assigned manually from 192.168.100.0/24. The air client gateways should be set to the address of the AEBS - 192.168.100.xxx. No port forwarding is necessary with this setup. (Alternatively this should work if you check the distribute IP addresses box and the share a range of IP addresses button and then use an unused range within 192.168.100.0/24. I have not tested this approach.) NOTE - this setup is also quite insecure. Everyone is on 192.168.100.0/24 with no separation of air and wired. If you don't need security this is the best solution. Everyone will have equal access to everything. Hugh ps - a secure setup would place the air clients and the wireless clients on their own subnets with a vpn gateway connecting them. The air clients should not be able to connect to anything without going through the gateway. EDITS: pps - the fact that you're running this whole setup on hubs makes this extra dangerous. Anyone who can get access to your air network can sniff and capture packets from your entire network very easily. This is especially true of option 2. ppps - http://www.oreilly.com/catalog/80211security/ - is a great book on the subject of wireless security. __________________ First they laugh at you, then they fight you, then you win. Last edited by hschickel; 05-14-2003 at 07:04 AM.

05-14-2003, 10:06 AM	#6
doxx Triple-A Player Join Date: Nov 2002 Location: Hell's Kitchen Posts: 84	hschickel - the uplink port did the trick... thank you so much