Archived from groups: microsoft.public.win2000.file_system (
More info?)
Hi there Val
First of all, thanks for response... then again, tried the solution as described. Didnt work out though. Signing is of at def domain policy and we only apply it at the top so i know that it wont get reapplied below in ad structure. Also verified that win98 poledit got running but with no success in regards to the error.
Seems to be that somethings interfeers with the saving function of the xls file as I can see that it creates a temp file. Tried to disable any "kernel filters" that might scan it upon save. Now I am down to 6 native Win2003 filters, which I cant disable or the server will BOD.
Seems as many are expierencing this problem though.
/Regards
"Val" wrote:
> Hi Lars!
>
> Maybe this will help you?
>
> --
>
> Val
>
> ----
>
> From: "Frank" <anonymous@discussions.microsoft.com>
> Sender: "Frank" <anonymous@discussions.microsoft.com>
> Subject: problems w/ 98 Clients
> Date: Thu, 18 Dec 2003 15:42:21 -0800
>
> Hey Gang,
>
> I have been reading through the threads on this in several
> MS newsgroups and posted messages in those newsgroups
> requesting assistance. I have been dealing with this
> problem since Monday and have been feverishly researching
> a solution.
>
> Here is what I have come up with so far:
>
> 1. At the Windows Server 2003 system, Enter at a cmd
> prompt: net config server /autodisconnect:-1
>
> 2. For Windows 95 workstations, do the following at the
> Windows Server 2003 system:
> Default Domain Policy: Account Lockout Threshold,
> increase to 15 or more.
> Default Domain Policy: Microsoft Network Clients ..
> Digitally Sign Communication Always - Set to Disabled
>
> 3. For Windows 98SE / ME / NT4.0 clients, check out the
> following:
> support.microsoft.com/default.aspx?scid=kb;en-us;814598
>
> I would appreciate knowing if these solutions worked for
> you.
>
> Regards,
>
> Frank
>
> >>-----Original Message-----
> >>We have a network with 3 different servers, a Novell
> >>Netware 5.0 server, a Windows Server 2000, and a new
> >>Windows Server 2003. I am using the most current Novell
> >>client for all workstations including my 98
> >workstations.
> >>The 2003 server is a domain controller. It is the only
> >>domain controller on the network. The clients are a
> >>mixture of Windows 98 & 98 SE, Windows 2000 and Windows
> >>XP. I have all my 2000 and XP clients logging onto the
> >>domain successfully.
> >>
> >>The problem I am seeing seems to only be happening on
> the
> >>98 & 98 SE clients. If I log onto the domain on the 98
> >>clients, after the Novell login, after a long delay, I
> >>receive the following error. "The domain password you
> >>supplied is not correct, or access to your logon server
> >>has been denied." Most of the time I can give about a
> >>minute or 2, respond OK, and then when the MS login
> >screen
> >>comes up, I try logging in again with the same User
> name,
> >>password and domain name, and it connects with no
> >problem.
> >>On occasion it takes several attempts before
> successfully
> >>logging in. Even if I am not logging into the domain and
> >>just mapping my 98 clients to a shared drive on the same
> >>server, I get the same results when the workstation is
> >>reconnecting to the mapped drive at startup. There will
> >be
> >>a long delay and then it will be unable to complete the
> >>mapping. If the user cancels during the mapping attempt,
> >2
> >>or 3 minutes later it will connect in the background.
> >>
> >>On a suggestion from another tech, I have installed the
> >>Windows 9x, DS client for Active directory services
> >>(found on the Win2k server cd) and it didn't seem to
> >help.
>
>