Cools Posted December 17, 2010 Posted December 17, 2010 Hello, I have a 2008 installation, where the 2008 server is unable to access shares on the r2003 server The SBS2003 is a dumb fileserver. The error is "Windows cannot access \\." with a detail of "Error code 0x80070035 The network path was not found". The 2008 server is also unable to access shares on XP/2003 machines. However it IS able to access shares on Windows 7 machines. But 2003/XP can access shares on win7 and 2008 and 2008 r2.. Machines are equipped with McAfee VirusScan 8.7, but they have access protection disabled. Firewalls are also disabled. TCP over Netbios helper service is started on both machines. I have disabled IPv6 on 2008, and done some reg tweaks found on google But im at a loss.. Any help much appreciated,
Cools Posted December 17, 2010 Author Posted December 17, 2010 Yes i can access it via IP .. i did think it was a dns problem.. i did try the FQDN but no joy...
Cools Posted December 17, 2010 Author Posted December 17, 2010 (edited) i have just added a trial.. 2008 R2 server on the network i have joined it to the domain but when i access any shares it asks for a user name and password.. Strange.. i reset the Domain and Domain controller GPO's back to default but it has not made any difference i did think it was a change i made to get samba/ntlm working in a Linux box. i have no problem accessing my 2003 Home server from windows 7 or (2008 server (over vpn)) shares.. Edited December 17, 2010 by Cools
skell Posted December 17, 2010 Posted December 17, 2010 Do you have the firewall on? I've had this problem before, couldn't see any computers that weren't running Windows Vista / 7. I'll try and remember what I did...
Cools Posted December 17, 2010 Author Posted December 17, 2010 (edited) 1st post: Machines are equipped with McAfee VirusScan 8.7, but they have access protection disabled. Firewalls are also disabled. TCP over Netbios helper service is started on both machines. i can see win7 PC's but win7 and 2008 cant see 2003 server or XP the error ms i get when accessing 2003 share at school is "insufficient system resources exist to complete service request" Edited December 17, 2010 by Cools
Cools Posted December 17, 2010 Author Posted December 17, 2010 http://www.edwardpeake.beds.sch.uk/servererror.jpg
skell Posted December 17, 2010 Posted December 17, 2010 (edited) If I recall correctly, its something to do with the NTLM settings. Under - Computer Configuration - Policies - Windows Settings - Security Settings - Local Policies/Security Options - Network Security try the following Network security: LAN Manager authentication level Send LM & NTLM - use NTLMv2 session security if negotiated Network security: LDAP client signing requirements None Network security: Minimum session security for NTLM SSP based (including secure RPC) clients Enabled Require NTLMv2 session security Disabled Require 128-bit encryption Disabled Network security: Minimum session security for NTLM SSP based (including secure RPC) servers Enabled Require NTLMv2 session security Disabled Require 128-bit encryption Disabled I'll keep looking. Just found this, similar issue. http://www.sevenforums.com/network-sharing/11155-windows-7-cant-see-xp-2003-shares.html Edited December 17, 2010 by skell 1
Cools Posted December 17, 2010 Author Posted December 17, 2010 Thanks Skell i will give it a try and let you know how its gone so far..
Cools Posted December 17, 2010 Author Posted December 17, 2010 Did not fix it... still the same problem hmmmmm.. .
Cools Posted January 18, 2011 Author Posted January 18, 2011 Problem solved! Don't ask added two new DC's and over night it fixed the problem. Strange.
Cools Posted January 27, 2011 Author Posted January 27, 2011 Problem cropped up again and I found a fix in MS forums.. who go it from Windows 7 Nonpaged Pool Srv Error 2017 | alan.lamielle.net ------------------------------------------------ Apparently you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly. Set the following registry key to ‘1′: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache and set the following registry key to ‘3′: HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size After making these changes and restarting, I haven’t seen this issue arise again so far..
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now