• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Map a network folder from Win7 to Server2003!?!

paperfist

Diamond Member
Ok I'm stuck, this is the 3rd Windows 7 Enterprise computer I setup where it needs to access a shared folder on the WinServer2003 drive. The other 2 worked perfectly right out of the box. This one is driving me nuts!!!

So far I've tried the syn the clocks trick and that didn't work. Unless I have to do that in BIOS?

Then I tried this:

"Network Security: LAN Manager authentication level" set to: "Send LM & NTLM - use NTLMv2 session security if negotiated".

Under Advanced sharing settings page of Network and sharing center:

-Enable network discovery
-Turn on file and print sharing
-Turn off password protected sharing
-Use user accounts and passwords to connect to other computers

Encryption I have set as use 128 bit

Group Policies I enabled:

Network access: Allow anonymous SID/name translation
Network access: Let Everyone permissions apply to anonymous users

And Disabled:

Network access: Restrict anonymous access to Named Pipes and Shares
Network access: Do not allow anonymous enumeration of SAM accounts
Network access: Do not allow anonymous enumeration of SAM accounts and shares

-----

Still I keep getting this error:

"Logon failure: unknown user name or bad password"

Does anyone have any ideas before I start to cry? 🙂
 
1. clock sync? AD requires 5 minutes but also provides ntp services.
2. i needed nothing other than disable ipv6 to make my win-whatever work with win2k3 servers. all day long. 50+ machines.

you are using a domain server?
 
Yes, sorry domain server. That's the strange part all the other Win7 machines work fine in this scenario, this one doesn't...

Yeah, a lot of answers on the net as to why the login failure was happening was due to the client's clock being 'out of sync' with the server meaning that the client was over a few hours difference in time then the server.

Way over 5 minutes. I can connect if I use my admin settings from the client to the server so something wonky is going on that I'm not seeing.

I'm also not getting any event viewer issues on the server side. I'll check out ipv6 though.
 
Last edited:
Disabled ipv6, but it didn't work. After that I disjoined the user from the server, re-joined them and got the drive to map out. Now however they lost their access rights to the files. Great 🙁
 
The event logs generated by a failed login would help a ton.

You have also basically disabled security on that machine with all the settings you set...
 
The event logs generated by a failed login would help a ton.

You have also basically disabled security on that machine with all the settings you set...

I know but it was the only way to trigger being able to map out the network drive. After I restore the permissions I'm going to undo the other changes I made to see if they effect it.
 
Back
Top