S
Scott
Hi,
I know this is a FAQ - I *did* read all posts with "netmeeting" and
"messenger" in the subject before posting, but didn't find the information I
needed (i.e. recommendations and comparisons). I just subscribed today.
I need a messenging client that will:
* let me do remote collaboration with co-workers (share application and
remote assistance)
* allow me to do remote support for customers (so best case is the
messenging client would normally be installed already). I need to see and
in some case control their machines.
* work in both W2K (usually Server, occasionally Professional) and WXP
environments (on the remote end - I have WXP Pro on my end)
* easiest setup for the customer re: inbound firewall configuration
I've seen from trolling the web and various newsgroups that MS is pushing
Windows Messenger 4.7 for this purpose. I've also seen some posts saying
Messenger 4.7 isn't there yet and to stick with NetMeeting.
I've installed and tested all three but my test environment is a bit
artificial: two machines, connected thru a router/hub/firewall. For
Messenger I'm using two different .NET accounts.
For NetMeeting, I opened port 522, 1503, and 1720. For Messenger(s) I
opened port 3389.
For NetMeeting, I was able to get it to work and share applications between
the two machines. I could connect on both the internal IP address
(192.168.0.x) and external IP address (which was forwarded to the "other"
machine via the firewall rules).
For Windows Messenger 4.7, I just get a "waiting" dialog when I try sharing
an application between the two machines. However, I did read here
http://support.microsoft.com/default.aspx?scid=kb;en-us;301529 that my test
scenario might not work - "Remote Assistance works if either the novice or
the expert is behind a NAT, but not if the novice and the expert are both
behind a NAT."
For MSN Messenger 6.0, I can make a request for Remote Assistance, but the
request just goes into the ether - I never get a window showing the novice
computer. Same thing for Sharing Application - I never get a window from
which I can share an application.
So, to wrap up:
* in your humble opinion, which is the better client for the usage I state
above? One thing I like about NetMeeting is I can connect by IP address
rather than having to add a buddy.
* and, if it's one of the Messengers, what do I need to do to my firewall to
get this to work?
Thanks, sorry this was somewhat long.
Scott
I know this is a FAQ - I *did* read all posts with "netmeeting" and
"messenger" in the subject before posting, but didn't find the information I
needed (i.e. recommendations and comparisons). I just subscribed today.
I need a messenging client that will:
* let me do remote collaboration with co-workers (share application and
remote assistance)
* allow me to do remote support for customers (so best case is the
messenging client would normally be installed already). I need to see and
in some case control their machines.
* work in both W2K (usually Server, occasionally Professional) and WXP
environments (on the remote end - I have WXP Pro on my end)
* easiest setup for the customer re: inbound firewall configuration
I've seen from trolling the web and various newsgroups that MS is pushing
Windows Messenger 4.7 for this purpose. I've also seen some posts saying
Messenger 4.7 isn't there yet and to stick with NetMeeting.
I've installed and tested all three but my test environment is a bit
artificial: two machines, connected thru a router/hub/firewall. For
Messenger I'm using two different .NET accounts.
For NetMeeting, I opened port 522, 1503, and 1720. For Messenger(s) I
opened port 3389.
For NetMeeting, I was able to get it to work and share applications between
the two machines. I could connect on both the internal IP address
(192.168.0.x) and external IP address (which was forwarded to the "other"
machine via the firewall rules).
For Windows Messenger 4.7, I just get a "waiting" dialog when I try sharing
an application between the two machines. However, I did read here
http://support.microsoft.com/default.aspx?scid=kb;en-us;301529 that my test
scenario might not work - "Remote Assistance works if either the novice or
the expert is behind a NAT, but not if the novice and the expert are both
behind a NAT."
For MSN Messenger 6.0, I can make a request for Remote Assistance, but the
request just goes into the ether - I never get a window showing the novice
computer. Same thing for Sharing Application - I never get a window from
which I can share an application.
So, to wrap up:
* in your humble opinion, which is the better client for the usage I state
above? One thing I like about NetMeeting is I can connect by IP address
rather than having to add a buddy.
* and, if it's one of the Messengers, what do I need to do to my firewall to
get this to work?
Thanks, sorry this was somewhat long.
Scott