Windows 10: Connecting to rdp - domain user

I connect to the Windows 10 Professional with Microsoft Remote Desktop app for MacOS - on my Windows PC, I've account created by logging to Windows with my work credentials, name@company.com - which I understand is domain account(but the remote computer is not in domain environment). When I want to connect with rdp, after establishing connection to remote computer I receive info that name or password is incorrect - which I'm 100% sure is correct, because I use it everyday and with this credentials I can establish rdp connection. I've added local user with admin rights - and I can use it to login to the desktop. How can I fix it and make it possible for my account to use rdp?

submitted by /u/teddy_pl
[link] [comments]

:)

 

User/Domain missing from RDP log

I experienced a security issue today where I was logged out due to RDP session (while I was RDP'd) when I reconnected someone was using the webs browser. I pulled the plug on the ethernet and deleted my RDP rules on my router. As well as reset the windows
firewall to only allow private networks.

But now I'd like to see if I can figure out the IP that made those connections.

If I drill down to

Event viewer-->Microsoft-->Windows-->TerminalServices-RemoteConnectionManagerin TerminalServices-RemoteConnectionManager OperationalEvent ID: 1149

I do see several entries

I see user/domain and an ipv6 address for hich I believe is my current ipv6 (it doesnt match exactly what I see when I ipconfig, but when I log out and reconnect it's the same in the event viewer)

but then I see many other entries which have no user or domain, but have either an ipv4 or ipv6 (both which happen to be the pc I'm currently using)

How can user authentication succeed but not log the user and domain?

Is there any other item in event viewer that I can lookup to help find the intruding ip address?

 

Slow initial RDP connection

Hello.

I have a strange problem: since we recently moved from a 2003 domain (I know, way too long used) to a 2016 domain (no domain upgrade but a fresh install), RDP to a PC is taking a long time to login. A connection is made, but the
RDP window shows a spinning circle at “Welcome” for around 90 seconds. After this, for the most PCs the desktop is shown and the RDP connection is as fast as it should be. Some PCs however never login, the welcome keeps spinning.
Even worse: if you disconnect/connect the RDP connection a couple of times and you try to reconnect again, the target PC will never login and even physically you are unable to login… a hard reset only will solve the problem…

This behavior is only when RDP to Windows 7 or Server 2012. Logging in remote to Windows 10 or Server 2016 works without any delay. I tried different combinations:

PC A taken out domain and PC B taken out domain: RDP from A to B no problem

PC A taken out domain and PC B taken out domain: RDP from B to A no problem

PC A taken out domain en PC B member of domain: RDP from A to B 90 sec delay at logging in

PC A taken out domain en PC B member of domain: RDP from B to A no problem

PC A member of domain en PC B member of domain: RDP from A or B to B or A 90 sec delay at logging in

PC A member of domain but no GPO policies applied and PC B member of domain but no GPO policies applied: RDP 90 sec delay at logging in

PC A and PC B are Windows 7 Pro, fully updated or vanilla.

I tried all the GPO fixes found on the net about RDP tweaking, changing ports, or adding
enablecredsspsupport:i:0 to default.rdp file.

The eventlog (of RDP or terminal services) of the target PC is not showing any errors.

Somehow the new domain is causing this behavior…

Thanks in advance,

 

Slow initial RDP connection

Hi,

Your question is beyond the scope of these Forums

This Community is mainly for home users and their computer problems, not business systems.

Kindly post your question in the TechNet Server Forums.

Technet forums

TechNet Forums:

Technet forums

MSDN Forums:

Msdn forums

Cheers.