Sign in with
Sign up | Sign in
Your question

Need some help with a unique configuration

Tags:
  • Remote Desktop
  • Computers
  • Configuration
  • Windows XP
Last response: in Windows XP
Share
Anonymous
August 23, 2004 1:07:25 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

OK, this sounds weird, but it is for real.


COMPUTER A ------------ ------------- COMPUTER B **COM1**TEST
EQUIPMEMNT
| |
| |
FIREWALL AND ROUTER
192.X.X.X SUBNET



COMPUTER A = WINDOWS XP SP1

COMPUTER B = WINDOWS XP SP1


COMPUTER B is connected to TEST EQUIPMENT through COM1

COMPUTER B is receiving AUDIO INPUT from TEST EQUIPMENT via AUDIO JACK

COMPUTER B is hosting an INDEPENDENT CALL with NETMEETING, and
AUTOMATICALLY accepts calls and requests for control.

COMPUTER A can access COMPUTER B from either NETMEETING or REMOTE
DESKTOP
IF COMPUTER A accesses COMPUTER B using REMOTE DESKTOP, sounds from
COMPUTER B are transferred BUT THE AUDIO INPUT FROM THE TEST EQUIPMENT
IS NOT TRANSFERRED. (I researched this extensively, it is not a bug or
a setup issue). Therefore, COMPUTER A must interact with COMPUTER B
using NETMEETING.

Connection is successfully established using NETMEETING, and COMPUTER
A successfully controles TEST EQUIPMENT remote AND the user on
COMPUTER A can hear the AUDIO INPUT from TEST EQUIPMENT.

After a period of time, COMPUTER B has a LOG FILE that COMPUTER A
needs locally. COMPUTER A disconnects from the NETMEETING CALL and
uses REMOTE DESKTOP with LOCAL DISK ASSESS for computer B. COMPUTER A
copies the log file from COMPUTER B to a local folder on COMPUTER A.
(So far, so good).

Now, COMPUTER A disconnects the REMOTE DESKTOP CONNECTION from
COMPUTER B.
Next, COMPUTER A attempts to reconnect using NETMEETING (the only way
to hear the audio over the link). But WAIT!! Although the call goes
through, the NETMEETING window is garbled and does not properly
display. Attempts to take control are unsuccessful. COMPUTER A hangs
up the NETMEETING call to COMPUTER B and reconnects via REMOTE
DESKTOP. Everything appears in order. COMPUTER A hangs up the REMOTE
DESKTOP and attempts again to call via NETMEETING. Same result, a
garbled window view and no way to gain control.

Any ideas? Is this a case of "once you use Remote Desktop to log in,
the remote machine will not function properly with NetMeeting?"

I realize that NetMeeting was replaced by Remote Desktop, but the
audio transfer functionality is not included in Remote Desktop.

Thoughts? Thanks. I realize this is weird, but I don't have a better
way to configure.

More about : unique configuration

Anonymous
September 4, 2004 2:07:31 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I'm not sure our collective patience is able to deal with the diagram and
the lengthy explanation. Can you say in fewer words what you need to be
able to do--why both NetMeeting and Remote Desktop are involved?

"M Lunday" <lundaym@hotmail.com> wrote in message
news:3fc504ad.0408222007.22dcee7b@posting.google.com...
> OK, this sounds weird, but it is for real.
>
>
> COMPUTER A ------------ ------------- COMPUTER B **COM1**TEST
> EQUIPMEMNT
> | |
> | |
> FIREWALL AND ROUTER
> 192.X.X.X SUBNET
>
>
>
> COMPUTER A = WINDOWS XP SP1
>
> COMPUTER B = WINDOWS XP SP1
>
>
> COMPUTER B is connected to TEST EQUIPMENT through COM1
>
> COMPUTER B is receiving AUDIO INPUT from TEST EQUIPMENT via AUDIO JACK
>
> COMPUTER B is hosting an INDEPENDENT CALL with NETMEETING, and
> AUTOMATICALLY accepts calls and requests for control.
>
> COMPUTER A can access COMPUTER B from either NETMEETING or REMOTE
> DESKTOP
> IF COMPUTER A accesses COMPUTER B using REMOTE DESKTOP, sounds from
> COMPUTER B are transferred BUT THE AUDIO INPUT FROM THE TEST EQUIPMENT
> IS NOT TRANSFERRED. (I researched this extensively, it is not a bug or
> a setup issue). Therefore, COMPUTER A must interact with COMPUTER B
> using NETMEETING.
>
> Connection is successfully established using NETMEETING, and COMPUTER
> A successfully controles TEST EQUIPMENT remote AND the user on
> COMPUTER A can hear the AUDIO INPUT from TEST EQUIPMENT.
>
> After a period of time, COMPUTER B has a LOG FILE that COMPUTER A
> needs locally. COMPUTER A disconnects from the NETMEETING CALL and
> uses REMOTE DESKTOP with LOCAL DISK ASSESS for computer B. COMPUTER A
> copies the log file from COMPUTER B to a local folder on COMPUTER A.
> (So far, so good).
>
> Now, COMPUTER A disconnects the REMOTE DESKTOP CONNECTION from
> COMPUTER B.
> Next, COMPUTER A attempts to reconnect using NETMEETING (the only way
> to hear the audio over the link). But WAIT!! Although the call goes
> through, the NETMEETING window is garbled and does not properly
> display. Attempts to take control are unsuccessful. COMPUTER A hangs
> up the NETMEETING call to COMPUTER B and reconnects via REMOTE
> DESKTOP. Everything appears in order. COMPUTER A hangs up the REMOTE
> DESKTOP and attempts again to call via NETMEETING. Same result, a
> garbled window view and no way to gain control.
>
> Any ideas? Is this a case of "once you use Remote Desktop to log in,
> the remote machine will not function properly with NetMeeting?"
>
> I realize that NetMeeting was replaced by Remote Desktop, but the
> audio transfer functionality is not included in Remote Desktop.
>
> Thoughts? Thanks. I realize this is weird, but I don't have a better
> way to configure.
Anonymous
September 4, 2004 2:09:36 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Can you accomplish the log file transfer without using rd--if these machines
are separated by an untrusted network, perhaps a VPN connection between
them?

I'd think you'd have a good chance of managing the job of moving the log
file without interrupting the NetMeeting call.

Otherwise, I don't really know where to start--your observations are clear,
but I think I'd have to replicate your setup to see whether it does the same
thing for me.

"M Lunday" <lundaym@hotmail.com> wrote in message
news:3fc504ad.0408222007.22dcee7b@posting.google.com...
> OK, this sounds weird, but it is for real.
>
>
> COMPUTER A ------------ ------------- COMPUTER B **COM1**TEST
> EQUIPMEMNT
> | |
> | |
> FIREWALL AND ROUTER
> 192.X.X.X SUBNET
>
>
>
> COMPUTER A = WINDOWS XP SP1
>
> COMPUTER B = WINDOWS XP SP1
>
>
> COMPUTER B is connected to TEST EQUIPMENT through COM1
>
> COMPUTER B is receiving AUDIO INPUT from TEST EQUIPMENT via AUDIO JACK
>
> COMPUTER B is hosting an INDEPENDENT CALL with NETMEETING, and
> AUTOMATICALLY accepts calls and requests for control.
>
> COMPUTER A can access COMPUTER B from either NETMEETING or REMOTE
> DESKTOP
> IF COMPUTER A accesses COMPUTER B using REMOTE DESKTOP, sounds from
> COMPUTER B are transferred BUT THE AUDIO INPUT FROM THE TEST EQUIPMENT
> IS NOT TRANSFERRED. (I researched this extensively, it is not a bug or
> a setup issue). Therefore, COMPUTER A must interact with COMPUTER B
> using NETMEETING.
>
> Connection is successfully established using NETMEETING, and COMPUTER
> A successfully controles TEST EQUIPMENT remote AND the user on
> COMPUTER A can hear the AUDIO INPUT from TEST EQUIPMENT.
>
> After a period of time, COMPUTER B has a LOG FILE that COMPUTER A
> needs locally. COMPUTER A disconnects from the NETMEETING CALL and
> uses REMOTE DESKTOP with LOCAL DISK ASSESS for computer B. COMPUTER A
> copies the log file from COMPUTER B to a local folder on COMPUTER A.
> (So far, so good).
>
> Now, COMPUTER A disconnects the REMOTE DESKTOP CONNECTION from
> COMPUTER B.
> Next, COMPUTER A attempts to reconnect using NETMEETING (the only way
> to hear the audio over the link). But WAIT!! Although the call goes
> through, the NETMEETING window is garbled and does not properly
> display. Attempts to take control are unsuccessful. COMPUTER A hangs
> up the NETMEETING call to COMPUTER B and reconnects via REMOTE
> DESKTOP. Everything appears in order. COMPUTER A hangs up the REMOTE
> DESKTOP and attempts again to call via NETMEETING. Same result, a
> garbled window view and no way to gain control.
>
> Any ideas? Is this a case of "once you use Remote Desktop to log in,
> the remote machine will not function properly with NetMeeting?"
>
> I realize that NetMeeting was replaced by Remote Desktop, but the
> audio transfer functionality is not included in Remote Desktop.
>
> Thoughts? Thanks. I realize this is weird, but I don't have a better
> way to configure.
!