clutch

Yep, I have used it before on all the versions (4, 5, 5.5) before v6.

http://office.microsoft.com/downloads/de...i-Virus|Updates

Did you run the command that Xiven posted? That is what prompts you for the OS selection. Remember, I stated "Xiven", and not "Wolf87".

What error does it give you when you try any of the things you mentioned? And, have you tried renaming them first? Also, did you try stopping the FTP service first, and then deleting them?

Either restore from a pre-codered backup, or simply format and start over. Then, if you still feel that strongly about IIS, don't install it.

I just saw this at MS, it's a free hotfix checker that can scan systems on a network and determine what these machines have installed on them. http://www.microsoft.com/technet/treevie...ls/hfnetchk.asp Just thought you guys might be interested. I know this isn't quite as cool as the product from St Bernard that Toby mentioned, but hell, it's free.

Welp, I haven't installed my copy, but if I did, I would have to say that "it's your copy"...

Do what? I back them up all the time. And if the program were to fail, you can grab the PST file that it was using and import it into another Outlook installation. Also, if you archive your mail, you can simply open the PST file in Outlook and search for anything you like, without the need to import all the data back into your profile. You can also export your contact info (address book) to several formats, including CSV (comma de-limited, and viewable in Excel and notepad) and PST.

Did you ever patch it for Code Red? Code Red servers will also show intermittent response delays and high CPU utilization. Have you run perfmon (or just kept an eye on the task manager) to make sure what processes are taking up all the utilization time? I had issues with McAfee NetShield sucking down CPU cycles while in "System Scan" mode. Once I changed the mode, all was better (although some servers will need system scan regardless of the consequences due to their function).

I use OutlookXP at home, and Outlook 2000 at work. I love the app, and I use Exchange server at both locations along with some CDO-based apps that work within Outlook (both versions).

It's the same as the post by Xiven here Brian: http://www.ntcompatible.com/vb/showthread.php?threadid=16590 You can select what OS you want to download for, or download IE for all of the OSs.

Do all of the workstations have the same IP as they did before it went out?

So, your PCs see each other OK on the LAN? Were you using it as DHCP server? If the DHCP portion went on the fritz (or just needs to be reset), you will lose connectivity to the router and hence have no control of it or access through it. If you set your PC to a static IP that is in the same range as what it was assigning, you should be able to "see" the router on the network and get back into it.

Is this with just copying discs, or any burn? Are you trying to burn on the fly? And if so, do you have the source drive and burner on the same IDE channel?

NP.

The IIS MMC console can be controlled remotely from the LAN (or across the internet provided all ports are opened--which wouldn't be such a hot idea). Now, as for across the Internet, I use terminal server for such activities. I can control any aspect of my server in this manner.

OK, don't worry about WINS, and I would go to static IPs on the workstations and enable NetBIOS over TCP/IP on them as well. If you really must know more about WINS, check out Technet for more info. Here is a basic description of WINS in Win2K Server: http://www.microsoft.com/technet/treevie...rt2/tcpch07.asp

How many machines are on your network? I tend to set it up whenever I setup a server just out of habit. Most peer-to-peer setups don't require this level of name resolution. If you just make sure that NetBIOS over TCP/IP is setup, you should be fine.

It may not, I am not sure with WinXP. I use DHCP on my WinNT/2K servers to assign DNS and WINS servers, and that also enables NetBIOS over TCP/IP. If you enable it, it will allow for name resolution information to be passed along with the packet info. That way, you can use the familiar "\\MYPC" or whatever, and Network Neighborhood will (tend to) work properly as well.

Do you have NetBIOS over TCP/IP enabled?

Also, here is a tool for those that have been infected, but you should read the "CAUTIONS" section of this page. It points out that there may be other effects of these worms that may not be easily spotted. http://www.microsoft.com/technet/treevie...ools/redfix.asp

Short answer; it affects Pro as well. Long answer: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/ms01-033.asp

Install the patch, then reboot. That should clear it out and keep it from coming back. In addition, if you are infected you are generating a ton of traffic and would be in fact, part of the problem rather than the solution. Also, CRII "installs" a backdoor that allows people to use your server for other tasks, and there are automated tools out there that will scan for these servers that are infected. So, it would be prudent to install the patch and reboot.

They have to "disable" or "enable" passive mode? Generally, you don't want to "enable" passive (PASV) mode on the client because it is a bit slower to authenticate and establish the connection, but it is needed when the client cannot actively negotiate additional ports to transfer data. FTP uses more than just ports 20/21 to function, and that is where the problem lies; the user and/or server may be behind a firewall that is restricting access.

I missed this one, but here's what you need. You will have to add the "load device drivers" right to the power users group if you wish to continue working in this mode. So, at this link: http://support.microsoft.com/support/kb/articles/Q297/7/80.ASP it shows a brief overview of what you are doing (yes, it is in WinXP, but the layout sounds similar). Now, at this link: http://support.microsoft.com/support/kb/articles/Q256/3/45.ASP it shows how to get there if you are using a domain. Basically, just add the device driver right to your power users group, and then reboot. Now, if it doesn't work the first time, you might have to logout/reboot again because some of the policy functions will only show up on the first reboot, and not get applied yet.