remote desktop issue

[seth melnick]

I am able to remote desktop into my windows 7 machine once - after that if i disconnect I cannot login to the machine locally - its gets "stuck" at the welcome screen. And then if i try to login remotely again I get an error that the remote desktop service is busy. Only way to login again is to do a hard reboot.

after i reboot i see the services nlasvc and crypt are both timing out waiting for a transaction response - not sure if thats related but its there everytime this occurs

Anyone see this or have any tips of which direction to go?

 

[Zidane24]

I would do a repair install since some of your windows files have gone corrupt

http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[seth melnick]

how would you know if the files have gone corrupt - i did a reinstall previously and it didnt fix the issue - I did a clean install from scratch

 

[seth melnick]

i just did a full repair installation and the same exact error still occurs - same nlasvc timing out - anyone have any suggestions? ii am desparate to get rdp working

 

[H2SO4]

i just did a full repair installation and the same exact error still occurs - same nlasvc timing out - anyone have any suggestions? ii am desparate to get rdp working

NLA = Network Location Awareness, a component used to determine whether the PC is currently on the same network as in the past. For example, laptops which roam between the office corporate network and out in the field will behave differently depending on NLA's impression of where the laptop is currently residing.

Having said that, I've got no idea (at present) whether what ails NLA is the root cause of your RDP problem, but my gut feeling is "no".

Have you checked the event log for anything relevant-looking at the point where terminal services starts experiencing problems?

 

[seth melnick]

the system log is where i see that nla message

the only other error messages even nearby are the sptd driver failed to load - i think that is from daemon tools and i dont think that is related to this issue

i also get a "A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service." - again cant see it being related

i also get a warning - The driver \Driver\WUDFRd failed to load for the device USB\VID_041E&PID_413E\627CE98A38D4830A.

 

[concino]

Same problem here

I am having the exact same problem. If I logon to my system remotely, I cannot logon locally afterwards. This is quite annoying as there is no way to figure out why the NLASVC is failing.

 

[seth melnick]

Yes I am still having this issue and dont have any clear way to diagnose it - i have even done a completely fresh reinstall of win 7 and the issue persists - very very frustrating

 

[RPeden789]

Try installing new nvidia drivers. We have had that same issue with RDP in xp and we updated the video drivers and everthing worked.

 

[seth melnick]

was your issue also with nla service hanging - cause i dont see how the video driver could effect the nla service.

 

[Shane86]

I'm having the same issue, and my nVidia drivers are updated to the latest version.
did anyone ever find a fix?

 

[seth melnick]

I havent found a resolution yet and it appear several people are experiencing this.

I have even tried a completely clean install and still didnt work

 

[chev65]

You can't just close the RD session, you need to log off or you will have problems logging back in locally.

To disconnect without ending your Remote Desktop session

• You can temporarily disconnect from a session by clicking the Close button
  
  on the connection bar (the horizontal bar at the top of your screen). This leaves your programs running so that, next time you connect, you can continue where you left off.

To end your Remote Desktop session and disconnect

• In the Remote Desktop Connection window, click the Start button
  
  , click the arrow next to the Lock button
  
  , and then click Log Off.

 

[Shane86]

Mine is a fresh install as of monday as well...
from some digging, looks like some people on 2k8 Server are having this issue as well...

What NICs do you have installed? I'm running a TP-Link TL-WN851N, and Dual onboard gigabit (who's controler escapes me right now)

i think i'm going to try reinstalling all the drivers from their manufacuters instead of using whatever windows decided would work.

 

[Shane86]

Chev, i do.
when this happens, it doesn't just "create problems logging in locally" it basically kills the box. i have to hard reset to recover, connecting through RDP again fails aswell.

 

[chev65]

Well the OP seemed to have a problem logging in locally after RD session but didn't mention the box being killed so it may help with his problem. From what I read about this problem the display driver can somehow cause this problem also.

 

[Shane86]

Seth, Let me ask you this... are you using Zone Alarm/Zone Alarm Pro?

Alot of digging tonight yeilded this thread:
The task you are trying to do can't be completed because remote desktop services is currently busy. Please try again in a few minutes. Other users should still be able to log on.

Aparently zone alarm is aware of this issue, it just doesn't seem very well documented. i uninstalled zone alarm, and i was able to remote in multiple times, without the machine crashing.

Good luck man, hope this helps ya

 

[aem]

I am able to remote desktop into my windows 7 machine once - after that if i disconnect I cannot login to the machine locally - its gets "stuck" at the welcome screen. And then if i try to login remotely again I get an error that the remote desktop service is busy. Only way to login again is to do a hard reboot.

after i reboot i see the services nlasvc and crypt are both timing out waiting for a transaction response - not sure if thats related but its there everytime this occurs

Anyone see this or have any tips of which direction to go?

It pays to tell us the steps you did to connect from one Pc to another via RDP. An how was your network set up?

 

[Coolclay]

I have had this problem as well.

The remote computer does keep running and all files are in tact.

I however cannot log back in locally or remotely... this means that if I log out of the session close the window or restart my remote computer... the only way that I can access it again is to reboot the remote computer.

Every thing worked fine when I was running vista64 on my local computer which happens to be my laptop, but since running windows 7 on both, I have started having this problem.

Remote assistance also is not working properly.
I liked when I had vista on, I would remote in pick a movie to play on my media box, enable remote assistance and watch it on tv controlling it from my laptop.

I am thinking about going back to vista 64 even tho I like windows 7 a little better otherwise.

I no longer have my vista backup, but I wonder If it is possible to run the vista64 versions of these programs on my win 7 machine

 

[Coolclay]

With the new install, I decided to implement a little more security and installed zone alarm
Tuns out that uninstalling zone alarm fixed my problem.
Works fine now.

I still have zone alarm on my laptop, but the computer I'm remoting into, I have it uninstalled.
Kind of a disappointment.
But I'll live with it.

I wonder if zone alarm will fix this issue.

I'm very happy that I got this working.