You cannot bind SourceOne to particular network adapter.
I have seen many customers with multiple network adapters and also with bindings especially because of backup needing its own adapter/network.
In these sites you will see network adapters named e.g. Production and backup. Both will have different network subnets configured.
What needs to be taken care of is that Production should be first adapter in network “Adapters and Bindings” page of advanced settings. This way most of SourceOne related queries will end up on that adapter and other adapter you can leverage for backup or whatever other purpose you may have.
If there is anything else, that I would not know about.
However sometimes we had to break the binding of multiple adapters if we find issue that could be network related to rule out if firmware or anything related to binding is causing the issue.
RKatwal
2 Intern
•
600 Posts
1185
0
Posted April 23rd, 2015 17:00
Hi Krisztián,
You cannot bind SourceOne to particular network adapter.
I have seen many customers with multiple network adapters and also with bindings especially because of backup needing its own adapter/network.
In these sites you will see network adapters named e.g. Production and backup. Both will have different network subnets configured.
What needs to be taken care of is that Production should be first adapter in network “Adapters and Bindings” page of advanced settings. This way most of SourceOne related queries will end up on that adapter and other adapter you can leverage for backup or whatever other purpose you may have.
If there is anything else, that I would not know about.
However sometimes we had to break the binding of multiple adapters if we find issue that could be network related to rule out if firmware or anything related to binding is causing the issue.
Best regards,
Rajan