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.

[Error running SFC over RDP on Server 2003]

Discussion in 'Windows Server System' started by Steve R Jones, 2014/02/10.

  1. 2014/02/10
    Steve R Jones

    Steve R Jones SuperGeek Staff Thread Starter

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    I am attempting to run the command:
    SFC /verifyfile=C:\Windows\System32\Ntdll.dll


    I keep getting this error:
    "You must be an administrator running a console session in order to use the Windows File Checker utility. "

    I'm doing this via RDP and am logging in as an Admin. I've also tried running the CMD.exe as an Admin.

    I've found info on the slightly old Server 2000 that didn't allow many things to be done via Remote Desktop.... But nothing directly related to 2003.

    Thoughts??
     
    Steve R Jones,
    #1
  2. 2014/02/10
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338
    SpywareDr,
    #2


  3. to hide this advert.

  4. 2014/02/11
    Steve R Jones

    Steve R Jones SuperGeek Staff Thread Starter

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    Thanks Doc. I haven't seen that one. I'll try it when I get to the office.
     
    Steve R Jones,
    #3
  5. 2014/02/11
    Steve R Jones

    Steve R Jones SuperGeek Staff Thread Starter

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    No Joy... Invalid Command. I was a little suspicious since the article was from 2001.

    I had high hopes yesterday when I read about adding /console or /admin after the IP address when connecting via RDP...but they didn't help either.
     
    Steve R Jones,
    #4
  6. 2014/02/11
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338
    Last edited: 2014/02/11
    SpywareDr,
    #5
  7. 2014/02/11
    Steve R Jones

    Steve R Jones SuperGeek Staff Thread Starter

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    OK... Will try that now. It has to be EASIER than doing "KVM over IP" that the data center support guys said to try... It's way over my Pay Grade:p

    Although - I thought I was close!?!?!?
     
    Steve R Jones,
    #6
  8. 2014/02/11
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338
    :) Here's hoping it works for you. Don't have any way to test it from here.
     
    SpywareDr,
    #7
  9. 2014/02/11
    Steve R Jones

    Steve R Jones SuperGeek Staff Thread Starter

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    Well double darn... I actually got it to connect... Had to start it from RUN and not from a cmd prompt..... Thought I was in hog heaven when I did a DIR command and could tell I was on the server.

    Then I found that the SFC VerifyFile is not valid on Server 2003 like it is on Win 7.
     
    Steve R Jones,
    #8
  10. 2014/02/11
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338
    How about just doing the complete SFC /SCANNOW?
     
    SpywareDr,
    #9
  11. 2014/02/11
    Steve R Jones

    Steve R Jones SuperGeek Staff Thread Starter

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    Cause I'm too chicken. The server in question is at a DC in Seattle. In theory, I shouldn't get prompted for an install cd.... BUT if the server went down all heck would break loose.

    AND, I'm doing all of this to prove to my developers that the stupid DLL file is probably unrelated to the issues we're having with our software that is installed...

    Different client with their own machine at a DC has similar issues but different DLL..

    Both DLL's are very common and many apps use them... I'd think the machines would be sicker than dogs if the DLL were really corrupted.

    Thanks for all of your help Doc;)
     
    Steve R Jones,
    #10
  12. 2014/02/11
    SpywareDr

    SpywareDr SuperGeek WindowsBBS Team Member

    Joined:
    2005/12/31
    Messages:
    3,752
    Likes Received:
    338
    Understood. Too risky to replace the Ntdll.dll with a know good copy? Maybe rename the current one to something like "Ntdll.dll.original ", and then drop the new one in?
     
    SpywareDr,
    #11

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.
    Accept Learn More...