I setup a Windows Server 2008 for VPN access using Remote Routing Access Service. When a user would connect to the VPN the DNS servers would be reversed. For example, I had two local DNS servers and an external (OpenDNS) DNS server.
However, the adapter would always assign the external DNS server first and then the internal DNS servers as secondary.
The VPN client couldn’t locate local resources on the network over the VPN.
In my troubleshooting this issue, I found that this is actually a bug. Here is what I did to fix the issue.
Step One: On your RRAS server open the Registry to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RemoteAccess\Parameters\IP
Step Two: Make a Dword32 Key and Name it SuppressDNSNameServers. Give the value of the key 1.
Step Three: Restart the RRAS service on the server.
You should be set! If the above doesn’t work, try rebooting your server and trying your VPN client again.
Thanks for reading! Please consider subscribing to my blog. This was posted by techspeeder.
A customer “complained” to me the other day that keyboard input on their computer was slow and delayed. I tested Microsoft Word and some other programs and everything worked normally. I troubleshot their computer some more and found that keyboard input was only slow and delayed in Google Chrome. Once I discovered keyboard input was slow in Google Chrome, I doubled down on the issue. Before I get into what all I did to troubleshoot the issues, this computer was running Windows 10 and Google Chrome Version 50.
I tried these troubleshooting steps and none of the below worked.
Started Chrome in Incognito Mode and typing was just as delayed
Created a new Chrome profile – same issue
Reinstalled Google Chrome – no go
Tried Mozilla Firefox and Internet Explorer – they were both fine
Checked Chrome browser extensions but only had LastPass & AdBlock Plus Installed
Disabled various flags under Chrome://flags – didn’t help
Checked to make sure the browser wasn’t starting in compatibility mode – it wasn’t
Tried starting the browser in compatibility mode – that didn’t work either
Disabled Hardware Acceleration in Chrome – No Change
Disabled Chrome from running in the background after the browser is closed
Removed Internet filtering software on computer- same trouble
I searched high and low on the Internet for an answer to this issue. However, I could find nothing that worked.
After all the above troubleshooting, I was convinced it was a process in Windows that was creating issues. I started by killing one process at a time and then typing in Google Chrome. After killing the iDrive process, for iDrive online backup, I tried typing in Google Chrome – everything was fine. I started iDrive backup again and once again my typing in Chrome was delayed.
I updated the iDrive application to the latest version and it seemed to have fixed the issue. If this issue returns again, I may need to uninstall iDrive and install a different online backup program.
I really can’t explain why this fixed the issue. I know the fix above may not solve your slowness issues in Chrome. If there is one person out there that this article can help, it will be worth this blog post. I will post some links below to some other articles that have Google Chrome troubleshooting tips that may help you.
I ran into a very frustrating issue today. My job was to join a brand new Windows 10 computer to a domain. The server was running Windows Server Essentials 2012 R2. I felt this would be a simple job- but it didn’t turn out that way.
Typically, I join the computer to the domain using the Windows Server Essentials connector tool. Here are the steps I use below.
Step One: I went //servername/connect and installed the connector software. I rebooted the computer when I was prompted to do so.
Step Two: The computer rebooted and started booting into a _clientsetup_$ profile. The computer took a minute or two but it logged into the _clientsetup_$ profile. I was then prompted to enter the user’s credential’s to connect the computer to the domain.
Step Three: I entered the credentials, and then I selected “Setup this PC for myself”. Instantly, the connector software froze and said: “Windows Server Essentials Connector” has stopped responding, end program. The Connector software closed but the computer kept me logged into the _clientsetup_$ profile until I rebooted the computer.
I then logged into the computer. The computer was joined to the domain but the Connector software was not installed.
I thought this may have been a one-off issue so I tried joining the computer again. Once again, I was greeted with “Windows Server Essentials Connector” has stopped responding. I will list below all the things I tried -none of them worked.
I tried to join the computer to the domain with the admin credentials instead of the user’s credentials.
During the Connector software setup, I selected “Setup this PC for myself and others” instead of “Setup this PC for myself.
I checked Event Viewer. It said clientdeploy.exe has stopped working. Right before that error, I got a .Net framework error as well. I ran the Microsoft .Net Repair Tool. The .Net repair tool didn’t fix my problem, so I turned off .Net framework in “Turn Windows Features On or Off” in Windows. That didn’t work as well.
Installed the Windows Server Essentials R2 Connector from Microsoft’s website.
Right-clicked on the connector file and “Ran as an Administrator”
Connected the laptop via an Ethernet connection (instead of wireless) and ran the wizard.
I joined the domain manually and then tried to run the Connector software. It still failed.
I created a new local admin profile and ran the Connector wizard from that profile.
I rebooted the server.
Disabled IPv6 on the laptop- we thought maybe there was a conflict
Renamed the laptop multiple times
I checked the server. The computer showed up under the devices tab in the dashboard as being on the domain. However, the computer showed offline and the server didn’t know what OS was installed or anything about the client.