WM4.7 - unable to use a/v when one or both ends are on dial-up

[Michael Taylor]

I'm having problems getting a/v to work with Wm4.7 between two of my PC's.

When both are connected to the internet using different accounts and
telephone lines, they are unable to connect p2p, with an error message from
one or the other saying it was unable to connect to the remote PC. I've not
seen this happen before when both PC's are on dial-up.

Previously, I had upgraded to WM5, and also installed MSN Messenger 6 just
to try it. Since installing them I've been able to use remote assistance,
but not a/v in Wm5 or MSN M6. I decided to revert back to my original
configuration, using wm4.7, but I still can't get the two PC's to use a/v
over dial-up together.

Before trying to get it to work over dial-up I thought perhaps there was a
problem with my DSL router - a Dlink DSL-504, so I even reverted to a
previous UPnP supported firmware that has worked for me in the past. I still
can't a/v with other PC's over my broadband connection.

However, if I return both PC's to my internal LAN, using the built in switch
of the DSL-504, I can get a/v working between any PC behind the DSL-504. I
just can't a/v with anything over the internet, whether the other clients
are on broadband or dial-up.

I believe my UPnP router is not at fault, and something else is affecting
both of my PC's, but I can't think what it might be. I don't use XP's built
in firewall on the LAN, only on dial-up connections, I don't have any other
3rd party firewall software installed. What else could it be?

Maybe I need to uninstall MSN Messenger V6 - could that affect anything even
though I'm not actually using it (I made sure it doesn't get started).

Please note, I have two firmware versions for the DSL-504. Both support
UPnP, the more recent one supports a SIP ALG and the older version does not.
I've tried both firmwares, and with the newer firmware I tried it with SIP
ALG enabled as well as disabled in case it made any difference. It didn't.
As I said before, I don't think the DSL-504 is at fault, since I can't get
the two PC's to a/v with each other even when both are on dial-up. I'm very
puzzled!

Thanks for any advice or help, and sorry for the length, I just wanted to
get as much detail in there as possible. Lets hope the solution is shorter
than my message. With any luck the solution will enable me to use Wm5 and
MSN M6 again too.

Mike

 

[Michael Taylor]

Here's the latest thing I've tried. I've uninstalled MSN Messenger in case
it was interfering with Windows Messenger. Unfortunately it made no
difference.
I've re-tested audio and video and both fail to work. I am able to do remote
assistance, but application sharing and the whiteboard do not work. For
those last two, I get the following error message on the PC that initiated
the request....

"The network or the computer that you are trying to contact is not
responding.

The network or the computer that you are trying to contact is experiencing a
problem, Try again later.

Error 0x80ee000c
SIP Transaction timed out"

Does this shed any light for anyone?
Thanks
Mike

 

[Michael Taylor]

I hope people are interested in this ) Here's the latest.......

After uninstalling MSN Messenger V6.0 and reverting back to Windows
Messenger V4.7.2009 I've been able to do successful audio/video when both
PC's are on dial-up. However this would only work after deleting RTCRES.DLL
from my c:\windows\system32 folder on both machines, and re-booting.
Magically, a/v started to work.
Windows Messenger V5.0 a/v would also work fine to on both machines.
Now I wanted to make my desktop machine (the one normally behind the UPnP
router) work. I can hear and se incoming a/v but no one can hear/see me
whether they are on dial-up or on broadband. I tried disabling QOS on my
desktop PC's LAN card. With this disabled I found that it was impossible to
get a p2p connection between my desktop PC behind the router and the laptop
on dial-up. Re-enabling it resolved that problem. So whats left to try? I'm
going to try rolling back the Intel NIC driver to see if that has any
affect. Anyone care to comment? Please? )
Mike

 

[Jonathan Kay [MVP]]

Greetings Michael,

I've been reading it =).

When you remove these files, Windows File Protection will replace them with the originals it
has stored in its dllcache folder.

Try downloading and running this .reg file:
http://messenger.jonathankay.com/downloads/intelnicfix.reg
Reboot after running and then try again.
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

 

[Michael Taylor]

Hi Jonathan, I hoped you were )
Before responding I thought I'd let you know what happened next....

I rolled back the Intel NIC driver (it's a version 6.1.3.0 dated
25/02/2002). Once I'd done this (no re-boot required), everything worked!
a/v was perfect. I'd tried this before, but that was with MSN Messenger V6.0
installed.

I've seen WFP replace deleted DLL's. Quite a neat idea. I've also noticed
that the RTCRES.DLL I deleted has been put back by WFP - initially I thought
it hadn't, so maybe I didn't wait long enough for it to re-appear.
I've looked at the registry key in the intelnicfix.reg and can see it has
something to do with QOS. If I use this, does it mean I can go back to the
latest Intel NIC driver, and does it make WM not utilize QOS, rather than
disabling QOS for the NIC?
Also, I really do like MSN Messenger V6.0, but I'm reluctant to re-install
it if it makes a/v stop working in WM. Is it likely to do this, or is it all
really a problem with QOS on the Intel NIC?
Many thanks
Mike

 

[Jonathan Kay [MVP]]

Hi Michael,

Actually this .reg fix is for the Intel driver itself, unfortunately Intel isn't providing
any technical details to this specific problem, so it's essentially trial and error at this
point. If you want to "experiment" and try it out with the old driver, I'd suggest that you
set a System Restore point (click Start, Help & Support, "Undo changes to my computer using
System Restore", then Create a restore point) so that you can always go back to when it was
working properly (aka now). You might try install MSN Messenger 6 now, just to see what
exactly will happen now that everything appears to be functional.
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

 

[Michael Taylor]

Hi Jonathan,

My dinners is ready and I'm pretty hungry! I will try out what you've said
tomorrow, and will let you know how it all goes. I'm keen to get MSN
Messenger V6.0 a/v working too as I like the ability to re-size video and
it's generally more friendly. I see WM as my failsafe so whatever happens
with MSNM6 I'll want to make sure WM is not affected.
Thanks for your help, and I'll get back to you tomorrow!
Mike

 

[Jonathan Kay [MVP]]

Hi Mike,

Good luck =).
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

 

[Jonathan Kay [MVP]]

Greetings Mike,

Thanks very very much for that test data, it may prove extremely valuable in the future. I
can't really say I knew what was going on all along, as you proved yourself, there are just
so many issues that this can occur with (the MSN Messenger 6 RTC supposedly 'broken' DLLs,
Intel NICs, different routers, etc.).

I highly doubt that you'll need to remove the registry additions (this NIC probably has
actually been around for awhile now, still no fix that I've heard about has been produced).

Hope your back feels better, glad to be of assistance =).
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com