Can't Start Foxray

[Duc M Do]

Hello Foxray users,

I have a back-to-basic question.

I drop a shortcut to Foxray on a user's desktop, make sure he has access to the server, "Run as Admin" the first time, the whole routine. Every time we execute the shortcut, we get the sliding green bar (so far so good), but no Network name shows up in the ensuing login dialogue box. If we go ahead and supply the username/password, we get an error.

The server is working fine, Foxray is working fine (I can start the application from my desktop w/o problems).

What am I missing?

Duc

[ricardoabech]

Make sure the machine can resolve the server name (on the fbp.dll file)

Sent via the Samsung Galaxy S8+, an AT&T 4G LTE smartphone

--
You received this message because you are subscribed to the Google Groups "LimeWare foxray™" group.
To unsubscribe from this group and stop receiving emails from it, send an email to limeware-foxr...@googlegroups.com.
To post to this group, send email to limewar...@googlegroups.com.
Visit this group at https://groups.google.com/group/limeware-foxray.
For more options, visit https://groups.google.com/d/optout.

[Duc M Do]

Ricardo,

I assume that once we have the green sliding bar, network connection is good and foxray_Launcher.exe is running. Is that not enough?

Duc

[Duc M Do]

We can ping, by the name in fbp.dll, the Foxray server.

Duc

[Maks Wilde]

Duc,

Are the required ports open in the firewall?

Maks

--
You received this message because you are subscribed to the Google Groups "LimeWare foxray™" group.
To unsubscribe from this group and stop receiving emails from it, send an email to limeware-foxr...@googlegroups.com.
To post to this group, send email to limewar...@googlegroups.com.
Visit this group at https://groups.google.com/group/limeware-foxray.
For more options, visit https://groups.google.com/d/optout.

--

Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system.

[Duc M Do]

Maks,

I have to assume that the required ports are open through the firewall, because I'm going through the same firewall as the user to get to the Foxray server.

*However* -- this is a big one -- he's logged in in a different domain (DOW) vs the one for existing users (DCC, for Dow Corning Corp) as we're struggling through the merging of DC into the Dow empire. But we've successfully set up another user with the DOW domain to get access to Foxray. That's why I am so baffled about this whole thing.

Thanks for your input.

Duc

[ricardoabech]

Can you try

Telnet servername 3306

You will need telnet client for this. But it will tell you of the port is open or not.

[Duc M Do]

Thanks, Ricardo. I'll try it first thing tomorrow.

If telnet doesn't work, I suppose we have to get the port open. But if telnet works and we still cannot run Foxray, what/where should I look at next?

Thanks!

Duc

[ricardoabech]

If you can ping, it is probably the port. If the telnet works then we would have to check the memory, etc. But it is unlikely

[Duc M Do]

List,

I want to report the final resolution of our problem in case it may be useful to other users somewhere in the future.

Our problem turns out to be neither the closed port on the firewall (Port 3306 is accessible) nor some per-user authentication that I had feared. It takes some literal snooping with Wireshark to determine the cause of the problem: In the back and forth with the Foxray server, we capture this error: "MySQL: Server Greeting Error 1042"

 

The MySQL error 1042 says something about "can't get hostname for your address," but we verify that the Foxray server can and does resolves the client's hostname successfully. The problem is MySQL also tries to do so, and is unsuccessful because the user comes in  though a different domain with a different nameserver.

The solution: Ricardo has us disable name resolving from the MySQL control panel, restart the MySQL service, and presto! The problem is fixed!

Hope this helps!

Duc