Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

FIXED: ADMIN$ and IPC$ share not found

I've been beating my head a bit on this issue. I can't connect to a Windows 7 workstation using my Domain Admin credentials. Running the Remote Repair tool locally showed no issues. Running it remotely showed that Admin$ and IPC$ were not able to be found (but it could complete the other two tests).

After some digging, I found some help from the eSET forums, and adapted. They suggested to make sure the "File and Printer Sharing" was enabled on the Network Adapter. I look, and it wasn't! So I added it. Still no go. I went to my PC, and opened the Network Adapter, and added in 3 others, so the list was complete:

Client for Microsoft Networks (Client)
QoS Packet Scheduler (Service)
File and Printer Sharing for Microsoft Networks (Service)
IP v6 (Protocol)
IP v4 (Protocol)
Link-Layer Topology Discovery Mapper I/O Driver (Protocol)
Link-Layer Topology Discovery Responder (Protocol)

If any of these are missing, I clicked the Install button, then either Client, Service or Protocol, and added them. I then rebooted the workstation, and I can deploy to it, and Remote Repair states it's working!

Suggestion to the team - add a check for whatever protocols or services or clients are absolutely required to deploy, and run the check locally.

0

Comments

0 comments