Specifying your ports is something some beginners mess up. Usually the host machine listens on a specific port of a specific interface. The client machine attempts to connect with a specified outbound IP+port pair, but usually leaves its own side blank, allowing the system to connect on any open interface and any open port that it thinks best. The combined tuple { SrcIP, SrcPort, DestIP, DestPort } needs to be unique so it is usually a bad idea to specify all four when you are establishing a connection. Specify only one pair of IP/Port and allow the system to figure out the other two.
As for the firewall possibility:
If both machines are inside your own local network, you can connect directly by their LAN IP address. Often this is 192.168.0.x, but can be other values. This corresponds with a netmask of 255.255.255.0, which means anything on the last byte is assumed to be directly connected. Double-check the IP addresses and netmasks of the machines if you need to. If both machine's addresses are in the same range within the netmask, and your machines are otherwise able to see each other, and it still isn't connecting, then yes it might be firewalls or antivirus tools on either machine. This can sometimes be tiresome to figure out. You can troubleshoot by disconnecting your NAT from your ISP to reduce infection risk, then turn off all the firewalls and AV tools, and connect again.
If both machines are inside your own local network and you are trying to connect using an external IP address, that is generally not going to work. For example, connecting from a local machine to a public IP address, which is actually the IP address of your home's connection, pointing back in to your network and being port forwarded to a machine, it probably won't work. This is called a "hairpin route", since just like a physical hairpin it loops back on itself from inside the NAT to outside the NAT to right back inside the NAT. Few consumer devices support this.