Frick
Fishfaced Nincompoop
- Joined
- Feb 27, 2006
- Messages
- 18,933 (2.85/day)
- Location
- Piteå
System Name | Black MC in Tokyo |
---|---|
Processor | Ryzen 5 5600 |
Motherboard | Asrock B450M-HDV |
Cooling | Be Quiet! Pure Rock 2 |
Memory | 2 x 16GB Kingston Fury 3400mhz |
Video Card(s) | XFX 6950XT Speedster MERC 319 |
Storage | Kingston A400 240GB | WD Black SN750 2TB |WD Blue 1TB x 2 | Toshiba P300 2TB | Seagate Expansion 8TB |
Display(s) | Samsung U32J590U 4K + BenQ GL2450HT 1080p |
Case | Fractal Design Define R4 |
Audio Device(s) | Line6 UX1 + some headphones, Nektar SE61 keyboard |
Power Supply | Corsair RM850x v3 |
Mouse | Logitech G602 |
Keyboard | Cherry MX Board 1.0 TKL Brown |
VR HMD | Acer Mixed Reality Headset |
Software | Windows 10 Pro |
Benchmark Scores | Rimworld 4K ready! |
Hey hey.
So a while back I was tasked with setting up a VM in VMware's Cloud Director. Which btw uses flash as an interface, which is so very stupid. But anyway, that VM was to be accessed via RDP. No worries, just create the vApp and the VM, set up some rules and off you go. Simple. Now though, we need another VM ... and I just can't get that damn NAT stuff to work, or something is up with my skills at server settings, which are abysmal. I tell you, wow, I have no idea what I'm doing. I will elaborate a bit in the end on the post on what we are doing with the VMs.
They run Windows Server 2016, without anything installed or set up except remote desktop. Firewall rules are the same on both machines, as are every security policy I have found, and they run the same services. Both have static IP adresses, both are Fenced, which probably means something.
So here is the NAT/firewall setup:
("external" in the FW rules is our assigned IP, and I will tighten up the rules when I get it working)
VM1 have one admin account (for the company I work for), and one user account for the user. Both of them work fine with RDP, using IPxxx:10001.
VM2 so far has one admin account, which does not work with RDP. Outbound traffic works on both machines. It was made from a template our cloud provider has, same as VM1.
I assume I have missed something in the OS setup, but I have no idea what it can be. What I have found out is that there is about a million different ways of doing almost the same things , so one question is if I'm even in the right place. Or it is something about the virtual network. There are several steps to untangle VMs from networks, but I think I have gotten the gist of it.
Any help is greatly appreciated, even if it's just a tiny pointer. I have all the time in the world and it's kinda fun actually, but it has to work too. People and their expectations on paid services.
So a while back I was tasked with setting up a VM in VMware's Cloud Director. Which btw uses flash as an interface, which is so very stupid. But anyway, that VM was to be accessed via RDP. No worries, just create the vApp and the VM, set up some rules and off you go. Simple. Now though, we need another VM ... and I just can't get that damn NAT stuff to work, or something is up with my skills at server settings, which are abysmal. I tell you, wow, I have no idea what I'm doing. I will elaborate a bit in the end on the post on what we are doing with the VMs.
They run Windows Server 2016, without anything installed or set up except remote desktop. Firewall rules are the same on both machines, as are every security policy I have found, and they run the same services. Both have static IP adresses, both are Fenced, which probably means something.
So here is the NAT/firewall setup:
("external" in the FW rules is our assigned IP, and I will tighten up the rules when I get it working)
VM1 have one admin account (for the company I work for), and one user account for the user. Both of them work fine with RDP, using IPxxx:10001.
VM2 so far has one admin account, which does not work with RDP. Outbound traffic works on both machines. It was made from a template our cloud provider has, same as VM1.
I assume I have missed something in the OS setup, but I have no idea what it can be. What I have found out is that there is about a million different ways of doing almost the same things , so one question is if I'm even in the right place. Or it is something about the virtual network. There are several steps to untangle VMs from networks, but I think I have gotten the gist of it.
Any help is greatly appreciated, even if it's just a tiny pointer. I have all the time in the world and it's kinda fun actually, but it has to work too. People and their expectations on paid services.
The purpose of the VMs: Electrical documentation. We have this ancient but simple CAD system in which we place everything related to electricity, usually in larger buildings: schematics, building blueprints, which tenant hires what areas and what exactly they are paying for, images of how it actually looks and so on. The CAD engine is truly ancient, but it works and even though there are speedier and better solutions avaliable they have a tendency to be complicated. This is so simple any technophobe can use it, and for that very reason I find it ... fiddly and non-intuitive. It is both of those things, but whatever. It works, and the market is infinite, especially now when Sweden recently passed a law stating the owners of buildings has to be able to procude documents on the electrical system. You know those large industrial buildings, or largeish office complexes from the 60's/70's? They have a tendency to be nightmarish for electricians to work in, and often they have to spend hours or even days on just finding out which circuit uses what breaker, and everything looks like Cthulu in badly salvaged power armor.