M
Mark Doran
OK, I definitely need expert help please...my brain hurts
from trying so hard to figure out what I'm doing
wrong!! ;-)
I have a LAN which is set up with an Active Directory
domain and all the user accounts using roaming profiles.
All the client systems are XP with SP1 installed. I have
a VPN/Firewall router managing the connection to the
internet; it's UPnP capable and enabled.
I have exactly one client system from which I can use
either the Windows or MSN Messenger clients to do
voice/video conferences with remote sites. Works
perfectly. Trouble is, that system is on its last legs
and desparately needs replacement. Enter the problem...
I can get no other system to work when using either
version of Messenger. Same OS version and service pack
level.
I have looked for the UPnP windows component. The
working system doesn't have this installed. Really, I
doubled checked in the add/remove programs "windows
components" place.
I have looked for the UPnP service in the "services" list
under the control panel. It's not enabled on the working
system. Really, I double checked this too ;-)
I have tried two different routers:
Asante VR2004AC VPN. In this case, "not working" means
that the local client receives incoming voice and video
but the remote end sees nothing and hears nothing. UPnP
is enabled on the router. The magic client system works
prefectly.
Linsys WRV54G. In this case, "not working" means that
the local client sees a black screen where remote video
should be an no audio and the symptoms at the remote site
are the same. UPnP is enabled on the router. The magic
client system works prefectly.
The remote site I'm using for testing is "known good" in
that it can video chat to a number of other folks wihtout
issue. The problem has to be local to my end.
Symptoms don't change if I use system local or domain
admin accounts versus regular user accounts for login to
the client systems.
In desperation I tried installing the Windows UPnP
component and enabling the UPnP service by hand on one of
the new systems. No change in symptoms.
Does anyone have any suggestions on what it is about that
one system that makes it magic and lets it work where no
other apparently can?? The magic system is dying as I
say so I really need to figure out how to annoint a new
magic machine... I've just stared at this too long now
and can't for the life of me figure out what could be
different.
Any clues would be much appreciated! Thanks in advance.
Cheers,
Mark.
from trying so hard to figure out what I'm doing
wrong!! ;-)
I have a LAN which is set up with an Active Directory
domain and all the user accounts using roaming profiles.
All the client systems are XP with SP1 installed. I have
a VPN/Firewall router managing the connection to the
internet; it's UPnP capable and enabled.
I have exactly one client system from which I can use
either the Windows or MSN Messenger clients to do
voice/video conferences with remote sites. Works
perfectly. Trouble is, that system is on its last legs
and desparately needs replacement. Enter the problem...
I can get no other system to work when using either
version of Messenger. Same OS version and service pack
level.
I have looked for the UPnP windows component. The
working system doesn't have this installed. Really, I
doubled checked in the add/remove programs "windows
components" place.
I have looked for the UPnP service in the "services" list
under the control panel. It's not enabled on the working
system. Really, I double checked this too ;-)
I have tried two different routers:
Asante VR2004AC VPN. In this case, "not working" means
that the local client receives incoming voice and video
but the remote end sees nothing and hears nothing. UPnP
is enabled on the router. The magic client system works
prefectly.
Linsys WRV54G. In this case, "not working" means that
the local client sees a black screen where remote video
should be an no audio and the symptoms at the remote site
are the same. UPnP is enabled on the router. The magic
client system works prefectly.
The remote site I'm using for testing is "known good" in
that it can video chat to a number of other folks wihtout
issue. The problem has to be local to my end.
Symptoms don't change if I use system local or domain
admin accounts versus regular user accounts for login to
the client systems.
In desperation I tried installing the Windows UPnP
component and enabling the UPnP service by hand on one of
the new systems. No change in symptoms.
Does anyone have any suggestions on what it is about that
one system that makes it magic and lets it work where no
other apparently can?? The magic system is dying as I
say so I really need to figure out how to annoint a new
magic machine... I've just stared at this too long now
and can't for the life of me figure out what could be
different.
Any clues would be much appreciated! Thanks in advance.
Cheers,
Mark.