I'll give that a try. Yes, we realize that the situation is dire. We have attempted more than once to replace it, and are in the process of yet another search for a solution. In the meantime ...
We have gone so far as to build (and test) plans for operation should the system fail irrevocably. --BM On Tue, Jan 20, 2009 at 2:46 PM, Kurt Buff <[email protected]> wrote: > Heh. > > You've most likely run into the difference between NTLM on NT4 vs. Win2k+. > > The only workaround I've been able to implement is to create a local > account on the file server. IIRC, you have to do some fiddling with > security policies on the file server as well - something about > signing, I think. That really degrades your network security. > > Or, you could try running the application under WINE on *nix - I just > grepped /usr/src/ on my FreeBSD box, for instance, and find that > there's an SMC driver for arcnet there. > > But, it's really time to tell the owners of the business to move on - > something in the hardware chain is going to die soon, and then they'll > really be stuck. > > On Tue, Jan 20, 2009 at 2:13 PM, Bill Monicher <[email protected]> wrote: >> Hi, >> To anticipate the objection, yes it must be W95. >> The reason is complex, but the machine is doing machine control work >> using Arcnet. There are no Arcnet drivers for later OSs. >> >> Currently, the machine is in a workgroup that has the same name as an >> NT 4 domain. They are the last two machines that show up on the NT4 >> DC's Server Manager applet. >> >> The shares exist on a server in a W2K domain, which trusts (and is >> trusted by) the NT4 domain. >> If I log on locally to the W95 box, I can access resources on the >> server, but ONLY IF THE NT4 PDC IS RUNNING. >> >> Can I not somehow configure a W95 machine to access resources on a W2K >> domain? >> >> Any ideas would be appreciated. >> >> When the NT4 PDC is down, I get: >> Error 2215 The logon server cannot be found. >> >> Even with Everyone:C permissions set on the share, I get >> The password is invalid for \\XBRQLZ1\TESTBM. For more information, contact >> your network administrator. >> >> >> I have tried: >> Putting the machine in a workgroup called WORKGROUP. >> Logging on as a different account. >> >> Thanks, >> --BM >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
