1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

windows 2003 server trusting issues?

Discussion in 'Windows Server System' started by katrix, 2005/11/02.

  1. 2005/11/02
    katrix

    katrix Inactive Thread Starter

    Joined:
    2005/11/02
    Messages:
    1
    Likes Received:
    0
    Alright I'll try to explain this the best I can.

    working conditions:
    Windows 2003 standard edition (server)

    Windows 2000 (client)

    We have this new application called Taske installed on one of our server, its dedicated for that one application. We are running a windows 2003 Domain controller as well with Active Directories.

    The problem:
    The Taske application is accessed through the network via client application (station). We installed the application on the client station as an Administrator, the install went well no problems. But now when the user logs into the computer under their domain name to access the application it doesn't allow them too. After much troubleshooting it turns out its only one file that can't be accessed its called Toolbox.cde

    We have tried to make the user the admin on the locaal machine that the didn't solve the problem. It turns out that the only way that user can access the file and run the application properly is to make the user a "domain admin" now for obvious reason we are not going to make the user a domain Admin.

    I hoped i have done my best to explain please let me know if there is anything else i could post to help me troubleshoot this.

    in advance i appericate all the help.
     
  2. 2005/11/02
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    It sounds like Toolbox.cde [or some other supporting file(s)] on the server may be causing the problem.

    Try giving Everyone rights to that file and possibly to the entire folder. Read & Execute would be the first thing I'd try and if that doesn't help, add write and then modify just in case the app is coded to make little changes from user activity.

    Also try doing the same to the client piece on the workstation and if necessary, go all the way up to Modify access there. This should enable you to make the users back to users or, at most, power users on their workstations.
     
    Newt,
    #2

  3. to hide this advert.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.