Member_2_79173
asked on
User sees "Contacting the server for information" and a security warning when using Outlook 2016.
One our users is reporting seeing a message in Outlook 2016. I've pasted her message to us below. I have replaced our domain name with xxx for privacy sake.
"For the last week and a half, when navigating in Outlook email I am constantly receiving a MS Outlook message that says, “Contacting the server for information” with a green bar that keeps pulsing. I then have to track down the Security Warning box that says “The current webpage is trying to open a site on your intranet. Do you want to allow this? Current site: https://linkprotect.cusasvc.com Intranet site: http://www.xxx.org” and click Yes in order for the green pulsing bar box to go away so I can access email again.
This is happening when I open current emails in my inbox and also when I try to file emails and open emails from the personal folder archive. It is frequent enough to really slow down my work."
I have also attached screen shots the user sent us. In the "Security warning" screen shot I have changed our actual domain name to "ourdomain.org"
According to info I found on the Internet, linkprotect.cusasvc.com is an email filtering solution from Barracuda but we don't use that solution.
I asked the user to scan her computer with Windows Defender and it came up clean. This computer is a VM in our Hyper-V server and is running Windows 10 Enterprise x64. The user connects to it via Windows RDP client. She has been using this VM for several months and just now reported this issue. Prior to that she has had not problems with this issue.
Thanks,
Don
"For the last week and a half, when navigating in Outlook email I am constantly receiving a MS Outlook message that says, “Contacting the server for information” with a green bar that keeps pulsing. I then have to track down the Security Warning box that says “The current webpage is trying to open a site on your intranet. Do you want to allow this? Current site: https://linkprotect.cusasvc.com Intranet site: http://www.xxx.org” and click Yes in order for the green pulsing bar box to go away so I can access email again.
This is happening when I open current emails in my inbox and also when I try to file emails and open emails from the personal folder archive. It is frequent enough to really slow down my work."
I have also attached screen shots the user sent us. In the "Security warning" screen shot I have changed our actual domain name to "ourdomain.org"
According to info I found on the Internet, linkprotect.cusasvc.com is an email filtering solution from Barracuda but we don't use that solution.
I asked the user to scan her computer with Windows Defender and it came up clean. This computer is a VM in our Hyper-V server and is running Windows 10 Enterprise x64. The user connects to it via Windows RDP client. She has been using this VM for several months and just now reported this issue. Prior to that she has had not problems with this issue.
Thanks,
Don
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It sounds like a certificate problem. Since this is only affecting one user, make sure the date and time is correct on that user's computer. Also make sure that the certificate is issued by an authority that is recognized by that computer.
ASKER
I sent the suggestion about safe mode to the user on Monday and have not heard back. I just pinged her to see if it had any effect.
"Start the user outlook in safe mode and see if you get the same issue. If not, then there maybe a addin causing this, or an d email attempting to access a site once outlook opens, so what ever the default browser is try to clean the cache."
"Start the user outlook in safe mode and see if you get the same issue. If not, then there maybe a addin causing this, or an d email attempting to access a site once outlook opens, so what ever the default browser is try to clean the cache."
Provided solution to question. Closing ticket unless author reopens still having same issue.