Server 2008 and Windows 95.

[Albion]

So I have a bunch of big cutting tools in my shop that are using Windows 95 on their PC based control. I cannot upgrade these machines because the control software is DOS 6.22 based and Win95 is the latest OS that will still run it, not to mention that the hardware control is a 16bit ISA card that doesn't have drivers for XP and above. And thirdly the DOS control software MUST be able to communicate directly to that ISA card, so no HAL.

Anyway.

I just upgraded my Server 2003 environment to Server 2008. The problem is when I try to copy files from the server file system to Win95 I get timeouts and disconnects from the drive mapping. Microsoft has informed me that 9x OSs will most likely not work with 2008.

I can keep a Server 2003 machine on the network as a domain controller, but is there a way to force those Machine Tools to log into that domain controller only? Or am I going to have to set up an entirely new domain for those 95 machines?

Thanks

-Craig

 

[Davetoo]

http://www.google.com/search?source...96&q=specify+domain+controller+to+logon+&aq=f

First link.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!

 

[Albion]

Yes I read that post. The only part of it that's anywhere close to what I need is the subject of the message itself.

I've found that the problem lays in the 2008 file system. When the 2008 server authenticates and tries to give the login script to the 9x workstation, the workstation is not able to read the script from the sysvol share. For some reason 9x OSs can't read from 2008 shares.

But I can toss a 2003 DC onto my domain. If that 2003 DC is the authenticating server the workstation is able to read from sysvol share on that DC and run the login script. The problem is forcing the workstation to authenticate from that 2003 DC only.

 

[kmcferrin]

It's a total hack, but you could create a new site in AD, and define a separate subnet for those Win95 machines that are is a part of that site. Then move that DC into that site in AD Sites and Services. This won't guarantee that they always authenticate to the 2003 DC, but they will authenticate to them by default. It would only try to hit another DC if the 2003 DC were down.

________________________________________
CompTIA A+, Network+, Server+, Security+
MCSE:Security 2003
MCITP:Enterprise Administrator

 

[baddos]

Is it the new authentication setting changes in windows 2008 and not the actual shares/file system? I know there is some NTLM changes in active directory that disables some Win9x authentication types, but I don't exactly remember what it is. You can change this to allow older clients in default domain controller group policy.

 

[itsp1965]

Do you already have the AD Client Extensions installed on your Win95 box? I know they had it available for Win98 and NT so it may/may not work for you. Also it's pretty old so I don't know if it would work with Win2K8. Take a look to see if it helps

http://support.microsoft.com/?kbid=288358

 

[Albion]

Yeah, I have the AD client on my 95 boxes. I have a 2003 member server on my Domain and I can map it's shares no problem at all. It seems that all the servers will authenticate, but when it comes to seeing files on shares in 2008 (login script in sysvol for instance) I'm stuck. I can see the share, I can map the share, but when I try to do anything with it I get timeouts and errors.