OK. You mentioned that you disabled forced SMB signing. I would check the
Local Security Policy on the W2003 domain controller to make sure it shows
as being disabled for Microsoft network server:digitally sign
communications(always). If it is not open Domain Controller Security Policy
on that domain controller and disable it there and then refresh policy with
"gpupdate /force" and then check Local Security Policy to make sure it shows
as being disabled. Also on one of the W98 computer modify the registry to
allow the use of ntlmv2 and SMB signing to see if that helps as described in
the links below.
http://support.microsoft.com/default...;en-us;Q239869
http://support.microsoft.com/default...b;en-us;230545
Beyond that refer to the KB link below and read up on security setting
incompatibilities that may be causing the problem. In particular review all
the settings that refer to "anonymous" access. I would suggest that you
configure to enable anonymous be part of everyone group at least until
problem is resolved and loosen restrictions on other anonymous access as
part of your troubleshooting. Be sure to document your changes from default
and refresh policy after each change. Another thing to check is that your
W2003 Server is current with critical updates. --- Steve
http://support.microsoft.com/default...b;en-us;823659
"Chuck Welch" <(E-Mail Removed)> wrote in message
news:046783E8-2095-4BCB-9E07-(E-Mail Removed)...
> It is a domain controller and has taken the role of global master.
> "Steven L Umbach" wrote:
>
>> Where does the Windows 2003 Server fit in? Is it a print server, domain
>> controller, etc?? -- Steve
>>
>>
>> "Chuck Welch" <(E-Mail Removed)> wrote in message
>> news:ADFB457D-27DC-4CAA-BCA5-(E-Mail Removed)...
>> > Netowork Desc: 1 windows 2003 server and 2 win2k servers approx 40
>> > win98
>> > machines. Some win98 boxes share printers for their area of the
>> > building
>> > All worked well until the 2003 was added to the network. Since adding
>> > the
>> > 2003 to the network,quit often people when people print, they recieve
>> > the
>> > error:
>> > "There was an error printing to \\machinename\printersharename on
>> > printer
>> > sharename due to an unknown internal system error. The printer will be
>> > placed offline. Please reboot and try printing again."
>> >
>> > All of the win98 machines have dsclient.exe install and there are no
>> > problems with file shareing or accessing other resources on the
>> > network.
>> > DNS
>> > is set up properly as far as the DHCP server goes. I tried disabling
>> > SMB
>> > Signing and left it off for 24hrs and problem continued. I disabled in
>> > domain policy Digitally sign communications. I also have netbios over
>> > tcp/ip
>> > enabled.
>> >
>> > Next, if I go to c:\windows\spool\printers and delete all of the
>> > spooler
>> > files, the printer instantly start printing again. I have had the
>> > folder
>> > open
>> > and had someone send a print job and watch multiple files appear, but
>> > not
>> > all
>> > of them disappear. I am not sure if the spool files should always
>> > delete
>> > when the job is finished printing.
>> >
>> > I have been totally stumped by this for 1.5 weeks now and am looking
>> > for
>> > suggestions.... any suggestion and I am willing to try anything to make
>> > this
>> > problem go away. IF anyone can suggest anything please post. I will
>> > be
>> > notified as replys are added.
>> >
>> > Thanks
>> > Chuck Welch
>>
>>
>>
Similar Threads
Linear Mode
