45 replies to this topic

[+Jdawg683]

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.

[Guolung]

Its the local security policy of the 2008 box.
You need to allow it to use NTLM & LanManager logins

[+Jdawg683]

Guolung, on 12 April 2012 - 16:02, said:

Its the local security policy of the 2008 box.
You need to allow it to use NTLM & LanManager logins

Thanks for the fast reply. can you elaborate and/or guide me?

[+sc302]

did you assign the nas a name in the network setup in the nas? it should have a name, try the folowing

username: nasname\userid
password: passwordforuseridsetinnas

[+Jdawg683]

sc302, on 12 April 2012 - 17:32, said:

did you assign the nas a name in the network setup in the nas? it should have a name, try the folowing

username: nasname\userid
password: passwordforuseridsetinnas

yep. no problems there

[+sc302]

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

[+Jdawg683]

sc302, on 12 April 2012 - 18:37, said:

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)

[+sc302]

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.

[+Jdawg683]

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.

[+sc302]

take a look at this doc
http://www.techrepub...stallations/577

[+Jdawg683]

Thanks sc302. i've already tried that, but it didnt help either 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.

[+sc302]

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.

[+Jdawg683]

im fairly convinced that it's something w/i group policy; however, everything i toggle makes no difference.

it's just odd that i can map a drive from other machines, but not the NAS.

[+sc302]

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).

[+BudMan]

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?