Netmeeeting & SP2

[Lappers]

I have also had problems using Netmeeting since I
installed SP2. I am using Norton Internet Security and
have tried turning both NIS and Windows Firewall off but
it makes no difference. Calls take an age to connect and
the incoming video is really slow. Any ideas?

[Brian Sullivan MVP]

Post by Lappers
I have also had problems using Netmeeting since I
installed SP2. I am using Norton Internet Security and
have tried turning both NIS and Windows Firewall off but
it makes no difference. Calls take an age to connect and
the incoming video is really slow. Any ideas?

How are you attempting to initiate the calls?

[Lappers]

Yes

-----Original Message-----

Post by Lappers
I have also had problems using Netmeeting since I
installed SP2. I am using Norton Internet Security and
have tried turning both NIS and Windows Firewall off

but

Post by Lappers
it makes no difference. Calls take an age to connect

and

Post by Lappers
the incoming video is really slow. Any ideas?

How are you attempting to initiate the calls?
--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp
.

[Brian Sullivan MVP]

Yes

???

Post by Brian Sullivan MVP
How are you attempting to initiate the calls?

[Lappers]

By double clicking on the persons name on the ils server
listing.

-----Original Message-----

Yes

???

Post by Brian Sullivan MVP
How are you attempting to initiate the calls?

--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp
.

[Brian Sullivan MVP]

Post by Lappers
By double clicking on the persons name on the ils server
listing.

Most public ILS servers use tcp 389 as the LDAP port. XP assumes ( and the
default on Win2000 based ILS servers is) tcp 1002 as the LDAP port. A
fallback mechanism when tcp 1002 fails allows XP to also work with ILS
servers that use 389. The failure to access 1002 and the fallback to 389
causes the long delay you experience on call startup.

To avoid the delay you should specifiy the tcp port of the ILS server
explicitly ( by adding ":389" -colon 389 to the server name in your ILS
server list) for those servers where it is appropriate ( this would be
virtually every public ILS server).

[Lappers]

Would this also account for the slow video connection
when connected? It used to work OK before upgrading to
SP2.

-----Original Message-----

Post by Lappers
By double clicking on the persons name on the ils

server

Post by Lappers
listing.

Most public ILS servers use tcp 389 as the LDAP port. XP

assumes ( and the

default on Win2000 based ILS servers is) tcp 1002 as the

LDAP port. A

fallback mechanism when tcp 1002 fails allows XP to also

work with ILS

servers that use 389. The failure to access 1002 and the

fallback to 389

causes the long delay you experience on call startup.
To avoid the delay you should specifiy the tcp port of

the ILS server

explicitly ( by adding ":389" -colon 389 to the server

name in your ILS

server list) for those servers where it is appropriate (

this would be

virtually every public ILS server).
--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp
.

[Brian Sullivan MVP]

Post by Lappers
Would this also account for the slow video connection
when connected? It used to work OK before upgrading to
SP2.

No -- once you are connected the ILS is not an issue anymore. I don't know
what your slowness while connected is caused by.

[lappers]

This doesn't seem to make any difference. It has only
been a problem since upgrading to service pack 2;
everything was OK before.

-----Original Message-----

Post by Lappers
Would this also account for the slow video connection
when connected? It used to work OK before upgrading to
SP2.

No -- once you are connected the ILS is not an issue

anymore. I don't know

what your slowness while connected is caused by.
--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp
.

[Brian Sullivan MVP]

Post by lappers
This doesn't seem to make any difference. It has only
been a problem since upgrading to service pack 2;
everything was OK before.

There is a new NetMeeting version in SP2- but afaik it should not have the
effect you are experiencing.

[Thomas Bliesener]

Post by lappers
This doesn't seem to make any difference. It has only
been a problem since upgrading to service pack 2;

In the German speaking newsgroup on Netmeeting, there are a couple of
similar reports on a significant slowdown of incoming video after
XP-SP2, and two reports on a repair of this effect by deactivation of
QoS.

[lappers]

Thaks for that; what is QoS?

-----Original Message-----

Post by lappers
This doesn't seem to make any difference. It has only
been a problem since upgrading to service pack 2;

In the German speaking newsgroup on Netmeeting, there

are a couple of

similar reports on a significant slowdown of incoming

video after

XP-SP2, and two reports on a repair of this effect by

deactivation of

QoS.
--
FAQ Netmeeting & Messenger: http://www.uni-

essen.de/kitt/faq-nm.htm

Mails bitte nur in die Gruppe. Requests please to the

newsgroup only.

Viele Gruesse, Regards, Thomas Bliesener, MVP,

http://tinyurl.com/rqed

.

[Brian Sullivan MVP]

Post by lappers
Thaks for that; what is QoS?

QoS = Quality of Service

Basically it is a mechanism for "reserving" bandwidth on networks(especially
important for real time audio/video). It really serves no purpose for over
the internet communications though as the internet does not have QoS
capablity.

[lappers]

Thanks Brisn; how do you deactivate/disable it?

-----Original Message-----

Post by lappers
Thaks for that; what is QoS?

QoS = Quality of Service
Basically it is a mechanism for "reserving" bandwidth on

networks(especially

important for real time audio/video). It really serves

no purpose for over

the internet communications though as the internet does

not have QoS

capablity.
--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp
.

[Brian Sullivan MVP]

Post by lappers
Thanks Brisn; how do you deactivate/disable it?

Open the Control Panel "Network Connections" applet, right click on the
Local Area Network connection ( or whatever is providing your internet
connection), select "Status", then on the "General" tab the "Properties"
button.

In the "General" tab of the pop up about a quarter down is a label "This
connection uses the following items". Deselect the "QoS Packet Scheduler" in
that list, and then select appropriate OKs to exit.

[lappers]

Brian

Thanks for that; the problem is now solved cheers.

-----Original Message-----

Post by lappers
Thanks Brisn; how do you deactivate/disable it?

Open the Control Panel "Network Connections" applet,

right click on the

Local Area Network connection ( or whatever is providing

your internet

connection), select "Status", then on the "General" tab

the "Properties"

button.
In the "General" tab of the pop up about a quarter down

is a label "This

connection uses the following items". Deselect the "QoS

Packet Scheduler" in

that list, and then select appropriate OKs to exit.
--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp
.