Mapping Drives...
-
I have two C# apps that address the same server "\\stlmo1". stlmo1 has a C:, D: and E: drive. The E: drive is the data drive that I need to address. I used to be able to address the share called "\\stlmo1" and it mapped to the root of the E: drive but that was before a ransomware hit. Then the share was gone. I can share the E: drive, but it is "\\stlmo1\E" now. That causes all kinds of problems since 3 servers are looking at that location. Can anyone suggest how to share the E: drive on \\stlmo1 as "\\stlmo1"
-
I have two C# apps that address the same server "\\stlmo1". stlmo1 has a C:, D: and E: drive. The E: drive is the data drive that I need to address. I used to be able to address the share called "\\stlmo1" and it mapped to the root of the E: drive but that was before a ransomware hit. Then the share was gone. I can share the E: drive, but it is "\\stlmo1\E" now. That causes all kinds of problems since 3 servers are looking at that location. Can anyone suggest how to share the E: drive on \\stlmo1 as "\\stlmo1"
That doesn't look like a valid UNC path. The share name is always required, not just the host name. Even with Distributed File System[^] you'd still need a domain name and a namespace. Do you have any documentation on how the server was set up previously?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
That doesn't look like a valid UNC path. The share name is always required, not just the host name. Even with Distributed File System[^] you'd still need a domain name and a namespace. Do you have any documentation on how the server was set up previously?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
I have no idea how it was set up originally, but it did work and only had the server name. ... My research agrees with you though, it shouldn't have worked.
