(sketch-IMG) - How do you specify a second NIC on three PCs?

[tgucm]

Hi there!

I have been wondering this for over a year and a half and just now got my arse in gear to register and ask about it


I have three computers in addition to my main computer that I would like to access directly through a Second NIC installed into each PC. Two of the pc's have a onboard gigabit NIC and I added a 100mb NIC for them to access the internet...

My reasoning is simple... I often have large internet activity going on and upload/download massive logs to and from our office remotely for various purposes including off-site backup of office files.

At home I have three computers, two of which are dedicated to the log transfer tasks and the third I use for personal software pre-processing tasks...


Here's a sketch:




All I need to know is how to tell Each of the UVNC servers "and" clients to use the Second NIC ONLY (( or another Third or Fourth NIC in a system I will be building here soon ))


I hope I have been able to explain this ok...

p.s.
@UVNC Admins/Devs: feel free to use the sketch in your tutorials or documentation if you like

[redge]

simple answer:
ip is different on every network interface card (NIC)

green LAN with Internet
orange LAN inhouse only.

(theory example)
x is the computer number
192.168.0.x 1Gbit LAN
192.168.1.x 100Mbit LAN

practical example
192.168.0.2 computer2 on 1Gb LAN
192.168.1.2 computer 2 on 100Mbit LAN

[B]

Also, that kind of assumes you're going to assign static IP addresses to each NIC.

I'm assuming that your router (either as part of your green "switch" or somewhere in your purple Internet bubble), is handing out DHCP addressing, but unless you add a second router or other DHCP server, that will have to change. If you like, you can hard code ONLY the Gigabit segment addresses (NICs), leaving the others DHCP. Just make sure they're different network IP subnets as redge described.

By the way, I'm not entirely sure you're benefiting from the secondary NICs; unless your Internet bandwidth is really generous and heavily pounded, it would represent only a small fraction of the Gigabit NICs' overall capacity, especially if you're not simultaneously and steadily shuttling gigabytes of data about the LAN. Good luck.

Oh, one last thing -- for local remote control I still find RDP (e.g., Microsoft Remote Desktop) far more responsive and accurate than any versions of VNC.


Edit: Upon review, you don't really need two subnets in your case -- if you just memorize which IP addresses are statically assigned to which NICs, you can keep everything on the same subnet. But redge's method is a lot easier to keep track of.

[tgucm]

Thanks Guys!! That is exactly what I needed

[tgucm]

Actually I forgot to ask one thing

How do I tell UVNC to use that particular ip address/subnet?

I have created a .vnc file but not sure how to edit it to use the other ip address?

[B]

Should just be able to add it to the VNCVIEWER command line, like:

vncviewer 192.168.1.3

or, if you've used a non-standard port such as "1234":

vncviewer 192.168.1.3::1234

You could put that command line in a desktop icon (or multiples in your case).

There's probably a way to embed it in the INI file too. I would check the documentation.

Oh wait a second -- are you asking how to tell the VNC SERVER to bind to <b>only</b> a particular network adapter and not the other ones? Sorry, I don't know.

I think the examples above all assume the VNC server is still listening on all adapters, but that it's you as the VIEWER who is choosing to only communicate to the desired adapter.

[tgucm]

Oh wait a second -- are you asking how to tell the VNC SERVER to bind to only a particular network adapter and not the other ones? Sorry, I don't know.

I think the examples above all assume the VNC server is still listening on all adapters, but that it's you as the VIEWER who is choosing to only communicate to the desired adapter.

Yes Sir! You said "bind to only a particular network adapter and not the other ones" that is exactly it: This way if i have every server on the other pc's and the viewer on my main terminal all set to that particular ip group like 192.168.2.xxx then have the internet only use the 192.168.1.xxx then everything will be perfect

umm any idea how i do that? I tried going through the documentation a couple times on this one but no luck finding what i needed

[B]

Again, I don't know, BUT... what's wrong with what we suggested above?

If you, as the "viewer" specify the "192.168.2.xxx" address as you connect to each PC, then ALL your VNC communications to that target PC will take place ONLY through the corresponding NIC. Isn't that what you want? The fact that the server software is also listening on the other NIC's address shouldn't mean anything (especially if you're not forwarding any ports in from your router).

You do understand that NIC A in a given PC should be given a different, separate IP address from NIC B in that same PC, right? Why doesn't that solve your problem?

[tgucm]

yep it's working great, sorry I read the bottom of your post first then replied right away not thinking ( it's almost 3am here ) but then I saw the rest about the commandline

Thanks a ton, B!!!! You really do rock!

[B]

Okay, great; you're welcome. Glad it's working for you.