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.

Local Machine problems with Windows 2003

Discussion in 'Legacy Windows' started by jeaz, 2004/04/26.

Thread Status:
Not open for further replies.
  1. 2004/04/26
    jeaz

    jeaz Inactive Thread Starter

    Joined:
    2004/04/26
    Messages:
    3
    Likes Received:
    0
    Hi!

    We've had a Windows 2003 Server running for several months without any major problems.

    But now a strange problem has occured.

    When logged in on the actual server I doesn't seem to have any rights to the network paths. Ex, \\nexus\sysvol\ (nexus is the dns name of the server).
    But from any other PC on the network I can access these resources.

    Any ideas?
     
    jeaz,
    #1
  2. 2004/04/26
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Does it work with \\ip-address\sysvol and why are you taking this route to see a local resource?
     
    Newt,
    #2

  3. to hide this advert.

  4. 2004/04/27
    jeaz

    jeaz Inactive Thread Starter

    Joined:
    2004/04/26
    Messages:
    3
    Likes Received:
    0
    Among other things I'm using Folder Redirection for My Documents.

    When I logon as administrator and try to access a network path I receive a username and password request, but it does accept the administrator username(i'm sure it's correct).
    Another problem this causes is that I can't use my backup program, which uses the same authentication.

    It's almost as if the server it self no longer is part of it's own domain. Very strange.

    EDIT: I also can't access Group Policies, "Access Denied" or Local Securiy Settings, Access Denied and so on...
     
    Last edited: 2004/04/27
    jeaz,
    #3
  5. 2004/04/27
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    It surely does sound like something is busted. I'd try these three things in this order and check after each one to see if the problem still exists.

    - start~run~cmd followed by chkdsk /f

    - start~run~sfc /scannow

    - While logged on as a domain admin, try taking ownership of the system drive - root and all sub folders.
     
    Newt,
    #4
Thread Status:
Not open for further replies.

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.