• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "RDP with domain user account"

Collapse

  • Boney M
    replied
    Originally posted by suityou01 View Post
    I did mate. I turned off everything.



    I'll give it a go, cheers.
    The admin switch is likely to work as it is a console session

    Leave a comment:


  • suityou01
    replied
    Originally posted by Boney M View Post
    Have you tried disabling the smart card enumeration service ?
    I did mate. I turned off everything.

    Originally posted by darrylmg View Post
    Also, try initiating the rdp with /admin.
    See here: Using command-line parameters with Remote Desktop Connection - Windows Help
    I'll give it a go, cheers.

    Leave a comment:


  • darrylmg
    replied
    Also, try initiating the rdp with /admin.
    See here: http://windows.microsoft.com/en-gb/w...top-connection

    Leave a comment:


  • Boney M
    replied
    Have you tried disabling the smart card enumeration service ?

    Leave a comment:


  • suityou01
    replied
    Originally posted by DimPrawn View Post
    Good luck Suity, we are all waiting here with baited breath!

    is that what that awful smell is.

    Leave a comment:


  • DimPrawn
    replied
    Originally posted by suityou01 View Post
    OK I am going to build 2 machines and use VNC so I have a workaround.

    No need to apply any more thought to what is clearly a very weird problem.

    Thanks all.

    Good luck Suity, we are all waiting here with baited breath!

    Leave a comment:


  • suityou01
    replied
    OK I am going to build 2 machines and use VNC so I have a workaround.

    No need to apply any more thought to what is clearly a very weird problem.

    Thanks all.

    Leave a comment:


  • suityou01
    replied
    Originally posted by stek View Post
    Try 'telnet ad_server 389' and 'telnet ad_server 689' from client same other way...
    Yep those ports are open, and I can see handshakes in wireshark.

    Leave a comment:


  • suityou01
    replied
    Originally posted by DimPrawn View Post
    Stoopid question, are there pending updates on the server?

    Try a server reboot and see if you can RDP on after that.
    Patched up the ying yang. Many reboots.

    Leave a comment:


  • suityou01
    replied
    nlasvc timeout is the error in the event log. Along with crpytosvc.

    A common problem on Citrix VDI, but I am running on Centos KVM.

    Logging into the machines using domain account is fine, problem only exists via RDP using a domain login.

    Leave a comment:


  • SimonMac
    replied
    Have you tried logging onto any of the three machines as the domain user but from the console of what ever hypervisor you are using? Eliminate the RDP aspect of any fault finding

    Leave a comment:


  • stek
    replied
    Try 'telnet ad_server 389' and 'telnet ad_server 689' from client same other way...

    Leave a comment:


  • DimPrawn
    replied
    Stoopid question, are there pending updates on the server?

    Try a server reboot and see if you can RDP on after that.

    Leave a comment:


  • suityou01
    replied
    Originally posted by DimPrawn View Post
    Sounds like to me (and I'm not expert in this), that the machine you are RDPing to has problem accessing the domain controller. Network / Firewall setup.
    Smells like that to me too. Nothing coming up on a wireshark trace to support this.

    Also the machine I am rdping to, I can log on successfully with these credentials locally so it authenticates via the DC fine.

    Leave a comment:


  • DimPrawn
    replied
    Sounds like to me (and I'm not expert in this), that the machine you are RDPing to has problem accessing the domain controller. Network / Firewall setup.

    Leave a comment:

Working...
X