nmX.Memnoch

Agreed...anything by Minasi is usually very good.

Add /PERSISTENT:NO to the end of each map in your logon script. For example: net use X: \\SERVER\SHARE /PERSISTENT:NO Are you using regular batch files for your logon script?

SystemRoot should be something like C:\WINDOWS\. The $WIN_NT$.* directories are directories that setup uses. They shouldn't exist anymore once setup completes.

First, make sure your motherboard will support a SATA hard drive. The reason for choosing SATA is because of the higher (theoretical) throughput and the easier to route cables. They also contain other technology that help to make them faster than a PATA drive (NCQ, TCQ, etc)...however, these technologies usually require that the SATA controller also support them before you'll see any benefit.

If you have another user with Administrative privs you can simply change the password on the built-in Admin account.

I've had this before and it turned out to be a bad memory stick. All of the hardware he listed is from manufacturers usually known for stable drivers.

You must've gotten one that the dealer had in stock for a while. WD recently changed the motors in their drives so they run really quiet now. I know what you're talking about though...I have a pair of WD 250GB SATA drives that I ended up taking out of my machine because of the noise. The drives are fast, I just couldn't deal with the whine.

Did you add it at the web server or web site level?

No idea...I've never used it. Sorry.

I'm willing to bet that taurus-1.siol.net is the DNS server for workgroup.org. You're getting the error because workgroup.org is probably still referenced in your DNS server somewhere...and the actual DNS server for that domain is telling your DNS server that it doesn't have access to update records. There's a proper way to clean up all of the DNS records when you change the domain name...but I'm not exactly sure what that is. I had problems with my AD when I changed the domain name; promoted first server with dcpromo and setup domain...changed my mind and demoted via dcpromo...then did it all over again. I would periodically get DNS errors in my Event Logs for the original domain name that I wasn't using anymore. That was several machines/installs ago though (my home network changes too frequently to worry that much about it).

That won't work either because IIS6 is blocking access to the file. It does this for any files that haven't been configured. A quick Google search says that you need to setup a MIME type for .bat files to be served by IIS6. http://www.webservertalk.com/message263612.html

Using Virtual Server is very much possible. Here's a good article to start with: http://www.sql-server-performance.com/inst...ual_server1.asp And a guide from Microsoft: http://www.microsoft.com/downloads/details...&displaylang=en

If you use eMule you can tell the application not to allow more than a set number of half-open connections (I have mine at 9)...which will also keep your event log clean without replacing system level DLLs. Since he's talking about a server operating system I would assume he would want it up and running as much as possible. Replacing system-level DLLs is a good way to start causing stability and reliability problems.

They're owned by Maxtor now (but see below). They are about to be one in the same...http://www.theinquirer.net/?article=28482

This isn't possible with Windows XP (or any Windows version based on the NT kernel). Permissions are granted on a user-by-user and/or group-by-group basis.

That motherboard doesn't have integrated RAID. It has SATA, just not RAID. I'm looking at either that same motherboard or the SE variant because I just acquired a Socket775 P4 3.4EE and don't want to replace my 4GB of Ballistix or my BFG 6800GT just yet...but I also don't want to give up a P4EE either. Personally, I'm leaning towards the SE variant because the onboard NIC is Intel, where on the non-SE model it's Marvell. I had an Intel NIC before, but now have a Marvell NIC on my current P4P800-E Deluxe. I like the Intel NICs a lot better.

As long as a valid connection is being established then nothing is being limited. The limit prevents worms and viruses from bogging down your server by preventing them from creating more than 10 connection attempts at a time. As long as the user/workstation has access then a valid, full connection should be established fairly quick.

Notice I said "less in the OS", not "less in Windows". As was mentioned, it's based on binary...not "because Microsoft says so". This is one case where they actually follow the standard.

I don't know if this would make any difference (although it seems it would)...but is your AD running in mixed or native mode?

You can run scripts with command-line arguments using the built in Task Scheduler.

It only limits half-open connections. Under most normal configurations you don't need to do anything.

NT4 trusts aren't automatically two way trusts...you have to manually configure the trust both ways. Until you do it'll only work one way. Trusts between AD sites are automatically two-way transitive trusts.

1. Does your case have front-panel audio ports? And if so...did you connect them? 2. Did you leave any unused motherboard mounts under the motherboard?

"workgroup.org" is a valid domain name that someone owns. If you open that page in your browser you'll see the same message you posted. If you're connected to the internet, which you are, you should never use a domain name that is already in use by someone else (this is easy to check using sites such as register.com or doing a simple whois). It'll cause errors in your DNS and could potentially be causing errors on their DNS server(s). When doing internal DNS domains on networks connected to the internet, but that won't be seen by the outside world you should use a suffix that isn't a "valid" suffix such as workgroup.local.

The 10 connection limit is just like that of Windows XP. It only applies to accessing shares on the server...it does not apply to 3rd party software as there is no way Microsoft can impose that sort of limit. I don't believe that connection limit applies to IIS though...it'd be a waste to pay for a Web Edition license if it did. You can compare the differences between Editions here: http://www.microsoft.com/windowsserver2003...turesorter.aspx One thing to also note is that Web Edition is limited to 2 CPUs and 2GB RAM. This is more than enough to host a BitTorrent seeder, but it's also something to think about in that the hardware support is much more limited than even the Standard Edition. I still say go with Standard Edition. It'll offer you more options in the future. Setting up a server like this always start out with one intention but then as you become more familiar with things you start to realize "Hey, I can do this with it, too"...Web Edition will limit those possibilities.