I am trying to get a piece of equipment in a machine shop (anilam 5300mk) that has a network card built in, to see a shared folder on the network. I have spent DAYS on the phone with their tech support person, who seems to understand their equipment quite well, but not necessarily "modern" systems or networks. This mill machine boots into a flavor of DOS, starts it's network drivers, then has a program (written for DOS) that runs the machine. The network drivers all seem to be working. First, I made sure that the server is in the C:\Net\Hosts and C:\Net\Lmhosts files. Pinging the server is successful . However, when I try the command: Net Use G: \\frodo\Fryer user:Fryer /yes I get the error message - "Error 5: Access has been denied" Which is better, but still not success. Attached is the security log from the server (frodo). It shows that the Anilam (machine name is \\mill) *IS* trying to connect to the server, but is being rejected. To test things, I created an account on a WinXP computer w/ the username of Fryer. I SUCCESSFULLY mapped the network drive \\frodo\Fryer (using the same password I've been using on the Anilam, of course). Which means the userid/password on the server is fine. In this case, the server is a Win2008 server. What am I missing? Additional: If I create a "fryer" account and a sharename on a WinXP box, the "Net use" command works. Which tells me there is something about mapping to the share on the Win2k8 box.... Security message: Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 1/21/2011 11:43:23 AM Event ID: 4625 Task Category: Logon Level: Information Keywords: Audit Failure User: N/A Computer: frodo.mydoman Description: An account failed to log on. Subject: Security ID: NULL SID Account Name: - Account Domain: - Logon ID: 0x0 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: FRYER Account Domain: Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc000006a Process Information: Caller Process ID: 0x0 Caller Process Name: - Network Information: Workstation Name: \\MILL Source Network Address: mill-ipnumber Source Port: 46621 Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" /> <EventID>4625</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2011-01-21T17:43:23.136Z" /> <EventRecordID>5655558</EventRecordID> <Correlation /> <Execution ProcessID="692" ThreadID="796" /> <Channel>Security</Channel> <Computer>frodo.mydomain</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-0-0</Data> <Data Name="SubjectUserName">-</Data> <Data Name="SubjectDomainName">-</Data> <Data Name="SubjectLogonId">0x0</Data> <Data Name="TargetUserSid">S-1-0-0</Data> <Data Name="TargetUserName">FRYER</Data> <Data Name="TargetDomainName"> </Data> <Data Name="Status">0xc000006d</Data> <Data Name="FailureReason">%%2313</Data> <Data Name="SubStatus">0xc000006a</Data> <Data Name="LogonType">3</Data> <Data Name="LogonProcessName">NtLmSsp </Data> <Data Name="AuthenticationPackageName">NTLM</Data> <Data Name="WorkstationName">\\MILL</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x0</Data> <Data Name="ProcessName">-</Data> <Data Name="IpAddress">mill-ipaddress</Data> <Data Name="IpPort">46 621</Data> </EventData> </Event>

Hello, a pure DOS OS doesn't work together with SMB settings required from Windows server 2003 and higher OS versions anymore. That's the reason you get access denied. If you really like to lower the security see here: http://support.microsoft.com/kb/823659 http://support.microsoft.com/kb/555038/EN Also important is after changing the "Network security: Do not store LAN Manager hash value on next password change", you have to reset the user password for existing users, otherwise you are not able to logon from DOS machines.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.