I just realized that they are in different network segments.WinSCP. See here.
Assuming both VMs are on the 10.0.0.X NW & can communicate between THEMSELVES, it doesn't make a difference where you access the VM from.My main network (physical machine) is at 192.168.1.X, while the VM is at 10.0.0.X
Thanks for the reply. I understand what they are telling me, but what I want is to be able to copy or transfer something from my physical machine directly to the virtual one. There are not two virtual machines, only one Virtual Machine. Both are on different networks. Within my PROXMOX I work with a virtual LAN in the 10.0.0.X range. My physical machine, as I said before, is not in the same range.Assuming both VMs are on the 10.0.0.X NW & can communicate between THEMSELVES, it doesn't make a difference where you access the VM from.
So for instance from your physical machine you access remotely (PVE, noVNC, RDP etc.) Windows VM1, from there you start WinSCP to access Windows VM2.
So I (correctly) understood that to mean 2 VMs. However it appears that is not what you meant (maybe English isn't your first language?).between virtual machines
I'm working with PROXMOX and learning something about PFSense. The LAN of my PFSense is 10.0.0.X. I have a VM that is within the indicated range, I have it configured this way in my laboratory.Well you either have to setup a route from your machine to the VM (and vice versa) or do it through a NAT. It really depends on why you're using different subnets, if it's for security reasons then NAT is the way to go. Do you have a network diagram of your setup?
Yes, you could do it for example with THUNDER. I would add NFS type storage in PROXMOX and that's it. But how would I access the data on that storage from my Windows VM?Thank you.Well your original question says:
So I (correctly) understood that to mean 2 VMs. However it appears that is not what you meant (maybe English isn't your first language?).
Anyway getting back to your problem. Network segregation is exactly what it implies - a network is segregated so that one part is separate from the rest. I imagine the reason for your doing it would be security concerns. Now you are trying to punch holes through the segregation.
If I were you I'd setup a small NAS (can be another VM on Proxmox) & give that access to both NW segments (pretty easy in Proxmox). Then you can transfer files to/from the NAS. I think this is the easiest/safest route.
Oh, okay, I can add an additional network interface to the virtual machine and put it on the same network as my main network, that of the physical machine, and from there share via SMB. Perfect, thank you very much!!!!Of the top of my head; create a Proxmox LXC (CT) or VM with OMV with a disk size big enough for your needs (you are only going to use this space - so no other added drives) add 2 NW devices (one for each NW segment) - setup your SMB shares etc. in OMV, setup your SMB share in both instances of Windows (Physical & VM) & you are good to go. You can probably think of many other alternatives - but in any case whatever you decide I would not directly involve the Proxmox host itself for that NAS/NFS/SMB etc.