Exchange 2013 refusing some SMTP connections but allowing others using anonymous receive connector

I have a single Exchange 2013 server, running for 6 months. We have several servers/devices that anonymously relay through it which are working fine. I attach screenshots of the FrontendTransport connector settings showing my PC 192.168.2.44 in the list of allowed IPs.
FrontEnd Receive Connector Properties (FQDN Erased)FrontEnd Receive Connector Properties (FQDN Erased)FrontEnd Receive Connector Properties (FQDN Erased)
I've tried to Telnet to it on port 25 but get refused.
    Microsoft Telnet> open 192.168.1.41 25
    Connecting To 192.168.1.41...Could not open connection to the host, on port 25: Connect failed
    Microsoft Telnet>

I've added two new IP addresses to the list of IPs in the receive connector but these two devices are being denied connection. The others are all still working fine.

    220 mail1.bywaters.co.uk Microsoft ESMTP MAIL Service ready at Tue, 2 Feb 2016 1
    2:03:39 +0000

The Application log doesn't show me anything, the SMTPReceive Protocol logs do not contain the source IP address of the failed connection., Windows firewall is disabled on the Exchange server. I have restarted the Exchange server with no effect.

Can anyone suggest how to proceed with fault finding? Or if you've solved a similar problem?
Hayden WellsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gilbert HauserConsultant informatiqueCommented:
Hi,
Could you give more informations concerning your network topology?

You are using different network, from the range 192.168.2.0/24 what kind of router are you using to reach the 192.168.1.0/24
Hayden WellsAuthor Commented:
Thank you for your quick response.

There is no router between the clients and the server, I'm using a 22 bit SM on a single LAN.

My subnet includes 192.168.1.0-192.168.3.254 using SM:255.255.252.0
Gilbert HauserConsultant informatiqueCommented:
I think you have already check if:

your computer is authorized to use the port 25
tracert the server
telnet the server on port 443

I suggest to run wireshark to capture the packet on port 25, the test a new telnet serveur 25

Even if it is not in the scop, it is strange to see your public serveur in your LAN, no DMZ?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DLeaverCommented:
I recommend this tool to give you a more specific output than telnet - https://www.microsoft.com/en-gb/download/details.aspx?id=17148

Run it from your PC to Exchange, the command line version is excellent.
Hayden WellsAuthor Commented:
Solved thanks to Gilbert.

The important part of your post was "your computer is authorized to use the port 25".

This made me look at the client which, although Windows Firewall is disabled, was being prevented from sending SMTP due to McAfee AV. Disabling the "Prevent mass mailing worms from sending mail" solved the issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.