Remote desktop causes timeout

Hi,
I am having some issues with my application when using it through remote desktop. Essentially it works fine when I am controlling it 'locally' - but when I control it using remote desktop, at times the band width seems to cause the time critical vis to hang - essentially they can't keep up with the data coming through the FIFO from my FPGA application. I have tried my best to make the 'time critical' parts of the app be time critical - but they still seem to be over-ridden by remote desktop. Any thoughts on how to improve things - ie to force remote desktop to accept lower band width-or to enforce labview being more important? Or is it worth trying to monitor things through remote front panels - what is the overhead for this in terms of development - there are quite a few front panels in my application.

Hi,
So Basically I have a 'Lab' computer which is connected directly to the FPGA. (It is one of the 'PCIe 7842R' series boards). It is running my Labview Application (in the development suite.). Essentially the issue is that when I'm remote desktopping in - from home\my office etc, the lab computer's interface with it seems to break(at least when the network is being slow).
I guess I would expect that when the network is slow the update rate would be slower - in terms of responsivity to the remote desktop - but i wouldn't expect it to actually cause the Lab computer to slow down. In some senses what i'm doing when i remote desktop in is monitoring a long running experiment - so i don't need to 'do' much - just check everything is fine. Obviously if me loggging in to check if it is running causes a breakdown - this isn't ideal.
I should say.... after messing around a little bit yesterday I have a suspicion that what is acutally causing the issue is 'queues' - basically i'm using single valued queues as a reference value to the data that is being aquired - so it can be used in several other analysis vis. I have a data aquisition VI that runs continuously getting data from the FIFO, analyses it, and then bungs the analysis object into the queue. The other vis preview the queue element- to get the data out. It seems like the 'lossy' enqueue seems to be what causes it to break - ie - when i remote desktop in the enqueue become jittery - and sometimes hangs for 100-200ms - rather than usually ~1-2ms. - which then causes the FIFO to timeout.
I'm considering re-engineering things - possibly to use datavalue references or something like this - since i've read they are slightly faster - although i'm hesitant since the queue solution seems a nice way of easily passing the data to another vi - only needing to know the queue name. I guess I am currently using a modified version of the Queued state machine template I got from the community forum - from a few years ago. I noticed that the newer version of LV has a similiar template - but I haven't checked out the details.
Do you have any thoughts on this?
JP

Similar Messages

A single TIMEOUT drops Remote-Desktop Session on ASA

Hello Guys,
Just recently we replaced our HQ Cisco-Pix with Cisco-ASA 5510. where we have many branches connecting to our HQ through site-to-site vpn.
Since putting this new ASA5510 at HQ , while we are getting a Remote-Desktop session into our branches clients, and at the time when even a single TIMEOUT occurs on the vpn-link so the remote-desktop session gets completly lost. then we have to re-connect the session.
This issue happens as i said above when a single timeout occurs on the vpn link. please tell me what is the issue with the ASA5510. because with pix we didnt have this issue, remote-desktops were never geting lost / reset with single timeout

Imran,
Thank you for posting this question. Now, we need a little bit more clarification into what you call TIMEOUT, The ASA wont drop a flow unless there is no data passing through within an Hour (If it is TCP). Does the tunnel goes down completely and the SA has to be rebuild?
What are the logs that you are seeing? What is the ASA saying about that terminated connection? As you rightly pointed, there should not be mayor differences between the devices (Assuming they were running version 8.2 or below).
Mike

Remote desktop connection caused host to lose a monitor and other settings

Hello
After a successful remote desktop login, on the host I can now no longer detect the 2nd monitor. Screen resolution on remaining monitor is off, it's gone over to use Microsoft Basic Display Adapter even though it was using the correct adapter previously.
Both previously working display adapters now show Code 12 error: "this device cannot find enough free resources that it can use". The system has also become very slow, when I right-click the desktop, it takes up to 30 sec for the menu to appear.
Anyone had a problem like this? I have restarted the computer several times, reverted system to a working state last week, done another successful remote desktop login/logout from my laptop to this computer.
Windows 8.1 Pro
Displays: Dell U2412M
Intel R HD Graphics 4600
Thank you in advance for any help/tips to help solve this problem!

This error message can also appear if the BIOS did not allocate enough resources to the device, I want to know how much RAM do you have on your computer, because the Display Adapter calls for extra RAM to run the monitor.
If you don’t have enough RAM to allocate, the monitor won’t start, that’s why the computer becomes very slow.
Here I suggest a possible solution:
Adjust the amount of memory dedicated to video/graphics. You can change that in BIOS. there might be an option in your PC's BIOS that lets you change the amount of system memory used for video/graphics.
You'll just need to find it in the BIOS, the BIOS options in the Advanced settings,
the option varies depends on the BIOS version
you can set the maximum memory that it can take to a lowest value.
Regards
Wade Liu
TechNet Community Support

Remote Desktop update has caused me to no longer be able to access work using Citrix/CAG. IT found my access to be intact on their end. What can I do?

How can I get access to my work after the Remote Desktop Update 3.8.2 blocked my access through Citrix/CAG?

Can you start Firefox in [[Safe mode]] ?
You can also do a clean reinstall and download a fresh Firefox copy from http://www.mozilla.com/firefox/all.html and save the file to the desktop.
Uninstall your current Firefox version and remove the Firefox program folder before installing that copy of the Firefox installer.
It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
You can initially skip the step to create a new profile, that may not necessary for this issue.
See http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Clean_reinstall

Remote desktop (MAC) app freezes after a sleep/scree-timeout

Hello,
My company needs the Remote Resource Connection -> Remote Desktop Client to be used to connect to Windows (7) desktops over the Internet. The connection is through duo-authentication and once connected all works fine. Highly recommending the Microsoft
Remote Desktop for MAC therefore.
One small annoying glitch I found was when the MAC goes to sleep or screen shuts off (This happens about in a minute to save battery). Once the screen awakes, the Remote Desktop doesn't seem to be able to restore it state. What I notice is that the screen
for Remote Desktop is Frozen. MAC is not frozen, its healthy and all the rest of the apps seem to work fine, just this Remote Desktop app isn't. I will have to either kill the process from the command line (terminal) or just exit the Remote Desktop app (well,
its not frozen, the menus work fine) and restart the process of logging in.
Any advise to fix this issue? Or is this a bug and needs fixing? Please ask if you need further from me.
Thanks
Madu

Hi,
Would you please provide us the log file after you reproduce the issue. Also, please give us the timestamp you put your Mac to Sleep.
Thanks.
Jeremy Wu
TechNet Community Support

"Licensing timed out" when creating to Remote Desktop Connection

Our company have two site (SiteA and SiteB), both have its own DC (SiteA.xx.local and SiteB.yy.local). A Windows 2012 Server setup a Terminal Service. All SiteB user will use remote desktop to connect to the Terminal Server.
Sometime it will prompted an error "A licensing error occurred while the client was attempting to connect (Licensing timed out). Please try connecting to the remote computer again." Before this error message shown, the connection box
will show the status "Estimating connection quality" for a while (my last test this will stay for 2 min 30 sec. before Licensing timed out prompt).
When we face this error, the only way to solve it is to reboot the Terminal Server. Once reboot, everything will be fined, all user can connect again. But sometime later (no fixed time period, from two hours - two days), user
will then have this problem. But we need to reboot server again.
I can't found in what situation this error will happened. But we do experienced the following situation.
1. Sometime the a RDS Connection just stopped directly. Then try to reconnect but failed. In this case, all other users are still using it.
2. I try to unplug a network connection for a client, it show the connection is lost and trying to reconnect. After I plug the network back. Cancel the reconnect process. Then open the remote desktop again it will have the error.
3. there has two machine will never have this problem (we have this problem for 3 months). no matter how the connection lost. it can built up the connection once the connection is back
I followed some forum to enable the netlogon.log. On the Server, I found:
1. [MISC] [872] In control handler (Opcode: 4): This log must there when the problem happened.
Not sure if the following log help:
1. NetpDcGetName: SiteA.xx.local. using cached information ( NlDcCacheEntry = 0x000000DE96694D50 )
2.DsGetDcName function returns 0 (client PID=2088): Dom:SiteA Acct:(null) Flags: NETBIOS RET_DNS
3. NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c03ffff1
4. DsGetDcName function called: client PID=23532, Dom:(null) Acct:(null) Flags: LDAPONLY RET_DNS (I found some log will be Dom:SiteA install of Dom:(null) )
5. NlTimeoutApiClientSession: Unbind from server \\SiteA-DC.Stingmars.hk.local (TCP) 0.
6. NlPrintRpcDebug: Couldn't get EEInfo for I_NetLogonSamLogonEx: 1761 (may be legitimate for 0xc000006e)
On the Client side: Not sure if the log can help:
07/11 11:56:01 [MISC] DsGetDcName function called: Dom:(null) Acct:(null) Flags: DS
07/11 11:56:01 [DNS] NlDnsHasDnsServers: DNS Server is NOT configured on this machine.
07/11 11:56:01 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
07/11 11:56:01 [MISC] NetpDcGetName: SiteB using cached information
07/11 11:56:01 [MISC] DsGetDcName function returns 0: Dom:(null) Acct:(null) Flags: DS
07/11 11:56:01 [MISC] DsGetDcName function called: Dom:(null) Acct:(null) Flags: FORCE DS
07/11 11:56:01 [DNS] NlDnsHasDnsServers: DNS Server is NOT configured on this machine.
07/11 11:56:01 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
07/11 11:56:01 [MAILSLOT] Sent 'Sam Logon' message to SiteB[1C] on all transports.
07/11 11:56:01 [CRITICAL] NlBrowserSendDatagram: No transports available
07/11 11:56:01 [CRITICAL] NetpDcGetNameNetbios: SiteB: Cannot NlBrowserSendDatagram. (1C) 53
07/11 11:56:01 [MISC] NetpDcGetName: NetpDcGetNameNetbios returned 1355
07/11 11:56:01 [CRITICAL] NetpDcGetName: SiteB: IP and Netbios are both done.
07/11 11:56:01 [MISC] DsGetDcName function returns 1355: Dom:(null) Acct:(null) Flags: FORCE DS
07/11 11:56:02 [MISC] DsGetDcName function called: Dom:(null) Acct:(null) Flags: LDAPONLY RET_DNS
07/11 11:56:02 [DNS] NlDnsHasDnsServers: DNS Server is NOT configured on this machine.
07/11 11:56:02 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
07/11 11:56:02 [MISC] NetpDcGetName: SiteB using cached information
07/11 11:56:02 [MISC] DsGetDcName function returns 0: Dom:(null) Acct:(null) Flags: LDAPONLY RET_DNS
07/11 11:56:03 [SESSION] V6 Winsock Addrs: fe80::bd63:1d49:d8fd:724%12 (1) V6WinsockPnpAddresses List used to be empty.
07/11 11:56:04 [MISC] NlPingDcNameWithContext: Ping response timeout for SiteB-DC.Stingmars.cn.local.
07/11 11:56:04 [CRITICAL] NlPingDcNameWithContext: Can't ping the DC SiteB-DC.Stingmars.cn.local.
07/11 11:56:04 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1
Thanks
Kenneth Lai

Hi Kenneth,
Thank you for posting in Windows Server Forum.
Please check the setting and workaround as per below thread.
RDP connection hangs on "estimating connection quality"
http://social.technet.microsoft.com/Forums/en-US/18819bef-5c01-4849-9c61-afb7e8c8a581/rdp-connection-hangs-on-estimating-connection-quality?forum=winserverTS
In addition, also check below details.
Cause: If you are using Internet Protocol security (IPsec) to help protect traffic over TCP between clients and terminal servers, then packet fragmentation might occur. As a result, some packets might not reach their destination, and
client connections to terminal servers might fail.
Solution: Configure IPsec to help protect traffic over UDP rather than over TCP.
Hope it helps!
Thanks.
Dharmesh Solanki

Yosemite 10.10.1 Update - Can no longer connect to Windows Remote Desktop

I use Mac's VPN to create a PPTP VPN connection to our Windows Server at work. I access the Server using the Microsoft Remote Desktop App from the App Store (v 8.0.10). After upgrading to Yosemite, I could get the VPN to connect but could not get the Microsoft App to connect to the Server. I fixed this problem by deleting the VPN Connection and setting it up new from scratch. It worked fine until the 10.10.1 upgrade. Now it no longer works and my previous fix does not work. I also noticed that I totally lose internet connectivity when the VPN is connected - Safari and Outlook Windows app show no internet connection.
Microsoft App error is :
Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
Please help this has broken with both Yosemite updates and now I am up a creek and unable to work remotely.
Thanks,

I've only one hint to you, cause I've mot on Mac-Server.
With 10.7 Apple have switched from Samba (maybe due to licence problems with GPL based stuff) to a own protocol called "XSMB"
This had caused problems with some NAS systems too.
Eventually someone have a glue to solve that, as several users have problems with SMB shares since that.
Lupunus

Macbook Pro remote desktop unable to connect to my office PC. Genius Bar told me the only solution was to wipe my Mac. Really??

I work remotely using my Macbook Pro (OS X 10.5.8) to connect to my office PC. I have always had issues using my "computer name" with the RDC but have no problem when using the IP address. Two weeks ago my company upgraded their server and ever since I have been unable to access the server. My coworkers (who use Macs) are not having the same problems as me. My IT guy was able to connect using my Mac, his security clearance and IP address. However, I no longer have the option of using the IP address to log in - per my IT guy. My IT guy is a PC guy so he suggested that I take my computer to Apple to see whats blocking me.
I met with Apple support at the Genius bar yesterday and was told basically it could be a problem with my computer and I needed to wipe it clean and start over. This was the proposed solution to the problem but the Mac guy I spoke with didn't seem completely sure this would solve / is the cause of the problem. Does anyone have any suggestions for figuring out what the root problem is prior to me wiping my Mac? Has anyone had issues working with remote desktop connection from their Mac connecting to a PC?
I appreciate any help possible!

Welcome to Apple Discussions!
There are no songs on your iPod, right (since it was restored)?
Make sure the software on your computer is up to date...
iTunes
iPod Updater
Update iPod's Software
Also, try connecting the iPod via a different USB port.
You may want to try putting the iPod in Disk Mode prior to connecting it and see if you are able to restore it (while it is in Disk Mode)...
Putting iPod into Disk Mode
Finally, if you can't get the iPod to restore, then try connecting it and opening My Computer. Does the iPod show up in My Computer? Try right clicking it and going to Format. Does anything happen?
btabz

Remote Desktop Connection to Windows 8 PC from other computers crashing

Hi all.
Was hoping someone would be able to help me with an issue I'm having.
I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
never will. The computer has a single user profile that has full administrator rights.
I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me.
The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
the connection or do anything. I have to restart the computer from then to be able to use it again.
I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
to continue using it. Dead end there, it seems.
The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck.
If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
you think I can provide anything.
Thanks in advance!
rugbyreff

The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet
Hi Brandon
Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
this still hasn't helped.
If you have any other ideas I'd be very glad to hear them!
rrugbyreff
"If it's worth doing, it's worth overdoing" -- MythBusters

Windows XP see blank screen when remote desktop to Windows 7 with fast user switching disabled

All computers are in workgroup environment, no AD.
Windows 7 pro are configured with fast user switching mode disabled so that only one login session can run at a time. When a Windows 7 machine remote desktop to another Windows 7 machine, the remote desktop 'server' will give 30 seconds count-down for the
console logged in user to accept remote connection, or when timeout expires it kicks out the console logged in user. This is completely ok.
This become a problem when a Windows XP rd client try to remote desktop to these Windows 7 machines, Windows XP see a blank screen if the remote Windows 7 machine has a user logged in, as it is waiting for the user to log off first. This is not desirable
as our administrators want the console session to be logged out automatically if they (administrators) want to remote desktop in.
Is this a configuration problem? Is this a OS design, can't be changed?
Valuable skills are not learned, learned skills aren't valuable.

Hi,
As I know, for RDP session in Windows 7, you don't need to configure the fast user switch option disabled. Windows 7 doesn’t support multiple Remote Desktop sessions by design, that means only one RDP session at a time.
I remote into my Windows 7 machine (which has a user logged in) from my XP machine, all work fine, the user logged in Windows 7 machine is automatically "kicked off".
May I ask a question? Does this issue happen in all XP machines? If you leave Windows 7 machine started and no user logged in, the RDP session in Windows XP established quickly?
I would suggest you keep latest drivers graphic card and latest updates paches for both Windows XP (Windows XP has come to its end of the lifecycle)and Windows 7.
Yolanda Zhu
TechNet Community Support

How to configure CISCO ASA 5510 for internal remote desktop ?

Helo,I have a client that want to install new ASA (5510) in their network.
and then I did some experiment to implement it. the topology is like this :
--------configuration---------
2800 router :
interface FastEthernet0/0
ip address 172.16.1.1 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
ip address 192.168.11.3 255.255.255.0
duplex auto
speed auto
ip route 192.168.12.0 255.255.255.0 172.16.1.2
1841 router :
interface FastEthernet0/0
ip address 172.16.1.2 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
ip address 192.168.12.1 255.255.255.0
duplex auto
speed auto
ip route 0.0.0.0 0.0.0.0 172.16.1.1
ASA 5510 :
: Saved
: Written by enable_15 at 19:21:31.639 UTC Mon Sep 13 2010
ASA Version 8.2(1)
hostname ciscoasa
enable password **** encrypted
passwd ***** encrypted
names
name 192.168.12.0 Branch
dns-guard
interface Ethernet0/0
shutdown
no nameif
no security-level
no ip address
interface Ethernet0/1
nameif inside
security-level 100
ip address 192.168.11.1 255.255.255.0
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
interface Ethernet0/3
shutdown
no nameif
no security-level
no ip address
interface Management0/0
shutdown
no nameif
no security-level
no ip address
management-only
boot system disk0:/asa821-k8.bin
ftp mode passive
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
access-list inside_access_in extended permit ip 192.168.11.0 255.255.255.0 Branch 255.255.255.0
access-list inside_access_in extended permit ip 192.168.11.0 255.255.255.0 any
access-list inside_access_in extended permit ip Branch 255.255.255.0 192.168.11.0 255.255.255.0
tcp-map mssmap
synack-data allow
invalid-ack allow
seq-past-window allow
urgent-flag allow
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-621.bin
asdm location Branch 255.255.255.0 inside
no asdm history enable
arp timeout 14400
static (inside,inside) 192.168.11.2 192.168.11.2 netmask 255.255.255.255
static (inside,inside) 192.168.12.2 192.168.12.2 netmask 255.255.255.255
access-group inside_access_in in interface inside
route inside Branch 255.255.255.0 172.16.1.1 1
timeout xlate 3:00:00
timeout conn 10:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 0.0.0.0 0.0.0.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh timeout 5
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
username ***** password ***** encrypted
class-map mymap
match access-list inside_access_in
class-map inspection_default
match default-inspection-traffic
policy-map global_policy
class inspection_default
inspect ftp
inspect h323 h225
inspect h323 ras
inspect netbios
inspect rsh
inspect rtsp
inspect skinny
inspect esmtp
inspect sqlnet
inspect sunrpc
inspect tftp
inspect sip
inspect xdmcp
policy-map myPolicy
class mymap
set connection advanced-options mssmap
service-policy global_policy global
service-policy myPolicy interface inside
prompt hostname context
Cryptochecksum:a605d94f29924e5267644dd0f4476145
: end
I can successfully ping from host 192.168.12.2 to 192.168.11.2, but I can't do remote desktop from those host.
then I use wireshark to capture packet in my computer and it says that TCP ACKed Lost Segment.
"1373","164.538081","192.168.11.2","192.168.12.2","TCP","47785 > ms-wbt-server [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=2"
"1374","164.538993","192.168.12.2","192.168.11.2","TCP","[TCP ACKed lost segment] ms-wbt-server > 47785 [RST, ACK] Seq=1 Ack=1407706213 Win=0 Len=0"
I can guarantee that both computers are remote desktop enabled and all firewall have been disabled.
please help, any suggest would be great .
thanks .
sincerley yours
-IAN WIJAYA-

ear Ian_benderaz,
Thank god i am not alone on this ,
Me too having the exact same problem , i can ping to the host ,but no remote desktop .
Somebody please help me on this , how enable remote desktop on asa 5505
Thanks

Why is Remote Desktop running when I have it disabled?

I am running Windows 7 Professional. Looking at the Event Viewer today, I examined Microsoft/Windows/Terminal Services/Local Session Manager/Operational. There are 1,959 events recorded, dating back to 7/30/2014. A typical entry--one from today, reads in
the details: Remote Desktop Services: Session Logon Successful. User: PC\UserName Session ID:2. Source Network Address: LOCAL. The subsequent entry reads: Remote Desktop Services: Shell Start Notification Received. User: PC\UserName. Session ID:2. Source Network
Address: LOCAL. There are also entries for Session Logoff Succeeded, Session Has Been Discontinued, and Session Has Been Reconnected. It appears that these entries have been recorded each time we log on, log off, and switch user. My question is: Why are these
events being recorded under Terminal Services and Remote Desktop Services events? Under Services, I have disabled Remote Desktop Configuration, Remote Desktop Services, and Remote Desktop Services User Mode Port Redirector. In Control Panel/System, I have
unchecked the box for "Allow Remote Assistance invitations to be sent from this computer."
About a month ago, I discovered a strange new hardware installation of a PS/2 mouse and i8042 port in the Event Viewer. Consequently, under Hidden Devices in Device Manager, I did see the PS/2 mouse that I never installed.
Yesterday, I ran netstat -anobv and it showed two ports listening on the network for which it said, "Cannot obtain ownership information." One was port 445, for which I have blocked incoming activity on the firewall. The other was port 5357,
which according to Microsoft has some security vulnerabilities related to Function Discovery Provider Host and Function Discovery Resource Publication. Since this is a standalone PC with no network attached devices, I disabled both of these services. As of
this morning, the PS/2 mouse has disappeared from Device Manager.
A new process has popped up using netstat -anobv, on port 8883. It's IANA registered to MQTT. Should I be concerned about the Remote Desktop Services shown in Event Viewer? I thought it was a cause for concern, especially due to the appearance of the PS/2
mouse and the i8042 port which I did not install. Thank you for your help with this issue.

Hi Tergivesada,
You may upload the log files into OneDrive and paste the shared link here, we will help to check it out.
For other considerations, some application might also take use of remote services to cause Windows record the logon events, which should be considered a normal behavior. Reference:
Remote Desktop Services.
For the security consideration, you may take use of Windows Security Essentials to help protect your machine:
http://windows.microsoft.com/en-HK/windows/security-essentials-download
And further questions, please feel free to post back.
Best regards
Michael Shao
TechNet Community Support

Windows server 2012 and windows xp remote desktop connection loss

I am having this problem for a month now, and i am stumped with trying to find an answer . I have talked with several network admins in my area and with no luck i have not found a solution. I have a windows server 2012 placed with 5 pcs that are connected
on a local network , those 5 pc's connect to the server via remote desktop. List of pc's:
1x Windows 7
4x Windows XP SP3
All have the latests network drivers, all have the latest version of remote desktop installed. All have been scanned for viruses. All have antivirus software.
Problem is the 4 XP machines lose connection on when connected via remote desktop. If one starts losing connection the other 3 start to lose the connection aswell. The windows 7 machine is not affected by this it works fine.
What have I tried:
Scanning for viruses.
Disabling Firewall and antivirus software.
Updating all drivers.
Did many changes to group policy like keepalives etc.
Turning off SMBv2 SMBv3.
Turning off network adapter Offload settings.
Changed some registry settings like keepalive, smb etc.
Updating every pc and server with all windows updates.
Changed the router and switch.
Port forwarded needed ports like 3389.
Updating remote desktop to 7.0.
I might be forgetting some stuff i will add as i remember anything.
So the thing is this. I use a Windows XP machine from my office I remotely connect to the server via the Internet and I DO NOT experience any connection loss. BUT the XP machines on the local network constantly experience connection loss via remote desktop.
I pinged every Machine from the server via CMD command PING. So when they lose connection the Packets get time outs . Packets get dropped between 1-10 packets when a connection is lost. This packet drop does not occur when using the internet or anything else.
ONLY when connected to the server via remote desktop. The packets get dropped at random intervals.
Problem is I use an XP machine and I am not experiencing any loss of connection , while the XP machines on the local network experience it , but not the windows 7 machine.
Router is ASUS RT-N53 , and switch is Dlink DES-1008D. Server is a Dell PowerEdge T110 II.
Can someone please tell me what can i do to solve this problem?

So today got some word from their office. They were using RDP from 8AM until 12PM all was working fine. Then got back after lunch about 1PM and got a few connection lost errors when they tried using RDP again. Its weird since they didn't have disconnects
in the morning, and started having them after lunch.
Also noticed, that two pc were not using RDP and were disconnected as shown in task manager. And they still got request timeouts.
Maybe this is not a remote desktop issue?
TASK MANAGER
The 2 disconnected pc's ping screens:

Remote Desktop Consuming ALL System Memory

Folks, I have a Windows 7 enterprise machine through which i RDP to another desktop on the same floor as mine, which ends up freezing my machine untill i donot close out the RDP program from Task Manager.
On checking from the Process tab i see that MSTSC.exe process is consuming almost all of the 8GB of memory i have on my machine. When i kill the present RDP session and start a new one, it starts consuming memory from MBs and reaches to GBs almost
all memory capacity.
I have replaced my machine with a new rebuilt machine alltogether, but still is the same issue.
I have also changed the Experience setting and optimised the session settings for RDP but no good.
Please suggest as it is hampering my day to day work.

Hi,
I suggest we first run Xperf tool to take a look for the high memory usage:
WPT: WPR/Xperf: Capture high cpu, disk i/o,
file, registry, networking, Private bytes, Virtual bytes, Paged Pool/Nonpaged pool and/or application slowness.
Similar threads suggested that the high usage caused by MSTSC.exe is some printer related issues, please take a check with your printer configuration and the printer drivers.
Here;
here.
In addition, please also take a look at this KB article:
High CPU utilization by the Svchost.exe process and the Lsm.exe process in the Remote Desktop session after you remotely connect to a computer that is running Windows 7 or Windows Server 2008
R2
Best regards
Michael Shao
TechNet Community Support

Remote desktop policy works on Windows 7, but not on Windows 8

Hey all,
We have a mixed environment of Windows 7 and Windows 8.1 machines.
Our standard policy enables remote desktop on all machines (and another part of the policy sets the groups allowed to remote access).
On windows 7, we are able to RDP to all machines
On windows 8.1, remote clients cannot connect, with a timeout error. This occurs from other Windows 7 or Windows 8 machines.
I have confirmed:
- The policy has applied (by looking in the registry under HKLM\software\policies\Microsoft\windowsNT\Terminal services)
- The windows firewall is letting the RDP traffic through (and the issue still occurs if the firewall is off)
- The group policy templates being used in the policy are Windows 8.1 and the GPO was created on a Windows 8.1 machine
- If I set the registry key HKLM\System\CurrentControlSet\Control\Terminal Server\fDenyTSConnections = 0, manually or via GP Prefs, it still does not work
- There are no visible errors in the application, system or security logs
- I have compared registry snapshots before and after the change below and cannot see any differences in the relevant keys
If I take the machine out of the OU and place it into a "noPolicy" OU, connections still do not work (after setting the regkey above) - however, if I use the GUI to turn off remote desktop then turn it back on, it works. I can then place the computer
back in the original OU (where policy is applied) and it still works.
All this leads me to believe that remote desktop is not being turned on "properly" (for want of a better term) by group policy and doing so via the GUI is doing something different/additional.
So...
- Has anyone seen this before ?
- Anyone know how to turn on some sort of trace logging for this ? I have been unable to find a setting for this as yet ?
Thanks.

Hi Ben,
Did this happen to all Windows 8.1 clients?
>>however, if I use the GUI to turn off remote desktop then turn it back on, it works. I can then place the computer back in the original OU (where policy is applied) and it still works.
Did we try restarting the machine to tackle the issue, for sometimes restarting can be helpful.
>>Anyone know how to turn on some sort of trace logging for this ?
I am not sure this is what we want for tracing this issue, but for tracing group policy processing, Gpsvc.log can be helpful.
Regarding how to collect Gpsvc.log, the following blog can be referred to for more information.
Userenvlog for Windows Vista/2008/Win7
http://blogs.technet.com/b/mempson/archive/2010/01/10/userenvlog-for-windows-vista-2008-win7.aspx
Best regards,
Frank Shen

Remote desktop causes timeout

Similar Messages

Maybe you are looking for