Dlink 504 Adsl router hangs with messenger

[Paul Cahill]

I am using a dlink 504 adsl router. It has the latest UK firmware which
supports uPnP.

If I try to use Windows or MSN messenger to video conference or webcam the
DSL504 hangs and broadband access fails for all users.

I am running dsl 405 firmware R2.21.002.06.b12uk.
I have enabled uPnP and ticked all the boxes in NAT ALG.
I have installed the uPnP network compenent on XP.
I have started the uPnP service on the pc.

Any ideas?

Paul Cahill

 

[NeoSadist]

I am using a dlink 504 adsl router. It has the latest UK firmware which
supports uPnP.

If I try to use Windows or MSN messenger to video conference or webcam the
DSL504 hangs and broadband access fails for all users.

I am running dsl 405 firmware R2.21.002.06.b12uk.
I have enabled uPnP and ticked all the boxes in NAT ALG.
I have installed the uPnP network compenent on XP.
I have started the uPnP service on the pc.

Any ideas?

Paul Cahill

Check if it has a firewall configured and/or if the computers using it have
upnp enabled. It may need upnp enabled (although upnp can be a big
security risk).

 

[Paul Cahill]

Oh yes it has a firewall the only way around that is to take my pc out the
loop and putting it in DMZ. I thought uPnP was meant to sort this.
I can't see a reason why the router should hang.

In my post you can see that I've enabled uPnP all over.


Paul

 

[Michael Taylor]

Hi Paul,

I have the same router and firmware as you but don't have any issues with
it. In the NAT ALG's, they are all checked except for SIP.
Do you have an A or B version of the DSL504? Mine is a B. It say Ver: B1 on
the underside of the unit.
Mike

 

[Paul Cahill]

Factory reset sorted it.

The only option I did not set ON this after the reset was the
NAT ALG SIP (video/audio/white board/remote control) check box.


All working fine. audio, video and remote assistance.



NAT ALGs


H.323
IPsec
PPTP
ICQ (audio)
SIP (video/audio/white board/remote control)

Do you think that SIP was the issue making the router itself hang. I did the
reset because dlink said so.

Paul

 

[Michael Taylor]

Hi Paul,

I think it's possible that it made your router hang. Windows Messenger uses
SIP and MSN Messenger doesn't (AFAIK), and I can use either product for a/v
when SIP ALG is off. However, I've not tried it with SIP ALG on so I can't
say for sure.
The only problem I have with this router/firmware combination is performing
file transfers using MSN Messenger - it locks the router up. If I use
Windows Messenger (V5) the p2p connection does not complete so the FT fails,
but the router remains stable.

HTH
Mike

 

[Paul Cahill]

Hi Mike.

I tried sending and receiving files last night. Fine, so I'm not sure what
your problem is. It was fairly slow though.

I read a post from an MVP about web cam performance. He suggested opening up
port 9000 otherwise messenger will go via a relay.
I must admit I find the firewall config fairly confusing. Do you need to
always add ip ranges to redirect to or can you open up a port for all?
It seems to want both source and dest ip addresses.

If you have time, could you email me a screen shot example.

Paul


Select index to set Not selected

Item Name
State enableddisabled
Pass or Block PassBlock
Interface ethernetPipex
Protocol ICMPTCPUDPAll
Direction InOut
Source
IP Address . . .
Subnet Mask 255.255.255.255 (/32)255.255.255.254
(/31)255.255.255.252 (/30)255.255.255.248 (/29)255.255.255.240
(/28)255.255.255.224 (/27)255.255.255.192 (/26)255.255.255.128
(/25)255.255.255.0 (/24)255.255.254.0 (/23)255.255.252.0 (/22)255.255.248.0
(/21)255.255.240.0 (/20)255.255.224.0 (/19)255.255.192.0 (/18)255.255.128.0
(/17)255.255.0.0 (/16)255.254.0.0 (/15)255.252.0.0 (/14)255.248.0.0
(/13)255.240.0.0 (/12)255.224.0.0 (/11)255.192.0.0 (/10)255.128.0.0
(/9)255.0.0.0 (/8)254.0.0.0 (/7)252.0.0.0 (/6)248.0.0.0 (/5)240.0.0.0
(/4)224.0.0.0 (/3)192.0.0.0 (/2)128.0.0.0 (/1)0.0.0.0 (/0)
=<>
Start Port
End Port
Destination
IP Address . . .
Subnet Mask 255.255.255.255 (/32)255.255.255.254
(/31)255.255.255.252 (/30)255.255.255.248 (/29)255.255.255.240
(/28)255.255.255.224 (/27)255.255.255.192 (/26)255.255.255.128
(/25)255.255.255.0 (/24)255.255.254.0 (/23)255.255.252.0 (/22)255.255.248.0
(/21)255.255.240.0 (/20)255.255.224.0 (/19)255.255.192.0 (/18)255.255.128.0
(/17)255.255.0.0 (/16)255.254.0.0 (/15)255.252.0.0 (/14)255.248.0.0
(/13)255.240.0.0 (/12)255.224.0.0 (/11)255.192.0.0 (/10)255.128.0.0
(/9)255.0.0.0 (/8)254.0.0.0 (/7)252.0.0.0 (/6)248.0.0.0 (/5)240.0.0.0
(/4)224.0.0.0 (/3)192.0.0.0 (/2)128.0.0.0 (/1)0.0.0.0 (/0)
=<>
Start Port
End Port

 

[Michael Taylor]

Hi Paul,

Thanks for the info on the webcam - I haven't had any speed problems with it
so I won't change anything unless I start to get a problem.

I don't have any fixed port re-directions configured, so I've got nothing to
screen print. Everything is UPnP so it's all changing dynamically depending
on what I do in Windows or MSN Messenger. Basically, using UPnP you
shouldn't need any port-redirections.

When I've experimented with re-directions I've always put in my local IP
address, after having set it to a fixed address in Network Connections
within Windows. I've done this to try and get remote access to work. I found
I could only get that to work if the PC was put in the DMZ because not all
protocols can be re-directed with the DSL504. For example, you can only
re-direct TCP and UDP protocols, not IPSEC, PPTP, and SIP.

Do you still have a webcam problem? Is it possible the problem is at the
other end? When I've had problems like this I always try to eliminate things
by trying it on dial-up, thus bypassing the DSL504, proving or disproving
that the router is the problem. At least it gives you more to go on.

I'll be away for a week. I'd be happy to help out further on my return.

Good luck
Mike

 

[Paul Cahill]

Mike

Everything is fine now. Thanks for all the friendly advise.
Hope its vacation and not work.

Paul