ewaite

We use Microsoft Software Update Services http://www.microsoft.com/windows2000/windowsupdate/sus/default.asp as our local windows update server. You simply point auto-update (included in Win2k-SP3 or higher or available as seperate download) to your local server. Lots of documentation on setting it up plus its free. You have to manually approve the patches but that's actually a good thing because it gives you time to test first. You can configure Auto-Update on client using group/local policy or registry settings. Hope that helps -Evan

Assuming your using Apache webserver, you can manage authentication with .htaccess or config files. Here's a link that describes them in detail Authentication in Apache: http://httpd.apache.org/docs/howto/auth.html .htaccess description: http://httpd.apache.org/docs/howto/htaccess.html Hope that answers your question PS. If your new to linux, install webmin (http://www.webmin.com) on your server to help you configure these things.

Or if its 2k/XP/2k3 then use findstr (Find String). Here is the output from findstr /? Searches for strings in files. FINDSTR [/b] [/E] [/L] [/R] [/s] [/i] [/X] [/V] [/N] [/M] [/O] [/P] [/F:file] [/C:string] [/G:file] [/D:dir list] [/A:color attributes] [strings] [[drive:][path]filename[ ...]] /B Matches pattern if at the beginning of a line. /E Matches pattern if at the end of a line. /L Uses search strings literally. /R Uses search strings as regular expressions. /S Searches for matching files in the current directory and all subdirectories. /I Specifies that the search is not to be case-sensitive. /X Prints lines that match exactly. /V Prints only lines that do not contain a match. /N Prints the line number before each line that matches. /M Prints only the filename if a file contains a match. /O Prints character offset before each matching line. /P Skip files with non-printable characters /A:attr Specifies color attribute with two hex digits. See "color /?" /F:file Reads file list from the specified file(/ stands for console). /C:string Uses specified string as a literal search string. /G:file Gets search strings from the specified file(/ stands for console). /D:dir Search a semicolon delimited list of directories strings Text to be searched for. [drive:][path]filename Specifies a file or files to search. Use spaces to separate multiple search strings unless the argument is prefixed with /C. For example, 'FINDSTR "hello there" x.y' searches for "hello" or "there" in file x.y. 'FINDSTR /C:"hello there" x.y' searches for "hello there" in file x.y. Regular expression quick reference: . Wildcard: any character * Repeat: zero or more occurances of previous character or class ^ Line position: beginning of line $ Line position: end of line [class] Character class: any one character in set [^class] Inverse class: any one character not in set [x-y] Range: any characters within the specified range \x Escape: literal use of metacharacter x \<xyz Word position: beginning of word xyz\> Word position: end of word For full information on FINDSTR regular expressions refer to the online Command Reference.

No problem, happy I could help. I really wish MS would warn you before installing the patch from windowsupdate (at least until they get it fixed). Everyone I know who runs XP has been screwed by it. This brings up another point, assuming MS tests their patches at least internally, how did such a big whoops make it past Q/A. Either everyone at MS runs a dual 10 GHz machine (not likely) or they don't run Antivirus (scary!). Or more likely they were just testing to see if the patch plugged the hole and didn't concern themselves with performance.

If you do have all the updates for WinXP SP1, you probably have the Q811493 patch installed. If you run Antivirus software (I would hope you do) this patch causes your Uber-fast computer to run like a 486. Microsoft has identified a performance problem when installing this patch and will be releasing an updated version some time soon. The patch can be removed without problems by going to Add/Remove Program and uninstalling "Windows XP Hotfix (SP2) Q811493". You can check out the full MS Bulletin here: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS03-013.asp

no problem HitLines, glad to see it was something simple

Go to Tools Menu => Internet Options => Connections Tab => LAN Settings and uncheck "Automatically Detect Settings" (if its checked). Its probably trying to find a proxy server on your network.

Hehe yes we have WAY too many files. The problem is our web software was written by someone who thought it best that every client had their own folder (with a copy of master version files) and every client project had its own sub-folder (also with a copy of master version files). Multiply this by 3 major products (and multiple versions of each) and we have a lot of the same files in different folders with a few customizations here and there. These files will eventually be archived but not in the near future. Luckily our new versions of software will be less file intense

Thanks for your reply Four and Twenty. How many files do you have in your wwwroot? Did you notice any performance hit? pmistry, here's a great link to learn more about DFS(http://www.labmice.net/Windows2000/FileMgmt/DFS.htm). Its a pretty sweet way of giving yourself fault tolerant file shares.

Hey Everyone I'm looking for some opinions about the performance of Windows 2000 Distributed File System (DFS) when dealing with a very large number of small files. Please reply with personal experiences using DFS and any impact on performance of the servers. I plan to implement a DFS share to replicate the wwwroot on 3 web application servers. The wwwroot contains about 230,000 small files in 24,000 folders. Total size is about 3 GB but the files rarely change. All three servers are large machines running Windows 2000 Server (SP3) with hardware SCSI RAID and are connected via 100mbit lan. I fully understand how to implement this but am looking more for input on the performance hit I can expect when replicating such a large number of files. Thanks for any help, Evan

Can you give a few more details (what OS and Service pack level). Are you talking about the built-in (microsoft) disk cleanup wizard or some 3rd party software? With a few more details I'm sure we can help you out

Are the new users profiles being created in the C:\Documents and Settings\ folder after you try logging them in? Are you able to hit CTRL-ALT-DEL and bring up the task manager while sitting at the blank screen? If you are, go to the Processes tab and kill explorer.exe then go to the Applications Tab and click New Task. Type explorer.exe into the Create New Task box. This is basically forcing a shell reload

Quick search on http://groups.google.com resulted in quite a few matches. Here is an interesting one http://groups.google.com/groups?hl=en&am...2&frame=off It looks like your not alone

Did you apply serivce pack 1 and 2 for office xp? I know the basic version of Office XP has more bugs than you can imagine and service packing it may help your problem.

Perhaps a few more details would help. Please provide: 1. What OS (Win2k, WinXP, etc) 2. What Service Pack Level (SP1, SP2, SP3 for win2k or SP1 for WinXP) 3. Any aditional changes (file permissions, disabled services, etc) 4. Some basic hardware info (speed of processor, size of hard drive, amount of memory) With this info, we should be able to help you out.