Unable to log Vista into fileserver

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
Yesterday, I installed a Vista Ultimate machine and hooked it up to our
network, everything whent fine with the exception of not being able to log
into our fileserver. We have three windows 2000 servers, Domain, Appserver,
and a fileserver.
If I open up explorer I can see all three servers and other PC's on the
network, I can open up every shared folder on all resources with the
exception of our fileserver. I get a login prompt, which won't except any
user name/password combination (admin or otherwise).
The fileserver has several shares on it, with permissions set for Everyone
(full control). I'm not recieving any errors either on the Vista machine, or
the server, and all the XP machines can access the server just fine, even
from the same physical connection.
I'm stumped, I've tried several registery hacks, but nothings worked. Any
help, please?
 
What's the system error if using net use \\servername?

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
Hi,
Yesterday, I installed a Vista Ultimate machine and hooked it up to our
network, everything whent fine with the exception of not being able to log
into our fileserver. We have three windows 2000 servers, Domain, Appserver,
and a fileserver.
If I open up explorer I can see all three servers and other PC's on the
network, I can open up every shared folder on all resources with the
exception of our fileserver. I get a login prompt, which won't except any
user name/password combination (admin or otherwise).
The fileserver has several shares on it, with permissions set for Everyone
(full control). I'm not recieving any errors either on the Vista machine, or
the server, and all the XP machines can access the server just fine, even
from the same physical connection.
I'm stumped, I've tried several registery hacks, but nothings worked. Any
help, please?
 
Hi.
"net use \\" asks to:
"Enter the user name for 'fileserver:"
and, when I enter the user's id, or admins, or any other user id, I get:
"
System error 5 has occured.
Access is denied.
"
However, if I try the domain or appserver I get:
"The command completed successfully."
Thanks, for your help so far:
Mark
 
The System error 5 is permission issue. These search result may help,

Windows
You may receive "System error 5 has occurred" and "Access is denied" when using net view command. In this case, you may have the permission issue. ...
http://www.howtonetworking.com/Troubleshooting/notaccessibalee1.htm - Similar pages

troubleshooting is not accessible error
"System Error 5 has occurred" · "System Error 51 has occurred" · "System Error 53 has occurred". Troubleshooting step by step: ...
http://www.howtonetworking.com/Troubleshooting/notaccessibale0.htm - Similar pages

not accessible
If you can net view IP while net view \\hostname gives you "System error 51 has occurred" ... "System Error 5 has occurred" · "System Error 51 has occurred" ...
http://www.howtonetworking.com/Troubleshooting/notaccessibalef1.htm


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
Hi.
"net use \\" asks to:
"Enter the user name for 'fileserver:"
and, when I enter the user's id, or admins, or any other user id, I get:
"
System error 5 has occured.
Access is denied.
"
However, if I try the domain or appserver I get:
"The command completed successfully."
Thanks, for your help so far:
Mark
 
Ok, I finally got the Vista client to access the windows 2000 fileserver. I
did a number of things all at once, so I'm not sure which one actually
worked. Here is what I did.

1. Install SP4 on the server (I don't think this is what actually did the
trick, as we only have sp2 on the appserver).
2. I changed a few local security policies on the Vista client (secpol.msc >
Local Policies > Security Options)
a. Microsoft network client: Send unencrypted password to third-party SMB
servers
Enabled
b. Network security: Do not store LAN Manager hash value on next password
change
Disabled (I think this one did the trick)
c. Network security: LAN Manager authentication level
Send LM & NTLM Responses

According to the "Explain" on the the LAN Manager hash value... it says"
Windows 2000 Service Pack 2 (SP2) and above offer compatibility with
authentication to previous versions of Windows, such as Microsoft Windows NT
4.0.
This setting can affect the ability of computers running Windows 2000
Server, Windows 2000 Professional, Windows XP, and the Windows Server 2003
family to communicate with computers running Windows 95 and Windows 98."

So, I think this one probably did the trick.
Thanks
Mark Garcia
 
Back
Top