Cannot connect to Terminal Server via Terminal Services Manager after upgrade to Windows Server 2003

Discussion in 'Windows Server' started by Steve Snure, Jul 1, 2004.

  1. Steve Snure

    Steve Snure Guest

    The following error is displayed in the Terminal Services Manager on our
    domain controller (DC-01) when trying to connect to Terminal Services on
    another server (TS-01).



    "You could not be authenticated on this server"



    This occurred when we upgraded the Terminal Server from Windows 2000 Server
    to Windows Server 2003 on TS-01. Interestingly I'm able to map and access
    TS-01's drives.




    Another symptom is that Veritas Backup Exec "cannot authenticate" to the
    TS-01 in order to backup the registry (Shadow Copy).



    Before the upgrade we could always access TS-01 via Terminal Services
    Manager and backup it's registry with Veritas BE. Any idea what could be
    wrong and how to fix this problem?



    Thanks - Steve Snure
     
    Steve Snure, Jul 1, 2004
    #1

    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. Cannot Connect to FTP via IE7 (but can via Firefox)

  2. Terminal Services not able to connect to Windows 2003 Server

  3. the terminal services can't start up after upgrade OS to 2003

  4. Server Windows 2003 problems after reboot (terminal server, network,services, storage errors)

  5. Unable to connect to servers via Terminal Services Manager

  6. Can Connect via RDC ,can't Connect via RWW

  7. Win 2003: Unable to connect to cluster via NLB manager

Loading...