2.4? Man, that is ooooold. Anyway, what it complains is that it can't contact server over ports it wants to use (connection ports). Initial handshake of data went over service ports, but actual data (like backup or restore) goes over connection ports and it seems something is blocking it. Could be fw for example.
Did SQL module 2.4.0 supported DDBoost in the first place? Anyway, issue seems to be connection from client to server (or DD if DDboost is used, but top of my head I doubt SQL module ever supported DDBooost - you had to use NMM I believe - you are pretty much behind what is current and supported in those terms with that module version). You can try to restart services on client and try once again. If it happens again, try to run it from CLI in debug mode to see which part of connection establishing fails in more details.
The error is clearly related to firewall ports. You can disable windows firewall on the client and that should take care of the errors that you are facing. Also, the version you are using is end of support life, i advise you to upgrade to the supported version and then try the restore.
I just get that I'm not authorized to view the content on that link Diana. However, this *IS* a case of your backup server is unable to connect to anything within the configured port range on dbhost.
Run nsrports on both systems. The should generally both come back with something along the lines of:
Service ports: 7937-9936
Connection ports: 0-0
I suspect that one of these will be coming back with different numbers, and that they can't talk to each other due to that. Most likely someone's gone "aha, we can improve security by shutting down unnecessary ports!" without considering why so many are available in the first place.
aaste
5 Posts
0
April 11th, 2016 12:00
Hello, thanks for your reply. There is no firewall in the middle, the networker server and the dbhost are in the same lan
ble1
4 Operator
•
14.4K Posts
0
April 11th, 2016 12:00
2.4? Man, that is ooooold. Anyway, what it complains is that it can't contact server over ports it wants to use (connection ports). Initial handshake of data went over service ports, but actual data (like backup or restore) goes over connection ports and it seems something is blocking it. Could be fw for example.
ble1
4 Operator
•
14.4K Posts
0
April 11th, 2016 13:00
Did SQL module 2.4.0 supported DDBoost in the first place? Anyway, issue seems to be connection from client to server (or DD if DDboost is used, but top of my head I doubt SQL module ever supported DDBooost - you had to use NMM I believe - you are pretty much behind what is current and supported in those terms with that module version). You can try to restart services on client and try once again. If it happens again, try to run it from CLI in debug mode to see which part of connection establishing fails in more details.
gautamgp
226 Posts
0
April 11th, 2016 20:00
The error is clearly related to firewall ports. You can disable windows firewall on the client and that should take care of the errors that you are facing. Also, the version you are using is end of support life, i advise you to upgrade to the supported version and then try the restore.
aaste
5 Posts
0
April 12th, 2016 02:00
Thanks for your reply. Obviously I have windows firewall disabled in both Networker Server and Dbhost........and yes, the DNS is ok.
aaste
5 Posts
0
April 12th, 2016 05:00
Thank for your reply. I tried to browse that link (I created an account) but when I try to login I see this:
I don't know if this is temporary problem or not.
StuartWhitby
45 Posts
0
April 12th, 2016 08:00
I just get that I'm not authorized to view the content on that link Diana. However, this *IS* a case of your backup server is unable to connect to anything within the configured port range on dbhost.
Run nsrports on both systems. The should generally both come back with something along the lines of:
Service ports: 7937-9936
Connection ports: 0-0
I suspect that one of these will be coming back with different numbers, and that they can't talk to each other due to that. Most likely someone's gone "aha, we can improve security by shutting down unnecessary ports!" without considering why so many are available in the first place.
nsrports -S -
should fix it.
aaste
5 Posts
0
April 12th, 2016 11:00
Thanks for your reply - I get exactly this
Service ports: 7937-9936
Connection ports: 0-0
When I run nsrports on both servers.