WD NAS & Port Forwarding & UPNP

[NuvverBloke]

I have two WD NAS. I want to back up one to the other.  When I set up the port forwarding on the destination NAS this is not reflected in the router port forwarding table.  I understood that since the router is UPNP it should "find" the port forwarding settings from the server and add it to the table?  When the NAS tests the Port access it fails. I have tried adding forwarding the ports manually but makes no difference!

Any pointers appreciated

thanks

EE ADSL BB Router

[Mustrum]

@NuvverBloke  which router are you using?

Are both WD's connected to your LAN or is one external?

Port forwarding tends to be used for external routes.

[NuvverBloke]

Hi,

EE Smart Hub 2.  They are both on the same network with fixed IP.  Following the WD instruction to setup backup between to devices they are specific about router being UPnP, and setting up Ports 22 (SSH) and 873 (remote back up).  No instructions for setting remote backup on same IP!

Initially bot ports we in stealth, according to shields up!.  Once I created rules in the router 22 is open but 873 is closed (RSYNC).  Since I can't progress until both are open I am at a loss.  WD server still fails port forward check even when Router rule exists and port 22 is open. 

[Mustrum · Accepted solution]

@NuvverBloke  can you provide a link to the WD instructions you are following?

I would expect the WD to be running a back up program and with it pointing to your other NAS. Like I said the ports and checks you are looking at are external, so I can;t see why you need external access to get one device to talk to another on your LAN.

[NuvverBloke]

@Mustrum 

Steps to Setup and Use Remote Backups on My Cloud OS 5 (wd.com)

Hi,

Looks like it might be working!, following your input about no need to Port Forwarding and realising that I should use the local IP and not WAN when creating the backup job on the target server, the job seems to be running and creating backup on the destination server. 

Appreciate your help! 

[Mustrum]

@NuvverBloke  No worries, glad it is now working.

Happy to have been able to help.