Before I didn't have this problem. All of a sudden, Windows 98/ME clients stopped logging on to my Windows Server 2003 domain. IDK why but it was perfect before and for some reason, I can't log into Windows 98 through Windows Server 2003. How do I fix this?

[Reply or follow-up to this message]

WHen did the problem start occuring?  Do you remember any software being installed? 
 How about updates?  What is the specific error you are receiving when you try to 
logon?

[Reply or follow-up to this message]

Pretty long explanation. I tried to Install Windows NT 4 on my other computer but then I can't seem to join that to the domain. I even updated that to Service Pack 6a but no solution, so maybe because the installation of Windows NT wasn't good, so I decided to go back to my Windows 98 computer to see, it gave me this message: No domain server was available to validate your password. You may not be able to gain access to some network resources. Same with my Windows ME Workstation. I think it happened a few days ago and I just found out this yesterday. I then did nslookup on my exchange server, which is my member server and it gave me this: Redir and Browser test . . . . . . : Failed List of NetBt transports currently bound to the Redir NetBT_Tcpip_{759A9B01-0856-4FBF-8349-A9FA8CC09EB0} The redir is bound to 1 NetBt transport. List of NetBt transports currently bound to the browser NetBT_Tcpip_{759A9B01-0856-4FBF-8349-A9FA8CC09EB0} The browser is bound to 1 NetBt transport. [FATAL] Cannot send mailslot message to '\\DOMAIN*\MAILSLOT\NET\NETLOGON' via redir. [ERROR_BAD_NETPATH] Domain is actually where my domain name is mentioned. When I tried to join a Windows XP Professional client, I typed in the domain and it didn't work, but I typed in the extention and it worked. I then went on my domain controller, tested NetBIOS (I forget the command I typed) and it did not display ANYTHING for my network card, the others it did. I then went on my Windows 98 client, pinged my member server, it worked but my domain controller didn't work. This is all the proof to lead maybe that's why my Windows 98/ME/NT clients won't log into my Domain, I mean it did work, but all of a sudden, it doesn't now. What seems to be the problem?


On Saturday, July 14, 2007 at 6:23 pm, appleoddity wrote:
>

>WHen did the problem start occuring? Do you remember any software being installed?
> How about updates? What is the specific error you are receiving when you try to
>logon?
>
>

[Reply or follow-up to this message]

Pretty long explanation. I tried to Install Windows NT 4 on my other computer but then I can't seem to join that to the domain. I even updated that to Service Pack 6a but no solution, so maybe because the installation of Windows NT wasn't good, so I decided to go back to my Windows 98 computer to see, it gave me this message:

No domain server was available to validate your password. You may not be able to gain access to some network resources.

Same with my Windows ME Workstation. I think it happened a few days ago and I just found out this yesterday.

I then did nslookup on my exchange server, which is my member server and it gave me this:

Redir and Browser test . . . . . . : Failed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{759A9B01-0856-4FBF-8349-A9FA8CC09EB0}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{759A9B01-0856-4FBF-8349-A9FA8CC09EB0}
The browser is bound to 1 NetBt transport.
[FATAL] Cannot send mailslot message to '\\DOMAIN*\MAILSLOT\NET\NETLOGON'
via redir. [ERROR_BAD_NETPATH]

Domain is actually where my domain name is mentioned.

When I tried to join a Windows XP Professional client, I typed in the domain and it didn't work, but I typed in the extention and it worked.

I then went on my domain controller, tested NetBIOS (I forget the command I typed) and it did not display ANYTHING for my network card, the others it did.

I then went on my Windows 98 client, pinged my member server, it worked but my domain controller didn't work.

This is all the proof to lead maybe that's why my Windows 98/ME/NT clients won't log into my Domain, I mean it did work, but all of a sudden, it doesn't now. What seems to be the problem?

[Reply or follow-up to this message]

Try pinging the domain controller by IP address, instead of netbios name from the 
Win98 machine...  Does it work?

[Reply or follow-up to this message]

Yes. That works.


On Saturday, July 14, 2007 at 7:22 pm, appleoddity wrote:
>

>Try pinging the domain controller by IP address, instead of netbios name from the
>Win98 machine... Does it work?
>
>

[Reply or follow-up to this message]

I don't have a lot of experience joining older operating systems to 2000 or 2003 
domains.. However, from what I am reading about your error, and from the fact that 
you can not ping the domain controller by name, but you can by IP address, tells 
me that the 9x machine is having trouble resolving the netbios name... 

I found this 
article about the issue.  It appears that Win9x and NT machines have to be able 
to use NetBIOS to find the domain controller on the network.. It requires a WINS 
server and special entries in the WINS server.  If this server is unavailable, they 
will not be able to contact the domain controller.  I'm not sure that pinging the 
server by name from a Win9x machine confirms this though.. Because it seems to me 
that it would use DNS to resolve the name.. So possibly it is a DNS issue too... 
Any of this sound like a possibility?  Please keep me posted on this.  

[Reply or follow-up to this message]

I set up a WINS server on my DC, tried pointing my DHCP the the WINS server, restarted my Windows 98 Client, still no luck. I mean it used to work before, how come it doesn't work now?


On Saturday, July 14, 2007 at 10:21 pm, appleoddity wrote:
>

>I don't have a lot of experience joining older operating systems to 2000 or 2003
>domains.. However, from what I am reading about your error, and from the fact that
>you can not ping the domain controller by name, but you can by IP address, tells
>me that the 9x machine is having trouble resolving the netbios name...
>
>I found this
>article about the issue. It appears that Win9x and NT machines have to be able
>to use NetBIOS to find the domain controller on the network.. It requires a WINS
>server and special entries in the WINS server. If this server is unavailable, they
>will not be able to contact the domain controller. I'm not sure that pinging the
>server by name from a Win9x machine confirms this though.. Because it seems to me
>that it would use DNS to resolve the name.. So possibly it is a DNS issue too...
>Any of this sound like a possibility? Please keep me posted on this.
>
>
>
>
>

[Reply or follow-up to this message]

There is something upon installation of server 2003 that you have to select to allow 
it to "relax" the security settings so older clients such as Win9x can work properly... 
I can't remember what those settings are now, is it possible that you moved the server 
to native mode or possibly a security patch was put on recently that would disable 
these older clients?  

Do some research on what all is involved in making Win9x clients connect to server 
2003.. I know that they fundamentally are different and certain security precautions 
can break them...

Is your 9x client able to resolve the hostname now, if you try to ping the DC by 
name?

[Reply or follow-up to this message]

Also, did you verify the "special" entries are present in the WINS server that allows 
older clients to find the DC?

[Reply or follow-up to this message]

Okay, I think that I installed Routing and Remote Access on my DC and that probably caused a problem, so I decided to disable it, as for WINS, I don't see a reason why I need it because it used to work without it, so I uninstalled that as well and then I'll have to see weather that made the change. I mean there is one error in the netdiag.exe, which is the Redir and Browser test. Maybe if I can get that to work, then my Windows 9x clients can log in. As for the Native Mode feature which I forgot to mention, I did not raise my Domain or Forest level and I know for a fact that if I did, Win9x clients will be able to log in because I tried it before in a Test VMWare environment. Any more suggestions?


On Sunday, July 15, 2007 at 10:38 am, appleoddity wrote:
>

>Also, did you verify the "special" entries are present in the WINS server that allows
>older clients to find the DC?
>
>

[Reply or follow-up to this message]

I found the solution to this problem! You just needed to Enable NetBIOS over TCP/IP. It was disabled on my Domain Controller, IDK how it got disabled.


On Saturday, July 14, 2007 at 2:22 pm, Jude Nihal Fernando wrote:
>Before I didn't have this problem. All of a sudden, Windows 98/ME clients stopped
>logging on to my Windows Server 2003 domain. IDK why but it was perfect before and
>for some reason, I can't log into Windows 98 through Windows Server 2003. How do
>I fix this?

[Reply or follow-up to this message]

I'm glad you figured it out.. I figured it was a problem with netbios seems how older 
operating system use NetBIOS to connect t the DC.

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum