Error Connecting to C$: Device Attached to the System is not Functioning

Troubleshooting
Published Apr 16, 2014 Updated Mar 18, 2018

When I tried to connect to the administrative file share C$ on my wife’s computer I got the error A device attached to the system is not functioning.

A device attached to the system is not functioning - 2

The other way round worked without a hitch, i.e. I could access my laptop’s C$ share from my wife’s computer.

When I tried to connect to her computer on the commandline I got this:

d:\>net use \\Computername\C$ /user:Computername\Username *
Type the password for \\Computername\C$:
System error 58 has occurred.

The specified server cannot perform the requested operation.

Different error message, same result.

After fruitlessly poking around some more I finally had the idea to check the target computer’s firewall settings. And indeed, file and printer sharing was disabled:

File and Printer Sharing disabled in Windows firewall

After enabling file and printer sharing for private networks and also disabling UAC remote restrictions (we are in a workgroup environment, not in a domain) things worked as expected.

Administrative Shares Firewall

Comments

Comments are powered by Giscus. Please enable JavaScript to view them, or view discussions directly on GitHub.

Related Posts

Streamed Video Audio Sync Problems on Windows 10 / Realtek Sound

Streamed Video Audio Sync Problems on Windows 10 / Realtek Sound

I have been watching streaming video for a very long time. It always worked beautifully, in high resolutions and from any site: YouTube, Netflix, Amazon Prime Video, you name it. Then suddenly I started to notice lip sync issues, probably around autumn/winter 2016. The longer a video played, the more the audio would get out of sync with the video, making watching and listening increasingly awkward. Recently I finally found the time to analyze these audio/video sync problems. Read on for a playback troubleshooting methodology followed by a workaround for the issue at hand.

Troubleshooting

Solved: Citrix Desktop Service Fails to Start, Logs Event 1006

Solved: Citrix Desktop Service Fails to Start, Logs Event 1006

I am sure you all love XenDesktop VDAs that just won’t register. Although this is becoming less and less of a problem I had another case recently. Checking the Obvious When a XenDesktop VDA is unregistered the first thing I do is check if the VM is actually turned on. With that out of the way I turn to the application event log, looking for entries with the source Citrix Desktop Service. This usually tells you what the problem is. Not this time, however. Apparently the Citrix Desktop Service (aka WorkstationAgent) ran into some error during startup. It logged the following event with ID 1006 and stopped:

Citrix/Terminal Services/Remote Desktop Services

Race Condition - a Troubleshooting Tale

Race Condition - a Troubleshooting Tale

The most obscure effects often have the simplest explanations - once you know where to go looking for them. Luckily uberAgent tells you exactly what is going on. People often ask about the resource footprint of uberAgent. I usually tell them “no IO at all, around 15 MB RAM and below 0.5% CPU” and everybody is happy. Not this time, however.

Troubleshooting

Remote Management of Windows PCs in an Isolated Security Zone

Remote Management of Windows PCs in an Isolated Security Zone

With the advent of BYO it has become fashionable to regard PCs as untrusted devices that should be isolated in a dedicated security zone. Zoning Such an approach has a big advantage: by separating clients from servers it is possible to treat them differently and potentially apply more relaxed security policies - which is a basic requirement for BYO. In a truly BYO-only environment you block everything except Citrix ICA or some other remoting procotol of choice at the firewall and life is good. In real corporate networks things are a bit more complicated, however. Say you want to isolate your managed Windows PCs. In that case you might want to be able to manage them remotely from systems outside the client security zone (e.g. from management terminal servers). And suddenly you have a problem: Windows management protocols, especially RPC and DCOM, are not exactly firewall-friendly.

Latest Posts

Introducing Sambee, Your Browser-Based File Manager for SMB Shares and Local Drives

Introducing Sambee, Your Browser-Based File Manager for SMB Shares and Local Drives

Sambee is a browser-based viewer and manager for files on SMB network shares and on your computer’s local drives. It supports single-pane and dual-pane views and can replace Windows File Explorer as well as Norton Commander-style tools on your PC and on your phone. And yes, it’s free and open source.

WSL Disk Space Cleanup

WSL Disk Space Cleanup

The Windows Subsystem for Linux (WSL) stores its virtual hard disks in the user profile on drive C:. These VHDX files can grow up to 1 TB in size, making it necessary to clean up and reclaim space occasionally. This article shows how.

Virtualization & Containers

Changing the Location of PowerShell Profile Scripts

A PowerShell profile is an init script that is executed when the shell starts. PowerShell searches for profile scripts in hard-coded locations. This article explains how to move profile scripts to any directory of your choice.

Changing the Location of the Windows Terminal Settings Files

Changing the Location of the Windows Terminal Settings Files

Windows Terminal stores its settings in configuration files that resides in the Windows user profile. This article explains how to move them to any directory of your choice. Where are the Settings Files Located? The location of the Windows Terminal settings file is hard-coded. The exact path depends on the app variant you installed, but it’s always in the user profile: