Hi,

I have recently got a laptop running vista.

I have a Dlink 323 NAS gizmo attached to my network.

On the Dlink I have a number of shares and I have setup various logins
(for example unless you log in to the drive as a 'super user' you
can't delete the photos, we have a 5 year old who uses the laptop you
see!).

On the old windows XP machine it was a simple matter of mapping the
drives, making the windows login and password the same as the Dlink
checking the reconnect at login box and everything "just worked (tm)".

Under Vista I mapped the drives ok but it took some fiddling. I had to
try a number of times variously telling it to connect as a differnt
user (even though passwords and logins line up) and just entering in
the box until it eventually took.

Then after each reboot the drives all fail to reconnect. Somtimes if I
double click on them they just come back. Usually I end up
disconnecting them and then with similar voodoo to the above get it
all working again but this is a PITA.

At the moment the share is visible under networking in the explorer
but I won't verify the password.

I have BitDefender Internet Security but I don't think that is the
problem.

Further googling has turned up an possible fix of running "secpol.msc"
but I don't seem to have that (Windows Vista Home Premium). In Secpol
you are supposed to change the NTLM something or other.

Is there either away to add secpol.msc to my machine, change the NTLM
thing someother way or anyone else have a suggestion on fixing this?

On Apr 19, 11:58 am, SlowLearner wrote:
Hi,

I have recently got a laptop running vista.

I have a Dlink 323 NAS gizmo attached to my network.

On the Dlink I have a number of shares and I have setup various logins
(for example unless you log in to the drive as a 'super user' you
can't delete the photos, we have a 5 year old who uses the laptop you
see!).

On the old windows XP machine it was a simple matter of mapping the
drives, making the windows login and password the same as the Dlink
checking the reconnect at login box and everything "just worked (tm)".

Under Vista I mapped the drives ok but it took some fiddling. I had to
try a number of times variously telling it to connect as a differnt
user (even though passwords and logins line up) and just entering in
the box until it eventually took.

Then after each reboot the drives all fail to reconnect. Somtimes if I
double click on them they just come back. Usually I end up
disconnecting them and then with similar voodoo to the above get it
all working again but this is a PITA.

At the moment the share is visible under networking in the explorer
but I won't verify the password.

I have BitDefender Internet Security but I don't think that is the
problem.

Further googling has turned up an possible fix of running "secpol.msc"
but I don't seem to have that (Windows Vista Home Premium). In Secpol
you are supposed to change the NTLM something or other.

Is there either away to add secpol.msc to my machine, change the NTLM
thing someother way or anyone else have a suggestion on fixing this?

Managed to solve it. As this seems a common problem and this "do it
without secpol" method is quite hard to track down.

Secpol does not exist on Vista Home Premium.

What you need to do is the following:

Run Program: windows key + r
Enter: Regedit.exe and hit enter
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa
\LmCompatibilityLevel
Change the value from 3 to 1 (I used the decimal if that makes any
difference, it might I don't really know).
Save or close or whatever and restart your machine.

When it comes back, hopefully your NAS drive problems are solved.

I think this does what the secpol.msc program does, I am not sure but
at least it works. Why an obviously important setting can't be
accessed other than through regedit is beyond me. Until this NAS
problem I was thinking maybe MS had got its act together. Guess not.

Thank you for sharing your experience with us.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"SlowLearner" wrote in message
...
On Apr 19, 11:58 am, SlowLearner wrote:
Hi,

I have recently got a laptop running vista.

I have a Dlink 323 NAS gizmo attached to my network.

On the Dlink I have a number of shares and I have setup various logins
(for example unless you log in to the drive as a 'super user' you
can't delete the photos, we have a 5 year old who uses the laptop you
see!).

On the old windows XP machine it was a simple matter of mapping the
drives, making the windows login and password the same as the Dlink
checking the reconnect at login box and everything "just worked (tm)".

Under Vista I mapped the drives ok but it took some fiddling. I had to
try a number of times variously telling it to connect as a differnt
user (even though passwords and logins line up) and just entering in
the box until it eventually took.

Then after each reboot the drives all fail to reconnect. Somtimes if I
double click on them they just come back. Usually I end up
disconnecting them and then with similar voodoo to the above get it
all working again but this is a PITA.

At the moment the share is visible under networking in the explorer
but I won't verify the password.

I have BitDefender Internet Security but I don't think that is the
problem.

Further googling has turned up an possible fix of running "secpol.msc"
but I don't seem to have that (Windows Vista Home Premium). In Secpol
you are supposed to change the NTLM something or other.

Is there either away to add secpol.msc to my machine, change the NTLM
thing someother way or anyone else have a suggestion on fixing this?

Managed to solve it. As this seems a common problem and this "do it
without secpol" method is quite hard to track down.

Secpol does not exist on Vista Home Premium.

What you need to do is the following:

Run Program: windows key + r
Enter: Regedit.exe and hit enter
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa
\LmCompatibilityLevel
Change the value from 3 to 1 (I used the decimal if that makes any
difference, it might I don't really know).
Save or close or whatever and restart your machine.

When it comes back, hopefully your NAS drive problems are solved.

I think this does what the secpol.msc program does, I am not sure but
at least it works. Why an obviously important setting can't be
accessed other than through regedit is beyond me. Until this NAS
problem I was thinking maybe MS had got its act together. Guess not.