Windows 2003 SP1 denies access from DOS client

After installation of SP1 on Windows 2003 Standard server a DOS client
can no longer login.

- Before SP1, the DOS client (Microsoft networking client v3.0) had
consistently logged in to this simple domain controlled by the Windows
2003 server.

- Same computer was also connecting to Windows 2003 server when booted
into Windows 98 SE.

- Immediately after installation of SP1 on the Windows 2003 server,
when booted into DOS, the DOS client on this computer could not login
to the domain, though the same computer is still able to connect and
logon when booted into Windows 98 SE. The error message that the DOS
client receives is "#5: Access denied".

Here are the settings on the server:

The Windows Firewall is disabled on the Windows 2003 SP1 server and no
other firewalls are loaded on it.

On the Windows 2003 SP1 server, the following Local Policies/Security
Options are set:
Domain member: Digitally encrypt or sign secure channel data
(always) Disabled
Domain member: Digitally encrypt secure channel data (when
possible) Disabled
Domain member: Digitally sign secure channel data (when
possible) Disabled
Domain member: Require strong (Windows 2000 or later) session
key Disabled
Microsoft network client: Digitally sign communications
(always) Disabled
Microsoft network client: Digitally sign communications (if server
agrees) Enabled
Microsoft network server: Digitally sign communications
(always) Disabled
Microsoft network server: Digitally sign communications (if client
agrees) Disabled
Network security: LAN Manager authentication level
LM & NTLM responses

Network security: Minimum session security for NTLM SSP based
(including secure RPC) clients No minimum
Network security: Minimum session security for NTLM SSP based
(including secure RPC) servers No minimum

In both the Domain Controller Security Policies and the Default Domain
Security Policies: All items corresponding to the above Local Policies
are set to "Not Defined'.

Except for the LAN Manager authentication level, I have tried setting
these to "Disabled" on the domain policies, with no success.

Info about the LAN:
The LAN consists of this Windows 2003 SP1 Server as the sole server on
a domain with 30 user licenses and 8 PC's, most of which are Windows 98
SE, some Windows XP Home/Pro, one Windows 2000 Pro. Periodically, the
Windows 98 SE computer is re-started into DOS to run an application
that requires a pure DOS environment. This computer was logging into
the domain via the Microsoft DOS networking client v3.0 until the
installation of SP1 on the Windows 2003 server. No other known changes
were made at the server or the DOS client.

Are there any other settings that I should try?

Tim

.

Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: MS and security: good effort but no cigar
    ... And last but not least, no fat, no dos, no multiboot. ... build upon the progress it's already made in security. ... a Windows system, it is still surprisingly easy to completely own that ... Then there's the issue of poorly secured server applications. ...
    (microsoft.public.windowsxp.general)
  • Re: after installing KB011829 OWA is not working anymore
    ... Based on my research, after you install hotfix KB911829, I suggest we ... Profile WMI Provider to each client computer that is running Windows Vista ... If you are running the Premium Edition of Windows Small Business Server ...
    (microsoft.public.exchange.connectivity)
  • Re: DHCP Issues. Very strange
    ... I understand the issue to be: some client computers ... can not obtain IP from SBS server. ... it is most possible a client side issue of Windows ... since you have join it to SBS domain and the Windows XP SP2 ...
    (microsoft.public.windows.server.sbs)
Loading