gadget Posted October 3, 2005 Posted October 3, 2005 Hi,I have a windows server 2003 system and it is a member server in a windows 2000 active directory.What I need to do is connect Ms-Dos clients to a network share using a local account created on the 2003 box.I have acheived this before but like a numb, I lost the documentation. For the life of me I cannot duplicate the process.Can anyone suggest the local policies on the server/domain I need to adjust?
I_Broke_My_MHZ Posted October 3, 2005 Posted October 3, 2005 Do you have trouble configuring the server to allow it or the clients to connect to the share? Can you give more info on what version of DOS you have on them, and any other programs?
InTheWayBoy Posted October 3, 2005 Posted October 3, 2005 Was looking into something totally unrelated and came by this:RISME and CMS allow you create DOS-based boot image to access resources on Windows-based servers such as Windows NT, 2000 and 2003 server. By default, Windows 2003 server does not allow DOS-based clients to access shared resources. This document explains how to configure your Windows 2003 server to allow access by legacy clients. Windows 2003 (formerly Windows.NET) is much more secure "out-of-the-box" than prior version of the Windows NT family. As a result, legacy clients such as DOS, Windows 3.x, and Windows 95 that use NTLM method of authentication may not be able to logon by default. Steps: To correct this problem, you should do the following: 1. Click Start, point to Programs, point to Administrative Tools, and then click "Default Domain Controllers Policy". If your server is not a domain controller, open Local Security Policy instead 2. Go to the following location: Windows Settings\Security Settings\Local Policies\Security Options 3. If any of the following policy settings are set to Enabled, double click the setting, click to select the "Define this policy setting" check box, click Disabled, and then click OK. Domain Member: Digitally encrypt or sign secure channel data (always) Microsoft Network Server: Digitally sign communications (always) 4. Reboot the server.Sounds like something you might need to think of...hope that helps!
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