Domain? Workgroup? Active Directory? Ahh!, come help a noob


Recommended Posts

I have a network of 3 computers which were all communicating fine. In an attempt to speed one of them up, I reformatted it (Windows XP Professional) and all went well . But now I'm faced with reconnecting the computer with the small business network as it's vital to the productivity of the company. Now, with my limited networking experience I've always simply set them all to a similar workgroup and set a few sharing permissions and all was well. But using the other two computers as reference I see instead of being in a workgroup they're part of a "domain". I assumed as long as I entered the domain address ("five6.local") that is listed on the other two computers I would be popped into the network and all would be well. Instead, I get the following error message:

A domain controller for the domain five6.local could not be contacted

Googling the error gives me swarms of people in varying technical trouble with every one of them having a more sophisticated system and superior knowledge on the subject. Now, heres what I find odd about the whole thing: From what I can deduce, this is an error generated while trying to interact with Active Directory. And I believe Active directory will only run on a server operating system. But there is none in the group, It's just three Windows XP Professional machines. And it's the machine I reformatted wasn't the server because the other two computers are still communicating fine.

What am I missing here?

And how do I get this damn machine back in the network?!

All thoughts, comments, and inane moral-boosting cheers are much appreciated.

http://technet.micro...y/bb456990.aspx

only thing i can think of is either you're not logged in as an administrator, did not provide a login with domain join credentials or some kind of network issue is preventing this computer from contacting the domain controller.

(pro tip: I don't really have much experience with windows active directory/domain environments, i usually administer linux networks)

To find out what the hostname of the computer that is running your domain run the following in a command prompt on one of the computers that is currently in the domain:

echo %logonserver%

Now try pinging it from the same computer, if you can ping it, it does exist somewhere on your network. If you can't ping it try navigating to a share on it, \\HOSTNAME, if you can see shares on it then again it does exist and isn't allowing incoming echo request which is fine. If you can't ping it or navigate shares then it either isn't part of your network any more in which case we can't help you really or it is turned off or there is some other factor blocking access to it such as a firewall.

If you can ping or navigate to shares on it, try pinging the hostname from the computer you reformatted if that fails try pinging the IP address. If the hostname fails but the IP address works than there might be a host record on the other two computers for your domain. Open the file called hosts in notepad which is found in C:\WINDOWS\system32\drivers\etc

If there is a line in there along the same lines of

192.168.0.200 five6.local

Try adding the same on the new computer and see if that works.

I hope this makes sense, it is far two early!

It sounds to me like these 3 computers USED to be connected to a server, but are not any more.

You can connect a PC to a server, join it to Active Directory running on the server, and then disconnect from the server and the users that were logged in while the server was available will continue to function.

I would check with the person in charge that you are doing work for and see if they are aware of the existance of the server that was once connected to these computers or where the computers came from.

If there is no longer any server to connect to, you should be able to run it in a workgroup while the existing computers stay on the domain (it will still be accessible by \\COMPUTERNAME, but will not show under the same group in My Network Places). This is the easiest thing to do without messing with the other computers.

Ideally (and I would only do this if you were confident in this), it would be best to switch all of the computers no longer connected to a domain onto a workgroup instead. You will lose all the user profiles so you would need to recreate them and restore the data (pretty much the same as a format c: job without needing to reinstall the OS).

Given the age of XP and therefore the age of the computers I would be more inclined just to get it up and running without messing with the other computers until such time they are ready to upgrade to new PCs (running Windows 7 presumably) and then the problem won't matter anymore.

Rules of a domain network...

dns. no other dns servers are in the network properties other than the domain controller or a domain controller of the network. It will forward internet domain lookups to the appropriate server for you to be able to get to the internet. Internet dns servers do not know about internal domains and will give you the error you are seeing.

IMO, you aren't using dhcp correctly to hand out dns servers or you manually configured dns in your network properties to an internet dns server. This is the most common issue that would cause the situation you are seeing, this is not the only thing that would cause the issue you are seeing....most common with AD "noobs" because they don't understand how networking works or how things get referenced on a network. AD does not use netbios to figure out what/where the computers are, it uses DNS...internet DNS servers do not know anything about your internal network so it can't resolve or find pc1.five6.local or server.five6.local. DNS plays such a huge role in AD, it isn't something to get wrong or to go around.

Workgroups do not revolve around dns to connect to local pcs or local servers. They can use netbios/broadcast to connect and know where pc's are. AD does not, it uses DNS to query and lookups and it is embedded into AD.

The fact that two of the machines are on a domain means there must've been a domain controller (ie. Windows Server) on the network at some point in time, even if there isn't now.

From one of the two machines on the domain, do a: ping five6.local. If you get a reply, this will be the IP address of your domain controller. Do an ipconfig /all also. More often than not, in a live domain the DHCP service will also run on the same box as the domain. If you don't get a response to the ping, then you clearly don't have a domain controller any more and there's going to be no way to get that rebuilt third machine back onto the domain. In that circumstance, you have two options... either find that domain controller and plug it back in/turn it on, or remove those other two machines from the domain and put all three on the same (ie. identical, not similar as you mentioned above) workgroup.

p.s. I'm a service desk technician at JCB in the UK, and am responsible for the daily operation and upkeep of our Active Directory Domain with over 4000 domain members across the UK and Europe. I also run a small 1 server/1 desktop/2 laptop domain running on Server 2008R2 at my house.

To find out what the hostname of the computer that is running your domain run the following in a command prompt on one of the computers that is currently in the domain:

echo %logonserver%

Now try pinging it from the same computer, if you can ping it, it does exist somewhere on your network. If you can't ping it try navigating to a share on it, \\HOSTNAME, if you can see shares on it then again it does exist and isn't allowing incoming echo request which is fine. If you can't ping it or navigate shares then it either isn't part of your network any more in which case we can't help you really or it is turned off or there is some other factor blocking access to it such as a firewall.

If you can ping or navigate to shares on it, try pinging the hostname from the computer you reformatted if that fails try pinging the IP address. If the hostname fails but the IP address works than there might be a host record on the other two computers for your domain. Open the file called hosts in notepad which is found in C:\WINDOWS\system32\drivers\etc

If there is a line in there along the same lines of

192.168.0.200 five6.local

Try adding the same on the new computer and see if that works.

I hope this makes sense, it is far two early!

This is exactly the sort of "flow-chart" style response I was looking for. This along with the bits supplied by everyone else (especially TCLN Ryster, thank you sir) should be enough to get this guy running. I figure worst case scenario I'll just switch it over to a workgroup.

I appreciate all your help immensely, thank you everyone.

If there is no domain controller existing on the network than sure you can switch everyone over to a workgroup, but if there is a internal domain with sbs fix the issue with the pc. It is probably a very easy fix but if you don't understand or don't know how a domain works you should bring in someone who knows and not switch over to a workgroup as it can and will create other issues. there are many benefits to active directory that you give up by switching over to workgroup, and if you do not know or understand you should step away from that situation.

This is exactly the sort of "flow-chart" style response I was looking for. This along with the bits supplied by everyone else (especially TCLN Ryster, thank you sir) should be enough to get this guy running. I figure worst case scenario I'll just switch it over to a workgroup.

I appreciate all your help immensely, thank you everyone.

You're welcome, feel free to hit me up on a private message or something if you need further assistance. I have a large amount of experience with all windows server versions going back to 2000 and have administered AD, DNS and DHCP on all of them. I can help you out if you do find the domain controller and need help resurrecting it or something.

I want to go on record and say that his machines are located in a satellite office, and they are tunneling in and connecting to server located in a remote location.

What os is the machine in question running? Look at tue other machines that are joined

You're welcome, feel free to hit me up on a private message or something if you need further assistance. I have a large amount of experience with all windows server versions going back to 2000 and have administered AD, DNS and DHCP on all of them. I can help you out if you do find the domain controller and need help resurrecting it or something.

Thank you, it's nice to know I have a line of help for networking issues.

In case anyone is curious as to how it worked out: Pinging the server found naught. I switched all the computers over to a workgroup, and it's all working well. They are only doing basic printer/file sharing so I see no foreseeable issues with the setup. I'm still rather curious as to why they were on a domain (especially one without a server) in the first place but I feel that is going to die a mystery.

Thank you all again for your help, it was all much appreciated.

  • 2 weeks later...

Check the shell properties of each of the computer.

Plus you need to be login as an administrator. If you can't ping it or navigate shares then it either isn't part of your network any more in which case we can't help you really or it is turned off or there is some other factor blocking access to it such as a firewall.

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

    • No registered users viewing this page.
  • Posts

    • Go for a Echo Dot or Pop instead. These Echo shows just advertise to you.
    • NetSpeedTray 1.3.3 by Razvan Serea NetSpeedTray is a lightweight, open-source Windows network monitor that shows live upload and download speeds directly on the Taskbar. Designed for efficiency, it quietly sits in the system tray, conserving CPU and battery with dynamic updates. It blends seamlessly with Windows 10/11, adapts to light/dark themes, and auto-positions to avoid overlaps. Features include accurate interface detection, customizable display, optional mini-graph, color coding, granular font and unit control, detailed per-interface history graphs, safe data management, and easy CSV export—bringing the network monitoring Windows forgot. NetSpeedTray key features: Lightweight & Efficient Runs quietly in your system tray without consuming resources. Features a "Dynamic Update Rate" that lowers refresh frequency when the network is idle to save CPU and battery life. Native Look & Feel Blends seamlessly with Windows 10/11 UI. Smart detection for light and dark taskbar themes ensures text is always visible. Intelligent & Adaptive Positioning Automatically finds empty space next to your system tray and shifts to make room for new icons, preventing overlaps. Seamless OS Integration Behaves like a native Windows component. Hides instantly with auto-hiding taskbar Hides when a fullscreen app is active Smart Network Monitoring Accurate by Default: Auto mode identifies your main internet connection and ignores noise from VPNs or virtual adapters. Easy Interface Selection: Switch effortlessly between Auto, All, or Selected network interfaces via intuitive radio buttons. Total Visual Customization Free Move Mode: Unlock and place the widget anywhere on your screen. Optional Mini-Graph: Real-time graph of recent network activity with adjustable opacity. Color Coding: Customize colors and speed thresholds to quickly see network status. Granular Display Control Text & Font: Adjust font family, size, weight, and alignment. Units: Automatic (B/s, KB/s, MB/s) or fixed Mbps display. Precision: Set decimal places and always show them for uniform appearance. Detailed & Intelligent History Graph Smart Scale: Logarithmic scale shows low-level traffic and large spikes clearly. Per-Interface Filtering: View speed history for specific adapters (Wi-Fi, Ethernet, VPN). Safe & Efficient Data Management: Adjustable retention, automatic cleanup, optimized database. Easy Data Export: Export raw data to .csv or save high-quality graphs for reports. NetSpeedTray v1.3.3: The Updater Fix A stabilization release that repairs a critical regression in v1.3.2: the app shipped without OpenSSL, which silently broke every HTTPS request — including the built-in update checker (the "Could not check for updates" error many of you hit). This release restores it, hardens the build so it can't happen again, and fixes a startup crash plus four other reported bugs. Changes: Fixed update checking — Resolved a critical issue that prevented the app from checking for updates ("Could not check for updates"). Fixed startup crash with Auto-Cycling — The app no longer crashes on launch after enabling Cycle display mode. Fixed incorrect network speeds on 10GbE adapters — Multi-gigabit network cards now display speeds correctly instead of being stuck at 0. Improved color coding — Default color is shown when idle, and color/threshold changes now apply immediately without restarting. Fullscreen visibility fix — The widget now correctly stays visible over fullscreen apps when Keep Visible is enabled. Improved AMD Ryzen temperature detection — More reliable CPU temperature monitoring for Ryzen processors. Cleaner upgrades — Installer now removes outdated application files during upgrades, preventing DLL/version conflicts while preserving user settings. Improved stability — Fixed potential DLL loading issues by excluding critical OpenSSL and NumPy components from UPX compression. Better settings window — Scrollbars removed and layout improved for a cleaner experience. Localization improvements — Updated translations and completed missing UI text across all supported languages. More reliable releases — Added regression tests covering recent critical fixes, bringing the test suite to 196 passing tests. [full release notes] Download: NetSpeedTray 1.3.3 | 87.9 MB (Open Source) Download: NetSpeedTray Portable | 101.0 MB View: NetSpeedTray Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Why Delta Chat is the best decentralized messenger you have probably never tried by Paul Hill There is no shortage of messaging apps out there; we have WhatsApp, Messenger, and Telegram, just to name a few. While Meta has taken steps to incorporate encryption into Messenger and WhatsApp, they still leave a lot to be desired. If you are in the market for a messaging app that promotes security, privacy, and optional anonymity, you'll want to read what I have to say about Delta Chat. For those not familiar with Delta Chat, rather than relying on centralized servers as you do with Facebook Messenger, it relies on email. Essentially, it is a chat interface that feels like a messaging app, but secretly in the background, it is firing off emails. In the past, you used to have to sign in with your email account. When you sent messages to people, it would just be sending encrypted messages to their inbox, which their Delta Chat client would decrypt. When I first learned about Delta Chat, it required users to sign in with an email account, but I was pleasantly surprised upon trying it in 2026 that this is no longer a requirement, or the preferred method was to use the app. Recently, I’ve tried UAD-ng on my old Nokia 3.4 to disable most of the Google apps because the bootloader is locked, and this is the next best option. While finding replacement apps in F-Droid, I came across Delta Chat again, and it has undergone quite a big change since I last used it, with its new chatmail relays, which no longer require you to sign in to your own email account, providing anonymity, and they offer greater security. Android and Desktop Delta Chat apps. Not only does it run on my de-googled phone, but it also works on desktop computers and iOS, making it truly ubiquitous. For me, Delta Chat is a wonderful alternative messenger because it gives you more control. It supports switching between different profiles, which you can set up super quickly; you don’t register a username, you don’t register a password. The only thing you do have is a random string email address on a chatmail relay (which you don’t have to memorize). To maintain access to your profile, you just need to add a second device to your account via QR code or make a backup of your account, which you can restore later. Fail to do these, your account is gone - as it should be if you don’t want to leave accounts that could get hacked later on. My decision to block Google stuff on my Nokia was done for practical reasons; the device sucked when it launched, and it sucks even more now. The nice thing about F-Droid and the apps within is that they’re usually lightweight, free of bloat, and work well on that device. What was inconvenient for me was that it was hard to send messages from that device, say if I wanted to copy a code over to my main phone or send family members a link from that device. That’s when I decided to look at the available chat apps and saw Delta Chat. Another nice thing about Delta Chat is its notifications. Some messaging apps rely on Google’s ecosystem for notification transport on Android; however, with Delta Chat, it can use Google’s solutions if you have Play Services or MicroG installed. Otherwise, it is able to keep a background connection to the chatmail relay server so that you can get notified when you receive a message. As free software, the code of Delta Chat is open for all who want to take it and build upon it. In the future, if the developers of Delta Chat make a catastrophically bad decision and take the app in an undesirable direction, users can take the code and fork the project. This contrasts with closed-source apps from corporations that can take their products in any direction they like. By relying on free software instead of closed-source programs, you actually control your computing. I’ve spoken at length about how running this type of software is like owning your own home rather than renting it. The same applies here; if you use Delta Chat, you don’t need to worry about it going away in the future. Whether it is Telegram, WhatsApp, or Messenger, you are required to register a username and password to use these services. A major flaw in this design is that anyone can try various passwords and potentially break into your account with your complete chat history intact. Sure, there is encryption in Messenger, where you need a second PIN and two-factor authentication in Telegram, but breaches happen all the time. Unlike before, when you used to sign in to your email account to send and receive messages, the primary way to do it now is to create an account on a chatmail relay. The resulting email address is a random string followed by the name of the relay you pick. This means you can start and begin adding contacts Without a username and password, you either need to ensure you have a backup or at least one device running your Delta Chat profile. The primary way to log in on another device is to go to the settings and add a second device. Then, you’ll just scan a QR code with your new device, and it’ll log in to your account and sync all your chat history and contacts. To end users, Delta Chat just looks like any instant messenger; however, it is really sending your messages as encrypted emails to your contact. This is pretty cool from a censorship perspective, as it makes the service more difficult to block. Previously, the main way to use the app was by logging in with email, but nowadays, it’s recommended that you use chatmail relays. Chatmail relays temporarily hold messages in case your device is offline. They are cheap, simple servers that don’t store data as group states. Other information, like your name and avatar, only exists on your device and the devices of those you share your contact information with. The relays are also decentralized and operated by various groups and individuals. It is even possible to set up your own chatmail relay, but most people will want to use one hosted elsewhere. To keep your messages secure, Delta Chat uses a secure subset of the OpenPGP standard that gives you automatic end-to-end encryption. It also uses Secure-Join to exchange encryption setup information through QR-code scanning or invite links. Autocrypt is also used to automatically establish end-to-end encryption between contacts and all members of group chat, but sometime this year Autocrypt v2 will be rolled out, bringing post-quantum resistant encryption and forward secrecy. The Delta Chat FAQ is an interesting read that explains many more details about the app. Credit: Pexels Delta Chat is unique among messaging apps because it is built on email, a technology that’s decades old and isn’t going anywhere soon. What’s more is that email is not centralized either, so it’s far more difficult for any authoritarian regime to disrupt the Delta Chat app. I haven’t spoken too much about features yet, so I will do that now. Delta Chat allows you to do one-on-one chats, group chats, and create channels. It also supports file sharing and making audio and video calls when chatting one-to-one, but it’s not available for group chats right now. At the time of writing, the calling functionality is disabled and can be enabled in Settings > Advanced > Debug Calls. I have used the video calling feature, and the quality is excellent. It works over WebRTC, another open standard. The app also lets you send voice notes, enables disappearing messages, and has its own app ecosystem. I did try playing chess one time there, but it was a bit spotty; though, we did manage to complete the game with a victory for me. To add people to Delta Chat, you can either give them your Delta Chat link or your QR code to scan. These are the only ways to add users, so you won't have any spam bots bothering you. If the people you want to chat with don't have the app yet, just send them your link, and it will take them to a webpage where they can install the app and then add you. It's really quick for them to install it and get started, which is nice. Credit: Microsoft. The Majorana 2 quantum chip unveiled in 2026. I do not think quantum computers are too far out now, and I do hope that Delta Chat is able to push out Autocrypt v2 sooner, rather than later, so bad actors do not attempt to collect encrypted communications and then decrypt them in the future using quantum computers. By getting people’s messages post-quantum-safe now, users won’t have to worry when quantum computers start cracking legacy encryption. Overall, I would recommend this app to people who are already past WhatsApp and Messenger and have perhaps begun using apps like Telegram or Session. It shares a lot of characteristics with these apps and goes a lot further than Telegram in terms of security. By being based on email, it is also resistant to censorship, and the lack of a username and password makes you anonymous (if you want to be) and safe from brute force password cracking attempts. Let me know in the comments if you’ve tried Delta Chat recently. Do you think it's a good bulwark against governments that are tightening their grip on the internet?
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +Edouard
      220
    3. 3
      PsYcHoKiLLa
      156
    4. 4
      Steven P.
      73
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!