Home Forums Discussions General Discussion problems with RDP

hello all,
I am having this strange problem with RDP .
Only the pop up messages from AC seem to freeze for upto 30 secs- e.g do you want to delete this message or are you sure you want to close this chart etc. Eventually they do close but this is annoying and slows me down
RDP seems to work fine otherwise
any suggestions from anyone would be welcome
thanks
bala

Hi Bala,

That would be annoying. Can you give more information? Is this RDP within your network to the server? From home? What OS are you using? Is this server/client with a remote gateway? Is this happening on every computer?

hi Bert,
This is me connecting from a outreach clinic usually. But it does happen even on those rare occasions that I us it in the network.
OS on client computer Win 8.1 pro , happens wireless and wired connection
server Win 7 ultimate which is encrypted with bitlocker .
happens on any computer that I use as a client
could it be something to do with bitlocker ?
No remote gateway chosen , set to ' automatically detect gateway server settings "

Thanks , sorry to sound so ignorant
Bala

You don't sound ignorant at all. While you are doing the safe and correct thing to remote into the clients, what happens when you remote directly to the main computer?

Bit locker shouldn't have anything to do with it.

This is likely not it, but what happens if you go to the main computer, right-click on Computer, Properties, Advanced System Settings.

Then in the System Properties window, select the Advanced tab, select performance Settings, select the radio button Adjust for best performance. Then select the Advanced tab and under Processor scheduling, choose Background services. Click Apply, OK, then restart the computer. Just an idea.

I know you stated this. Does this happen only:

1. From your home
2. To a particular computer

This happens both from outside the office and also if used ( rarely) in the office
thanks
Bala

I am sure Sandeep could remote in and fix the problem. Much easier that way. I would troubleshoot by downloading a trial of LogMeIn and see if it works.

The trial should be free, but if it works well, sometimes you just have to bite the bullet and pay for the pro version. There are a lot of features you don't have with RDP. Like remote printing for example.

thanks Bert.
I was using LMI but have stopped using it as they started charging for it .
I need to think about that.
Bala

Trial it first. But I think LogMeIn should charge. Too many people used the free version and they're weren't enough features worth upgrading for.

What if you RDP to a client in the office instead of the server?

havent done that so far.
mainly because the way my comcast business modem works .
I wold have to change the registry in the client also and I am somewhat reluctant to do that. Unlike the DSL modem that I had previously, the comcast modem only allows port forwarding if the registry default port is changed to the same. I have chosen a random port number for security reasons not the default .
thanks Sandeep

Which brings up several questions:

Is the modem a modem/router? If this is router dependent, could you just use a different router? If you don't want to use port 3389 and you use a random port xxxxx,
you have to change the registry setting to xxxxx? If so, why not do it? I am lost there.

Are you using a server with Windows 2008 or 2012? You could then just use Remote Desktop Gateway.

Or just use LMI Pro for $14.99 a month or GoToMyPC for $11.99 a month.

Yea it's a common thing for the provider's modem/routers. They don't have nearly as many features. What I like to do is use my own router and plug it into their modem/router. Just make the router's IP a DMZ. That way my internal LAN or port forwarding isn't affected by the provider's modem/router. If I were to switch or if my modem fails, my internal network is unaffected. Also, you can cut the Internet to your office without affecting the LAN.

But this part:

If you did this without changing the registry on the server, that means your comcast router should have the option. Just use a different random port, but forward to 3389 to the client IP.
http://ltmedical.net/microsoft-windows/rdp-security-port/

Thanks Sandeep.
Actually we had to change the registry listening port on the main computer to the same random port number as Comcast does not have the option of a remote port
that is why I am not remoting in to a client as I would have to change the registry on that computer also .
do you have any ideas why the AC messages could be freezing when I use RDP?
also can you explain what you mean by DMZ ?
thanks
Bala

It doesn't take long to change.

Start>Run>regedit
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber


As to why AC freezes. It could be linked to a bad installation of the .NET framework. It wouldn't mess with SQL but it could causes issues with the main program.

DMZ stands for de-militarized zone. Basically by setting your own router in the DMZ, you tell Comcast's router to pass all* traffic. That means you can use your own router for portforwarding and such. The big benefit is that if comcast's modem/router fails, your whole network keeps going. It also adds a layer of security.

thanks Sandeep .
In one of our previous threads you had mentioned that you were not keen on changing the registry as it would interfere with web access or something similar. That is one of the reasons I was not doing it.
Should I try reinstalling the .NET framework and how hard is that to do ?
I will try and get a new router and follow your advice - any suggestions which one ?
thanks
Bala

The RV042G Gigabit Dual WAN VPN Router is a fairly decent router. GUI is rather straight forward. I remember the old Cisco PIX 501 or 505. They did have a GUI, but not as easy to work with, plus anyone familiar with them would only give you command line info, which for the novice (in the beginning) could be tough. But, it was a great sense of accomplishment once you did it.

Sorry, couldn't resist.

You never said what server and OS you are using. These issues used to be a bit more difficult with the 2003 servers, but with the remote gateways, it is a cinch to do RDPs using 443 which gives you SSL. You can remote to any computer, and the setup from a RDP client takes about 20 seconds. Very fast. Very secure. Another advantage of a domain.

Yes, that would interfere if you were using RD Gateway or planned to use it in the future. Since you are running a Windows 7 Ultimate Server, it shouldn't be an issue.

You can find the .NET Framework Version you have in the Control Panel. E.g. Net Framework 4.0. Download the installer from the Microsoft Website. Run it and choose the repair option.

I like the TP-Link line of routers.
TP-LINK TL-ER604W - This one is my favorite for solo practices. Has support for multiple SSIDs, VPN, and Dual WAN for $100. Pretty hard feature set to come by on your average home router. Multiple SSID's means you can have separate wireless networks. E.g. 1 for work, 1 for guests or 1 for work, 1 for mobile devices, 1 for guests. Dual WAN means you can have 2 different Internet providers simultaneously. Also has things like network monitoring so you can track which computers are pulling a lot of bandwith.

That's a great router. Nice suggestion. I agree with .NET as well.

This isn't disagreeing with you on the Windows 7 thing. I just hesitate to call a client OS "server" because that is part of the problem here. Not so much the problem but how it would be so much easier with a server OS designed to run networks.

I always recall one of my favorite statements from an IT guy with Microsoft when I asked him why he wouldn't help a friend of mine with a peer to peer network. He said, "They are just too hard and complicated to work with." LOL

Thanks Bert and Sandeep .
I will see if I can implement your suggestions
Bala

You are welcome. But, the best help I can give you is to make sure you use SANDEEP's suggestions.