[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1058
  • Last Modified:

Firewall off, Same Subnet (NO hardware Firewall), Why is Telnet saying "Connection Refused" when I try to connect on a certain port?

This is a strange one. I'm trying to communicate between 2 Mac Pro-s, on the same subnet (so NO hardware firewall is between them), software Firewall turned off on both machines. Both are running Lion 10.7.4 (one is Lion Server). So, I'm using a FileMaker plug-in that needs to communicate between the 2 machines using port 51769 and the support folks for this plug-in tells us that if we can telnet between the machines using port 51769, the plug-in will work. Well, I can telnet between the machines fine, I can even telnet each machine locally (127.0.0.1), but, when I try to telnet between the machines using port 51769, I get connection refused (same deal when telnet locally each machine 127.0.0.1). What could be blocking this port? No Firewalls anywhere. Is the port blocked on the Ethernet adapter somehow? Is there a Terminal command I need to execute for the Ethernet adapter to allow traffic to pass through this port? Why is telnet refusing this connection? So Weird!! Let me know if anyone has ever run across this problem. I will put the specs of both machines below.  Thanks!!

 
  Model Name: Mac Pro
  Model Identifier: MacPro1,1
  Processor Name: Dual-Core Intel Xeon
  Processor Speed: 3 GHz
  Number Of Processors: 2
  Total Number Of Cores: 4
  L2 Cache (per processor): 4 MB
  Memory: 5 GB
  Bus Speed: 1.33 GHz
  Boot ROM Version: MP11.005D.B00
  SMC Version (system): 1.7f10
0
Matthew Wolfe
Asked:
Matthew Wolfe
  • 3
  • 3
1 Solution
 
Will LovingPresidentCommented:
I'm wondering about the router/switch that the two machines are connected to... Have you tried connecting the two machines directly with a single ethernet cable? It might require a crossover ethernet cable or a simple switch or hub in-between if you don't have a crossover cable (though the ethernet ports may be smart enough to make the connection even without a crossover cable).  If that works then the issue is with the router or switch between the machines.
0
 
Matthew WolfeAuthor Commented:
oooooohhhhhhh, didn't think about the switches! Wondering now if there would be an issue if multi-cast is enabled or disabled on the switch.

I do have a crossover cable, going to give that a try.   Thanks!
0
 
Feroz AhmedSenior Network EngineerCommented:
Hi,

This is something which looks wiered for you as you are not aware of HDD connections there is nothing wiered as both machines are similar the cablin ghsould be cross cabling and whereas when you connect from 2 dissimilar devices you have straigih cabling ,but here in this scenario as both are similar devices the cabling should be cross cabling and not staright cabling and the climping sequence should be accordingly .The climping sequence between 2 similar and dissimlar devices is totally different due to which you are unable to communicate between to similar devices without any hardware firewall or router .check your cabling and it should be cross cabling in case of 2 similar devices and straight cabling in case of 2 dissimilar devices fo communication to take place between devices.which is a part of hardware .
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Will LovingPresidentCommented:
sm_feroz - some devices, including most current routers and switches as well as the ethernet connections on some computers, are able to auto-detect when similar devices are connected and allow the connection without a cross-over cable. I couldn't remember if the ethernet port on a Mac Pro has this feature which is why I said that a cross-over cable was probably necessary but might not be if Mac Pros had the auto-negotiate feature.
0
 
Matthew WolfeAuthor Commented:
Thanks Guys!!  Ok, tied them together with a cross-over, was able to telnet each other fine, but still the same results when you telnet port 51769, connection refused. Weird!! I was hoping it was the switch, but looks like it's not. I'm still researching.... I will post if I find anything
0
 
Will LovingPresidentCommented:
OK, here are a few more ideas to try.

1) can  you telnet using a different port, such as FileMaker's default networking port 5003? Try both standard ports and random ones to see if some are blocked and others not

2) is telnet connection blocked in both directions, meaning initiated from either side?

3) Look into OS X Server as the possible culprit. Server software in general has higher security needs and more tightly set default settings. OS X Server may be blocking most ports by default. I don't know OS X Server well enough to tell you where to look but the problem is obviously in the configuration of one or both computers and I would start by looking at the server.
0
 
Matthew WolfeAuthor Commented:
Thanks! Turned out to be none of this actually. Was a java problem with the plug-in
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now