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

    • Windows 10 IoT LTSC is supported until 2032, Windows 11 LTSC until 2029. So oddly enough the Windows 10 version is supported longer.
    • Latest Rufus update improves new Windows 11 install method by Taras Buria Pete Batard, the maker of Rufus, a very popular app for creating bootable Windows (and other OS) media, has released a new beta version of its app. Rufus 4.15 beta is now out, and while it offers no new features, there are all sorts of improvements and fixes, including for the new Windows 11 installation method that was introduced in version 4.14 in early May. The "Silent Windows 11 installation" is a new feature whose goal is to automate operating system installation. All you have to do is boot from the drive, and then Rufus takes over, doing all things for you, such as setting up a new account, skipping ads and prompts, and more. It is a very handy tool, but initially, it had some bugs and issues that required addressing. With version 4.15 beta, Rufus is fixing that, particularly a bug with installation failing at 75%, crashes on Snapdragon X-based PCs, and more. Here is the changelog: Rufus 4.15 beta is now available for download from its GitHub repository. If you have never used Rufus before, you can check out our guide here. It is a very useful utility to have, as it allows you to deal with plenty of Windows 11's annoyances, which are still there, despite Microsoft's ongoing efforts to fix them.
    • Microsoft fixes one of Excel Copilot's most frustrating limitations by Usama Jawad Microsoft began integrating Copilot into Excel a couple of years ago and has been upgrading it with new functionalities since then. While some changes have been controversial, Microsoft is hoping to win over users by allowing them to be more productive via Copilot. To that end, it has now announced a Copilot improvement that may actually be appreciated by people who use it regularly. Excel customers often use the Copilot prompt box to issue instructions to format and customize their data, but it can become quite tiring to keep repeating the same instructions again and again. Microsoft now allows you to define Copilot personalization rules for formatting, naming conventions, formulas, and report styles. These can be accessed via Settings > Personalization, where you can explain your rules in natural language like "Always format currency in USD with no decimals", and just let Copilot take care of the rest. Microsoft is going a step further in this direction by allowing you to set workbook rules too. These rules are stored as a .Rules sheet, and are preserved while the workbook is shared. This fosters collaboration while making sure that standard rules govern the Copilot editing experience across the organization. Other advantages of this capability include pointing it to specific examples, defining dynamic formulas, and referencing an entire sheet and asking Copilot to infer rules based on that. You can leverage this feature by opening Copilot in Excel, clicking on "+", and selecting Create workbook rules. If you have an existing .Rules sheet, you can simply start listing the rules in column A as well. Personalization features are available to all Copilot in Excel users across the web, Mac, and Windows. Meanwhile, workbook rules are currently being previewed for Windows and Mac customers on the Insiders channel. General availability is scheduled after a few weeks, but a concrete date is currently unknown. Overall, the Excel capability is quite similar to ChatGPT's memory features, which allow you to permanently store items in the AI model's context window.
    • Imagine you still haven't discovered Total Commander that is doing all those things for three decades already...
    • This sounds like underneath the nice marketing spin, either someone at Adobe got tired of their lazy devs and asked Microsoft to help them sort at least some of Adobe's ancestral spaghetti code to make it go faster, or Microsoft wanted Adobe's crap to run better on Windows to make it look better when compared to Apple, so they offered to intervene. Either way, GOOD.
  • Recent Achievements

    • One Month Later
      Vincian earned a badge
      One Month Later
    • First Post
      Jocimo earned a badge
      First Post
    • Week One Done
      suprememobiles48 earned a badge
      Week One Done
    • One Month Later
      Windows Guy earned a badge
      One Month Later
    • One Month Later
      Prasann earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      515
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      90
    4. 4
      Steven P.
      78
    5. 5
      ATLien_0
      68
  • Tell a friend

    Love Neowin? Tell a friend!