NTLite can not access mapped drives when in the file select dialog.

[Lew@Lew-Adv-Sol]

G

Thread 'RESOLVED: SMB not working'

Dec 18, 2019

This has cost me about 1 month of trial and error so far to try to figure out why I cannot browse the c drive from another computer:
\\192.168.1.159\c$

Working
lumia.xml

Not working
nosmb.xml

Both are virtually identical in terms of components!

What significant difference exists in the configuration that might explain why I can browse network shares remotely using lumia.xml - but not nosmb.xml?

Any help would be appreciated!

• gilius
• Replies: 4
• Forum: Questions and Reports

Thread 'Running NTLite inside a VM - File Access Issues?'

Jun 27, 2024

Hello!

I have NT-Lite currently setup inside a Virtual Machine on a server for easy bulk storage and file access.
The issue I keep running into is that NT-Lite for whatever reason doesn't like accessing files on a Remote Share. I cannot get it to pull or push any files to the share.

I also tried mounting a folder with KVM, and it does show up as a "Disk" type device, but somehow NT-Lite still detects it's not a proper Disk and will not use it.

Is there any way around this? I am currently using a physical HDD mounted directly in the VM, but this loses me an entire slot in the Server that...

• GraphicHealer
• Replies: 11
• Forum: Questions and Reports

Are just a few that I have reviewed to see if this is a common deal but I can't find a similar case.
NTlite doesn't like mapped drives? UNC and pinned locations are good to go but mapped drive make NTLite go burrr. All jokes aside, it's minor but a bug none the less. I am hoping that someone is like oh ya its blahblahblah because it isnt the firewall(turned off) and authentication. I have tested on different machine in different geo locations with the same outcome. Thanks

 

[garlin]

NTLite doesn't really work correctly on network shares, because DISM (required for adding Windows updates) has a kernel-level filter driver dependency on the filesystem. Certain DISM-based file operations are mapped back to the driver, which only works on a local volume.