Posted By: ehuna | Dec 26th, 2005 @ 5:48 PM
page 1 of 1
Comments: 8 | Views: 28069
ehuna
ehuna
Grand Poo-Bah
Hello,

In MSN Messenger 7.5 there's an option for sharing your desktop with whoever you're chatting with (Actions > Request Remote Assistance).

Unfortunately, firewalls will by default block the port used by Remote Desktop / Terminal Services, making this request pretty useless.

Instead I have used in the past Citrix products which load an ActiveX control on a web page that then connects to a server.  I can then just send the link to my chat buddy, allowing us to completely bypass the firewalls.  I can then help someone across the hall or my aunt in France.

Does anyone at Microsoft know of a MS solution for this issue?  Specifically a system that is not blocked by firewalls - for example by having the clients connect to a central server.  Outgoing connections are generally not blocked.

Also, why not implement something like this in the MSN Messenger platform?
ai
ai
there is a policy setting/rule filter on MS Firewall - just select the program/port you wish to add as an exception.

RDP is 3389 (port) so open that port on your firewall (if not MS firewall) otherwise select the RDP/Remote assistance program on the MS Firewall!

blowdart
blowdart
Peek-a-boo
ehuna wrote:


Also, why not implement something like this in the MSN Messenger platform?


Putting my very old network hat on.

I really dispise software that tries to get around firewalls. AIM was the first thing I ever encountered that would look for an open port if you had blocked the specific ones it used. I ended up blocking all connects to the AIM login servers. Then YIM. Then ICQ. Then MSN. Couldn't take admin rights away from the users in question, they needed it to develop (as did I), but company policy prohibited instant messangers.

So please; Microsoft DON'T keep developing software which bypasses firewalls without giving clear instructions to network admins on how to block that software.

Can you imagine the fuss slashdot would make if suddenly MS produced a web page that allowed remote control of a PC and skipped every check that a network admin had put in place?
I have had the same problem in both personal support and in work. The solution I had to this problem was to use UltraVNC

There is a feature called single click that allows you to create a special vnc exe file. This contains just the client verson of VNC and is configured to connect to a IP of your choosing. To use you simply send this customised exe file to the person you are trying to help. When that person runs the exe, it opens the vnc client and connects to your pc. Once you have finished fixing the problem you disconect and the exe file you've sent is automatically deleted.

This is something that we use in work alot and save us a good deal of time. With Dynamic dns I can also remotely help clients even when i'm out of the office.

This is a blog posting here that breaks down the steps in creating the exe file

http://ajaxtricks.blogspot.com/2005/11/put-geeksquad-out-of-business.html
Another anomoly is that the person that is recieving the request must have windows messenger (up to date) and installed on their computer. Msn Messenger just isn't up to snuff for that..

I've had remote assistance requests sit in lala land until I brought up windows messenger .. then it connected without a hitch
Ehuna, RDP over HTTP is a feature being added to Vista and Longhorn server. I know your frustrations on this one as I experience it quite a lot. Ive been waiting for RDP over HTTP since they talked about adding it to Windows Server 2003 R2. Small Business Server 2003 has small glimpses of what this technology in Remote Web Workplace and its pretty nice indeed.
page 1 of 1
Comments: 8 | Views: 28069
Microsoft Communities