Netmeeting on XP pro no sound
Frenchguy
the host and i tryed it with a collegue and we cannot make the audio
work. The chat work, the whiteboard work, but cannot share desktop
either. My ISP is Sympatico and i have a linksys router.
In the UPnP Forwarding i have the port 1720 TCP, 1731 TCP, 1024 TCP
enable
To connect to my Company Network I'm using IPSec client, this work
perfectly.
I did run netstat -a on my laptop and the result shows that 1720 is
listening.
I can use audio with Instant messenger 5.1 (5.1.0701) it's for
exchange cannot use the public one.
I don't know where to check anymore,
Any Ideas!
Thanks
usasma
- John
Frenchguy
>
> - Show quoted text -
I just did...installed IPV6 and nothing change.
Do I have to activate interfaces ?
I want to have port 1731 which is audio port for NetMeeting open so
that I can have an audio conference.
Brian Sullivan
> On Apr 4, 12:20 pm, usasma <usa...@discussions.microsoft.com> wrote:
>
>
>
>
>
> > Just a shot in the dark here, but have you enabled IPv6?
>
> > - John
>
> > "Frenchguy" wrote:
> > > the host and i tryed it with a collegue and we cannot make the audio
> > > work. The chat work, the whiteboard work, but cannot share desktop
> > > either. My ISP is Sympatico and i have a linksys router.
> > > In the UPnP Forwarding i have the port 1720 TCP, 1731 TCP, 1024 TCP
> > > enable
> > > To connect to my Company Network I'm using IPSec client, this work
> > > perfectly.
>
> > > I did run netstat -a on my laptop and the result shows that 1720 is
> > > listening.
> > > I can use audio with Instant messenger 5.1 (5.1.0701) it's for
> > > exchange cannot use the public one.
>
> > > I don't know where to check anymore,
> > > Any Ideas!
> > > Thanks- Hide quoted text -
>
> > - Show quoted text -
>
> I just did...installed IPV6 and nothing change.
> Do I have to activate interfaces ?
> that I can have an audio conference.- Hide quoted text -
>
> - Show quoted text -
For NetMeeting to have audio/video functionality behind a router it
will necessary to designate the NetMeeting computer as the dmz
machine. NetMeeting uses H323 for audio/video which uses tcp port 1720
for call connection but then negotiates a set of udp ports for
transport. Fowarding/opening individual ports (perhpas on a trigger
basis) is theoretically a solution but I have not heard of it working.
A problem with some ethernet adaptors (and maybe wireless as well) can
cause no audio/video transmission at the sending end. If this is a
problem disabling the QOS packet schedule at the sending end (http://
radio.weblogs.com/0127028/2004/10/18.html for details) may be
necessary.
With regard to your desktop sharing problem -- the only thing I can
think of that would prevent desktop sharing ( and still allow
whiteboard, chat and file transfer to work) is not transport related
but but group policy related -- there is a group policy setting that
will disable use of desktop sharing (I can't tell from your problem
description if this is a possiblity though).
Frenchguy
>
> - Show quoted text -
About the sharing application grayed out I did exactly what it says
here: http://support.microsoft.com/kb/175956 because I had Procomm
Plus as I think it's one of the best terminal emulator, so I'll need
to find something supported by Microsoft. Anyhow it didn't resolve the
grayed out issue, it's still doesn't work.
for the Audio I'll set DMZ to my laptop address, but since I'm
tunneling to my company network, do you think it DMZ will still work
as I'm getting a different IP when I tunnel to another network.
I'll look into all the group policy...
Thanks for your support
Brian Sullivan
> > will necessary to designate theNetMeetingcomputer as the dmz
> > for call connection but then negotiates a set of udp ports for
> > transport. Fowarding/opening individual ports (perhpas on a trigger
> > basis) is theoretically a solution but I have not heard of it working.
>
> > A problem with some ethernet adaptors (and maybe wireless as well) can
> > cause no audio/video transmission at the sending end. If this is a
> > problem disabling the QOS packet schedule at the sending end (http://
> > radio.weblogs.com/0127028/2004/10/18.html for details) may be
> > necessary.
>
> > With regard to your desktop sharing problem -- the only thing I can
> > think of that would prevent desktop sharing ( and still allow
> > whiteboard, chat and file transfer to work) is not transport related
> > but but group policy related -- there is a group policy setting that
> > will disable use of desktop sharing (I can't tell from your problem
> > description if this is a possiblity though).- Hide quoted text -
>
> > - Show quoted text -
>
> About the sharing application grayed out I did exactly what it says
> Plus as I think it's one of the best terminal emulator, so I'll need
> to find something supported by Microsoft. Anyhow it didn't resolve the
> grayed out issue, it's still doesn't work.
Did you examine the group policy settings?
> for the Audio I'll set DMZ to my laptop address, but since I'm
> tunneling to my company network, do you think it DMZ will still work
> as I'm getting a different IP when I tunnel to another network.
> I'll look into all the group policy...
> Thanks for your support- Hide quoted text -
>
I am not sure what tunnelling means in this case -- are you saying you
are using a VPN? Generally H.323/NetMeeting audio/video does not work
when running through a NAT . Using the DMZ on a router that you are
NATed behind relieves that problem -- but if you are connecting via a
VPN NATing at the router should not be a factor. If there is a NAT
somewhere else in the network path though or if the VPN itself is
somehow mangling the H.323 transmission there is not much you can do
at your end.