Hi,

Just wondering what is the final verdict. Is it that FMS always uses port# 5003, and FMP can use any port? Same port #s on both Mac and Windows?

The reason I'm asking is I want to block unused TCP/UDP ports on Windows, and want to know what I'm doing first.

I believe both must use 5003 unless their communication protocol will go for some other port.

Anatoli,

I have just moved my FMS 5.0 onto Windows 2000 Server system that has a ZoneAlarm firewall. That takes care of shuting down ports for me.

But when I try to open FileMaker Server Console in order to schedule backups, etc. I can not get to any utility. I click on the link, but nothing happens!

The server is serving up files and users can get to it, but it

Try to disable ZA.

I was using ZoneAlarm, but because it was colliding with my CD Nero burning software I've stopped to using ZA.

Anatoli, there's a workaround:

highlight the "Scqedule" and right-click on the right pane.

Here's something bizzare though: Does FMS not like to be installed on another partition (other than difault C:)?? I tried, and got "insufficient priviledges" message. Meanwhile my priviledges are EXACTLY the same as on C: partition.

So I can install on C: but not on any other volume:(

Good tip!

Sorry, I've never tried to install FMS somewhere else.

BikeBoy,

Do you have an NTSF and a Fat32 partition on that server.

If so it will not work.

The installer that comes along with FMServer doesnt support that.

otherwise try installing it first on C:

then DeInstall and install again on D:.

Most of the time it will work fine then.

Jelte,

both partitions are NTFS.

I've tried to install on C, uninstalling and then installing on D, but still received access error.

I've done it so many times I remember License code by heart now. This is the first time when I come across software that won't install on the same exact partition where I have exact same priviledges.

This makes me wonder if this is undocumented issue w/FMS

the last thing you might try is registering certain files with Regserv32.exe

if you look in the manual you will see several DLL files.

register those by hand.

Example.

FMS is installed on D:FMServer

the command line would be

"Regserv32 D:FMServerTCPIP.DLL"

and so on. untill you have registerd all of the DLL files.

If this doesnt work, its probably an other error.