Solved

Mapped drives and remote desktop erratic

Posted on 2013-02-05
6
664 Views
Last Modified: 2013-02-11
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
Comment
Question by:bobox00
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
6 Comments
 
LVL 10

Expert Comment

by:tmoore1962
ID: 38856446
Sounds like a firewall configuration issue, try turning of the firewall on the workstation and see if problem persists.
0
 

Author Comment

by:bobox00
ID: 38856484
I turned off the firewall. Didn't resolve the issue.
0
 

Author Comment

by:bobox00
ID: 38856620
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
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 

Author Comment

by:bobox00
ID: 38856649
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
 

Accepted Solution

by:
bobox00 earned 0 total points
ID: 38857694
My DNS server service stopped on the DC. I just started it, and everything looks fine. Will report back later.
0
 

Author Closing Comment

by:bobox00
ID: 38875491
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

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Resolve DNS query failed errors for Exchange
An article on effective troubleshooting
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

690 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question