Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 5645 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Hi,

I am on windows server 2003 with a version of filemaker server 10 adv...

I setup a ODBC connection, I install sequelink 5.5... when I tried to connect, it's always, connection refused....

I do a netstat-an but the 2399 port seem to not listen...

no firewall on this computer...

I tried the same thing on another computer, works well.... but on my server... don't work at all...

I rebooted, I reinstalled fmsa ... nothing change...

the 2399 port is not use whit any other application....

anybody have a issue for me?? I am getting crazy.....

Thanks

Bruno

Posted

When you say:

no firewall on this computer...

do you mean that the Windows firewall is turned off? Becasue it is there as part of the install.

Also, are you sure you have the Advanced version of FMS?

And is there a file with the fmxdbc bit enabled that is hosted for access for you to test against?

Steven

Posted

thanks for the reply

the firewall is disarmed,

I have a version of filemaker advanced, I am tried the evaluation version that i download last week.

And I have a database shared for odbc, in my filemaker server admin console, the odbc is turn on, and the check under odbc/jdbc is on...

but, when I want to open the server admin console, is very long, takes almost a minute...

Posted

is there any privilege set in the hosted file that has the xDBC extended privilege bit set on? Are you testing the connection with an account that belongs to that privilege set?

This topic is 5645 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.