How can I run a local DNS Caching nameserver on Vista? - windows-vista

I'm used to running my own DJB dnscache on all unix-like systems I have, i.e. Linux and Mac OSX. Now that I got me a Vista, I wonder what can I run on it to the same effect?

Windows already has a service (DNS Client) that caches dns requests.

Built-in DNS servers are considered server functionality in the Windows world. On Vista, you'll need to get a third-party DNS server. After that, it's as simple as setting your DNS server entry to 127.0.0.1 in your TCP/IP settings.
A quick Google search found SimpleDNS, but I've never used it and can't attest to how well it works.

The defacto most popular BIND software runs on Windows, as do many other DNS servers.
There's also experimental versions of Unbound for Windows available from here. Unix versions of Unbound have been available since last year and are already in production use in many ISPs.
The author of Unbound is looking for beta testers for these experimental versions. If you try Unbound and find any problems please report them at http://www.nlnetlabs.nl/bugs/

Related

How does macOS assign hostnames

I'm using some application software which I have installed on an Azure VM. I have a MacBook laptop which I use to connect to the Azure VM, using Microsoft's Remote Desktop client for Mac software.
The software installed on the Windows Azure VM is proprietary (developed and licenced by a third party company), and only compatible with Windows (hence not running it locally on the MacBook). I've gone down the Azure route (as opposed to Bootcamp or Parallels for example) as I can take advantage of the cloud model - no worries on operating system licence costs, updates, maintenance and I can also turn it off when I don't need it (to save energy and cost).
The licence is for one user and one machine only, which is fine for my needs. So far as I understand it, the software's licencing algorithm takes the network hostname of the installed machine (i.e. Azure machine) and also the hostname of any remote connected client (i.e. my MacBook), concatenates both hostnames together, applies some sort of algorithm (presumably some sort of one-way hash), and records this as a HostID. The same algorithm is repeated on each sign-in and compared with the originally recorded HostID (thereby preventing someone else remotely connecting and using the software).
My problem is that my MacBook's hostname seems to be variable. Sometimes it is "mymacbook" and sometimes it is "mymacbook.local". If I connect to the Azure server, I think I can see my local hostname by going to task manager > users [tab] > client name [column - needed to add by right-clicking on the header and selecting column]. The variability of my client's hostname is causing the licencing to fail when it is not exactly the same as it was on the first installation.
I did a bit of research - if I understand correctly, the hostname is assigned to my MacBook by my local router as I am using DHCP? Also, Apple Bonjour, which is Apples mDNS implementation can cause .local to be appended onto the end of the hostname (e.g. when my MacBook is connected to or is in range of other devices)? Is this right or am I barking up the wrong tree!? Just trying to figure out whether I can control the hostname of my MacBook, before I write back to the software company to tell them that their licencing algorithm is incompatible.
Thanks in advance for any help, advice or pointers.
P.S. https://en.wikipedia.org/wiki/.local

is it possible to use AWS to run a regular windows 10 machine?

I want a Windows 10 x64 Professional hosted on AWS, is that possible? And if so, how might one go about it?
To expound.
I just want a real windows 10 environment hosted remotely with static IP address so i can use it like a personal computer + server for some dev stuffs.
This is likely what you are looking for:
https://aws.amazon.com/workspaces/
Amazon WorkSpaces is a managed, secure cloud desktop service. You can
use Amazon WorkSpaces to provision either Windows or Linux desktops in
just a few minutes and quickly scale to provide thousands of desktops
to workers across the globe. You can pay either monthly or hourly,
just for the WorkSpaces you launch, which helps you save money when
compared to traditional desktops and on-premises VDI solutions. Amazon
WorkSpaces helps you eliminate the complexity in managing hardware
inventory, OS versions and patches, and Virtual Desktop Infrastructure
(VDI), which helps simplify your desktop delivery strategy. With
Amazon WorkSpaces, your users get a fast, responsive desktop of their
choice that they can access anywhere, anytime, from any supported
device.
and this is how you can give it a static ip:
https://aws.amazon.com/premiumsupport/knowledge-center/associate-elastic-ip-workspace/
Edit:
Amazon WorkSpaces now offers bundles that come with a Windows 10
desktop experience, powered by Windows Server 2016. Amazon WorkSpaces
Windows 10 bundles provides you an easy way to move users to a modern
operating system, while also simplifying licensing. Amazon WorkSpaces
continues to offer bundles that come with a Windows 7 desktop
experience, provided by Windows Server 2008 R2. You can also run
Windows 7 and Windows 10 Enterprise operating systems with Amazon
WorkSpaces if your organization meets the licensing requirements set
by Microsoft.
#BrownChiLD
You can create your own AMI on AWS. Steps are below:
1. create the machine on your system by using vmware wokrstation or hyper-v
2. Export the VM
3. Upload it to S3 bucket
once your vm is uploaded to S3, follow the steps on the below link
https://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-image-import.html#import-vm-image
At present time the only way to achieve what you want is by spinning your own Win10 instance assigning the static internal IP while creating it or by adding an Elastic IP if it's in an Internet Gateway enabled subnet.
It's not that convenient, you'll need to set up the environment yourself, including Security Groups, ACLs, etc to allow a bit of security and connecting using RDP will be a bit of a pain (beside doing so over internet isn't exactly advisable). You might start thinking about Chrome Remote Desktop or even Teamviewer.. and will be very pricey running it. First things first, apparently there's no Win10 available as AMI, so you'll need to deploy it yourself. Once running you'll need to license it. A type suitable for this could cost around 80$ per month.. unreserved.
Using AWS Workspaces isn't really an option: besides it is not "Windows 10" but Windows server 2016 (I needed WSL, which has been introduced with Server 2019 so, no joy), the only way to have a proper Win10 is using BYOL but... (cit from FAQ) :
You need to commit to running 200 Amazon WorkSpaces in a region per month on hardware that is dedicated to you. If you want to bring your own Windows desktop licenses for graphics use cases, you need to commit to at least 4 monthly or 20 hourly GPU-enabled WorkSpaces.
:-/
Amazon WorkSpaces is a virtual desktop that runs on AWS but you connect through an Amazon client software that acts a lot like virtualbox, except the OS that you're using is not on your local machine. So it's more like a Thin Client environment over the internet. I believe the OS through Workspaces is managed by AWS as far as patching and updates through a software called A.C.M.E. (Amazon Client Management Engine).
https://youtu.be/jsqI7KU3S8I
Amazon EC2 instances also provide Windows instances that you would connect through an RDP connection. You'll have to manage the patching and updates yourself though.
Here's a link for your reading pleasure
https://aws.amazon.com/windows/resources/licensing/

Snmp Server for Windows

I'm looking for a snmp server for windows, are there any free (or at least working trial version) ones, I can only find clients?
I know I could install the windows snmp service but here at work it is not really an option (I don't have the "win xp" CD needed and support is as complicated as slow, even worse, it's Friday).
Thanks!
The Net-SNMP software contains both clients and servers. Specifically, the project contains both an SNMP agent server than runs on windows, as well as a trap receiver application as well.

Setting IGMP Version on Windows 7

I have a piece of software written "out there" (e.g. no source code available) that allows me to use it in multicast mode. I'm trying to use this software on a network that, for technical reasons, can only use IGMP Version 2.
My OS is Windows 7 (64-bit, though I doubt that makes a difference). So far my searches have only given me Windows XP & Windows Server solutions, all of which involve editing the registry. In addition to the usual reasons (aka "registry paranoia"), I hesitate to edit the registry in this case because this particular network is not the only one that I will be using; I have not problems at all in all the other networks I try using multicast on.
Is there a straightforward way to force this software onto IGMP V2?
Thanks!
John Price
As far as I remember, adding IGMPVersion=3 to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters is the only way to solve your problem.
Anyway, there is another creepy solution - just write a little daemon, that will sniff for IGMPv3, parse data from it and send IGMPv2 packets =)

What is the best way to connect remotely to a Mac?

I'm trying to remotely control a Macintosh computer. I know that in the Windows world, you can use Remote Desktop to connect from one Windows computer to another Windows computer. This works relatively well.
I know that you can use a VNC server but this isn't always the most secure or give the best performance. Are there other options available for remotely connecting to a Mac?
In some situations Copilot is a good solution. Not so much for day-to-day admin, but great for remote tech support.
If you need the solution to be cross-platform (ie, controlling an OS X box from Windows) then VNC is the obvious choice. I've had much better luck with the free Vine VNC Server than with Apple's built in one. As for viewers, Chicken of the VNC on OS X or Tight VNC on Windows are good solutions.
As others have said, for security firewall VNC and then use an SSH tunnel. There's lots of ways to do that, and the exact details depends on OS, firewall, network, etc. One method of creating an SSH tunnel for VNC is described here.
If you're trying to connect from one (Leopard) Mac to another, you can use the built-in Screen Sharing functionality; turn the server on from the Sharing System Preferences pane, and either use the network browser (on a LAN) or just open a vnc:// URL.
If you're trying to manage a bunch of Macs, try Apple's Remote Desktop (ARD) software; it's sold in 10- and unlimited-client versions, so if you've got fewer than 5 or so Macs it's probably not worth the money. The client bits for ARD are part of OS X. Screen Sharing and ARD use the same protocol, which includes some Apple-proprietary extensions to VNC which do encryption (either of all data, or of just keystroke/password info) and support adaptive JPEG compression, which gives you decent-enough performance (usable, but nothing like RDP or NX unfortunately).
If you need something cross-platform, check out TeamViewer (which will punch through firewalls and so forth).
Apple's Remote Desktop has AES encryption. Another good way is to just enable SSH in sharing and use shell access to perform tasks without interrupting the user.
http://www.apple.com/remotedesktop/
^That's your best solution.
If you go into the Settings panel, you can find a variety of other remote access options including SSH.
You can use VNC which is built into Tiger.
Yeah, VNC is good, but what about Apple's Remote Desktop?
If you are looking for a free, secure solution: I would recommend using any of a number of VNC servers that are available, blocking the ports that VNC uses to communicate, and then using SSH tunneling to connect. This way, ssh is encrypting everything, and you can still rely on free, open source (?), and cross platform standards for controlling the Desktop remotely.
Citrix, the people behind pc anywhere and the windows remote desktop have a hosted app called "Go to my pc" https://www.gotomypc.com/
I've heard people says it good.
I personally like RHUB's service for remote access and collaboration. It's an appliance that's easy to use and very secure. The device works from behind your firewall (instead of outside of it).
if you need low bandwidth or cross platform there's RDP server for mac that also offers there own iRapp protocol
from their site:
http://www.coderebel.com/2013/11/08/irapp-mac-client-available-download
Lowest supported speed: 512 kbit/s (64 KB/s) for iRAPP protocol
By adjusting the image quality you are able to make iRAPP work on
lower bandwidth connections as recommended above.
iRapp TS (Mac Terminal Server) allows multiple users to connect one
Mac simultaneously

Resources