Jump to content

Unable to Map Network Drive / Cannot Access Error

Los_Jackal
By Los_Jackal
in Windows
 Share
Posted

I'm trying to map a network drive and having no luck as I keep getting hit with a "You do not have permission to access" error despite being logged into both PC as an Admin with the same Windows account, both connected via ethernet and having the same network advanced sharing settings. I've given full permissions to all groups/users, restarted both systems and still get the same error. 

 

Can anyone identify what I'm doing wrong exactly here? I was able to map a network drive before but never ran into this problem. 

TV PC Screen 1.png

TV PC Screen 2.png

TV PC Screen 3.png

TV PC Screen 4.png

Error.png

Link to post
Share on other sites
Posted
6 minutes ago, Los_Jackal said:

Error.png

Use \\[IP address]\Share Drive\ instead of \\TV-PC\Share Drive\.

 

Sometimes the local domain names don't get registered properly with your gateway, so IPs are the foolproof method.

Main System (Byarlant): Ryzen 9 5950X | Asus B550-Creator ProArt | EK 240mm Basic AIO | 32GB G.Skill DDR4 3600MT/s CL16 | XFX Speedster SWFT 210 RX 6600 | Samsung 990 PRO 2TB / Samsung 990 EVO Plus 4TB | Corsair RM750X | StarTech 4× USB 3.0 Card | Realtek RTL8127 10G NIC | Hyte Y60 Case | Dell U3415W Monitor | Keychron K12 Blue (RGB backlight)

 

Laptop (Narrative): Lenovo Flex 5 81X20005US | Ryzen 5 4500U | 16GB DDR4 3200MT/s (soldered) | Vega II 384SP Graphics | SKHynix P31 1TB NVMe SSD | Intel AX200 Wifi | Asus 2.5G USB NIC | Asus ProArt PA278QV | Keychron K4 Brown (white backlight)

 

Proxmox Server (Veda): Ryzen 7 3800XT | ASRock Rack X470D4U | Corsair H80i v2 | 128GB Micron DDR4 ECC 3200MT/s | 2× Samsung PM963a 960GB SSD / 4× WD 10TB / 4× Seagate 14TB Exos / 4× Micron MX500 2TB / 8× WD 12TB (custom external SAS enclosure) | Seasonic Prime Fanless 500W | Intel X550-T2 10G NIC | LSI 9300-8i HBA | Adaptec 82885T SAS Expander | Fractal Design Node 804 Case

 

Proxmox Server (La Vie en Rose): GMKtec Mini PC | Ryzen 7 5700U | 32GB Lexar DDR4 (SODIMM) | Vega II 512SP Graphics | Lexar 1TB 610 Pro SSD | 2× Realtek 8125 2.5G NICs


Media Center/Video Capture (Jesta Cannon): Ryzen 5 1600X | ASRock B450M Pro4 R2.0 | Noctua NH-L12S | 16GB Crucial DDR4 3200MT/s | EVGA GTX750Ti SC | UMIS NVMe SSD 256GB / TEAMGROUP MS30 1TB | Corsair CX450M | Viewcast Osprey 260e Video Capture | TrendNet (AQC107) 10G NIC | LG WH14NS40 BD-ROM | Silverstone Sugo SG-11 Case | Sony XR65A80K

 

Workbench (Doven Wolf): Lenovo m715q | Ryzen Pro 3 2200GE | 16GB Crucial DDR4 3200MT/s (SODIMM) | Vega 8 Graphics | SKHynix (OEM) 256GB NVMe SSD | uni 2.5G USB NIC | HDMI add-in module

 

Network:

Spoiler 
                       ┌─────────────── Office/Rack ───────────────────────────────────────────────┐
Google Fiber Webpass ── Cloud Gateway Max ══╦═ Pro XG 8 ══╦═ Flex 2.5-8 ══╦═ Doven Wolf
                      La Vie en Rose (DNS) ═╬═ Narrative  ╠═ Veda-NAS     ╠═ La Vie en Rose (vmbr)
                                Veda (DNS) ─┘             ╠═ Veda (vmbr)  ├─ Ptolemy (vmbr)
╔═════════════════════════════════════════════════════════╩═ Ptolemy-NAS  ├─ Veda (Mgmt)
║   ┌ Closet ┐      ┌───────── Bedroom ─────────┐                         └─ Veda (IPMI)
╚═══ Flex XG ══╦╤═══ Flex XG ══╤╦═ Byarlant
       (PoE)   ║│              │╠═ Narrative 
Kitchen Jack ══╣└─ Dual PoE ┐  │╚═ Jesta Cannon*
   (Testing)   ║┌─ Injector ┘  └── Work Laptop
     Bedroom ══╝│        ┌─────── Media Center ────────────────────────────┐
     Jack #2    └──────── Switch 8 ────────────┬─ nanoHD Access Point (PoE)
Notes:                                         ├─ Sony PlayStation 4 
─── is Gigabit / ═══ is Multi-Gigabit          ├─ Pioneer VSX-S520
* = cable passed from Bedroom to Media Center  └─ Sony XR65A80K (Google TV)
Link to post
Share on other sites
Posted
On 4/23/2024 at 6:10 PM, AbydosOne said:

Use \\[IP address]\Share Drive\ instead of \\TV-PC\Share Drive\.

 

Sometimes the local domain names don't get registered properly with your gateway, so IPs are the foolproof method.

@Los_Jackal just an FYI, if you do this and the link stops working in the future, it's likely because the IP address for your desktop had expired and DHCP from your router provided a different IP address instead of renewing the old one. 

 

One way to combat this is to set the IP for your desktop to a static IP, that way the address for the desktop will always remain the same even if the entire network gets rebooted due to a power outage or whatever. The same can be done to share a local printer, effectively making it a network printer.  

Intel® Core™ i7-12700 | GIGABYTE B660 AORUS MASTER DDR4 | Gigabyte Radeon™ RX 6650 XT Gaming OC | 32GB Corsair Vengeance® RGB Pro SL DDR4 | Samsung 990 Pro 1TB | WD Green 1.5TB | Windows 11 Pro | NZXT H510 Flow White
Sony MDR-V250 | GNT-500 | Logitech G610 Orion Brown | Logitech G402 | Samsung C27JG5 | ASUS ProArt PA238QR
iPhone 12 Mini (iOS 18.3) | iPhone 15 (iOS 18.3.1) | KZ AZ09 Pro x KZ ZSN Pro X | Sennheiser HD450bt
Intel® Core™ i7-1265U | Kioxia KBG50ZNV512G | 16GB DDR4 | Windows 11 Enterprise | HP EliteBook 650 G9
Intel® Core™ i5-8520U | WD Blue M.2 250GB | 1TB Seagate FireCuda | 16GB DDR4 | Windows 11 Home | ASUS Vivobook 15 
Intel® Core™ i7-3520M | GT 630M | 16 GB Corsair Vengeance® DDR3 | Samsung 850 EVO 250GB | macOS Catalina | Lenovo IdeaPad P580

Link to post
Share on other sites
Posted
  • Author
2 hours ago, AbydosOne said:

Use \\[IP address]\Share Drive\ instead of \\TV-PC\Share Drive\.

 

Sometimes the local domain names don't get registered properly with your gateway, so IPs are the foolproof method.

Tried using the \\[IP address]\Share Drive\ format in both Map Network Drive and Add Network Location and still get the same error unfortunately. Same message as before but with the IP address network path. The folder appears in This PC under Network Locations but when I open it I get hit with that error. 

Link to post
Share on other sites
Posted
5 hours ago, Los_Jackal said:

Tried using the \\[IP address]\Share Drive\ format in both Map Network Drive and Add Network Location and still get the same error unfortunately. Same message as before but with the IP address network path. The folder appears in This PC under Network Locations but when I open it I get hit with that error. 

Have you checked in advanced sharing and on button permissions?

 

Have you tried to add that account like PCNAME\NAME to your share permissions?

 

Try make new folder call it "share" or "disk"

And try again?

 

You're using account of the pc you share to log in? Like prompt coming up?

 

It's unusual to use same account to connect drive. Most people use different account usually it works that way.

At least that's what i think.

 

But is it really same account?

Technical wise.

 

I'm jank tinkerer if it works then it works.

Regardless of compatibility 🐧🖖

Link to post
Share on other sites
Posted
  • Author
8 hours ago, BoomerDutch said:

Have you checked in advanced sharing and on button permissions?

So I was finally able resolve the issue by checking Advanced Security Settings and adding "Everyone" as principle as it was missing before. Now I'm able to access the drive without issue.

 

Thanks to all who tried helping! image.thumb.png.b4b48a588cc6d9db1349d9af1a99de1e.png

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Windows

×