A Domain is a logical group of computers having versions of Microsoft Windows OS.
All these computers shares a central database which is known as Active Directory.
An Active Directory is basically group of computers, users, objects, etc.
the vending machine is at the wizards domain
check the dns first check the IP would has admin rights on the domain to add machine. restart PC
the printing machine, file server and domain
Many times this is because the resources are part of a Windows Domain. Domains have strict security capabilities that will lock computers not part of the domain out. You can have your machine physically on the same network, but not part of the domain, and if that is the case, you will not be able to use domain resources. Ask your tech support goons to either add your machine to the domain, ensure that your current user login is a domain user, and make sure that your password has not expired.
If your PC is not a part of a domain it doesn't matter which name you put over there (Network Domain). Server Name is a network name for your PC which can be used instead of ip address.
You will need a Active Domain Server (e.g. a computer running Windows Server as the operating system) as far as I remember.
Yes, if the client is part of the domain then the standard procedure is to log into the domain, which requires a secure login. However, the client could also log on locally to the machine, not the domain, in which case the log on requirements are not as strict.
Yes, You can COndition: both should be able to ping each other ie subnet should be recognized by each other if in a domain or workgroup they will be able to communicate
Remove the workstation from the domain then rejoin the workstation to the domain. ...if you want to run the risk of losing some security credentials. When you leave and rejoin the domain you are no longer in the same machine account. The simple fix is to log in as a local admin and from the command prompt type: netdom.exe resetpwd /s:<x.x.x.x> /ud:<AccountName> /:pd* Where <x.x.x.x> is address of a domain controller and <AccountName> is a domain account. You will be prompted for the password for the account you used and 2 seconds later the job is done. You do not need to reboot just log off your local admin and carry on. Your machine password will have been reset and trust restored.
What we call a Domain Server is a machine that is like a complicated traffic control centre. When a computer joins a network is needs an address. The Domain Server either has an address for it or creates an address for it. The address is important as that computer needs to introduce itself to other computers and the Server needs to know who is connected and who is not.
Microsoft recommends that access control to computer resources be administered by using groups. In this way, many users that have similar needs for resources can be dropped into a group that has the correct permissions already configured instead of individually modifying each user account. Group permissions to access resources are configured using group policy. A policy usually addresses one very specific aspect of a system's configuration. There are many policies that can be configured for a group to control system access and behavior. Local group policy addresses only users who are physically logging into one particular machine such as the server itself or a stand alone operating system. To log into a machine locally, a user must create a unique ID/Password pair that authenticates the local user to the local physical system. Once authenticated to the local physical machine, group policy according to which local group the user is assigned is initiated. Domain authentication as well as domain group policy is maintained centrally by the server for the domain. Even if a user has configured a local ID/Password pair for their local physical computer, a different and unique ID/Password pair is created to log onto the domain. When a domain user is created, they also must be assigned to a domain group. Once the server for the domain authenticates the domain user, the policy for the domain group the user belongs to is initiated. These policies are centrally administered by the domain administrator instead of each computer in the domain being configured separately for each user. Domain group policy can be configured to control access and behavior for any resource on the entire domain including resources on client computers. Local group policy can only control what is on the local machine at which a user is sitting. Finally, domain group policy supersedes any local group policy.
Windows 98 machines don't join a domain - they are just able to browse it. You only have a choice to change the workgroup name on a Win98 machine - you make the workgroup name the same as the domain name and they can browse the network resources and map drives to them. They are like XP Home edition which can just join workgroups and not domains.