IE Proxy Setting Keeps Changing

Follow me I worked on an issue recently where the IE Proxy Setting would keep on enabling by itself no matter how many times you disable them. I googled on the issue and found numerous articles and posts suggesting different solution, and none of them worked. I ended up running multiple scans to check for any Malware, Adware, Virus, and Spyware etc., and all would may show that there is problem, and is fixed. However, every time I disable the IE Proxy Setting, it would enable again all by itself. Solution: After spending hours, here is how I resolved it, and I’m sure that you’ll be able to do it by yourself. Please note that this article applies to all version of Microsoft OS like Windows 7, Windows 8, Windows 8.1, Server 2003, Server 2008, Server 2012, etc. Download Process Monitor from Microsoft. (If your PC is not connecting to internet, do it from another PC, and transfer file) Extract the files and launch the application. First step is to Stop the Capture, by either CTRL + E  or clicking on the icon . Disable all the filters except Registry Activity. This is all we need in this particular scenario. Also clear the logs by pressing CTRL + X or the icon . Go to Start — Run (or press Window Key + R) — Type inetcpl.cpl — Go to Connections Tab– than to LAN Settings. Bring the Process Monitor and LAN Settings window side by side. Start the Capture on Process Monitor by clicking on the icon  or press CTRL + E. On the LAN Settings window, uncheck the box for “Use...

W2K8R2:DNS not responding

Follow me Recently we faced an issue on a Windows 2008 R2 domain controller where it stopped responding to DNS queries over a period of time as a immediate resolution we can reboot the server, it works OK for a few days and then it fails again. We investigated NETSTAT output on the server, we found that DNS.exe is occupying a lot of ports on the server. Open command prompt with elevated privileges on the server and execute following command to check the DNS.exe port consumption on the server Netstat -ano >Output.txt PS: Netstat output will show you PID not the process name, you will have to match the PID in task manager to find process name.   This is a well-known side effect of the hotfix distributed to address MS08-037, since the hotfix is intended to decrease the predictability of ports used for DNS responses. You can restrict the amount of ports used by defining a lower Socket Pool Size, as described in this article: Using dnscmd.exe Open an elevated Command Prompt (Run as Administrator…) Issue dnscmd /Config /SocketPoolSize where is a number between 0 and 10000 Using regedit.exe Open regedit.exe and expand the HKLM hive Navigate to SYSTEM\CurrentControlSet\services\DNS\Parameters If not already present, create a new DWORD value named SocketPoolSize Set a decimal value between 0 and 10000 Restart the DNS Server service: net stop dns && net start dns On a long run, we found issue still re-occured, we were not able to true resolution to the issue, however as a workaround we scheduled the DNS server service on the Server to restart everyday. I will update...

DNS Service fails to start on Reboot with Event 7023

Follow me This issue was observed on a clients location when he restarted the server and the DNS Stopped working. Actually the DNS Service did not start. After further troubleshooting, we found that the DNS Service fails to start on Reboot with Event 7023 Environment: Windows Server 2008 R2, with NIC Teaming on HP NICs. Analysis: During the course of troubleshooting various steps were performed to narrow down what’s causing the issue. We finally found that when the NIC Teaming is enabled, everything works fine. The DNS Service starts normally with no problem. The moment, we break the Teaming and disable the NIC, the DNS Service will not start on Reboot. However, we can restart the service manually. Log Name: System Source: Service Control Manager Event ID: 7023 Task Category: None Level: Error Description: The DNS Server service terminated with the following error: The network is not present or not started. This did not make any sense, so we kept on researching and at one point, we completely removed the Teaming Software, disabled Teaming, and restarted the server. Found all working fine. Well, that was a start, what did we do different this time, only removed the Teaming Software. So we installed it again, and as thought, it Service failed again. Since, the client had no interest in using the Teaming, we removed the software again, and all went well. Conclusion: The NIC Teaming software was causing some kind of issue. If you are not using the Teaming feature on NIC, you may also consider removing the Software...

Windows 2012: Rdp black screen on Windows Server

Follow me A client reported an issue that when some one RDP into their Windows 2012 server (which is also a domain controller) s/he get a black screen, The same black screen exist even if some one logs into console session, however apart from this all the services on the server functions just fine.  The only thing they can do to resolve the issue is to reboot the server. We researched on the issue and found that a lot of people are facing same or similar issues on server 2008 R2 and Windows 2012, We did implement some possible solutions on the server but as of now I am not Cent Percent sure if the issue is resolved as it happens rarely. Solution 1: We have observed that when a user gets black screen s/he, usually it has a disconnected session which is not getting reinitialize, so as a solution we implemented an idle session timeout limit on the server, so that after a specific time (18 hrs in our case), any disconnected session will be logged off immediately. The settings can be implemented in session state if the server is configured as a Terminal server or session host server.  it can also be configured by manually editing registry, we although configured it using local Group policy on the server. Solution 2: Some people have claimed to resolve this issue by configuring following group policy setting to enable both TCP and UDP protocols, if you do so, ensure that you make required changes in your network router or Firewall. Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections Solution 3:...

DNS Service Crashing due to issue with Name Server

Follow me DNS Service Crashing: This can happen due to a number of reasons, however this solution may get ignorance factor on the first step. Lets take a look at the error message first. Environment: Windows Server 2008 R2 Log Name:      Application Source:        Application Error Date:          22.12.2014 10:32:58 Event ID:      1000 Task Category: (100) Level:         Error Keywords:      Classic User:          N/A Computer:      <Removed> Description: Faulting application name: dns.exe, version: 6.1.7600.16385, time stamp: 0x5bbac638 Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x5bbad923 Exception code: 0x80000003 Fault offset: 0x0000000000043578 Faulting process id: 0xe3c Faulting application start time: 0x024c2c6df29ea187 Faulting application path: C:\Windows\system32\dns.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll After troubleshooting the issue, we noticed that the Name Server (NS) records were missing from the server. That did not resolve the issue, we also found that the Client has disabled the Root Hints in DNS. Hence, in any circumstances the query did not make it to the Outside world and failed. So, in simple words, the solution was to FIX Name Servers, and Enable Root Hints. Follow...

W2K8R2: w32tm /query /source returns Local CMOS Clock

Recently I was working on a windows 2008 Domain controller, where everything was looking fine even the DCdiag was clean. There were some intermittent DNS not working issues reported for which I was digging around. Thats when I saw that the clock was off by 3 mins or so, though that shouldn’t cause any issue as permissible limit with Kerberos is 5 mins but still I decided to fix that. We executed the following command to force sync the time but got the following error w32tm /resync /rediscover The computer did not resync because no time data was available We also found the following events logged on the server We check the registry for external time source under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\ NTPServer and found it pointing toward time.windows.com. Through when we tried querying the time source using cmdline switch w32tm /query /source we got the source as Local CMOS Clock w32tm /query /peers returns #Peers: 1 Peer: State: Pending Time Remaining: 549.2477392s Mode: 0 (reserved) Stratum: 0 (unspecified) PeerPoll Interval: 0 (unspecified) HostPoll Interval: 0 (unspecified) We executed the following steps to reconfigure windows time service on the Windows 2008 R2 Domain controller and that fixed our time issue. w32tm /unregister  :This steps unregister’s windows time service from the server, it even deletes the registry entries for windows time service w32tm /register :  This reregisters the windows time service on the server Following is  a critical step as it reconfigure all the windows time settings on the server, you may change the time sources (Peerlist) per your preference but it most cases this should work fine w32tm.exe /config /manualpeerlist:”0.us.pool.ntp.org 1.us.pool.ntp.org 2.us.pool.ntp.org 3.us.pool.ntp.org” /syncfromflags:manual /reliable:YES...