No Voice Connection or Remote Ass, (Vid, FT & Chat Do Work)

Howdie, to everyone out there who is pulling their hair
out.

We recently opened a secondary office in New Jersey and
have been trying to get MSN Messenger to work as our
primary means of dialog between our offices. Currently
we are able to chat, have video connections, and transfer
files; however, we are unable to have voice conversations
or remote assistance.

I have followed all steps that are listed in the help
sections and correctly configured the firewall on our end
and router on the other end to to have the required ports
open as listed at
http://www.microsoft.com/windowsxp/...info/deployment
/natfw/natfwissues.asp

Further more, I am certain that the packet is at least
heading toward MSN .Net service since i have watched and
traced the destination IP for the outgoing packets. I am
beginning to think that for somereason that one of the
hops the packets takes while trying to connect to other
end is blocking the ports that we are sending on. Don't
even have a clue if this is correct or not, but it's
looking more and more like the reason we are having this
issue.

This is becoming a very frustation problem, and I am not
looking forward to creating my own custom chat program
when there is a tool already out there to do what we
need. So if anyone knows what is wrong, weather it be
something that I can fix or not please let me know
because all of our personel are very tiered of seeing
this message

"The network or computer you are trying to reach is
experiencing a problem. Please try again later."

When they start a voice conversation or try to add audio
to a an already running Video session.

Thank you,

Eric W. Cahoon
ecahoon@cgvisions.com

Is remote assistance enabled right click on my computer go to properties
and on the remote tab tick the
remote assistance
also people have reported that QoSpacket scheduler has interfered with voice
Try this
right click on my net work places and go to properties,
right click on Local area connection and go to properties and un-tick QoS
packet scheduler
may help

"Eric Cahoon" <ecahoon@cgvisions.com> wrote in message
news:0eef01c346ec$4daaa100$a301280a@phx.gbl...
> Howdie, to everyone out there who is pulling their hair
> out.
>
> We recently opened a secondary office in New Jersey and
> have been trying to get MSN Messenger to work as our
> primary means of dialog between our offices. Currently
> we are able to chat, have video connections, and transfer
> files; however, we are unable to have voice conversations
> or remote assistance.
>
> I have followed all steps that are listed in the help
> sections and correctly configured the firewall on our end
> and router on the other end to to have the required ports
> open as listed at
> http://www.microsoft.com/windowsxp/...info/deployment
> /natfw/natfwissues.asp
>
> Further more, I am certain that the packet is at least
> heading toward MSN .Net service since i have watched and
> traced the destination IP for the outgoing packets. I am
> beginning to think that for somereason that one of the
> hops the packets takes while trying to connect to other
> end is blocking the ports that we are sending on. Don't
> even have a clue if this is correct or not, but it's
> looking more and more like the reason we are having this
> issue.
>
> This is becoming a very frustation problem, and I am not
> looking forward to creating my own custom chat program
> when there is a tool already out there to do what we
> need. So if anyone knows what is wrong, weather it be
> something that I can fix or not please let me know
> because all of our personel are very tiered of seeing
> this message
>
> "The network or computer you are trying to reach is
> experiencing a problem. Please try again later."
>
> When they start a voice conversation or try to add audio
> to a an already running Video session.
>
> Thank you,
>
> Eric W. Cahoon
> ecahoon@cgvisions.com
>