Something happened in the last few days. I have a Windows 2K Active Dir Native Mode network. I have Windows 95/98/2000/XP clients. I have 5 Domain Controllers. My PDC Emulator DC (ProblemServer) that also holds Exchange 5.5 won't athenticate Widnows 95/98 clients. In fact, if the NETLOGON service is running on that DC all Windows 95/98 machines get "The domain password you supplied is not correct, or access to your logon server has been denied." If I stop the NETLOGON service the Windows 95/98 clients logon find (With the logon script and everything). Windows 2000/XP client always logon fine. If I go Start > Run, \\ProblemServer from Windows 9x I get "Cannot find \\ProblemServer". Windows 2000/XP are fine. They can go Start > Run \\ProblemServer and access shared folders. All other servers I can access from Windows 9x by going start > run \\OtherServer. I can ping for Windows 9x to ProblemServer. The only thing I can think that I added to that server this week is "Exchange 5.5 CDO Patch 2657.55" to solve an OWA problem. Any ideas? How do I log logon problems? Monitor logon problems?

"Jeff" wrote:
: Something happened in the last few days. I have a Windows 2K Active Dir
Native Mode network. I have Windows 95/98/2000/XP clients. I have 5 Domain
Controllers. My PDC Emulator DC (ProblemServer) that also holds Exchange
5.5 won't athenticate Widnows 95/98 clients. In fact, if the NETLOGON
service is running on that DC all Windows 95/98 machines get "The domain
password you supplied is not correct, or access to your logon server has
been denied." If I stop the NETLOGON service the Windows 95/98 clients
logon find (With the logon script and everything). Windows 2000/XP client
always logon fine. If I go Start > Run, \\ProblemServer from Windows 9x I
get "Cannot find \\ProblemServer". Windows 2000/XP are fine. They can go
Start > Run \\ProblemServer and access shared folders. All other servers I
can access from Windows 9x by going start > run \\OtherServer. I can ping
for Windows 9x to ProblemServer. The only thing I can think that I added to
that server this week is "Exchange 5.5 CDO Patch 2657.55" to solve an OWA
problem. Any ideas? How do I log logon problems? Monitor logon problems?

All of your DCs are W2K and above?
You're not running native IP mode now, are you?

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/service...p?fr=0&sd=tech

We have been in native mode for over a year with no
problem. All DC's are Win 2k. Evrything has been great
until 4 days ago. Last time this happened I upgraded the
NIC driver on one of the servers and the problem went
away. I upgraded everything and nothing changed.
>-----Original Message-----
>"Jeff" wrote:
>: Something happened in the last few days. I have a
Windows 2K Active Dir
>Native Mode network. I have Windows 95/98/2000/XP
clients. I have 5 Domain
>Controllers. My PDC Emulator DC (ProblemServer) that
also holds Exchange
>5.5 won't athenticate Widnows 95/98 clients. In fact, if
the NETLOGON
>service is running on that DC all Windows 95/98 machines
get "The domain
>password you supplied is not correct, or access to your
logon server has
>been denied." If I stop the NETLOGON service the Windows
95/98 clients
>logon find (With the logon script and everything).
Windows 2000/XP client
>always logon fine. If I go Start > Run, \\ProblemServer
from Windows 9x I
>get "Cannot find \\ProblemServer". Windows 2000/XP are
fine. They can go
>Start > Run \\ProblemServer and access shared folders.
All other servers I
>can access from Windows 9x by going start > run
\\OtherServer. I can ping
>for Windows 9x to ProblemServer. The only thing I can
think that I added to
>that server this week is "Exchange 5.5 CDO Patch 2657.55"
to solve an OWA
>problem. Any ideas? How do I log logon problems?
Monitor logon problems?
>
>All of your DCs are W2K and above?
>You're not running native IP mode now, are you?
>
>--
>Roland Hall
>/* This information is distributed in the hope that it
will be useful, but
>without any warranty; without even the implied warranty
of merchantability
>or fitness for a particular purpose. */
>Online Support for IT Professionals -
>http://support.microsoft.com/service...echnet/default.
asp?fr=0&sd=tech
>
>
>.
>

you should be in mixed mode


>-----Original Message-----
>Something happened in the last few days. I have a
Windows 2K Active Dir Native Mode network. I have Windows
95/98/2000/XP clients. I have 5 Domain Controllers. My
PDC Emulator DC (ProblemServer) that also holds Exchange
5.5 won't athenticate Widnows 95/98 clients. In fact, if
the NETLOGON service is running on that DC all Windows
95/98 machines get "The domain password you supplied is
not correct, or access to your logon server has been
denied." If I stop the NETLOGON service the Windows 95/98
clients logon find (With the logon script and
everything). Windows 2000/XP client always logon fine.
If I go Start > Run, \\ProblemServer from Windows 9x I
get "Cannot find \\ProblemServer". Windows 2000/XP are
fine. They can go Start > Run \\ProblemServer and access
shared folders. All other servers I can access from
Windows 9x by going start > run \\OtherServer. I can ping
for Windows 9x to ProblemServer. The only thing I can
think that I added to that server this week is "Exchange
5.5 CDO Patch 2657.55" to solve an OWA problem. Any
ideas? How do I log logon problems? Monitor logon
problems?
>.
>

"Jeff" wrote:
: We have been in native mode for over a year with no
: problem. All DC's are Win 2k. Evrything has been great
: until 4 days ago. Last time this happened I upgraded the
: NIC driver on one of the servers and the problem went
: away. I upgraded everything and nothing changed.

Jeff...

I think you misunderstood my question. Native/Mixed mode is different than
native IP/NetBIOS over TCP/IP mode. Windows OS, prior to W2K, can only use
NetBIOS over TCP/IP, even though it says TCP/IP. Native IP is what *nix
uses unless they're running SAMBA.

Native/Mixed mode relates to the make up of your DCs (domain controllers).
Mixed mode means you have W2K/3 and NT4 DCs. Native Mode means they're all
W2K/3. Both of these can serve Win9x/ME/NT/W2K/XP clients. In Native IP
mode, ONLY W2K and above clients can communicate with the servers.

This is why I made sure I said Native IP mode and not just Native mode.

RE: your response... Do you recall, last time this happened, if you had
upgraded or installed something that required you also upgrade a NIC driver?
Servers do not normally just stop working unless something has changed
somewhere that requires and update unless it has to do with capacity, i.e.
disk space, traffic, etc.

HTH...

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/service...p?fr=0&sd=tech

Oh, I see. I added an update to the OWA because it kept
crashing, I would reboot the server, and it would be fine
for a day. I added:

http://www.microsoft.com/downloads/details.aspx
FamilyId=B106C749-71F8-44CC-86CF-
AB5CDA169127&displaylang=en

Then people with Win 9x started complaining. The wierd
thing is them (Win 9x not Win 2k)not being able to go
Start > Run \\ServerName. They can do that to any other
server but that. It is the PDC emulator. The patch I
installed doesn't come with a uninstall. Help. Last
time this happened I updated the NIC driver (on the
server) and it worked. Is there like a sniffer tool that
is good to see what is happening? How about NetDiag?

>-----Original Message-----
>"Jeff" wrote:
>: We have been in native mode for over a year with no
>: problem. All DC's are Win 2k. Evrything has been
great
>: until 4 days ago. Last time this happened I upgraded
the
>: NIC driver on one of the servers and the problem went
>: away. I upgraded everything and nothing changed.
>
>Jeff...
>
>I think you misunderstood my question. Native/Mixed
mode is different than
>native IP/NetBIOS over TCP/IP mode. Windows OS, prior
to W2K, can only use
>NetBIOS over TCP/IP, even though it says TCP/IP. Native
IP is what *nix
>uses unless they're running SAMBA.
>
>Native/Mixed mode relates to the make up of your DCs
(domain controllers).
>Mixed mode means you have W2K/3 and NT4 DCs. Native
Mode means they're all
>W2K/3. Both of these can serve Win9x/ME/NT/W2K/XP
clients. In Native IP
>mode, ONLY W2K and above clients can communicate with
the servers.
>
>This is why I made sure I said Native IP mode and not
just Native mode.
>
>RE: your response... Do you recall, last time this
happened, if you had
>upgraded or installed something that required you also
upgrade a NIC driver?
>Servers do not normally just stop working unless
something has changed
>somewhere that requires and update unless it has to do
with capacity, i.e.
>disk space, traffic, etc.
>
>HTH...
>
>--
>Roland Hall
>/* This information is distributed in the hope that it
will be useful, but
>without any warranty; without even the implied warranty
of merchantability
>or fitness for a particular purpose. */
>Online Support for IT Professionals -
>http://support.microsoft.com/service...echnet/default
..asp?fr=0&sd=tech
>
>
>
>.
>