Recommended Posts

I have a local network setup using a standard 192.168.1.x range. there's no domain involved. there is no hardware firewall involved - only an unmanaged switch.

there are 4 machines on this subnet - Win7, Synology NAS, Server 2008 R2, Server 2003

i have 2 shared folders on the NAS which can be accessed easily by the Win7 and Server 2003 machines, but not by the R2 machine. fwiw, the R2 machine can access shares on both the Win7 and 2003 machines, just not the NAS.

When i try to map a network drive (a shared folder on the NAS) through Windows Explorer on the R2 box, i type in the appropriate creds, and about 10 seconds later, the credentials box pops up again (over and over.) If i try to use cmd to map the drive, i get "System error 58 has occurred. The specified server cannot perform the requested operation." Also, Synology has a product called the Synology Assistant. Within this program, i can [try to] map a drive using their wizard. This results in the same Error 58. I've contacted Synology support, and they were unable to rectify the issue.

Again, the win7 and 2003 boxes can access the shared folders on the NAS. The 2008 R2 box cannot.

After searching the internet for a fix, nothing has worked for me. I've tried uninstalling MSE, numerous Group Policy settings, numerous registry tweaks. i've also disabled the windows firewall and tried various tweaks to the network adapter's properties. nothing has worked.

I'm not sure where else to go w/ this.

no problems there typing in the computername\userid and password? if that is the case just use that to auth with.

i cant use the method you described. the NAS has no idea about the server's local users - only the users assigned in the NAS itself. (plus, i've tried that already) :p

you fail to understand what I am talking about....let me try to explain better...

device type : network name

server : server1

nas : storage

On the server you have no user passwords a user called owner and on the nas you have a user called user1 and a password of password.

when on server 1 and logged on with the user called owner and you want to access a share on the nas you open a run prompt and type in the following

\\storage\share1

now it prompts you for a username and password you type in:

storage\user1

password

--------------------

You can see in this example I am not using the user on the server for any type of authentication.

I have no clue what you have named your nas box so you will need to go into the network properties of your nas box to find out what it is called if you didn't rename it.

and what you described does not work. i continually get prompted to enter my credentials for the NAS. again, the NAS logs that the authentication was successful; however, windows just constantly re-prompts for the creds. if i do the same thing you mentioned in CMD, using "net use" i get the Error 58.

this same thing does NOT happen on the win7 or 2003 machines.

Thanks sc302. i've already tried that, but it didnt help either :s i had it set to ?Send LM & NTLM responses - use NTLMv2..." and it didnt work. i switched to ?Send LM & NTLM responses? and that didnt work either.

server 2008 isn't liking something, and there isn't much we can do further at this level. perhaps getting a network sniff and seeing what is transpiring on the network layer can lead to a more definitive cause if you are infact authing to the nas box and are getting logs stating that you have been granted access but continue to get access denied.

if it is group policy you can see what gp changes have been made by running rsop.msc at a run prompt you will be able to drill down through anything that has a policy change. if nothing is listed there are no policy changes (local or through a dc).

And what account are you running with on the 2k8 box? I do not believe I have ever seen that error before. But sounds more like the account your using does not have the ability to map

When you keep getting prompted -- are you trying to map it, or just browse it? Sounds like mapping to me

"When i try to map a network drive"

Vs trying to map -- just access it

run, \\nasname -- put in your creds, do you get access now?

if it is group policy you can see what gp changes have been made by running rsop.msc at a run prompt you will be able to drill down through anything that has a policy change. if nothing is listed there are no policy changes (local or through a dc).

let me look into that this morning. thanks!

And what account are you running with on the 2k8 box? I do not believe I have ever seen that error before. But sounds more like the account your using does not have the ability to map

When you keep getting prompted -- are you trying to map it, or just browse it? Sounds like mapping to me

"When i try to map a network drive"

Vs trying to map -- just access it

run, \\nasname -- put in your creds, do you get access now?

I've tried 3 different windows user logins - all of them in the local Admin group.

i get constantly prompted for my creds whether i try to browse (start, run) or map the drive in Explorer.

So when i try to map a drive in CMD, i get the Error Code 58 message. This same error code occurs in the Synology Assistant.

post-34502-0-45056500-1334580863.jpg

post-34502-0-32521400-1334580858.jpg

Again, you do not use windows logins....you will never auth with windows logins. You might as well try logging in with the user name of jesus and the password I am god, it will yield the same results.

You need to login with a user that was created on the nas or the nas admin user. You may have to use the nas computer name (which you have not mentioned what it was) in the auth method with the nas admin user name.

I feel bad because 2 years ago when I was a network administration student we had the same issue when we were building our end projects for class. I have a billion (and one) documents stored from all the stuff me and the other guy (who was the top of the class with me) and we DID figure out how to fix it, it's just after graduation I never got a job in the field (very little up here in South Dakota, and my wife did not want to move) so a lot of the stuff I've forgotten. I can't even remember where I stored all of the crap we read to try to fix the issue. ?Send LM & NTLM responses - use NTLMv2..." does sound VERY familiar though. If I remember right, those older NAS systems do not play well and there is some policy you need to change dealing with that. I feel horrible, it's on the tip of my damn tongue but I just can't spit it out... Lemme keep rolling it around my head for awhile and I'll try to get back to you.

Again, you do not use windows logins....you will never auth with windows logins. You might as well try logging in with the user name of jesus and the password I am god, it will yield the same results.

You need to login with a user that was created on the nas or the nas admin user. You may have to use the nas computer name (which you have not mentioned what it was) in the auth method with the nas admin user name.

again, im not using the windows login to try to access the NAS. Budman asked about the windows user i was trying, implying that it's a group policy issue.

just a quick summary, as i still believe this is a GP issue, but i simply cant narrow it down.

  • i cannot access a shared folder on the NAS from Server 2008 R2
  • i can access the shared folder on the NAS from Server 2003 and Windows 7
  • i can access folders shared on either Server 2003 or Windows 7 from 2008 R2
  • The shared folder on the NAS uses an account local to the NAS - not tied to any specific computer, server, or domain
  • there is no domain involved at all

and thanks to all that have been helping me so far :beer:

This topic is now closed to further replies.
  • Posts

    • Given only Volume license customers and specific resellers can obtain the LTSC versions legitimately it seems likely that this has been tinkered with quite a lot!
    • Apple CEO Tim Cook confirms looming price hikes due to memory shortages by Hamid Ganji Image via Apple Memory and chip shortages have led to significant price increases for electronics over the past year, and it seems that more hikes are on the way for upcoming smartphones and computers. Apple CEO Tim Cook has confirmed that the company is planning to increase the prices of some of its products due to the ongoing memory and storage shortages. In an interview with The Wall Street Journal, Cook confirmed the looming price hikes for Apple’s future products, adding that “Unfortunately, price increases are unavoidable.” He also said the company is doing its best to “mitigate the huge increases that are being passed to us, and we’ve been trying to shield our customers from the increases, but the situation has become unsustainable.” The Apple CEO also noted that the allocation of a large portion of memory chips to AI companies has contributed to shortages in the market, resulting in lower supply at a time when demand for devices remains high. “We definitely need memory pricing and supply to return to reasonable levels for consumer products. That’s the bottom line,” Cook said. Cook also added that Apple is ready to use its vast cash reserves to help boost supply in the market because additional production capacity is needed. While he declined to specify how Apple plans to do that, he said the company will not build its own memory and storage factories despite its financial resources and silicon expertise. Cook did not provide further details on the scale of the price increases or which Apple products would be affected, though iPads and Macs could see higher prices sooner than other products. Apple’s next product launch event is scheduled for September, when the company is expected to unveil the iPhone 18 Pro, iPhone 18 Pro Max, and its first foldable iPhone. It remains unclear whether the upcoming iPhones will be affected by the price increases, but given the current memory shortage, higher prices seem increasingly likely. There is currently no clear timeline for the end of the memory shortage. Samsung, one of the world’s three largest memory chip manufacturers, recently said the shortage could persist for several more years.
    • Downloads does not equal actual usage, even less when the app is pre-installed in some Galaxy phones.
    • +1000 to this, don't understand why they added that margin around the top bar, even the close button is a PITA to click without aiming. Ofc, this is just preview and hopefully they will revert such odd UX decision before hitting final version.
    • so the people who bought this will get a refund?
  • Recent Achievements

    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
    • First Post
      Jocimo earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      542
    2. 2
      +Edouard
      167
    3. 3
      PsYcHoKiLLa
      85
    4. 4
      Steven P.
      64
    5. 5
      ATLien_0
      64
  • Tell a friend

    Love Neowin? Tell a friend!