Remmina won't connect to Windows machines?

If you're like me, you still have to deal with Windows servers in your environment.  I typically RDP over to the ones in my environment with Remmina.  Every so often I run into an issue where a saved RDP connection will stop working and I have to blow it away and recreate it.  I finally had my fill and looked for a solution today.  Apparently the fix is to just change the security method from 'Negotiate' to 'TLS'.  Amazing what you can find when your annoyance level exceeds your laziness level.

Take a look at the original post where I found the fix over at Bauer-Power.net.

Dude, where's my A record?

I ran into something a bit odd today while setting up a couple of new CentOS 6.5 virtual machines.  The VM's were both set to receive IP addresses via Windows DHCP, which was working except for one small bit.  That particular DHCP scope is set to dynamically create both forward (A) and reverse (PTR) records when a lease is obtained.  Oddly, this was not happening.  Being a Linux admin, I immediately thought, "must be Windows!"

After digging into the Windows side of the house, I was left scratching my head.  All of the settings for both DHCP and DNS were as they should be.  I set up a packet capture and sent a few DHCP requests from the VM's which revealed the issue.  The default behavior for dhclient in CentOS now is to not pass the hostname in the request.  Adding one simple parameter in the /etc/sysconfig/network-scripts/ifcfg-eth0 file solved everything.  If you run into this issue, simply add the following to the file for the affected interface:

DHCP_HOSTNAME=`hostname -s`

 By including this line, you are telling dhclient to pass the hostname to the DHCP server in the request.