Help accessing server 2008 shares
- Hello everyone, We just upgraded our server to windows 2008. We didn't
realize there would be an issue with our machines until all of them couldn't
connect to the server. Our Milling machines range from windows 95 to NT 4.
We don't have the firewall on the 2008 server but the machines say the same
thing. Unable to lcoated network device. We can ping the server and we can
connect to our 2003 server just fine so it is like windows 2008 doesn't allow
the NT 4 or 95 clients to access it. does anyone have any ideas?
TIA Mike
All Replies
- Hi EvoBora,
The below post might be helpful for you to solve the issue.
http://social.technet.microsoft.com/Forums/en-US/winservercore/thread/844bb67a-6528-4f5d-b41c-b5d011027b18
Best Regards,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights. - Thanks wilson,
That post gives much of the detailed troubleshooting steps
EvoBora, please follow the link and further if you still have the issue, do post back. thanks for the suggestions I looked thru the post and tried a number of things and still came up empty with no luck since min is giving me a network can not be found I think it is another issue. I did however find this http://support.microsoft.com/kb/942564 that seemed to look more like the solution but it didn't seem to work. I didn't restart the server after i made the change but I did restart the netlogon service. I can't restart it yet since it is in full production but hoping to restart it tonight and see if that helps any. Let me know if anyone has any other suggestions.
Thanks,
Mike
TIA Mike- I was able to get the server restarted last night and still ahve the same problem. I just can't see to figure out what the problem is. I'm working on 95 & NT 4 computers and unfortunatly I don't have a way around it right now since these are old milling machines. anyone else have any suggestions that would be great.
TIA Mike Hi EvoBora,
Thank you for your response.
Do you have Windows 2008 Domain controller in your environment?
If so, the default behavior of the Allow cryptography algorithms compatible with Windows NT 4.0 policy setting may cause this problem. This setting prevents both Windows operating systems and third-party clients from using weak cryptography algorithms to establish NETLOGON security channels to Windows Server 2008-based domain controllers. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
http://support.microsoft.com/kb/942564
When a Windows NT 4.0-based computer tries to use the NETLOGON service to establish a security channel to a Windows Server 2008-based domain controller, the operation may fail
Best Regards,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights.Hi EvoBora,
Thank you for your response.
Do you have Windows 2008 Domain controller in your environment?
If so, the default behavior of the Allow cryptography algorithms compatible with Windows NT 4.0 policy setting may cause this problem. This setting prevents both Windows operating systems and third-party clients from using weak cryptography algorithms to establish NETLOGON security channels to Windows Server 2008-based domain controllers. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
http://support.microsoft.com/kb/942564
When a Windows NT 4.0-based computer tries to use the NETLOGON service to establish a security channel to a Windows Server 2008-based domain controller, the operation may fail
Best Regards,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights.
No we do not have a 2008 domain controller but I have modified that setting on the local group policy of the 2008 server with no luck.
TIA Mike- Hi Mike,
Please also disable autotuning on Windows 2008 and try again.-
Click Start , click All Programs, and then click Accessories.
- Right-click Command Prompt, and then click Run as Administrator.
If you are prompted for an administrator password or for confirmation, type the password, or click Continue. - At the command prompt, type the following command, and then press ENTER:
netsh interface tcp set global autotuninglevel=disabled - Close the Command Prompt window.
- Restart the computer.
Please have a try and let us know your result.
Best Regards,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights. -
Hi Mike,
Please also disable autotuning on Windows 2008 and try again.-
Click Start , click All Programs, and then click Accessories.
- Right-click Command Prompt, and then click Run as Administrator.
If you are prompted for an administrator password or for confirmation, type the password, or click Continue. - At the command prompt, type the following command, and then press ENTER:
netsh interface tcp set global autotuninglevel=disabled - Close the Command Prompt window.
- Restart the computer.
Please have a try and let us know your result.
Best Regards,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights.
This did work now our 95 and Nt 4 machines can see the files and navigate the server. However the NT 4 stations can open the files and read the contents. The 95 stations can not. they try and open the file and it times out or opens the txt file and it is blank.
I have logged in as an admin as well on the 95 stations and I get the same result. I double checked the security and made a new share completely will full control and still having the same result.
Any ideas? This one has me scratching my head for sure now.
TIA Mike-
