error diagnostic test local connect

Use this forum if you have installed hMailServer and want to ask a question related to a production release of hMailServer. Before posting, please read the troubleshooting guide. A large part of all reported issues are already described in detail here.
Post Reply
robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

error diagnostic test local connect

Post by robertog » 2020-06-22 19:14

Hello,
I hope someone can help me really I don't know where it's the issue.
With diagnostic always I receive error message where it isn't possible connect to my ip public on port 25.

I opened port on firewall and as well I created rules in windows firewall.
Testing port 25 and is opened.

what else I can check ?
thank you for your advise

Virinum
Normal user
Normal user
Posts: 105
Joined: 2018-11-23 14:42
Location: Germany

Re: error diagnostic test local connect

Post by Virinum » 2020-06-22 22:38

Maybe your ISP is blocking port 25?

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-23 10:12

Hi Virinum,
thank you for your advise, and really strange...It's true! My Isp blocked port 25.
So I created rule on my firewall to forward request from 587 to mail server port 25.
Unfortunately still I have issue...

Virinum
Normal user
Normal user
Posts: 105
Joined: 2018-11-23 14:42
Location: Germany

Re: error diagnostic test local connect

Post by Virinum » 2020-06-23 10:23

robertog wrote:
2020-06-23 10:12
So I created rule on my firewall to forward request from 587 to mail server port 25.
Unfortunately still I have issue...
That won't help. You can't change the incoming port because the whole world uses port 25 for mailserver to mailserver communication.

So your ISP is just blocking incoming requests or also outgoing requests on port 25? Maybe you could share a screenshot of the test result?

You could try and ask your ISP to unblock this port for you. Some ISPs block by default but unblock on request.

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-23 11:17

thank you for your swift reply, port 25 incoming is ok so just blocked for outgoing.
I will try to ask to ISP if they can open the port and I let you know.

Bye and thank you again

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-24 11:02

Hello,
I sortie out! with smtp relayer and port 587 my port 25 was blocked.
Now I have another issue...in office I receive error using outlook but outside from my local network works fine!

I hope to find the problem.

Virinum
Normal user
Normal user
Posts: 105
Joined: 2018-11-23 14:42
Location: Germany

Re: error diagnostic test local connect

Post by Virinum » 2020-06-24 12:16

Does your router support NAT-loopback?
Does it work when you use the interal IP address in Outlook to connect to your mail server?

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-24 12:35

Hello,
thank you for your answer,
I'm using firewall and support NAT-loopback.
my email server is another subnet... 192.168.200.0/24
my client is on 192.168.69.0/24

if I try to setup in outlook ip server 192.168.200.x receive error message

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-24 16:58

I created ip range for 192.168.69.1-192.168.69.254

User avatar
jim.bus
Senior user
Senior user
Posts: 403
Joined: 2011-05-28 11:49
Location: US

Re: error diagnostic test local connect

Post by jim.bus » 2020-06-24 22:31

Outlook errors can be vague but you might want to say what Outlook is saying the error is. Right now everybody is just guessing as to what the error is.

User avatar
johang
Senior user
Senior user
Posts: 285
Joined: 2008-09-01 09:20

Re: error diagnostic test local connect

Post by johang » 2020-06-25 06:28

robertog wrote:
2020-06-24 12:35
Hello,
thank you for your answer,
I'm using firewall and support NAT-loopback.
my email server is another subnet... 192.168.200.0/24
my client is on 192.168.69.0/24

if I try to setup in outlook ip server 192.168.200.x receive error message

NAT-loopback .. have you configured that firewall to accept traffic via hairpinning ? ( port 143 and 110 and 25 and 587 .. and what not..)

IF you have 2 subnets with private ipadresses and want to send traffic between them .. have you configured your firewall to route and accept that traffic pattern ?
jim.bus wrote:
2020-06-24 22:31
Outlook errors can be vague but you might want to say what Outlook is saying the error is. Right now everybody is just guessing as to what the error is.
its a guessing game .. guess the error .. :D :D :D

im guessing it says .... wrong password ..no.. no.. wait, wrong username.. no.. no wait i change my mind i guess wrong password.. yes now i have settled for .. WRONG PASSWORD ... answer is: use the right password .. sweet, that was an easy problem to solve..
___________________________________________________________end of the line
spam filter appliance gateway: www.mailcleaner.org

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-25 09:22

Hello!
thank you for your reply...I would like to say it was simply password wrong but it isn't in this case unfortunately...
error in outlook

Task 'Synchronizing subscribed folders for "my email" reported error (0x800CCC0E) : 'Outlook cannot synchronize subscribed folders for "my email" Error: Cannot connect to the server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'

ports 110,25,143,587 opened.

traffic between subnet are allowed, I tried too to connect pc with one ip in the same subnet server (192.168.200.x)

ip range created for 192.168.200.0 192.168.200.254 priority 25
.............................192.168.69.0 192.168.69.254.............25

User avatar
jim.bus
Senior user
Senior user
Posts: 403
Joined: 2011-05-28 11:49
Location: US

Re: error diagnostic test local connect

Post by jim.bus » 2020-06-25 11:11

I am having to assume what your network configuration looks like and therefore, the below may not be accurate for your configuration. But I do something similar in my system and I have no problems except I do not use IMAP. Only POP3 and SMTP. I, also, assume since you say when you try to connect to hMailServer in your Office from a Client computer from outside your Office Local Network that this is successful that means you have IMAP and SMTP service checked in hMailServer Options.

I use Outlook to access hMailServer.

I, also, have two separate Local Networks each using a different IP Address Pool from the other.
Example: Local Network A has IP Address Pool 192.168.1.1 to 192.168.1.254.
Local Network B has IP Address Pool 192.168.2.1 to 192.168.2.254.

My hMailServer is in Local Network A and Outlook A also is in Local Network A and connects to hMailServer in Local Network A.

I have another computer in Local Network B which uses Outlook B connect to hMailServer in Local Network A.

I have no problem with this configuration. I am only familiar with a Router which only allows one IPv4 Address Pool per Router (or Local Network in this example) excluding the Router's VPN Server. I use a Consumer Grade Router.

Each Local Network has a Hostname assigned to its External Public IP Address.
Local Network A: Hostname A.
Local Network B: Hostname B.

In Outlook in both Local Networks A and B, for the Incoming and Outgoing Mail Server names are the same Hostnnames where in this example the Hostnames would be Hostname A for Outlook a in Local Network A and Hostname A for Outlook B in Local Network B.

I suspect your problem is that despite what you've said, Outlook cannot locate your hMailServer Local Network IP Address because it is in a different IP Address Subnet. In my case the Hostnames are External Public IP Addresses. I, also, have NAT Loopback. By using the Hostname in the Outlook configuration I do not have to worry about possible changing IP Addresses for any other Outlook Client whether it be in my Local Networks or an outside Local Network. Therefore, my Outlook configuration is the same no matter where it is used. It would be possible to substitute for the Hostname the actual External Public IP Address but Hostname is easier to use. Also, unless you have need to limit what IP Addresses can connect to hMailServer, this configuration allows you to just use the hMailServer supplied Default Internet IP Range.

You seem to be trying to use a Local Network IP Address for your hMailServer Server computer whereas I use the External Public IP Address and the Router Port Forward to the hMailServer computer.

I don't believe this is the issue but when you installed hMailServer on your Server IP Address Pool did you make sure your Server Computer's IP Address was fixed. If you did not fix the IP Address it could possibly change though usually they don't in my experience. But if it did change then Outlook will not be able to find it using a hard coded Local IP Address as oppose to using the Hostname. Likewise your Router's Port Forwarding will not be able to find the hMailServer computer either.

I don't believe this is related to your problem but I would suggest you also open Port 995 for a POP3 SSL/TLS connection. Port 110 is the standard POP3 Unencrypted Port whereas Port 995 is the Standard POP3 Encrypted Port. Likewise I would suggest you use Port 993 for IMAP connections as this is the Standard IMAP Encrypted Port as well. But again I do not believe these Port designations are your problem. Its just good practice to use Encrypted Connections.

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-25 13:20

WOW Thank you so much! Jim,
for your advise and suggestion...really I appreciate a lot!!, I have to say now something new...
if I setup outlook with server ip address internal (192.168.200.x) outlook works fine!!!
but if I configure with nameserver (ip public) doesn't work again. :(

My outlook outside lan works!
Something with dns maybe? or what else can be... I 'm getting crazy...

thank you again

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-25 13:39

FINALLY WORKS!!!!
I setup dns mx in my firewall with my domain and ip address public.
I can send and receive email!!!! :)

Thank so much to everybody in particular to Jim Johang and Virinum

User avatar
jim.bus
Senior user
Senior user
Posts: 403
Joined: 2011-05-28 11:49
Location: US

Re: error diagnostic test local connect

Post by jim.bus » 2020-06-25 14:23

robertog wrote:
2020-06-25 13:39
FINALLY WORKS!!!!
I setup dns mx in my firewall with my domain and ip address public.
I can send and receive email!!!! :)

Thank so much to everybody in particular to Jim Johang and Virinum
I still stress to not use your Local (LAN) IP Address in your Outlook Server Name Entries. You should be using the External Server Hostname. But if I understand what you said in your last post you would have to be using the Hostname because a MX record cannot be using a Hard Coded IP Address. MX Records require a Hostname.

Also Outlook doesn't use MX Record Entries. It uses either the Server Hostname entry (from DNS) or the Hard Coded IP Address.

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-25 14:34

in outlook I'm using name server mail (external hostname)

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-26 18:40

just the last issue...not serious...
if configure outlook with mail server (public domain mx) I can't complete setup outlook.
if configure................................with private ip address server (192.168.69.x) outlook is fine.
I found workaround...after outlook is configured with private ip I changed setting and I wrote public domain.
Works!!

Something maybe is wrong...but I don't understand what....
Thank you for your help..

robertog
New user
New user
Posts: 15
Joined: 2020-06-22 18:58

Re: error diagnostic test local connect

Post by robertog » 2020-06-26 19:27

SORRY!!! fixed I created rule on firewall to forward from ip address public to my ip server email

Post Reply