Failed to enable Remote Access - Connection failed (31520)

I see there’s also similar thread in community but no effective solution for this issue.

When trying to enable Remote Access, always I got Error 31520 and says there’s no internet connection. But actually in Dashboard → Network → LAN configuration, it displays Internet Access is good.

Also from MBLD console, ping www.wdc.com with no difficulty:

MyBookLiveDuo:~# ping www.wdc.com
PING a1026.g.akamai.net (184.50.87.91) 56(84) bytes of data.
64 bytes from a184-50-87-91.deploy.akamaitechnologies.com (184.50.87.91): icmp_seq=1 ttl=54 time=98.1 ms
64 bytes from a184-50-87-91.deploy.akamaitechnologies.com (184.50.87.91): icmp_seq=2 ttl=54 time=96.3 ms
64 bytes from a184-50-87-91.deploy.akamaitechnologies.com (184.50.87.91): icmp_seq=3 ttl=54 time=96.2 ms
64 bytes from a184-50-87-91.deploy.akamaitechnologies.com (184.50.87.91): icmp_seq=4 ttl=54 time=94.2 ms
^C
a1026.g.akamai.net ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 94.220/96.228/98.175/1.432 ms

UPnP has been enabled on my LAN gateway ( a Cisco RV180W)

I also see same problem on my friends MBL last sunday, so I doubt this may be WD’s software issue.

I’m afraid I found some interop issue between My Book Live Duo / My Book Live and some other brands’ router

The SSDP Discover sent out by MBLD cannot be responded by my Cisco RV180W router

While the SSDP interop between my Windows 7 laptop (192.168.1.208) and Cisco RV180W (192.168.1.1) is some kind of fine

Look into MBLD’s SSDP Discover message, it is very specific:

M-SEARCH * HTTP/1.1\r\n
[Expert Info (Chat/Sequence): M-SEARCH * HTTP/1.1\r\n]
Request Method: M-SEARCH
Request URI: *
Request Version: HTTP/1.1
HOST: 239.255.255.250:1900\r\n
ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1\r\n
MAN: “ssdp:discover”\r\n
MX: 2\r\n
\r\n

While Win7 SSDP Discover is relatively generic:

M-SEARCH * HTTP/1.1\r\n
[Expert Info (Chat/Sequence): M-SEARCH * HTTP/1.1\r\n]
[Message: M-SEARCH * HTTP/1.1\r\n]
[Severity level: Chat]
[Group: Sequence]
Request Method: M-SEARCH
Request URI: *
Request Version: HTTP/1.1
Host:239.255.255.250:1900\r\n
ST:upnp:rootdevice\r\n
Man:“ssdp:discover”\r\n
MX:3\r\n
\r\n

I guess the similar situation happens on my friend’s TP-Link router. I do not have uPnP experience and the protocol document is very rare online, just mark this down. Does anyone have some idea about this?