Imagine the scenario: the company’s emails work perfectly at home, on your mobile phone with mobile data, on any public Wi-Fi network, but as soon as you enter the office or business premises and connect to the local network, the own domain mailbox simply won’t load. Gmail works, websites open, everything seems normal, but the company domain emails are inaccessible. This problem, although confusing, has well identified causes and a solution, as long as you know where to look.
This type of failure affects businesses of all sizes that use email hosting with their own domain, in the format name@company.pt. The error is often attributed to the email server or the hosting provider, when in reality the source is almost always within the company’s own local network. In this article we explain the most common causes, the correct diagnostic process and what to expect from a professional technical intervention.
Why does the problem occur only on the company network?
The key to understanding this problem lies precisely in this selectivity: if emails work with any other connection, the failure isn’t in the email server or in the email client settings. It’s in the local network.
The most frequent causes include:
- Email ports blocked on the router or firewall: Email servers communicate through specific ports, such as 25 and 465 for sending (SMTP) and 993 and 995 for secure receiving (IMAP/POP3 with SSL). Many business-grade routers have firewall rules that block these ports by default or after firmware updates.
- Internal DNS conflict: The router may be resolving the domain to a wrong internal IP address, creating a loop or pointing to a non-existent server within the local network.
- Internet provider restrictions: Some operators block port 25 to prevent spam originating from their networks, which prevents direct email sending.
- Misconfigured network devices: Repeaters, switches or powerline adapters with incorrect settings can isolate certain devices or services.
How to diagnose the problem step by step
A correct diagnosis saves time and avoids unnecessary interventions. The process should follow a logical order, from the simplest to the most complex.
1. Confirm the selective behaviour
The first step is to check whether the problem occurs only on the local network. Test email access using mobile data on your phone, using the same device that shows the error. If it works with mobile data and doesn’t work with the company Wi-Fi, the source is the local network.
2. Check the DNS resolution
Confirm that the router is correctly resolving the email server’s domain. Tools such as nslookup or ping from a computer on the local network allow you to check whether the returned IP address is correct. If the DNS resolves correctly but the connection fails, the problem is in the ports.
3. Test connectivity on the email ports
Tools such as telnet or online port-checking utilities allow you to confirm whether ports 25, 465, 993 and 995 are accessible from the local network. If the test fails on these ports but works with others, the router firewall is the main suspect.
4. Review the router’s firewall rules
Access the router settings and check if there are rules blocking outbound traffic on the email ports. In many cases, simply adding an exception rule solves the problem immediately.
When the problem lies with the internet provider
There are situations where all the internal settings are correct, DNS resolves properly, the firewall isn’t blocking anything, and yet the connection to the email server still fails. In these cases, the problem may lie with the internet provider.
Some operators block port 25 on business connections to prevent mass spam sending. This practice is common and, when it happens, you need to contact the operator to request the port be opened or use an alternative port, such as 587 (SMTP with STARTTLS), which many email servers also support.
In these cases, the operator opens a support ticket for the engineering team, which may involve a resolution time of a few business days. It’s important to keep a record of all communication and obtain a ticket reference number to track the process.
While waiting for resolution, consider configuring your email clients to use the alternative ports supported by your email server, or temporarily access webmail through the browser, which is usually not affected by these port restrictions.
Best practices to avoid this problem in the future
After resolving the immediate situation, it’s worth implementing some preventive measures to avoid recurrence:
- Document the network settings: Keep a record of firewall rules, DNS settings and ports used by the company’s services. In case of a future failure, this document greatly speeds up the diagnosis.
- Periodically review the router settings: Firmware updates can reset settings to factory defaults. After any update, check whether critical services remain accessible.
- Check and reconfigure auxiliary network devices: Repeaters and powerline adapters should be checked regularly to ensure they are synchronised and operating within the correct parameters.
- Use service monitoring: Simple monitoring tools can alert you when a service becomes inaccessible, allowing you to respond before the problem affects business operations.
- Have a contingency plan for email: In case of a failure of your own domain email, having an alternative account configured allows you to keep communication uninterrupted while the problem is resolved.
Frequently Asked Questions
Why do emails work with mobile data but not on the company’s Wi-Fi network?
This behaviour is a clear sign that the problem lies in the company’s local network and not in the email server or the email client. The most common causes are firewall rules on the router that block the email ports (25, 465, 993, 995), an internal DNS issue preventing correct domain resolution, or even an IP addressing conflict within the network. The solution involves reviewing the router and firewall settings with a specialised technician.
What are ports 25, 465, 993 and 995 and why are they important for email?
These ports are the channels through which email traffic flows. Ports 25 and 465 are used for sending messages (SMTP protocol), while 993 (IMAP with SSL) and 995 (POP3 with SSL) are used for receiving emails securely. If the router or firewall blocks any of these ports, the connection to the email server fails, even if the DNS is resolving the address correctly. Many companies have these ports blocked by default in their security settings, which causes exactly this type of problem.
Can a powerline or network repeater cause email access problems?
Yes, although indirectly. Misconfigured powerline devices or network repeaters can create isolated network segments, generate IP addressing conflicts or introduce latency and instability in the connection. If a computer is connected through a powerline that isn’t properly synchronised with the main router, it may have limited access to certain services, including email servers on specific ports. It’s always recommended to check and reconfigure these devices when selective connectivity issues arise.
Need help? Contact MEGABIT at comercial@megabit.pton-site support in Baixa do Porto and the entire Northern Portugal region.
Want to be notified when we publish our next article or video?
Free. Get notified as soon as we publish. No spam, easy to unsubscribe.


