Search results for query: *

The computer name is ok. DNS looks ok. But I'll Google some questionmarks. I feel like uninstalling DNS and reinstall it during the weekend. Has anyone done it and gotten away with it without problem on Monday?

Hmmm. Missed the kinda important part ;) And the thing is.... it's just called "Domain". The #(¤/%¤ who built it didn't bother to add the .local or .ad. to the name. Here's the message: Note: This information is intended for a network administrator. If you are not your network's...

Hello. I have this problem with joining computers to a domain that's just called "Domain" not "Domain.ad or Domain.local" I didn't set it up but can someone help a little? 2003, XP, AD, DNS. Accounts/groups can be created, DC can be pinged and everything works except joining the client to the...

Something like dsquery user OU=Managers,DC=YourDomain,DC=Com -o upn Patrik

Are you using Roaming Profiles? Patrik

Hello. Look at Server 2003 Resource Kit. It has REDIRCOMP (or REDIRCMP) don't really remember. It allows you so set a default OU for your computers. Patrik

Make sure you have the same subnetmask and subnet, and try starting WINS so that you can resolv the NetBios name to IP addresses. Can you connect if you write the IP address? Patrik

So you can logon to the first server through Remote Desktop?, but can't connect to the second server through Terminal Server. What services are running on the second server? Patrik

You can configure DNS with a wildcard "*" so that everything that comes before domain.com will point to your web server. Patrik

Do you mean deny the user and computer access to specific objects in the domain? Otherwise just remove the computer and the user from AD and you're done. Patrik

I use the MSCE books. (Certification guides) and everything else I Google :)

Lock down the SMTP Virtual Server otherwise you're gonna get blacklisted again if your VS is known for being a relay for spam.

Is it the same if you run it on the server? Patrik

One way is to create a template with the common settings and just copy it. Patrik

If you have Dynamic DNS enabled DHCP will fix it for you. Patrik

Don't forget about the FSMO roles before decomissioning the 2000 DC. and http://www.tech-geeks.org/geeklog/article.php?story=20041223002509333

I'm too slow today. hehe

Or you can set up a Superscope: http://technet2.microsoft.com/windowsserver/en/library/150ddc41-a7e3-4c86-96d1-d706e27116f21033.mspx?mfr=true Look at Example 3. Patrik

Since you don't know how to do it, I think it's best if you to Google it, and understand how to do it before you start. If you just read it here, set it up and it doesn't work for some reason you may have a #&#%¤ of a time correcting it. Just one thing. Exchange and DNS are best of friends. 90...

Since you have 2 domains and 2 forrests that's not connected by trust, you can get an Internet router. Put them both on the same subnet and connect them. Maybe? Patrik