First time here? Check out the FAQ!
THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
0

How to examine traffic to 1 specific server?

  • retag add tags

Hi all - i'm afraid i'm not at all knowledgable in this but was hoping for some direction...

I've written a small filemaker pro database app that is meant to run at our workplace for a small number of users to communicate with a server containing anonymised data. The snag is that this is in a hospital, and while i have clearance from IT and IG to do this, I can't i'm afraid expect any techinical support.

This particular case is regarding a Filemaker Server and Filemaker Pro clients. The server has all the ports required open and is accessible easily from outside the hospital firewall. Within the hospital firewall i can still access the server via 'webdirect' (which uses ports 80 and 443) but this isn't good enough for the application. I read the documentation as the client needing ports 80, 443 and 5003 open and the first two are, but probably not 5003 on the hospital firewall side.

However on a filemaker support forum, i've been told that the client doesn't specifically need 5003 on the hospital side, only on the server side, and it uses 'random port' which must be getting blocked by the firewall and I've been advised to use Fileshark to examine the traffic.

I'd be very grateful for any hints/direction on how to set up Fileshare to monitor traffic between the Filemaker client and server... sorry if this is a very basic question, any help would be appreciated...

Stam's avatar
1
Stam
asked 2020-01-02 18:28:32 +0000
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

0

You can try to capture on the server, or even better in front of it, but for this task a capture on the client should be sufficient. Run Wireshark on the client, select the interface on which the traffic to the server will be present and add a capture filter similar to host ip.of.the.server.

I think you may have mistyped "Fileshark", but at least you've found the Wireshark Q&A site which is relevant.

grahamb's avatar
23.8k
grahamb
answered 2020-01-02 20:45:59 +0000
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer