Recommended Posts

I own a small business and run Windows Server 2008 R2 and about 7-8 workstations. The problem I've run into recently is odd network behavior on my workstation. For instance, every morning I come in and there's an X through all my shared network drives (not mapped but set in my user profile on the server) when they worked perfectly the previous day. I have to reboot the computer in order to get them back. I also started having an issue where websites would not load until I hit reload in the browser a bunch of times. I solved this one by changing the DNS server addresses on my workstation. I also have developed a problem printing to network printers until a reboot.

Just for information, my server address is 192.168.10.2 and the default gateway is 192.168.10.1. All my workstations have static IP's, for instance my personal workstation is 192.168.10.40

What could possibly have changed to make my network so messed up? I've noticed this behavior on 2 other workstations. Do I need to change some setting on the server in Administrative Tools? I barely ever touch the server so I don't know what could have gone wrong.

Link to comment
https://www.neowin.net/forum/topic/1119406-server-domain-problems/
Share on other sites

Hmm sounds odd, so it has been working in the past without the issues and all of a sudden they've started to happen?

The first thing i'd check tbh is the time on the DC, then look at each machine and ensure the same time is there, as it sounds abit like a credential failure, which can occur if times are out, usually anymore than 5 mins is considered a big chance difference in Active Directory.

Report back your findings, I wouldn't want to say do this and do that if it has worked in the past without any modifications occuring, would make sense for this to happen if you/someone has been playing around.

Yeah all of a sudden. The only change I did do was upgrade AVG Business Edition to the latest version. I just checked the time on the DC and it's exactly the same as my workstation. Your line of think does seem to make sense since this literally happens over night. Is there something I should do to make sure my time is properly synchronized with the DC at all times?

"I solved this one by changing the DNS server addresses on my workstation."

What did you change it too? the ONLY dns that a member of a domain should point to is the AD dns, normally in small setup this is the one DC they have. If you are pointing to your isp, googledns, opendns, etc. on the workstation even if added as secondary then yeah your going to have nothing but grief with your AD.

googledns does not know anything about your AD. Clients need to talk to AD dns, AD dns then forwards to googledns, isp dns, etc. or looks up from roots directly. If you were having issues with looking up websites, this tells me you have something wrong setup in your AD dns.

"I solved this one by changing the DNS server addresses on my workstation."

What did you change it too? the ONLY dns that a member of a domain should point to is the AD dns, normally in small setup this is the one DC they have. If you are pointing to your isp, googledns, opendns, etc. on the workstation even if added as secondary then yeah your going to have nothing but grief with your AD.

googledns does not know anything about your AD. Clients need to talk to AD dns, AD dns then forwards to googledns, isp dns, etc. or looks up from roots directly. If you were having issues with looking up websites, this tells me you have something wrong setup in your AD dns.

The website loading errors got to be so annoying that I changed them to 4.2.2.1 and 4.2.2.2

I know what you're saying and for years I pointed it to the AD DC by using 192.168.10.1. I could change it back but would that have anything to do with these other issues?

Sorry you NEED to point to your AD for dns - maybe there is something wrong with it resolves outside domains slow. FIX IT!!

How do you resolve your AD records if your not usnig its DNS? 4.2.2.2 does not know about it for damn sure.

If your AD is having issues with resolve outside domains - then you Need to FIX that. And yes not pointing to your AD dns could cause all kinds of issues like not being able to auth to stuff, stuff being disconnected, not being able to log in or taking a LONG time to, etc. etc.

Having issue finding the MS article that lists it as one of the top mistakes, but here

http://mcpmag.com/ar...ur-network.aspx

10 DNS Errors That Will Kill Your Network

1. TCP/IP Configuration Points to Public DNS Servers

This is by far the most common DNS error. Each network interface has a set of TCP/IP settings that lists the DNS servers used by that interface.

If the TCP/IP settings for a member computer specify the IP address of a public DNS server?perhaps at an ISP or DNS vendor or the company?s public-facing name server?the TCP/IP resolver won?t find Service Locator (SRV) records that advertise domain controller services, LDAP, Kerberos and Global Catalog. Without these records, a member computer can?t authenticate and get the information it needs to operate in the domain. It then acts like a teenager who can?t get the car keys, growing sullen and exhibiting a variety of bad behaviors.

I pointed my workstation DNS servers to the DC and website loading problems started immediately. When I went back to the ones listed above, everything went back to normal.

I just don't know how there can be any "DNS errors" when my Domain has worked fine for 10 years.

you need to learn active directory and dns....

cliffs:

dns....setup forwarders in your ad dns to your dns servers that are not having issues. uncheck use root hints if no forwarders are available.

clients use the ad dns server for all lookups. also the ad server points to its ip in tcpip properties, not the loop back.

post-118098-0-15402700-1352921254.jpg

"I just don't know how there can be any "DNS errors" when my Domain has worked fine for 10 years."

Well where are you forwarding your non authoritative zone lookups too on your AD dns? As sc302 points out on your AD dns you can have it either use root hints or your isp dns or some other dns server.

FACT!!! - All members of AD NEED!!! and Require to ONLY use your AD for dns, if they point or have multiple entries to other outside dns, then your going to have issues with your AD, plain simple FACT!! The only dns that knows anything about your AD is your AD dns, googledns sure and the hell does not have your srv records, nor does 4.2.2.2, etc. So if you ask them for stuff about your AD, your going to get back nxdomain. This is going to cause you NOTHING but pain!!!

Point your clients to your AD dns, and then work out why your AD dns can not resolve google.com, neowin.net, etc.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
    • So how did you solve the problem? Disabling Secure Boot isn’t a solution.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!