Can't connect to WIN 2K Share

[mywebwork]

Hi

I've installed Windows 7 on a machine on my home network. The network has several other machines with various OS's.

Using the Win 7 machine I can connect to shares on my XP and Vista machines, but not to my 2 Windows 2000 Server machines. This is actually a big problem for me because one of the W2K boxes is both my file server and my print server. Of course all of the XP and Vista (and LINUX and Mac) machines connect to the Windows 2000 server just fine, only Windows 7 seems to have a problem.

I get the login box and give a valid login (including machine name) but it won't authenticate.

The Windows 2000 Server is not a domain controller if that helps.

Any help would be most appreciated.

Bill

 

[torrentg]

Saying it won't authenticate....does it give an error code or message? If so, what is it?

-Try using the ip address as opposed to machine name. Can't hurt.
-In 7, make sure the TCP/IP Netbios Helper service is running.

 

[Alexx]

I have the same problem.
I try to connect to the server by IP, but it won't authenticate, there are no any errors, the password asked again and again. The TCP/IP Netbios Helper service is running!
Can anybody help me?
Win 7 Enterprise 7600 En

 

[torrentg]

Yep, I think so Alexx. A reason why it will keep asking for a password is if both machines have the same user account name but different passwords. Does that describe your pcs? If so, easy fix for this is to make the passwords identical.

 

[Alexx]

I solved this problem by changing LAN Manager Autentification level to NTLM v.1 in Local Groupe Policy.

 

[Dan7]

Same problem here, but Win 7 Home Premium doesn't offer access to the Local Security Policy. I have tried changing the authentication level on the Win 2000 machine to NTLMv2, which I believe is the default on Win7. Didn't work. I have checked user/pass/workgroup/sharing etc and have no problem with the other PCs on my network. Any other ideas would be appreciated. Thanks

 

[Dan7]

Got there in the end. Some combination of authentication level and firewall adjustments seemed to do the trick.