Need Immed help with port problem!

Am giving Filemaker pro database training.  I'm in a computer lab and none of the computers can access the database.  I can remote desktop onto the server to confirm the database is working.

I suspect that this lab is on a subnet with port 5003 blocked.  But I do not know what tests to quickly isolate and debug this problem.

How do I make the netstat command check port 5003?

Who is Participating?

Improve company productivity with a Business Account.Sign Up

rfc1180Connect With a Mentor Commented:
can you try on the server that is listening on 5003

log onto

telnet 5003
telnet localhost 5003

or check netstat to see if it is listening

sounds like there is a policy deny access to 5003 or the port is not bound to the IP


latchwaysConnect With a Mentor Commented:
quickest way to check if a port is open is to use telnet eg.

telnet 3389

the above will check if port 3389 (RDP) is open on the destination

netstat command will only check to see if the ports socket activity (Listening, established, wait, etc)
The commend that you want to use if the port is open from end to end is telnet:

Assuming this port is TCP and not UDP

telnet x.x.x.x 5003

if the port is blocked, you will not be able to connect, if the port is not listening, you should get a connection refused. If the host is on another subnet, you could check the firewalls policies/ACLs.
On the network the host is on (Host that is listening on 5003), check connectivity from another host too:

telnet x.x.x. 5003

Also, from the host that is listening on 5003,

telnet localhost 5003
telnet x.x.x. 5003

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

tmonteitAuthor Commented:
Here's latest, ran commands:
> telnet ServerIP 5003  
> netstat -a
    Lots of stuff here are a few of the lines.

  TCP    457-105-LAB3:netbios-ssn  LISTENING
  TCP    457-105-LAB3:1156  ESTABLISHED
  TCP    457-105-LAB3:1367  ESTABLISHED
  TCP    457-105-LAB3:1577  CLOSE_WAIT
  TCP    457-105-LAB3:1589  TIME_WAIT
Does this tell us anything?  What should I try next to troubleshoot?
tmonteitAuthor Commented:
here's the latest.

W:\>telnet localhost 5003
Connecting To localhost...Could not open connection to the host, on port 5003: C
onnect failed
I'm sitting in front of live audience.  How do I explain whats happening so it doesn't look like my database is down?

>> telnet ServerIP 5003  
where did you try this from
tmonteitAuthor Commented:

Windows IP Configuration

Ethernet adapter Local Area Connection:
        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . :
        Subnet Mask . . . . . . . . . . . :
        Default Gateway . . . . . . . . . :
>telnet localhost 5003
    see above
> W:\>telnet 5003
   black screen hangs
tmonteitAuthor Commented:
The machine I'm on is the IP of the ipconfig command above.
tmonteitAuthor Commented:

telnet 5003 -- Conection Failed
telnet localhost 5003 - hangs
Please help me fill in the blank here.
To my audience:
"The reason you cannot connect to filemaker server is because _______"
"The reason you cannot connect to filemaker server is because _it is not bound to the IP______"

is the service running?
Is the service UDP?

tmonteitAuthor Commented:
Service is running.
Service is Filemaker Pro Server TCP/UDP.
McAffee is also running and I can't turn it off, I'm not admin.
In Filemaker on a user machine which is supposed to access the server:

-Open remote...
-Host: fmnet:/serverIP/fmdbname.fp7

What happens?
Well, if is TCP and you can not connect to port 5003 and you can not disable mcafee (Assuming it has firewall features), then you need to contact the admin to allow the port through.

Rant32Connect With a Mentor Commented:
To find out if the database server is listening on 5003 at all, type:

netstat -an | find ":5003"

Please post the output.

McAfee VSE 8.7 does have Access Protection for outbound traffic, but the default configuration does not restrict this port.
tmonteitAuthor Commented:
Thanks all for this.  You provided enough troubleshooting tips to at least explain the problem.  As this was done in the midst of a live presentation, time was short and our troubleshooting detracted from our demo.  
We concluded that McAffee was blocking 5003 and that no one had permissions to disable McAffee.  We were able to circumvent with another laptop through wireless that wasn't constrained by McAffee.
Points will shortly be awarded to all who helped out.  Again, many thanks!
tmonteitAuthor Commented:
Confused about how the sysytem is trying close this question.  This interaction seems to be a bit different.  Question was answered.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.