Take it easy on me 
I want to make the initial Replication to my new backup server ...... long time and $$$ in the making. It's on my local network and don't need security.
TN 12.0 U5.1
Source : "Nessy" @ 192.168.1.90
Destination : "Backup" @ 192.168.1.210
On 'Backup' appropriate datasets are made.
User/PW is same as source.
Root P/W is same as source.
No snapshots are involved.
My trouble is the destination 'TrueNAS URL' ..... I have tried :
Backup
192.168.1.210
https\\mnt\Backup
https\\192.168.1.210
Plus a whole lot others.
I get a 'does not resolve' error -- EMO8 I believe. The Example has ' https://10.231.3.76 '.
So a Newb wants to know "What gives"
As always TIA ..... Kevin
Well ... at least now all of a sudden it's accepting the URL .... but refusing the connection whether I use the root or my account. The instruction are rather lacking and ASSUMING many things. I even created a unique user hoping that the same user/password (from host) was not allowed ......
Follow up : Don't follow the instructions ..... I left the (s) off the https (as given in the example) and it worked fine ......
I want to make the initial Replication to my new backup server ...... long time and $$$ in the making. It's on my local network and don't need security.
TN 12.0 U5.1
Source : "Nessy" @ 192.168.1.90
Destination : "Backup" @ 192.168.1.210
On 'Backup' appropriate datasets are made.
User/PW is same as source.
Root P/W is same as source.
No snapshots are involved.
My trouble is the destination 'TrueNAS URL' ..... I have tried :
Backup
192.168.1.210
https\\mnt\Backup
https\\192.168.1.210
Plus a whole lot others.
I get a 'does not resolve' error -- EMO8 I believe. The Example has ' https://10.231.3.76 '.
So a Newb wants to know "What gives"
As always TIA ..... Kevin
Well ... at least now all of a sudden it's accepting the URL .... but refusing the connection whether I use the root or my account. The instruction are rather lacking and ASSUMING many things. I even created a unique user hoping that the same user/password (from host) was not allowed ......
Follow up : Don't follow the instructions ..... I left the (s) off the https (as given in the example) and it worked fine ......
Last edited:
