Greetings Gene,

Forwarding port 3389 is not good enough in this scenario - Messenger does not use this port
directly for remote assistance.

Instead, Messenger makes use of Universal Plug and Play (UPnP) to establish Remote Assistance
connections. A random port is used which then redirects to your local port 3389. As such,
in order for this to work, the person needing "assistance" must have a router which supports
UPnP.

You can check ones UPnP status by opening up any Messenger window, pressing the Alt key to
bring up the menubar, choosing the Tools menu, then Options, then Connection category and
after waiting several seconds for the information to population, it should display there.

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2007 Jonathan Kay.
You *must* contact me for redistribution rights.
--


"Gene" <Gene@discussions.microsoft.com> wrote in message
newsD432D6C-20AD-4208-93C6-50AB743F1A19@microsoft.com...

> Remote assistance via Microsoft Windows Live will not connect
>
> Instant Messenging is connected and working fine.
>
> Remote assistance request sent and received by "expert". Expert accepted
> request and sender received acknowledgement that remote access accepted.
>
> Expert received window displaying "waiting for connection" and then message
> received:
>
> "remote assistance could not be established because the remote host name
> could not be resolved please try again". Repeated attempts without success.
>
> Router Port 3389 opened at location requesting assistance. Nothing done to
> router at expert location.
>
> Both computers using Windows XP home edition with same version of Windows
> Live 8.1.0178
>
> Any suggestions how to connect? Any help appreciated. Thanks very much!!
>
> --
> Gene

thank you very much. I will research with the person needing my assistance.
--
Gene


"Jonathan Kay [MVP]" wrote:

> Greetings Gene,
>
> Forwarding port 3389 is not good enough in this scenario - Messenger does not use this port
> directly for remote assistance.
>
> Instead, Messenger makes use of Universal Plug and Play (UPnP) to establish Remote Assistance
> connections. A random port is used which then redirects to your local port 3389. As such,
> in order for this to work, the person needing "assistance" must have a router which supports
> UPnP.
>
> You can check ones UPnP status by opening up any Messenger window, pressing the Alt key to
> bring up the menubar, choosing the Tools menu, then Options, then Connection category and
> after waiting several seconds for the information to population, it should display there.
>
> --
> Jonathan Kay
> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone/
> Messenger Resources - http://messenger.jonathankay.com
> All posts unless otherwise specified are (c) 2007 Jonathan Kay.
> You *must* contact me for redistribution rights.
> --
>
>
> "Gene" <Gene@discussions.microsoft.com> wrote in message
> newsD432D6C-20AD-4208-93C6-50AB743F1A19@microsoft.com...

> > Remote assistance via Microsoft Windows Live will not connect
> >
> > Instant Messenging is connected and working fine.
> >
> > Remote assistance request sent and received by "expert". Expert accepted
> > request and sender received acknowledgement that remote access accepted.
> >
> > Expert received window displaying "waiting for connection" and then message
> > received:
> >
> > "remote assistance could not be established because the remote host name
> > could not be resolved please try again". Repeated attempts without success.
> >
> > Router Port 3389 opened at location requesting assistance. Nothing done to
> > router at expert location.
> >
> > Both computers using Windows XP home edition with same version of Windows
> > Live 8.1.0178
> >
> > Any suggestions how to connect? Any help appreciated. Thanks very much!!
> >
> > --
> > Gene

>
>

Hi,

Shame you can't use Remote Assistance to diagnose Remote Assistance

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2007 Jonathan Kay.
You *must* contact me for redistribution rights.
--


"Gene" <Gene@discussions.microsoft.com> wrote in message
news:FC77AC40-525B-404F-903E-FFE12E57B999@microsoft.com...

> thank you very much. I will research with the person needing my assistance.
> --
> Gene
>
>
> "Jonathan Kay [MVP]" wrote:
>

>> Greetings Gene,
>>
>> Forwarding port 3389 is not good enough in this scenario - Messenger does not use this
>> port
>> directly for remote assistance.
>>
>> Instead, Messenger makes use of Universal Plug and Play (UPnP) to establish Remote
>> Assistance
>> connections. A random port is used which then redirects to your local port 3389. As
>> such,
>> in order for this to work, the person needing "assistance" must have a router which
>> supports
>> UPnP.
>>
>> You can check ones UPnP status by opening up any Messenger window, pressing the Alt key to
>> bring up the menubar, choosing the Tools menu, then Options, then Connection category and
>> after waiting several seconds for the information to population, it should display there.
>>
>> --
>> Jonathan Kay
>> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
>> Associate Expert
>> http://www.microsoft.com/windowsxp/expertzone/
>> Messenger Resources - http://messenger.jonathankay.com
>> All posts unless otherwise specified are (c) 2007 Jonathan Kay.
>> You *must* contact me for redistribution rights.
>> --
>>
>>
>> "Gene" <Gene@discussions.microsoft.com> wrote in message
>> newsD432D6C-20AD-4208-93C6-50AB743F1A19@microsoft.com...

>> > Remote assistance via Microsoft Windows Live will not connect
>> >
>> > Instant Messenging is connected and working fine.
>> >
>> > Remote assistance request sent and received by "expert". Expert accepted
>> > request and sender received acknowledgement that remote access accepted.
>> >
>> > Expert received window displaying "waiting for connection" and then message
>> > received:
>> >
>> > "remote assistance could not be established because the remote host name
>> > could not be resolved please try again". Repeated attempts without success.
>> >
>> > Router Port 3389 opened at location requesting assistance. Nothing done to
>> > router at expert location.
>> >
>> > Both computers using Windows XP home edition with same version of Windows
>> > Live 8.1.0178
>> >
>> > Any suggestions how to connect? Any help appreciated. Thanks very much!!
>> >
>> > --
>> > Gene

>>
>>

I have updated too windows live messenges 8.5 and i find i am no longer able
too use the remote assist feature, if i try too ask for remote assist it
tells me i need too update too the latest version, if i am saked for remote
assist it shows i have refused,

I have version 8.5.1302 1018 and i dont refuse i dont even get a message
telling me i have been asked just the time off the last message.

I have tried repairing it, and i have deleted it and done a fresh install,
still the same.

Hoping someone can help.

Greetings Kona,

What the error message really means (it's written wrong and the links are wrong) is that you
need the latest Windows Messenger (not Live) installed on your PC.

You can grab Windows Messenger 5.1 here:
http://microsoft.com/downloads/detai...f-9157a3b3d774

Note: you don't actually have to use Windows Messenger, it just needs to be installed on XP
for the Remote Assistance feature within Windows Live Messenger to work.

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger
MSN Messenger/Windows Messenger
MessengerGeek Blog: http://www.messengergeek.com
Messenger Resources: http://messenger.jonathankay.com
(c) 2008 Jonathan Kay - If redistributing, you must include this signature or citation
--


"Kona" <Kona@discussions.microsoft.com> wrote in message
news:120A9317-C1A7-40D6-9A4E-0BA74C21CC17@microsoft.com...

> I have updated too windows live messenges 8.5 and i find i am no longer able
> too use the remote assist feature, if i try too ask for remote assist it
> tells me i need too update too the latest version, if i am saked for remote
> assist it shows i have refused,
>
> I have version 8.5.1302 1018 and i dont refuse i dont even get a message
> telling me i have been asked just the time off the last message.
>
> I have tried repairing it, and i have deleted it and done a fresh install,
> still the same.
>
> Hoping someone can help.

This reply just blew my mind! Not because of what it says - but because of
what I found when I followed the instructions ("...check ones UPnP status
....") - when I did this I got the status "You are currently connected to
..NET Messenger Service using a direct connection (no firewall)" - this
despite the fact I am running NIS 2008 AND my computer IS behind a hardware
firewall - is this just a quirk of the software? My IP address is 192.168.1.2
- so very definitely private - but is the status check simply seeing my
"public" IP address connected to .NET Messenger Service ?

"Jonathan Kay [MVP]" wrote:

> Greetings Gene,
>
> Forwarding port 3389 is not good enough in this scenario - Messenger does not use this port
> directly for remote assistance.
>
> Instead, Messenger makes use of Universal Plug and Play (UPnP) to establish Remote Assistance
> connections. A random port is used which then redirects to your local port 3389. As such,
> in order for this to work, the person needing "assistance" must have a router which supports
> UPnP.
>
> You can check ones UPnP status by opening up any Messenger window, pressing the Alt key to
> bring up the menubar, choosing the Tools menu, then Options, then Connection category and
> after waiting several seconds for the information to population, it should display there.
>
> --
> Jonathan Kay
> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone/
> Messenger Resources - http://messenger.jonathankay.com
> All posts unless otherwise specified are (c) 2007 Jonathan Kay.
> You *must* contact me for redistribution rights.
> --
>
>
> "Gene" <Gene@discussions.microsoft.com> wrote in message
> newsD432D6C-20AD-4208-93C6-50AB743F1A19@microsoft.com...

> > Remote assistance via Microsoft Windows Live will not connect
> >
> > Instant Messenging is connected and working fine.
> >
> > Remote assistance request sent and received by "expert". Expert accepted
> > request and sender received acknowledgement that remote access accepted.
> >
> > Expert received window displaying "waiting for connection" and then message
> > received:
> >
> > "remote assistance could not be established because the remote host name
> > could not be resolved please try again". Repeated attempts without success.
> >
> > Router Port 3389 opened at location requesting assistance. Nothing done to
> > router at expert location.
> >
> > Both computers using Windows XP home edition with same version of Windows
> > Live 8.1.0178
> >
> > Any suggestions how to connect? Any help appreciated. Thanks very much!!
> >
> > --
> > Gene

>
>

Hi,

Let it sit there for a minute to fully populate all the data. The first line is referring to
your connect to the .NET Messenger service itself, not your actual network topology (that's
later presented in the dialog).

What "direct connection (no firewall)" means is that you've made an outgoing connection to
the Messenger service on port 1863. The only other thing this line can read is that you're
behind a firewall using HTTP mode (connecting to Messenger on port 80).

So, as long as you can make that outgoing connection, it will say direct. Just lousy wording
on Microsoft's part here.

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger
MSN Messenger/Windows Messenger
MessengerGeek Blog: http://www.messengergeek.com
Messenger Resources: http://messenger.jonathankay.com
(c) 2008 Jonathan Kay - If redistributing, you must include this signature or citation
--


"loptap" <loptap@discussions.microsoft.com> wrote in message
news:F9E7DEBD-107D-4D85-8649-80CD46AD78E9@microsoft.com...

> This reply just blew my mind! Not because of what it says - but because of
> what I found when I followed the instructions ("...check ones UPnP status
> ...") - when I did this I got the status "You are currently connected to
> .NET Messenger Service using a direct connection (no firewall)" - this
> despite the fact I am running NIS 2008 AND my computer IS behind a hardware
> firewall - is this just a quirk of the software? My IP address is 192.168.1.2
> - so very definitely private - but is the status check simply seeing my
> "public" IP address connected to .NET Messenger Service ?
>
> "Jonathan Kay [MVP]" wrote:
>

>> Greetings Gene,
>>
>> Forwarding port 3389 is not good enough in this scenario - Messenger does not use this
>> port
>> directly for remote assistance.
>>
>> Instead, Messenger makes use of Universal Plug and Play (UPnP) to establish Remote
>> Assistance
>> connections. A random port is used which then redirects to your local port 3389. As
>> such,
>> in order for this to work, the person needing "assistance" must have a router which
>> supports
>> UPnP.
>>
>> You can check ones UPnP status by opening up any Messenger window, pressing the Alt key to
>> bring up the menubar, choosing the Tools menu, then Options, then Connection category and
>> after waiting several seconds for the information to population, it should display there.
>>
>> --
>> Jonathan Kay
>> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
>> Associate Expert
>> http://www.microsoft.com/windowsxp/expertzone/
>> Messenger Resources - http://messenger.jonathankay.com
>> All posts unless otherwise specified are (c) 2007 Jonathan Kay.
>> You *must* contact me for redistribution rights.
>> --
>>
>>
>> "Gene" <Gene@discussions.microsoft.com> wrote in message
>> newsD432D6C-20AD-4208-93C6-50AB743F1A19@microsoft.com...

>> > Remote assistance via Microsoft Windows Live will not connect
>> >
>> > Instant Messenging is connected and working fine.
>> >
>> > Remote assistance request sent and received by "expert". Expert accepted
>> > request and sender received acknowledgement that remote access accepted.
>> >
>> > Expert received window displaying "waiting for connection" and then message
>> > received:
>> >
>> > "remote assistance could not be established because the remote host name
>> > could not be resolved please try again". Repeated attempts without success.
>> >
>> > Router Port 3389 opened at location requesting assistance. Nothing done to
>> > router at expert location.
>> >
>> > Both computers using Windows XP home edition with same version of Windows
>> > Live 8.1.0178
>> >
>> > Any suggestions how to connect? Any help appreciated. Thanks very much!!
>> >
>> > --
>> > Gene

>>
>>

I have Windows XP SP3. Recently, I tried to use Windows Live Messenger for a
remote assistance, but all we got was a voice conversation. No session
authorization, no access to the other computer. However, when we used the
Windows Messenger (v.4.7 and 5.1), everything worked fine and access was
granted and help obtained.
Why WinLive messenger would not work, while the Win Messenger works fine?
How to make WinLive messenger to work for Remote Assistance?

--
Ilya Zeldes
Fort Myers, Florida

Greetings,

Just to be clear, you clicked the Activities tab in Windows Live Messenger, chose Remote
Assistance and got a voice conversation?

Or you just couldn't find the option period?

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger
MSN Messenger/Windows Messenger
MessengerGeek Blog: http://www.messengergeek.com
Messenger Resources: http://messenger.jonathankay.com
(c) 2008 Jonathan Kay - If redistributing, you must include this signature or citation
--


"ilyaz" <ilyaz33@hotmail.com> wrote in message news:OCYIZ#ZJJHA.1160@TK2MSFTNGP05.phx.gbl...

> I have Windows XP SP3. Recently, I tried to use Windows Live Messenger for a remote
> assistance, but all we got was a voice conversation. No session authorization, no access to
> the other computer. However, when we used the Windows Messenger (v.4.7 and 5.1), everything
> worked fine and access was granted and help obtained.
> Why WinLive messenger would not work, while the Win Messenger works fine? How to make
> WinLive messenger to work for Remote Assistance?
>
> --
> Ilya Zeldes
> Fort Myers, Florida
>

Jonathan,
I did as "instructed" in the Windows Live Messenger v.8.5.1302.1018.
Highlighted a person, who was on line, Actions, Request remote assistance.
In a new Window, highlighted that person again, clicked OK. In the friend's
chat window, a message appeared about my call for assistance. He accepted
it. I got a message that my friend accepted it and on the bottom of the chat
window message "connecting...". After a while, we were able to write and
talk to each other, but no access to either computer (we run it both ways at
two different occasions).
On the other hand, there was no problem connecting and getting access to the
other computer with Windows Messenger v. 4.7 and 5.1.
Don't understand why?
Thanks for your input.
Ilya

"Jonathan Kay [MVP]" <msnewsreplies@jonathankay.com> wrote in message
news:%23np8inbJJHA.5576@TK2MSFTNGP05.phx.gbl...

> Greetings,
>
> Just to be clear, you clicked the Activities tab in Windows Live
> Messenger, chose Remote Assistance and got a voice conversation?
>
> Or you just couldn't find the option period?
>
> --
> Jonathan Kay
> Microsoft MVP - Windows Live Messenger
> MSN Messenger/Windows Messenger
> MessengerGeek Blog: http://www.messengergeek.com
> Messenger Resources: http://messenger.jonathankay.com
> (c) 2008 Jonathan Kay - If redistributing, you must include this signature
> or citation
> --
>
>
> "ilyaz" <ilyaz33@hotmail.com> wrote in message
> news:OCYIZ#ZJJHA.1160@TK2MSFTNGP05.phx.gbl...

>> I have Windows XP SP3. Recently, I tried to use Windows Live Messenger
>> for a remote assistance, but all we got was a voice conversation. No
>> session authorization, no access to the other computer. However, when we
>> used the Windows Messenger (v.4.7 and 5.1), everything worked fine and
>> access was granted and help obtained.
>> Why WinLive messenger would not work, while the Win Messenger works fine?
>> How to make WinLive messenger to work for Remote Assistance?
>>
>> --
>> Ilya Zeldes
>> Fort Myers, Florida
>>

>