Windows 10: DSN Problem when Network Mapping

I restarted my computer because it was bugging out and when it came back online my U drive mapped had a red X on it and was unavailable. I've tried remapping it, removing it and even many online tutorials because Microsoft fails to have any actual support, however whenever I go to remap the drive it says that the drive cannot be connected and that the DSN is not responding? This is a school drive and has many important files I need quickly.

:)

 

Can't create System DSN (ODCB, Microsoft Access Driver)

I have a new pc and I'm trying to configure everything the same as it was on the system it's replacing. I need to create a 2 system dsn in order for my fedex shipping software to grab order data. On my old PC this was extremely straightforward, I would go to create the dsn and from the "drives" drop down, I could choose my existing mapped network drive and select the database that I need.

Both PC's are windows 10 pro. I've configured the mapped network drive, but it's not listed in drives drop down on dsn creation window.

If I instead delete the existing mapped network drive, and click the "network..." button. I can create a mapped network drive and select my accdb file. However in doing so and clicking okay, 1 the mapped network doesn't show up in "this pc" and 2, the dsn I created does NOT show up in the system dsn tab.

If I try to create it again, I do see my mapped network drive int he drives list, which is nice BUT when I click okay after choosing the database, it says "the datasource named "mydsn" already exists. Replace it with this definition?

If I choose Yes, it still doesn't show up in the system DNS list. Nor can my fedex program find it. It MUST be in the list in order for my fedex software to use it.

Incidentally, even on the originally PC, I can no longer create any NEW system DSN using Microsoft Access Driver(*.mdb, *accdb) ACEODBC.DLL.

On both pcs, the only thing that I can successfully create is a Driver do Microsoft Access (*.mdb) ODBCJT32.DLL . Although that will work for one of my needs, the other is an accdb. And while I have tested creating one with this driver and choosing the accdb anyway, fedex can't use it.

 

Connecting NAS - mapping of drives

Ok, If you want, we can do a step by step troubleshooting of your current situation: If you are able to ping your Machine and it responds. Code:

Try to view if your NAS appears on the Network List: Code:

If Your NAS appears on the list, try to view it: Code:

The available shares will be listed there. Then Try to List the content of one of the directories: Code:

This should list the content of the directory, If all this works Try to map a drive on one share: Code:

Pls reply with the "response" of the first "encounter" of a non positive output. This exercise should reveal if you have a Network or Protocol or Cipher or Authentication problem.

 

Problems with mapped drive

Well I got one step closer to getting the mapped drive working.

Instead of using Windows 10 File Explorer to map the Network Drive, I do it manually from a Command Prompt run as Administrator:

net use G: \\XP07\XP_Dev

After executing this command I can copy files to and from the mapped drive to the system disk. And while this is a huge step forward there are still other problems with the mapped drive.

Opening a jpg file in Paint by clicking it from File Explorer loads the picture just fine, but I can't save it. When Paint tries to save the file it can't find the mapped drive, it doesn't even show up when browsing for a place to save it.

There are a few links on the web discussing this very issues of not being able to browse a mapped drive from within a program. There is supposed to be a registry fix for this by adding EnableLinkedConnections and settings it's value to 1 but it didn't work.

So the next step after getting File Explorer working is to somehow get programs to see the mapped drive.