9x Machines in a 2003 Domain

[Aleyda Solis]

I have problems when I try to authenticate the 95, 98 and Me machines to a Win2003 Domain Controller, I get a message saying that they cant find the domain to logon. And checked this issue and it has been reported to work if you install the active directory client at the machines and disabling the SMB authentication at the server policy, things that I have already tried, ut it still doesnt work :( ... what can I do ??

[Roger Faucher]

Aleyda:

This article talks about how to 'Allow Lan Manager Authentication' which is required for WIN9x/Me clients:

http://support.microsoft.com/default.aspx?scid=kb;en-us;826157&Product=winsvr2003

HTH

Make a great day!

Roger

[Aleyda Solis]

Thanks very much for the answer, but I think it doesnt apply to my situation because im inside a LAN.. and all the ports needed are opened, and is not a communication problem because I dont have any problems with the 2000/XP machines ... :( that article is about machines that are using remote access server :( or Internet authentication service

[Roger Faucher]

Have you inserted the domain name in the networking properties? Have you tried logging in with a username/password known to work at the domain controller console?

Roger

[Aleyda Solis]

Yes, I configure the TCP/IP settings, with the name of the domain, and I checked the dns configuration, the wins, and is all OK, plus I added the client for microsoft network with the domain name, but still doesnt work ... :(

[Aleyda Solis]

I forgot to tell that I already tried to logged myself to 9X machines with the domain admin username so Im sure the user is not a problem.

Thanks ! :)

[WebWalker]

Hi,
the problem could be the name of the domain witch you join the windows 98 machine to.
Just type the second level domain name without the first level (e.s. withou .com or .local)
Check the attachment...

I have many win 9x client and it works fine...

Make a great day...

[Aleyda Solis]

Yes, I have tried with the netbios name of the domain too... but it didnt work neither.. :(

[Roger Faucher]

Have you tried to PING the DC from the WIN9x clients and does that work? Are you using DHCP server and if so, where does it reside (in the DC, or elsewhere)?

I'm sorry I'm reduced to grasping at straws.

Roger

[Aleyda Solis]

We cant ping because the 9x clients are in a different subnet and because of security matters long ago the communications specialist just let to do ping to the proxy servers between the subnet and the domain controller. He also had to open these ports at the PIX Firewall at the beginning:

· Microsoft-DS traffic (445/tcp, 445/udp)

· Kerberos authentication protocol (88/tcp, 88/udp)

· Lightweight Directory Access Protocol (LDAP) ping (389/udp)

· Domain Name System (DNS) (53/tcp, 53/udp)

And it worked OK the first time I tried to authenticate the 9x clients and the NT ones too. Im going to check with him if he closed something at the Proxy servers or the PIX, but I dont think so.

[Norman_21]

If the firewall administrator didn't do any changes that might have blocked the connectivity to the DC, then you best bet is to upgrade your Win9x to WinXP. It'll be helpful in the long run anyway.
That's actually what we have done here in the Corp.

Good luck

[Jasper Tiggelaar]

Since the Win9X clients are on a different subnet than the domaincontrollers, WINS will be used to locate a domaincontroller. Your Win9X network configuration should have the netbios domain name as domain name (properties of the client for microsoft networks).

You say you have checked the Wins settings. Also check that Wins traffic can pass between Win9X client and WINS server and that your domaincontrollers are WINS clients of this particular WINS server. (Wins netbios over tcp/ip uses UDP port 137 to communicate, see http://www.microsoft.com/windows2000/techinfo/reskit/samplechapters/cnfc/cnfc_por_simw.asp)

A less managable solution to your problem is editing the lmhosts file on the Win9X clients. Example:
102.54.94.97 dino #PRE #DOM:yourdomain

This tells your Win9X client to preload (#pre) this entry, that server 'dino' is located at 102.54.94.97 and that it is a domaincontroller for 'yourdomain' (again the netbios domain name of your AD-domain)

Or perhaps your machines already have a lmhosts file entry for 'yourdomain' pointing at the wrong IP addresses for domaincontrollers.

Hope this solves your problem.

[Ann Gregory]

I know this is late. Have just read this problem. Microsoft provides an executable for 9x machines. dsclient95 and dsclient98 that will fix this problem with win2003 domains.

[Norman_21]

Hello Aleyda,

Do you have the hot fix Q323466?
Check out this MS KB, it addresses your issue:
http://support.microsoft.com/default.aspx?scid=kb;en-us;555038

Please keep us updated
Latif