Discussion Locked

Mysterious Rights Issue

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

OK, here's the scenario:

My client has a DOS application loaded on an NT 4.0 workstation. All the NT workstations in the office log-on to an NT 4.0 server. This particular application is run by the other NT workstations via a peer-to-peer mappingto the target workstation.

The app (an insurance rating program) calculates a premium and prepares a print file to print the resulting quote. However, on all the workstations the application bails out when it tries to calculate the premium UNLESSthe user is logged-on as the domain administrator or is running the application at the workstation it's loaded on.

One other clue, it runs fine from a Windows 98se workstation mapped to the target workstation. I believe I have the Win98 machine authenticating to the NT domain.

I've tried adding the users to the NT Administrators group, both at the target workstation and at the server, to no avail.

This appears to be a rights issue, but why would administrator rights AT THE SERVER have anything to do with an application running ON A WORKSTATION?

So far, the folks at the insurance company that wrote the application can't figure it out, either, but I'm hoping a Tech Republic member can --- and I'm more than willing to offer the points to do it.

5 replies

by raffi_

I would humbly suggest that you need to check to see where the application (a DB?) is keeping it's temp files.

SF

by artcabot

This had already been checked. Turned out to be as simple as going to the app via a PIF instead of a shortcut directly to the DOS executable. Once again the KISS principle prevails!

by artcabot

I'm going to try and test these today. The support folks that wrote the app have yet to be very helpful; I wish they'd just let me talk to the programmers but I suspect that this thing is so old there may not be any programmers who really know it anymore. I don't think ODBC is involved, though, for the same reason, age of the application.

I'll let y'all know when (and if) I find a solution. Meantime, any more input is certainly welcome.

This discussion is closed to new replies.