Archive for the ‘Remote’ Category

VPN’s & DNS riddles

December 9, 2015

So you setup a VPN and it works. Well it kinda works. You connect and can ping but you can’t use DNS right? You can’t ping “remoteserver” but you can ping 192.168.1.10.

Simple… just add the VPN’s DNS sever right? Sure that should work… but it doesn’t does it?

Grrr annoyed you add an entry to the hosts file! WTH? Who uses that anymore anyway? But it STILL doesn’t work!

Ahh forget it. They can just remap their drives using an IP address.

-OR-

Here’s how to fix it! Yay. I finally got tired of this issue and spent some time getting it to work. So before I ramble on any longer here’s the fix;

  • Open properties on your VPN connection.
  • Go to the Networking Tab
  • Bring up TCPIP (v4 – for now)
  • Advanced
  • DNS
  • If you haven’t already, then add your VPN’s LAN DNS server in the first field under “DNS server addresses”
  • In the second field you want to append these DNS suffixes
  • Add in here the FQDN or something like mylocaldomain.local (or what ever your local AD domain is)

Worked for me.

I can never remember the RDC port number

February 10, 2014

So here it is… 3389.

Turn on RDC remotely (Pretty good tip from Spiceworks)

August 6, 2013

I read this pretty good tip from Spiceworks and figured it would be good to include on the blog…

Full URL is here : http://community.spiceworks.com/how_to/show/33687-remotely-enabling-rdp?utm_source=swemail&utm_medium=newsletterresource&utm_campaign=0806

Have you ever tried to remotely access someone else’s computer in your office, just to be shot down by a “can not connect” line? This is a quick tutorial on how to evade that little bugger, and enable remote access, remotely.

1.
The problem
Noticing you have the problem, would obviously have to be the first step. If you don’t have this problem, no need to fix it.

93e254d7874f74f47f8ade15970f94d28c4b47c5ea5b310e7bd418f8b6894024_untitled_big
2.
Open up Regedit
First real step is open up registry editor (start, run, regedit), and locate “Connect Network Registry…”

951982d3cd1da8eabbc8f101c18373e33a5a2bc98f91acf776c5e54051243b6b_untitled2_big
3.
This is what will happen
Once that is opened, locate your offending PC, this is what it should look like when all is said and done.

2e5f0c7ab253098b03e64c9e44fabad85f4c48217de35820073d088ab7182046_untitled3_big
4.
1 more search
Find HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server
And locate the Key fDenyTSConnections

Cfc1ce0719634e754146bf27f9667111058a32d03e368ffdfd30b0ce7b686bbe_untitled4_big
5.
Change the value
Change the value from 1 to 0, now you can connect

Aad2a1479326d03293767c3cba7ff2e11f016438a3863ce9dcb54a384a21521b_untitled5_big
Conclusion
I’ve encountered this issue many times, and when an issue happens in a remote office, this saves you a boat load of driving time. Hope it helps at least one spicehead out there.

Logmein – “Your input is being blocked”

April 2, 2012

So this message freaked me out when I tried to connect to a server today. My initial thought was “Hackers!” but no, nothing so exciting. Turns out that it was someone leaning the keyboard of the server against a wall so it was pressing one of the keys…

The fix for remote access was to disable the host keyboard and mouse from within Logmein.
Just go to;
Options
Check the “Lock keyboard” option

This worked for me and I was able to resume duties 🙂

Quick awesome remote access tool

December 3, 2010

http://www.teamviewer.com http://join.me (Team viewer blocks you from using it after a while but Join.me is free forever!!!)
Awesome tool. It’s free to try or for non-commerical and allows you to remote into other machines. Doesn’t matter if you are coming from or connecting to a Mac, Windows or Linux box (or iPhone for that matter).
Had to put it down here.