Stoic Joker

I've worked with Windows I've worked with *niX I've worked with Mac I use Windows

That would have been my first answer also... (hehe) But as it turns out it's not actually listed in GP, but you can "add" it via Administrative Templates. Below is the contents of a .txt file that happened to be on my desktop, I've not a clue as to the source of the info...but if it's made it to my desktop to was a good enough source to be worth saving... So...

I have searched Google for several variatons of "CLSID Computers Near Me", but without any success. I really appreciate your example and the small correction, and will continue looking for the answer, but any hints you can give me on where to find it? <{POST_SNAPBACK}> Unfortunately no, at this point I'm also googling the hell out of the question (got me curious) with out any luck. I know I've run across this before while working on a network browser control for a program I was writing...but I'll be **** if I can find it now. ...But I'll keep looking

Actually you need the CLSID, not the GUID that might make it easier to find. Try this: Create a new folder and name it: Network Test.{208D2C60-3AEA-1069-A2D7-08002B30309D} that folder will now become My Network Places because of the CLSID. A bit of digging on a few programming sites should give you the CLSID for the WorkGroup machine list (Computers Near Me) view level, just remember that your looking for the CLSID not the GUID.

By default no, but it is a selectable option. So yes it will give you the MAC, IP, & HostName of anything on the network you are scanning.

I use Angry IP Scanner for that, it requires no install (so runs great from a thumb drive) and will give you a list of everything with a MAC address in a given IP address range.

Hm...Let me backup a sec, to make sure we're on the same page...before I answer that. Both servers are DCs, on the same domain, and in the same forest. Yes? Did both servers report the same time? and if not, how far off were they? The biggest problem people seem to run into with NTP, is that the NTP service starts up before the DNS service, so if your "time source" is identified by its FQDN...the lookup fails and the time service shuts down. The best bet, is to configure both DCs as a "reliable Time Source" Stratum 2 time server which will have them sync with a Stratum 1 (atomic clock). Then the SNTP service will stay up & service the time service requests that are sent to it by default by all the machines in the domain. Note: There were a few issues that were "fixed" in Win2k3 SP1, so that would be a good place to start. I strongly recommend that you spend some "quality time" in at the MS support knowledge base to get familiar with the configuration details for the Windows Time Service...as it will help fill in the blanks left by all the info I'm not able to include here. As a quicky shortcut, I have a reg snippet that I use to configure the time service when I'm in a hurry. If you run it on both of your DCs, it will configure them as above. Note: You will need to restart the time service after including the changes. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config] "MaxNegPhaseCorrection"=dword:0000d2f0 "MaxPosPhaseCorrection"=dword:0000d2f0 "AnnounceFlags"=dword:00000005 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters] "NtpServer"="192.5.41.40,0x1" "Type"="NTP" "Period"="SpecialSkew" "ReliableTimeSource"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient] "Enabled"=dword:00000001 "SpecialPollInterval"=dword:00007080 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer] "Enabled"=dword:00000001 The IP used for the external (stratum 1) time source is for tick.usno.navy.mil ...And yes, using it is legal.

That's usually a syntax error in one of the load lines in the registry's run keys. One of them either has an extra ' ' (space char), or has a ' ' in a string that is not incased in "quotes". You should be able to find which string it is by using msconfig, then use regedit to do any corrections

Hubs - broadcast everything to all ports Switches - have CSMA/CD (Carier Sensing Multiple Access / Colision detection. There in lying the primary difference between hubs & switches...switches don't broadcast.

check the time on both machines to see how far off they are. From the command line: net time \\server_name then net time \\client_that_can't_connect if they're 5 or more minutes off, on the client run: net time \\server_name /set /yes double check to make sure they're in sync, & then retry connection

The two different Program Files folders are just to make it easier for people to figure out where stuff is. The puter doesn't care what folder a program is in, it is going to execute it based on what is in the executable's header info (e.g. what runtime library it was compiled with)...not it's file path.

The Kerberos security protocol (used by 2k3 by default) requires (also by default) that the clocks on all machines be no more than 5min apart. Now a 5min clock drift in 3 weeks sounds easily do-able, and I've seen clock skew cause some really flakey behavior. Also considering there aren't any Windows services that have a three week refresh interval, I'd take a really serious look at your SNTP configuration.

This should help Administering the Indexing Service Gives registry location, explanation of how the service works, and info on how to tweak it.

Um... The answer to both will take way to long to type, but... The MS Support Knowledge base has some excellent "How To's" for getting server services working. Link to articles for these issues Link to MS Support Knowledge base home page <-Just in case first link doesn't work. @Quaylan If your using SBS2k3 half your problem is that MS Exchange is installed and not being used. The SMTP service is tied to Exchange by default and should be left there. Either way SMTP needs to be "fixed" but while Exchange does have a bit of a learning curve...it's well worth it.

Okay... Now that's weird. Long shot, but you mentioned earlier that you were getting Win32time errors in the logs. If the time on both servers is different by 5 or more minutes (by default) then Kerberos will start rejection traffic. How is you time service (SNTP) configured? ...Also found 2 links that might be helpful EventID 5719 Problem with domain trust after W2003SP1 upgrade

Folder Options->View Tab, Uncheck "Show encrypted or compressed NTFS files in color" Done...

I'll second that.

Okay... It's been a while since I've don this myself...So I had to go RTFM It's amazing how many details there for a config like this. Any how.... Here's a section of "The Manual" on how to setup the trust: ...Sorry about the formatting, I'm just doing a quicky cut-N-paste at work.

For the one account used for the remove/rejoin yes this is true...However the other accounts on the machine usually aren't so lucky. Do they work? Yes...But they tend to login rather slow and things get worse depending on the complexity of the network (e.g. it's easy to miss, but it's there).

A logical drive is not a true partition, they're are just a segment of an extended partition. The only reason to use an extended partition is if (for some reason) you need to segment a physical drive into more than 4 pieces. Logical drives have a lower order of priorty in drive letter assignments, so if you running a multiboot configuration and add/remove an IDE device...you'll end up playing hell trying to figure out where your OSs went. It's just simpler dealing with primary partitions as they tend to be a bit more predictable (drive letter wise) and if you only have one OS and need more that 4 partitions (/volumes) Dynamic Disks are a much more flexible (resize on the fly, span and no reboots needed) option.

If you can't ping the NetBIOS name, make sure that recursion is not disable. Also make sure the DCs are registered with (themselves) their DNS servers properly. DC1 of Domain1 should have itself listed as the primary (and only) DNS server DC1 of Domain2 should have itself listed as the primary (and only) DNS server Add DC1 of Domain2 to Domain1's DNS forwarders list Add DC1 of Domain1 to Domain2's DNS forwarders list That's the quick-N-Dirty way to get A to resolve B. A split-zone DNS with Zone transfers is the cleaner/correct method. Actually they must be different, or there would be no point in setting up a trust between them (as they would presumably be in/on the same domain).

Rejoining the domain changed the machine's RID, now the user's GUID (combination of their SID & the machine's RID) are all invalid. Put all of their user profile folder's in a backup directory so they're recreated during their next login. Then you can restore their files to their new profiles. In the future never remove/rejoin a machine to a domain...it tends to make a mess.

Simple, to edit another users HKCU either login as them (Yeah I know too easy...). Or in regedit, go to the file menu, notice the "Load Hive" option? Highlight HKU then select the Load Hive option browse to the (target) user's user directory (In Documents and Settings), and open the ntuser.dat file...Which is actually that user's HCKU As a side point, this type of thing is supposed to be done (the easy way) through Group Policy.

Your allowed to create 4 Primary Partitions on a physical drive (only one can be set as active) Or you can create 1, 2 or 3 primary partitions & then create several Logical Volumes in an Extended Partition (but that can get silly after a while...). Logical volumes in an extended partition are flakey at best, I do not recommend using them. Either way if you format one partition the others are perfectly safe...Just make reall sure you format the right one (drive letters tend to change some times).

Well...I got tired of answering this type of question a while back...so I put this tutorial together-> DynamicDisks 101 ...Hope it helps