Click OK twice to logon

[Guest]

I have a small network with a NT 4.0 Server running TCP/IP and 30 98SE
clients. Every so often a client will not logon to the network without
pushing enter twice or clicking OK twice. The password turns blue the first
time then logons on the second time. So far if I format the hard drive and
reinstall windows everthing works. I am getting tired of this. Can anybody
point me into the right direction?

 

[Herb Martin]

I have a small network with a NT 4.0 Server running TCP/IP and 30 98SE
clients. Every so often a client will not logon to the network without
pushing enter twice or clicking OK twice. The password turns blue the
first
time then logons on the second time. So far if I format the hard drive and
reinstall windows everthing works. I am getting tired of this. Can
anybody
point me into the right direction?

Since this doesn't usually happen for everyone else, my
first advice would be to STOP reinstalling Windows.

Such action is seldom required for any problems and
likely you are just getting an apparent fix accidentally.

Chances are good that you have some sort of network,
possibly DNS issue, but this doesn't fit the usually
scenarios where DNS would be an almost certainty.

Maybe network hardware or drivers, perhaps something
as simple as BAD "drop cables" (which are much flakier
than most people realize.)

Below is a guide for checking DNS but you might easily
have some other problem...

--
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /serverC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]

 

[Guest]

Nice of you to use the forum to hawk you products, but there is no AD or DNS
so to speak in NT 4.0. This is a simple logon to the network problem. At this
point I have to do what works.

I have a small network with a NT 4.0 Server running TCP/IP and 30 98SE
clients. Every so often a client will not logon to the network without
pushing enter twice or clicking OK twice. The password turns blue the
first
time then logons on the second time. So far if I format the hard drive and
reinstall windows everthing works. I am getting tired of this. Can
anybody
point me into the right direction?

Since this doesn't usually happen for everyone else, my
first advice would be to STOP reinstalling Windows.

Such action is seldom required for any problems and
likely you are just getting an apparent fix accidentally.

Chances are good that you have some sort of network,
possibly DNS issue, but this doesn't fit the usually
scenarios where DNS would be an almost certainty.

Maybe network hardware or drivers, perhaps something
as simple as BAD "drop cables" (which are much flakier
than most people realize.)

Below is a guide for checking DNS but you might easily
have some other problem...

--
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /serverC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Lanwench [MVP - Exchange]]

In

I have a small network with a NT 4.0 Server running TCP/IP and 30
98SE clients. Every so often a client will not logon to the network
without pushing enter twice or clicking OK twice. The password turns
blue the first time then logons on the second time. So far if I
format the hard drive and reinstall windows everthing works. I am
getting tired of this. Can anybody point me into the right direction?

I suggest you try posting in a more relevant group as this one is for
Win2000 issues. Try crossposting to an XP and NT group....good luck.