• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 670
  • Last Modified:

Mapped drives and remote desktop erratic

For the past 3 days, users on my network have complained about not being able to access mapped drives (red X shows on mapped drive) and also remote desktop to network computers would sometime not work. When the clients try to browse to a network share, such as \\servername they get the following error message:

The system has detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.

Sometimes, I also get the following message:
Windows needs your current credentials to ensure network connectivity. Please lock this computer, then unlock it using your most recent password or smart card. To lock your computer, press CTRL-ALT-DEL and then press Enter.

Furthermore, I get error messages like the ones seen in the attached image.
Remote-desktop-err1.jpg
0
bobox00
Asked:
bobox00
  • 5
1 Solution
 
tmoore1962Commented:
Sounds like a firewall configuration issue, try turning of the firewall on the workstation and see if problem persists.
0
 
bobox00Author Commented:
I turned off the firewall. Didn't resolve the issue.
0
 
bobox00Author Commented:
My DFS shared folders are especially taking a hit. They are not working on most computers and I've had to map network drives individually.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
bobox00Author Commented:
I recently changed the network card that our domain controller uses. The DC is also our DNS server for the LAN. The former network card was causing the server to hang after bootup. Configured the server IP address on a different network card that's already in the server, and disabled the old network card. I don't know if that's the cause. However, I have added 8.8.8.8 as the secondary DNS on the domain controller (the DC's IP address is there as primary DNS). Just removed the 8.8.8.8 from the server and left only the DC's IP address, under DNS. Haven't noticed the differemnce yet. Maybe I'll need to have someone restart their computer, so I can check.
0
 
bobox00Author Commented:
My DNS server service stopped on the DC. I just started it, and everything looks fine. Will report back later.
0
 
bobox00Author Commented:
Starting the DNS service on the domain controller resolved the craziness. I sure should have looked there first. Thanks for your comments.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now