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

    • I bought this game. Played it for an hour, and then got a refund from Steam. Not a fun game at all.
    • Nothing Ear buds with active noise cancellation are at their lowest price ever with 51% off by Fiza Ali Amazon is currently offering the Nothing Ear wireless earbuds at their lowest price ever with 51% off limited prime deal. The earbuds feature an 11mm dynamic drivers with a ceramic diaphragm, and support high-resolution audio codecs including AAC, SBC, LDAC, and LHDC 5.0. They support active noise cancellation of up to 45dB across a frequency range of up to 5000Hz, and include a smart ANC algorithm, adaptive noise cancellation, and a transparency mode that allows surrounding sounds to be heard when needed. Connectivity is provided via Bluetooth 5.3, with support for multiple profiles including HFP, A2DP, AVRCP, and others. The earbuds also support dual connection, allowing them to be paired with two devices at the same time. Additional features include IP54 water and dust resistance for the earbuds and IP55 for the charging case, in-ear detection, pinch controls, low-latency mode, Google Fast Pair, Microsoft Swift Pair, and a three-microphone system per earbud for clearer voice calls. The Nothing X app, available on Android and iOS, provides access to custom EQ settings, bass enhancement, personal sound profiles, ear tip fit testing, firmware updates, customisable controls, dual-device management, and a find-my-earbuds feature. In terms of battery performance, each earbud has a 46mAh battery and the charging case has a 500mAh capacity. With active noise cancellation (ANC) turned off, the earbuds should offer up to 8.5 hours of playback on a single charge and up to 40.5 hours in total with the charging case. With ANC enabled, playback should last up to 5.2 hours on the earbuds and up to 24 hours with the case. For calls, talk time should reach up to 5 hours on the earbuds and 23 hours with the case when ANC is off, while ANC on should provide up to 4 hours on the earbuds and 18 hours with the case. Finally, fast charging should deliver up to 10 hours of playback from 10 minutes of charging when ANC is disabled. Nothing Ear Wireless Earbuds Bluetooth: $73.15 (Amazon US) - 51% off Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • Microsoft officially launched its Copilot Cowork enterprise AI agent on June 16, 2026, switching to usage-based pricing on the same day it disclosed it is considering a Microsoft-hosted version of China's DeepSeek V4 as a lower-cost engine for the platform — a pairing that puts the company on a collision course with both its enterprise customers' security teams and a White House that has spent months trying to wall off Chinese AI from American infrastructure.................... https://www.techtimes.com/articles/318647/20260618/microsoft-eyes-deepseek-v4-copilot-cowork-what-azure-hosting-cannot-fix.htm  
    • Forza Horizon 6 gets another hotfix for one of the game's online modes by Taras Buria Recently, Forza Horizon 6 players discovered an interesting glitch that allowed farming a crazy amount of in-game credits in a few minutes. Playground Games quickly pulled the plug on the exploit by disabling one of the game's online modes, and today, the studio is rolling out another hotfix. In my review, I complained about the game still showering gamers with cars, credits, and wheelspins. As such, earning money in Forza Horizon 6 is not a particularly difficult task. You simply have to play the game, crazy, I know. However, people still found an easier path to becoming a billionaire in Forza Horizon 6. All you had to do was purchase the Hummer EV, install a specific tune, shift in reverse while going at about 15 MPH, hit a wall, and get launched into the stratosphere at the speed of light. While mid-air, launch Eliminator and quickly get eliminated. Boom, the game just awarded you with a few million in-game credits. Initially, Playground Games disabled Eliminator to prevent people from farming credits. Now, following the release of the first balancing update, developers are rolling out a new update that re-enables Eliminator and gives users a free McLaren Sabre as a gesture of goodwill. Here is the changelog: One critical issue remains unpatched, though. There are quite a few reports of the game wiping gamers' saves, and developers are still looking into that. To avoid potential data loss, Playground Games recommends taking one of the steps outlined in a previously published support article.
  • Recent Achievements

    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      591
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      67
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!