clutch

They gave up on competing with performance a long time ago and decided to make them more visually appealing. While this one looks nice, it costs too much for what it really has to offer. But hey, it sure does look swell... ;(

Are all 3 machines on the same subnet when getting their IPs? Also, do you have NetBIOS over TCP/IP enabled on all 3 machines? Have you tried simple connecting to another client using \\IP\share to see how fast you could transfer a file? If you have answered "Yes" to all of those questions, and you are using 3 DHCP assigned IPs on that switch, then you are pretty much stuck with having all the name resolution handled via your cable modem. You could: A. Use NetBEUI, or B. Get a Linksys Router, save some money and only get 1 IP from RR, and that way you can use static IPs on your LAN.

Are you using IISLockDown v2? That's the one that installs URLScan, and hence the blocking ability. It actually works extremely well and reduces server overhead while processing annoying attacks like the ones from CodeRed/Nimda infections. Instead of handling the URL and resolving it as unavailable, the filter just drops the request and sends back a "404" while logging it. Check to see if that directory exists, and make sure that you can view all hidden and system files as well.

That is pretty cool, tnx for the link.

Quote: IIS Lock Down for nimdA fix (IISLockD.exe) Yep, that can do it if you just setup the defaults. You will have this entry in your "urlscan.ini" file located at %windir%\system32\inetsrv\urlscan: Code: [AllowExtensions];; Extensions listed here are commonly used on a typical IIS server.;; Note that these entries are effective if "UseAllowExtensions=1"; is set in the [Options] section above.;.asp.htm.html.txt.jpg.jpeg.gif.css Make sure that the "Allow Extensions" option is enabled, and that ".ASP" is listed. You can also confirm that ASP files are being blocked by checking out the URLScan Log file located in that same directory. Once you amend the ini file to allow for ASP extensions, restart your IISAdmin service (which will restart several other services, depending on your configuration) and the new ini file will be loaded.

Call MS, and they will help you out. If you have the pimpy disk, I am sure they will give you a new key.

ASP is run by an integrated compiler on the server itself, so there shouldn't be a need to turn it "on". However, there are a couple of settings in the IIS control panel that allow for script execution (defualts should be fine though). So, to repeat what was asked, what are your errors?

When you setup your new OS, did you have all of your workstations join your new domain/workgroup, or just try to recreate the accounts manually on the server? NT works on the principle of SIDs (Security IDs-which is why you can rename an account and still keep all of the permissions that were assigned to it), and these IDs are unique to the installation. You could install Win2K on a server, give it a domain name, and then create a user and wind up with SID "A". However, if you repeat the exact same process (domain and all) on another server, you would more than likely NOT get the same SID. Since you went from NT4 to Win2K, I can guarantee that they wouldn't wind up with the same SIDs, and the machine accounts would no longer match. So, what to do. Well, you can try to reset the account and see if they'll sync the new SID and generate a new password, or just have the machine join another generic workgroup and then delete the account (recommended). Afterward, let the machine rejoin the domain. NT-based systems are much more strict about using SIDs than 9X OSs, which is why many administrative functions are no longer permitted from 9X boxes.

Also, since you won't know for certain if a new fix replaces an older one (or one is no longer needed, like the P3 patch that was up initially and then removed), it will also "chain" the fixes for you so you only have to reboot once. While I am not a fan of having to download a ton of fixes either since I adminster a few networks, it is still nice to have a customized patching process that will only give the machine what it needs and still allows you to select what you do and do not install. As for the Java plugin, you can get the one from MS or get the one from Sun that is more compliant with universal Java apps/applets. I had to get it for my Compaq Remote Insight board in my new server, and it works rather well. http://java.sun.com/getjava/download.html

Looks cool, and seems quite functional. I also like the fairly simple layout of it. If you want to get even heavier into it, check into "Digital Dashboard" development at http://msdn.microsoft.com. You know the "Outlook Today" homepage? Well, that's a fairly simple version of what you can do with it.

My avg backup runs 40GB at work, and I don't have any problems restoring from tape. There used to be major issues with tape quite a while ago, but for the most part they are pretty reliable depending on the format. I use a 21 tape rotation as follows: M-Th: 4 tapes Fridays: 5 tapes Last weekday of the month: 12 tapes And then we rotate out a spare for the annual backup which isn't in the normal rotation, but is archived much longer. Now, keeping 21 harddrives and restoring from them would be quite expensive and a *real* pain in the a$$...

Doing that will degrade and eventually destroy your client's ability to resolve AD resources. I would suggest reading through the documentation on setting up DNS, and then starting over. It isn't hard, but you need to understand the concept before you jump into it again.

This is in your online documentation that comes with Win2K server, but in case you haven't looked there yet: http://www.microsoft.com/windows2000/en/...ode.htm?id=1848

Setup your internal DNS servers to use "forwarders", and have those forwarders set to your old outside (ISP) DNS server IPs.

Well, if you check out the site it seems to favor satirical overtones in articles, so I would say that it was a joke.

OK, I did receive a nicely done email about this from the topic author, but (as CUViper correctly pointed out) this is based entirely on getting around a license limitation on the demo version of the product: Quote: Used the trial version of WinWasher once or twice over the 30-day trial period. Appears to be a nice program. Didn't use it enough, however, to determine if I wanted to spend for the complete package, so I tried to uninstall then reinstalled the demo. In short, the Install Wizard said, "Your 30 days are up!" Now, I would imagine that it is a problem with a registry key or some vague file somewhere, but the premise is to override an existing protection scheme that blocks what you have done already, and what you are trying to do again. Please don't continue in this manner on this forum.

Check your mail, and we'll see if we can get this running properly.

OK, I am under the impression that you haven't administered NT based OSs for long, is that correct? If so, first GET ALL OF THE SECURITY UPDATES IMMEDIATELY! Also, it sounds like you have WAY too much hardware for the simple things you are trying to accomplish, but it should work. Now, how many clients are going to connect to this server, and will you be using NT/2K DHCP (or at least a DHCP system that will provide a WINS IP and broadcast format) for them to get their config settings? The naming convention that you are using for your sites mandates a need to use a NetBIOS name resolver, and WINS is generally the easiest and most stable. If, however, you can get away from that and use http://shella1.mydomain.com and http://shella2.mydomain.com for your websites, then what you want to do is enter "A" records on the LAN DNS hosting box that will point those names to the main (or virtual) IP of the webserver, so when someone enters one of those names in his/her browser, it will pass that name info to the DNS box, get the IP, and then have the request go to the server (at this point it will hit the server and be handled as a Host Header name). Also, make sure that you have the corresponding (sub)domain name bound to its appropriate site. To setup WINS, all you have to do is add it as a networking component in the "Add/Remove Windows Components" portion of the Add/Remove Programs applet. Once you have that installed, you can create static mappings (similar to DNS) for shella1 and shella2. Then, you setup the client to use that server as the WINS server for the network and it will find shella1 and shella2 just fine when it is entered into the browser.

OK, lots of stuff here, so let's just concentrate on getting you familiar with the 3 methods of hosting multiple WWW and FTP sites (some of which covered by CUViper already): Different IP Address: If multiple IPs are assigned to a given server (AND can be reached by pinging them), you can use a different IP for each site. If you plan on using different names for each site as well, this can be done by using Host Header Names (explained in a bit) or mapping the name in your chosen name resolution method (using WINS, bind http://intranet1 to 192.168.1.100, bind http://intranet2 to 192.168.1.101, etc.) so that the name used by the requesting client gets translated to the proper IP, and sent to the handling server. Different Port: You can host multiple sites on the same IP using multiple ports, such as 80, 81, 8080, etc. without the need to bind multiple IPs or use Host Header names. Host Header Names: This is generally my chosen method, as it doesn't require the use of mapping ports or binding extra IPs to a given server. This method *can* have some side-effects using older, non-IE versions of web browsers. Basically, you map the site name (such as "intranet1" or "www.intranet.com") to a site, and when the request comes into IIS, it will read the host header and respond to the client with pages from that particular site. This method will REQUIRE that you map whatever the name is (such as "shella") using WINS/LMHOSTS to the IP of that server (192.168.0.30) so that clients that request http://shella will know where to go. If you don't, you will only be able to get to the *server* (not site) using the IP, but you will NOT get the site since the host header of "shella" wasn't in your address request. So now, it sounds like you don't have any name resolution scheme that is binding the intranet site names to specific IPs, so you should do that first. Also, I would recommend not using all those NICs (like CUViper was hinting to) because you can have some "interesting" behavior show up if you aren't used to that type of configuration. How to make "Shella" show up as a site on a server using host headers: 1. If "Shella" is not the name of the server, then bind that name to the IP of the hosting interface using either a WINS server or the LMHOSTS file on the client. Make sure that the client can now ping that name and get the right IP. If not, since it is a NetBIOS name, use nbtstat -R (capital R) from the command line to flush and renew the NetBIOS name resolution cache table (if using a DNS name, like intranet.mydomain.com, use ipconfig /flushdns to perform the equivalent function) and then try again. Also, when using the LMHOSTS file for the first time, it will have a ".SAM" extension on it, just remove the extension so the file will become active to the client OS (I hate LMHOSTS files in general, so I use WINS whenever possible ). 2. On the site that is to respond to "Shella", enter that name in the Host Header properties, and save it. 3. Try connecting to the site now, as it should work. If you have any other questions, let me know. I have use all three setups many times, so I am fairly sure we can get a combo that works for you.

I wrote the following response to a gentleman claiming that Linux was so stable because you could easily modify what the OS would load by recompiling the kernel: Quote: quote: -------------------------------------------------------------------------------- Originally posted by jfrayzier Yes... and I recently started using Linux myself. You must also know that it is not as easy to configure as Windows. Most everything you do will no doubt require you to recompile the kernel to implement your changes. However, that is what makes Linux so stable. People can write their own code into the kernel to make it work exactly as they want it to. i.e. if you use it on a machine without a soundcard (like me... how many webservers need a sound card??) you can take out everything in the operating system that has to do with sound and recompile it. lower the overhead. -------------------------------------------------------------------------------- No, that is not what "makes" Linux-based OSs so stable. While the ability to streamline code can contribute to stability by removing things that YOU perceive as not needed, that is by far not the reason it is getting this wonderful reputation for speed and stability. So, why is it getting this reputation? First, the average admin of a Linux box is far better at administering his system than the average NT admin. This person has gone through a LOT of effort to learn the OS (many of which were from the command line days) and some of them are also Unix admins with classic training as opposed to downloading a ***** copy of NT and learning on your own. When I first starting fiddling around with Redhat 5.1 to see what was so special, I got *acquainted* with the term "kernel panic" as I kept crashing it out. Also, when all I wanted to do was to get a Redhat 6.0 system to be seen on my MS network, it took me a few days to get SAMBA up and running and some more tuning for stability (I am sure it is much more stable now, not to mention that I would be able to set it up much faster as well). Most MS admins are undertrained, as you will usually the "computer guy" in a small office winds up working with the server because he happens to know how to change the ink in the printer. If MS kept administration as complicated as *nix or Novell (), then you would see a lot less people playing admin on NT systems. The second reason is the great lack of applications that can be installed locally on a server. There are very, very, very few applications that should EVER be installed locally to a server. These are usually databases and collaboration based packages (like MS SQL and Exchange), however I have seen people install things like PC Anywhere (which had that lovely little side effect of crashing out Win2K systems with 9.0 and some 9.1 releases that claimed to be Win2K compliant) and desktop applications like Office* so that it can be used as a workstation. When someone sets up a Linux box to host an Oracle DB, chances are that person isn't going to throw on Word or something else onto that system because that box is now pretty much function specific. So, combine an improperly trained admin with having the ability to install just about anything on a server (not to mention that many programs that were written poorly to begin with can STILL be installed on a server because of backward compatibility) and it's amazing that half the servers run at all. I am not saying that all of the problems NT-based servers have encountered are merely through poor administration, but the majority are. There's a reason why you see high-end applications and hardware that have "Yes:Netware" logos on them for Novell approval, or why there's a lot less hardware out there for Sun (non x86) boxes; those companies want to keep the low-end hardware/software off of those systems. Why introduce more variables to the situation? Why beg for problems? They control what goes into the boxes as much as possible through certifications and marketing, and then stand back and laugh while some joker has 4 realtek NICs shoved into the new MS Small Business Server that he "built" out of an old PC with a couple of new hard drives, trying to get ISA to host his ftp site from work, and all the while getting hardware issues and all kinds of other problems. But that's OK, MS *should* have seen this coming and made ANOTHER wizard for this problem, right? *Outlook does have to be installed for use by MS SQL 2000 so it can generate emails to admins, plus using proper transforms you can install Office 2K/XP on a Win2K server running Terminal Server in Application hosting mode so that thin clients may use it. However, the comment I made is more reflective of low-level admins just using it as a workstation and in effect inviting problems to occur on these servers. If they are using the servers to check their email (viruses/worms) and word docs (worms), it would be logical to say these same people are browsing the web (more viruses and worms) and begging for more instability. That's my response, and now I am interested in hearing yours.

That's weird, as I haven't had any issues with changing ports and using a Linksys router. I have another site on port 90, and it worked fine with my Linksys unit and works fine now using ISA server. In the past I was also able to host FTP sites on alternate ports, so I don't know why that would be an issue for anybody (however Atreyu has, but he has all kinds of problems anyway...).

Empty your temp files (just use disk cleanup as it's easier), as there appears to be a bug between extracting files for an install and either having a large amount of temp files or *maybe* trying to overwrite similar install files.

Since you are looking to introduce Active Directory, simply use "dcpromo" and go through the wizard. If you do not have internal (internal, not external as in using the ISP) DNS setup then it will prompt you to create a DNS zone as well. I would recommend scouting around Technet for some articles on Active Directory first so you can get an idea as to what is going to happen, as well as checking out how Win9x workstations fit into the bill.

Well, I wouldn't proclaim that "it's here!" just yet. Unless you believe that "Duke Nukem:Forever" and *any* 3D chipset from the BitBoys are here as well...

Well, that, and *maybe* because it's a bit of a hog and might be too unstable for a server OS. Not to mention there is no reason for a server to have theme-based interfaces anyway.