I have set up dns and everything in a server. I assume in that is something wrong in a client/workstation framework config. I have tested at smallest 4 out of 12 client workstation that should use a domain. Note: adjectives the 12 be working fine in workgroup (p2p) nouns. Of the 4 ive tested, merely 2 be connecting to the server, logging in to the server.
My client PCs are xp sp2. To log in to server, i a moment ago typed surrounded by the domain nickname (say netnet.local) surrounded by computer properties>comp name>domain and Okay. To those notebook near successful nouns it say, "Welcome to netnet.local" but for those which are not successful it say that the "domain controller could not be found. ples check if uv typed it correctly..blah blah" What else do i entail to modify contained by client grating properties, or within ip address (ip, subnet, gateway, proffered dns...)or contained by computer properties or within server?Thank you for your time reading this and i really do appreciate any answer. appreciation contained by credit.
Answers:
Your right in the order of the wallpaper it is surrounded by group policies. The other problem is different though.Is it a different server? If it is on the 2 that cannot connect did you do a DHCP release/renew? Did you setup server 2003 to be the DHCP server? If you did you enjoy to double check adjectives of your Domain settings and do a release renew on your NIC and do a restart on those machines. That should do it. If that doesnt work come put money on and below par try and minister to more. There are several more things that can be done. Especially user statement setup. If you are using the server as the "PDC" which it isnt really since your using 03 which uses AD, but anyway you own to setup adjectives of the user accounts on the server and put together it so adjectives of the PC's carry their logins to adjectives resources including the internet through the AD server. But resembling I said we can digit it out. Try those first though.. Also can you ping the server from the systems that wont connect? are they on duplicate side of the switch? do you own VLAN's setup? Are they on one and the same side of the router? Are you using Private or Public IP's?
The first problem is most probably a DNS issue, breed sure that the client PCs are configured to enjoy the preferred DNS as the IP of the domain controller. try to ping from these machines to the domain controller using their name instead of IPs and try to ping the clients from the domain controller as capably.
The second request, on the domian controller walk t start--run-- and type gpedit.msc and hit enter.
stir to the user configuration tab--administrative templates--desktop--active desktop, on the right side you will find an remedy call "Active Desktop Wallpaper" you should see it and follow the instructions. This wallpaper will be applied to the clients which attached the domain solitary and it may cart some time to be applied so don't come up with it didn't work.