O Canada! → Canadian → Rogers > [ Extreme] Rogers Throttling also affecting Logmein AND RDP

Ever since I started noticing my Torrents downloading much slower, i've also been experiencing VERY slow "Logmein" collections to the point that I might as well be using RDP. If they are throttling more then just "assumed" pirating then they're going to have a MAJOR fight on their hands. I use Logmein as a business tool and if they're going to slow it down on me, they're in for a fight!

I believe if Rogers has their way, their scripting kiddies would eventually make it impossible to transfer any data in any quantity that does not look like plain websites.

After all, they are the grand master overlord of throttlers, and pretty much are trend setters for the entire North American industry.

In the meantime, Europe is seeing speeds at such incredibly low costs, it's insane. Canada is losing its competitive edge step by step. Costs are getting higher, doubling in some cases, and the things you can do with your internet connection is getting less and less.
I'm afraid that soon I won't be able to show live baby videos to the grand parents any longer...

Europe is also heading towards more 3 strikes laws which will eliminate the need for throttling.

The security issues with RDP into a corporate network aside, do you actually find using logmein to be faster?

I've used all kinds of remote apps and frankly RDP is about the fastest around.
--
Jake: "Four fried chickens, and a coke" Elwood: "And some dry white toast, please"

Depends which country you're talking about.
When employing proper encrypting, they can't see what you're doing unless they place booby traps and pretend to offer videos.
There are ways to make p2p'ing anonymous enough where literally noone can't know what any ip address is doing.

That cat-and-mouse game is not something the government can win.

Logmein is actually the fastest i've found... its almost 1-1 where RDP always seems to have a bit of a delay (especially if a flash advertisement is running in the bg). Check it out, its free and totally worth it.

I just tested RDP and found that after 5-10 min of using RDP it begins to slow down as well. TO A CRAWL. I've never had RDP slow down that much unless I was downloading at the same time (which I wasn't)... FUCK YOU ROGERS.

I've had no problems with log me in from a Rogers Connection to a Rogers connection. My throttling started around the same time as everyone else

I've noticed in the last week that LogMeIn via the web (e.g., Firefox plugin) has become unusably slow, if not outright disconnects within seconds of establishing a connection.

Interestingly, using the iPhone LogMeIn app results in a flawless experience, providing the normal speed I'm used to.

Anyway just wanted to resurrect this old thread to see if anyone else is having this issue right now?

I'm assuming some sort of throttling on Rogers part?

Hi,
Just wanted to say that I too am having slow RDP connection issues.
I am at work now and from work, making a direct connect to my home office servers goes max 40KB for seconds before dropping to 5-10 on average.
BUT when I make an IPSEC VPN connection and then use RDP to the same server, it goes max speeds of 100-120KB. I can actually copy and paste files between my local and remote desktop.
Direct RDP connection, no way. So far it's been off and on in terms of speed. But last weekend I was at my friends house in Barrie (fyi I live in Brampton), tried RDP and it literally went as fast as a porn download in the early 90's on a modem line. Line by line loading of the screen, waiting 5min after clicking the Start Menu. Just horrible!
I'm gonna call Rogers later tonite when I get home and open a support incident with them for this. It's been acting up for 2 months now. I thought it was my side for some reason, did MS hotfix patches, TCP tweaks, upgraded service packs for my firewall/vpn software.
I found this post linked from this article on torrentfreak - »torrentfreak.com/rogers-bittorre···-101213/

Having read some of the reports. Now... yeah... I'm pissed. Spent hours trying to fix the problem on my end...

I agree, using logmein, it appears to be very laggy these days, when it in the past has been very close to actually sitting in front of the remote machine.

I dunno, rogers sucks, what can you do?

Whats the point in offering internet if you throttle everything? Might as well get the lowest speed if it's always going to be slow. I'm going to get the 50/2 from Rogers soon and do my own test because I'm seeing so much people complaining about slow downs. Is it really happening? Am I going to flush down $170 a month for slow internet? Is Rogers a shit load of fuck? well I guess I'll find out soon enough.

It hasn't been pleasant lately, no. I'm actually using a DSL connection these days and I hop back onto my 50/2 connection once a week to see if Rogers has unsucked the service.

So far no. Going on second month. Basically, it seems like Rogers installed some new DPI and it's broken and it's trashing the service and rather than just remove the DPI, they're leaving it in place and trying to fix it. At least, that's what it looks like.

I used to actually like Rogers. Pretty disappointed in them right now.

I'm experiencing the exact same issues with Remote Desktop. Its definitely something to do with the networking changes has made, and its very aggravating.
At the best of time, its laggy and slow. If you're downloading a torrent at the same time...yeesh, just forget about trying to connect.

Cmon Rogers, this is ridiculous! I cannot even VPN into work and I am on-call this weekend.

Rogers = degenerate company

My RDP is crazy slow lately as well. It started maybe a month ago....I am done with Rogers.

just wanted to add an update to anyone else still having rdp problems.

i have called microsoft tech support and began working with the network team to analyze network captures.

i'm using a windows mobile phone (htc att tilt 2) tethered via usb as an "outside" connection when using rdp into my servers. it's still slow but rdp inside vpn works fine.

i got the network captures and i'm currently working on figuring them out. what i see is that captures done while connecting over the internet direct to port 3389 show many many tcp retransmission errors. i tried to copy/paste a 4MB file from the server to my client and it eventually just dropped the connection.

i used a bandwidth monitor on both sides to see the traffic speeds and i get approx 3-10kbps with a max of 15 but it's not sustainable at max speeds. i average 5kbps.

same server, same tests done over a vpn connection to my network work fine. full speed. little to no tcp errors in the network capture.

i have scheduled another tech call with microsoft support in a few hours. we will probably try some tcp tweaks and mtu changes on the front end firewall router, we'll see how that goes. i remain skeptical they can fix it. but i have high hopes someone from ms level 3 network support can at least assist in gathering enough of the right evidence so that when i do call rogers to complain i'll have enough ammo to go on.

my only concern is as such... if/when i call rogers support it is for residential tech support and not business since i don't pay for a business line.

any suggestions for how and what i should say for them to acknowledge the issue might be on their end?
i don't intend for them to know or actually support windows server rdp services, but i need them to at least understand that if ftp, http, skype, and most other forms of upload traffic can go full speed uploading (except of course p2p bittorrent, as an example), then there has to be a reason that rdp directly over rogers cable line is getting dropped packets so badly. which in turn would point the issue in their laps. sound logic? or am i just hoping for too much?

and fyi, if they tell me i need to upgrade to business so it'll "just work" i do intend to ask them to prove what gets fixed on the business package that seems to be broken on a residential package. i dont intend to throw money at a problem in the hopes it will "just work", without knowing what is broken and what gets fixed. sound logic, or not?

once i have further updates i'll post.

any advice would help. thanks

EVERYONE NEEDS TO WATCH THIS, JOIN THE WEBSITE AND SIGN THE PETITION!!!!

»www.youtube.com/watch?v=PfHjP0jR···embedded

I can't comment on what you'd need to tell Rogers. You're basically rolling the dice calling them at any given time. You may get a really good tech who understands you're totally not a neophyte and having a legit issue, or you may get someone totally green who just reads the script and tells you to reboot your router.

I can tell you that your issue is probably isolated to your node/phub/area - as I can run RDP sans tunnel without issues here in Toronto (High Park on Wolfdale phub).

Business service in my experience seems to be identical to residential service. They're just priced and capped differently. If one is problematic the other will be too. I wouldn't hope for much moving up to a business line as far as solving the problem goes.

Some suggestions:

- Assuming that your issue is a throttling problem and that Rogers is incorrectly identifying your RDP connections as something throttle worthy, try adjusting the security layer settings in Terminal Services Configuration. I have no issue sans tunnelling and I'm set to "client compatible", which should default to "high" (Mac client).

- Try changing the security layer to "negotiate", which will attempt for TLS 1.0. There is really no reason a TLS connection should be throttled by Rogers.

The idea with both suggestions is to try to get the server to vary the packet composition in order to 'duck around' any DPI related problems.

Failing the above two issues, maybe bite the bullet and tunnel? RDP has some security issues pre version 6 so it may be best anyways.

Good luck.

I am also experiencing the same issues with RDP.

1. As one poster mentioned the problem is isolated (and growing) to certain areas.(Basically, are you hitting the Cisco that's got the throttle turned on.) It's my understanding that Rogers will push out various config changes to their firewalls to test it out on users. This has been going on for years.. Even here in Ottawa, you will find one side of the city complain at a certain time, and the other side not experience the same issues at all.

2. This specific throttle seems to attack encrypted traffic. If it detects you are transferring encrypted traffic, it will actually slow down the rest of your traffic. (Hence the poster that mentions if you have a torrent running good luck connecting at all) . I have 2 RDP servers listening on 80 and 443, and I'm experiencing extreme slowness (I have 1 torrent running that's downloading at 2k/s and uploading at 5k/s)
Rogers just can't battle the cat and mouse game of torrents. since they can't inspect packet headers on encrypted packets. So they have only a few ways to throttle.
a. Throttle anything that's encrypted
b. Throttle specific users that contact trackers such as piratebay, torrentleech, etc. your dns lookups and http requests are not encrypted. (aka they can tell if you're accessing those IP's)

3. It's possible Rogers can also auto-flag certain users that they've monitored torrent-tracker access on. and impose the throttle on that user(or a enhanced level of the throttle)

4. So far, I haven't heard any issues with Rogers Business accounts. Businesses depend on encryption to function, So throttling any encrypted traffic is sure to cause a lot of problems with the clients.

5. Calling Rogers doesn't do anything. You'll only get ahold of an outsourced tech that plays man in the middle to anyone worth talking to. What we really need is a Rogers Network Engineer to hop on here or somewhere and tell us exactly the formula they're using for throttling.

One of the major problems is that that CRTC doesn't lay down any technical network requirement to the ISP. There are simple agreements like 'Throttle Torrent Traffic' and 'not throttle FTP traffic' (someone post the exact link of the requirements if they know where it is). So the ISP is left open to do whatever they want. Really!

I would like to see more technical requirements from CRTC.

Where to start?

I've been having the same problem for months and today I tried something that appears to have worked.

In the rogers SMC router I edited the port forwarding for RDP.
Old: external 3389, internal 3389
New: external 27, internal 3389

Basically I now connect to my host as hostname:27 in remote desktop, the router forwards the traffic on the home lan to the RDP port on my home computer.

The result is full speed. I have no idea why this works. Perhaps rogers is throttling port 3389. Perhaps the SMC modem/router reset whatever the problem was when I made the change.

I'll post any updates if the problem returns.

RDP on 3389 is fine for me in Waterloo on Ultimate.