How do I connect my servio to 2 networks?

I am running my serviio (the licenced version) on a microserver under windows 7 withe 2 network cards. They each feed seperate networks. Serviio binds itself to one card or the other if I give the cards seperate ip addresses, so it only appears in one network. If I set the ip address of both cards to one ip address, windows automatically asigns another ip address to one card, even if I disable the DHCP client. Can I manually configure the Serviio to use two ip addresses, maybe?

[atc98092]

Unfortunately, no. Serviio can only bind to a single address. To make it accessible across multiple subnets requires some fancy routing.

[DenyAll]

Not possible to bind Serviio to two addresses but you may be able to run two instances of Serviio on the same machine using virtualisation. Alternatively install the other instance of Serviio on another PC on the second network.

Unfortunately, no. Serviio can only bind to a single address. To make it accessible across multiple subnets requires some fancy routing.

Ok, thanks for your reply, I have some basic knowledge of routing. I know about routing tables. I know 'they' have to work both ways Can you suggest a good forum for networking, please

Not possible to bind Serviio to two addresses but you may be able to run two instances of Serviio on the same machine using virtualisation. Alternatively install the other instance of Serviio on another PC on the second network.

Thanks for your reply. Interesting. I have got vmworkstation, however my microserver is already stretched running one real instance of Serviio! As regards running two instances, I have about 7 terrabytes of files, so I think this is impractical, and costly

[DenyAll]

I have about 7 terrabytes of files, so I think this is impractical, and costly

you don't need to put these files on the second PC, just run a second instance of Serviio and reference the files across the network as an SMB share, but anyway....

To use your router to overcome this the router must forward broadcast (discovery) packets from one network to the other. Forwarding broadcast packets is advanced networking (Google for your router type), and generally can't be done with consumer grade routers. Your router must also have a direct link to both networks - I suspect that might not be the case here.

Why the two networks? Using a PC to bridge networks is not good practice generally.

I have about 7 terrabytes of files, so I think this is impractical, and costly

you don't need to put these files on the second PC, just run a second instance of Serviio and reference the files across the network as an SMB share, but anyway....

Thanks but I don't want to start that sort of file sharing on my network but also surely I would be connecting to that network remotely and it's bound to slow things down and cause congestion and require a path to the other network, which I don't want, for technical reasons

To use your router to overcome this the router must forward broadcast (discovery) packets from one network to the other. Forwarding broadcast packets is advanced networking (Google for your router type), and generally can't be done with consumer grade routers. Your router must also have a direct link to both networks - I suspect that might not be the case here.

No, it doesn't. It can't ! Because I have two routers on the two networks! connected to two ADSL lines!

Why the two networks? Using a PC to bridge networks is not good practice generally.

I've tried bridging the two networks on the machine running Serviio. That doesn't work properly. I think NAT gets confused! Both networks are in the same range. The reason for this is so that my networked printers can be attached to directly (by ip address, not by SMB!
I have got a specialist router a Soekris net6501-50 which will bind the three (!) ADSL lines together (with a suitable operating system) I thought I might be able to do it more simply but I think I'm going tp have a bite the bullet and use it. I know this will not increase any individual connection speeds.

[atc98092]

I think DenyAll's suggestion of a virtual PC on the same computer running a second copy of Serviio is you easiest solution. Since all the media files reside on the same physical computer, there's no sharing between the networks by the computers themselves, unless you configure it that way. The 2nd copy of Serviio simply looks at the same location for media files as the original copy. You then bind the virtual PC to your 2nd NIC, and that copy of Serviio is available on the 2nd network. there's no interaction at all between the two networks, and nothing to mess with as far as routing table, broadcast messages, etc. The only caveat of course is a) the computer needs to have powerful enough hardware to support the virtual PC and b) you need a 2nd copy of your OS for the virtual PC.

There's numerous freeware solutions to allow installing a virtual PC. I've used VirtualBox with good results in the past. Microsoft has a Virtual PC available as well that may work just fine, but I've never used it for any length of time.

I think DenyAll's suggestion of a virtual PC on the same computer running a second copy of Serviio is you easiest solution. Since all the media files reside on the same physical computer, there's no sharing between the networks by the computers themselves, unless you configure it that way. The 2nd copy of Serviio simply looks at the same location for media files as the original copy. You then bind the virtual PC to your 2nd NIC, and that copy of Serviio is available on the 2nd network. there's no interaction at all between the two networks, and nothing to mess with as far as routing table, broadcast messages, etc. The only caveat of course is a) the computer needs to have powerful enough hardware to support the virtual PC and b) you need a 2nd copy of your OS for the virtual PC.

There's numerous freeware solutions to allow installing a virtual PC. I've used VirtualBox with good results in the past. Microsoft has a Virtual PC available as well that may work just fine, but I've never used it for any length of time.

Thanks, but can I run two instances of my licence? Don't I have to change it's name as well? (I didn't think this was possible)

[atc98092]

It's simple to change the Serviio advertised name, but unnecessary. It's named in one of the first lines of the Profiles.xml file.

I use the same license for my two Serviio installations. For me, I only use one for testing purposes (new versions, changes to the profiles). Since you're feeding the same library from the same computer on two different networks, I'll have to let Zip say if that isn't covered under the existing license.

I've been using the two Serviio instances for many years now. This solves the issue of DLNA protocol operation in two different networks.

But there are also some inconveniences:
1. Any configuration changes must be made twice.
2. You can't use the "recently viewed" folder because each Serviio has its own folder.

The ideal solution would be Serviio's support (binding) of several IP addresses, I've been waiting for this for 10 years...