Where did you list?
<rant>I don't think I can wait two weeks for the beer to finish carbonating. If you think FedMess gives you a headache, try Microsoft. Me and my team have spent the last week troubleshooting a client's critical issue. He runs our software and gets no results (basically, product never flows to the end of the manufacturing line). We run it and get the correct results. 3 man-weeks later, no closer to figuring out what HE did to mess up the data. Had to be operator error.
I recalled that the client uses a browser to log into the VM as their corporate firewall doesn't allow a direct connection. So, I log in that way and get no results. WTFender? Microsoft did something so that software operates differently depending on how you log in to the VM...not how you log into the software, just how you get to the desktop. Let's see what BS they say about this one.</rant>
So what does the corporate VPN do, if they login to an onsite host, (on the same internal network as the VM) and connect to the VM from this host?
Seems an issue with the VPN first:
The permissions set for a browser based RDP can be more limited , and uses different ports.
Additionally it may have little to do with the VPN rather more of an issue with the perimeter firewall. If the VPN and firewall are one in the same (IE Meraki) that is where you’ll find the communication breakdown.
Sure beats working on 256 QUAM demodulators.....(today)...BIG yawn...
While I’m sure you folks that understand this stuff have made in the order of 100x the amount of money I have made over 40+ years of working, I somehow feel, while my work can be dirty, tiring, and sometimes frustrating, it is much more basic, and solving the problems I am presented with are very analog, eg; find the broken wire, replace the malfunctioning device, or my favorite, blame the user…. A much easier way to get by.
I know, if I had went down the path of computer systems, IT, etc., I would have been good at it, as I know my mind works that way, and there was computer lab in my school, which I did for 3-4 semesters, but in 1983-1984, they were TRS-80’s with 5 1/4” floppy’s and there was no “neat” factor. They just seemed like clunky little machines that were really complicated word processing calculators. I didn’t actually find an interest in computers until I saw Windows 3.11 (as I recall) with the GUI and what I felt was a system that was more user friendly, I started to really get into it, but I think that was around 1990, and I was stuck in my paycheck to paycheck grind, and the thought of career change and night school was out of the question.
I did, for a time, find myself building my own Windows machines during the windows 98 through windows XP era. Constantly making faster more updated machines, with SCSI drives and faster and faster video cards. But that was during a strange time in my life when I didn’t have a 9-5, and was in a super cheap apt in SF (rent controlled, in the range of $515 to not more that $1k for my small 1 bedroom, during the 11 years I lived there), so I had a lot of time to teach myself the hardware side of PC’s. By 2004 when I went back to work, I was over building PC’s….
