Link to home
Start Free TrialLog in
Avatar of tmonteit
tmonteitFlag for Afghanistan

asked on

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?

Thanks!
SOLUTION
Avatar of latchways
latchways

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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

Billy
Avatar of tmonteit

ASKER

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

  TCP    457-105-LAB3:netbios-ssn  457-105-LAB3.schools.sdistrict.org:0  LISTENING
  TCP    457-105-LAB3:1156      tjnt01.schools.sdistrict.org:microsoft-ds  ESTABLISHED
  TCP    457-105-LAB3:1367      fmsserver.fmsuser.sdistrict.org:3389  ESTABLISHED
  TCP    457-105-LAB3:1577      www49.filemaker.com:https  CLOSE_WAIT
  TCP    457-105-LAB3:1589      ldsk04.fmsuser.sdistrict.org:http  TIME_WAIT
Does this tell us anything?  What should I try next to troubleshoot?
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

>ipconfig
Windows IP Configuration

Ethernet adapter Local Area Connection:
        Connection-specific DNS Suffix  . : sdistrict.org
        IP Address. . . . . . . . . . . . : 10.193.66.107
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.193.66.11
>telnet localhost 5003
    see above
> W:\>telnet 164.92.2.52 5003
   black screen hangs
The machine I'm on is the IP of the ipconfig command above.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial

telnet 164.92.2.52 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?

Billy
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.

Billy
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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!
 
 
Confused about how the sysytem is trying close this question.  This interaction seems to be a bit different.  Question was answered.