Re: Windows 98 getting stuck logging into a W2K3 domain.

From: Pegasus \(MVP\) (I.can_at_fly.com)
Date: 02/08/04


Date: Sun, 8 Feb 2004 11:15:37 +1100


"Bloke at the pennine puddle (Replace n.a.v.d with vodafone.net.)"
<news006ddes@n.a.v.d> wrote in message
news:irta20tbs0htnvbdfucvov0g6366muumrm@4ax.com...
> The good news is that the symptoms are all the same. As a temporary
> workaround I've turned off Windows 98's ability in Client for MS
> networks to validate usernames and passwords.
>
> The problem is that at random times Windows 98 pops up a message on
> login stating that the domain can not be found, or wrong password.
> Sometimes the account gets locked out on the server. Yes, directory
> services client for 9x is installed.
>
> Now, turning off the login to domain option on Client for MS networks
> allows the workstation to login, but here lies a problem with
> remembered driver letter mappings, because login scripts only run when
> Client for MS networks does the password validation.
>
> What happens is that the dialogue (`Quick login` used) shosing the
> drive letter is being mapped shows and, just hangs.
>
> I can get past this by clicking on cancel, then `Start` and then `Log
> off`. At this poing I'm returned to the Windows login dialogue and
> possibly an imcomplete dialogue behind that which tries to tell me
> that the next drive letter in line can't be mapped.
>
> Logging into Windows a second time works perfectly.
>
> Client and server communications signing is disabled on the Windows
> 2003 server within group policies.
>
> Windows 95 seems to not to suffer from this problem. Windows 2000
> Professional works perfectly.
>
> BEcause of a legacy application, I don't have a choice and the
> machines running Windows 95 and WIndows 98 have got to stay. The
> legacy application will be redesigned, but this will not be for a
> number of months.
>
> Can anyone help me with this annoyiong problem? I would really like
> Win9x to validate the login to the domain and also have the facility
> of using login scripts as they are supposed to be used.
>
> In a nut shell, I'm stumped. I've never need this sort of behaviour
> before.
>
> HELP!!!!!

I have seen a few Win98 machines before that would intermittently
fail to get domain validation. Rather than trying to solve the problem,
I walked around it, by telling the machine NOT to get domain validation,
and by placing this batch file into the Startup folder:

@echo off
\\YourPDC\Netlogon\YourNetlogon.bat

This will get you the usual drives mapped. The only thing you will
miss is central password administration: If the password changes
then you will have to change it manually on the domain controller
and on the Win98 machine.



Relevant Pages

  • Re: Windows Login
    ... perfect...no public DNS servers used internally at all. ... We manage several hundred client networks. ... Windows XP desktops, Exchange 2003, WSUS deployments SQL, etc. ... CTRL-ALT-DEL, select Logoff, and RE-login, and they can login ...
    (microsoft.public.windows.server.setup)
  • Re: AutoLogin
    ... I understand that you may want to configure your Windows XP client to ... I would like to confirm whether you type the user2 ... but this login does not appear on the ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Windows Login
    ... We manage several hundred client networks. ... Windows XP desktops, Exchange 2003, WSUS deployments SQL, etc. ... CTRL-ALT-DEL, select Logoff, and RE-login, and they can login ...
    (microsoft.public.windows.server.setup)
  • Re: Policies Not Applying
    ... Are your test clients using Windows XP or Windows 2000? ... Are there any errors in the application log on the client machine ... AllUsers has a login script assigned in the User ...
    (microsoft.public.win2000.active_directory)
  • Re: How much is to much? Why should my clients have to pay again?
    ... Q. " I have one client that is going to look for a new tech because she doesn't ... The Windows Genuine Advantage validation check process ... does not complete when you try to validate your copy of Windows XP ...
    (microsoft.public.windowsupdate)