Question Outlook emails not sending on Hardwired connection?

Nov 19, 2019
2
0
10
We can send the emails with attachments with no issues on WiFi but when using a hardwired connection we have the error 0x800CCC0F. We have tried putting the end user on a different switch but the error still occurs. We have tried the following:

1. Check for Internet Connections
2.Disable MS Windows Firewall. You can follow the steps given below to disable the firewall.
-Go to Control Panel, then Network Connections
-Right click on Internet connections
-Click on Properties on the Menu
-Click on Security and disable the firewall
3. Check for Outlook Profile settings: Check for Outlook Profile settings and correct them.
4- Try removing the emails from Outlook that you feel are suspicious.
5- Also try opening Outlook in Safe Mode. This can also resolve the issue.
6- If you are sure that the error is caused by corrupt or damaged file, then try using the inbuilt Inbox Repair Tool. This way you can repair the minor corruption issues in file.

However, the issue persists. Anyone have any other suggestions as to why it works when using WiFi but not on a Hardwired connection?
 
Need more info about the setup, is the WiFi open or secured on the domain like the ethernet? This the only person with the issue? Has it always happened for them? If not, did you try to restore the system with a restore point or checked on what was done before the issue started? Try another computer for this person or test with another user account on their computer? Try to re-create the user account or email profile? Lots of things to try.
 
Need more info about the setup, is the WiFi open or secured on the domain like the ethernet? This the only person with the issue? Has it always happened for them? If not, did you try to restore the system with a restore point or checked on what was done before the issue started? Try another computer for this person or test with another user account on their computer? Try to re-create the user account or email profile? Lots of things to try.

We do not operate off of a domain server. All end users are local accounts. However, we have noticed the users having the issue is operating off of OS version 1903 and the others who do not have the issue have OS version 1809. We are going to try and roll back the update and see if this fixes the issue.