clutch

The box (better than "rig" ) in your sig looks like it would be better, so I am getting the impression that you are hogging up all the high-end hardware from your area. Are you trying to build a supercomputer out there?

Have you looked in the device manager and selected "show hidden devices"? Also, do you have any firewall software installed on the machine?

I have owned 4 myself (P2L97, 2 P3B-Fs, and a CUSL2), and worked with many more at offices/customer sites with no problems from any of them. I tend to buy them whenever possible since they have been so reliable.

Wow, good thing you bumped it again... I have the same router, and all I have are LAN connections on my XP (2K, NT, etc) clients. If you have one NIC and no ICS, then I wouldn't see why you would have that.

I write stuff in it, so that was the simplest explanation I could come up with that would cover most bases without getting too involved.

ASP (Active Server Pages) is a script-based code that is a lightweight version of Visual Basic Scripting (VBS), and is commonly combined with ActiveX Data Objects (ADO) to make pages dynamic and connect to datasources. This type of page was release by MS to make dynamic page writing easier to do and to help remove the need for CGI scripting and/or dll compiling. The current version is ASP.NET (.asax and .aspx) and it allows for the use of both VB.NET and C# at the moment, and can allow for other languages as well provided that they can speak to the .NET Framework.

That sounds about right. It could be that you have one particular config that it isn't prepared for (such as requesting a var that doesn't exist or is contradicting one that already does). However, ASP code is handled server-side, so I wouldn't worry about it.

Quote: I would agree, disabling the page file on this box does three things: 1) Lowers framerate in games I haven't seen any loss, and everything has been cherry (not to mention all apps that have been cached launch even faster). Quote: 2) Increases heat produced by cpu and drives {always a BAD thing} Again, I haven't seen this, nor would I see how this could be the case. Also, on my main box it's a 1.6GHz Northwood running at 2.4GHz (150x4 FSB), so I think I would *definately* see a weakness in this case. Where have you seen this at? Quote: 3) Doesn't allow some programs that need it to work properly because of design {photoshop, but this can be adjusted IN ps, not really an issue w/this particular program} I haven't checked as of yet, but I will be fiddling with that when I get home tonight.

That's a problem with their page, or more specifically line 318 on "thread.asp".

What machine is 192.168.1.1 on your LAN? That's "normally" reserved for a router/NAT device, and that entry would indicate that the request was coming from that device. Now, it is possible that a workstation can be infected since many workstations have IIS installed by default (sometimes referred to as "Peer Web Services") and can be infected in the same manner as a regular server. Also, the workstation can be infected by an email carrying the worm, making said workstation into a drone that will scan for servers in the same manner as the IIS boxes, while also forwarding the worm to other addresses in the address book. This behavior was done in CRII, which was also designed to attack local subnets thus making it infect machines faster since many poorly administrated machines tend to be on the same subnet (such as broadband networks like cable and DSL). The three options that I could think of for that entry on the info I currently have are: 1. It's a GET statement from a HTML editor (or some webfolder) at that IP that was trying to access a document. 2. That IP was forwarding an illegal request (it's a router, ICS/RRAS server, etc) and IIS perceived it as a request from that local IP. 3. That's a local machine on your network that is infected, and is actively scanning your local subnet for vulnerable hosts. You might want to investigate this a bit further, and make sure that you have the newest anti-virus definitions on all the systems.

From what I have learned and read of the pagefile and its usage by a Windows OS, it's beneficial to get rid of it when you can. Unfortunately, MS doesn't have much in the way of documentation on it since the days of NT4, and they seem interested in giving the users the option to can the pagefile since XP can now be set to "disable pagefile". I don't care about memory dumps on my workstations and my main station at home currently has 1GB of RAM on it, so I have been running without it just fine. However, last night I went to launch Photoshop and surprise!, I can't get it to launch since it perceives the lack of virtual memory as an incredibly low amount of virtual memory freespace. I have heard of this issue, but never actually encountered it so I don't know if there is a fix for it yet. If I have to keep that stupid thing around *just* for PS6, then I will probably hold to my old rule for pagefiles and set the min and max to be equal to each other, and the total amount equal to 150% of the system RAM to a max of 250MB (which in this case would be 250MB).

Also, here is a list of general HTTP reply codes that I found today: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q173971

The "default.ida" (ida/idq in general) is a file that's used for querying against Index Server, which is the built-in search/scavenging engine for IIS. As for the "200" reply, I am not sure if it means that it just found the file, or if it not only found the file but successfully initiated the overflow. On the first pass of Code Red, all you had to do was reboot the server and the worm would be gone (of course another attack would re-infect it, so your best bet was to disconnect the server, reboot, and then patch the server before you could reconnect it again). However with CRII that changed; the worm could now bring in payload and leave a back door open on the box. So, I don't have any idea what may have happened to your box, but it *is* possible it might have been compromised. Check out Technet and do a search on the removal of Code Red as MS released a tool to help with this process. Also, for future reference here is a list of HTTP reply codes: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q173971

First, make sure that you have "File and Print Sharing" installed and properly configured on the workstations that you want seen on the network. Next, make sure that NetBIOS over TCP/IP is enabled on all of the workstations (not just "Get this option from DHCP settings"). Now, if this doesn't work, then here's something else you can try that's a lot more dependable than Network Neighborhood (without WINS/DDNS, it's very unstable). Depending on whether or not you have missed a refresh cycle, the browse service can actually take up to 55 minutes (and not 15) to pick up a new machine. Now, something you could do is just go to the "LMHOSTS.SAM" file (%windir%\system32\drivers\etc) and edit it following the examples. Just add the workstation names and their respective IPs, and afterward remove the ".SAM" extension. Then, just copy that file to the other workstations and they should now be certain of what name goes to what IP, and not have to go through such a long name resolution loop to get to the proper resource.

Quote: Yes i agree it should only be tcp/ip until you can solve my problem, it's both protos What problem is that?

I am a little familiar with the MS KB problem, since I had the same issue with this SOYO mobo (Via USB controller, go figure...). For some reason, I thought they had a NEC unit on there, but they don't. One thing that might help you though; I called SOYO support and the tech told me that there was a KB article on this exact issue with Windows XP and it not picking up certain devices. For some reason though, it was always my KB. My Intellimouse Explorer and SanDisk reader would work fine, but the KB would have a 1-in-5 chance of not being picked up at boot time. The suggestion was to just plug in both the PS/2 and USB connectors (mine has a built-in "Y" at the end of the cable with both connectors). Since then, I have not had one issue with any USB device, and I can use all the extended functionality of my KB (the media player and browser keys) along with the built-in USB hub of the KB. But, this is the only system that has had this issue, and all my other (Intel based) systems have been fine. Gotcha on Web View now; I miss that as well since I would easily get my drive stats on the left-hand pane. However I have been a pretty big fan of the newer interface where you can collapse and expand the info you are interested in, so it kinda washed out for me. The nForce will kick a$$ once it's a bit more mature.

Quote: I do agree NetBEUI is old and not good for larger networks, but you can avoid the collisions by using a SWITCH. We tested throughput between the 2 protos and NetBEUI was faster. Well, there are many SWITCHES that aren't OPTIMIZED for use with NetBEUI, especially ones in the price segment that a small office would use (plus many small networks still use HUBS anyway). So, why not stop using the "Band-Aid" of Windows-compatible protocols and just use a current one that all the OSs are supporting? It's bad enough to still be on a network that needs NetBIOS for something, but you can at least let that ride on the back of TCP/IP rather than install ANOTHER protocol that MS wants as dead as everybody else has. They have gone out of their way to make a little bit harder to install on their newest OS, and I would imagine that canning it altogether in their next release is a completely reasonable prediction. At some point, you will HAVE to move forward in protocols since almost nothing supports NetBEUI or IPX/SPX (NWLink) anyway. Print servers, WAPs, managed SWITCHES and HUBS, etc. all have support for TCP/IP, but none come screaming to mind that support NetBEUI. And if you have one of these gizmos (or Heaven forbid you want to get ONLINE to the Internet) you will now have 2 protocols to babysit; NetBEUI and TCP/IP. All-in-all, not such a hot choice. Now, as I asked earlier, what OSs were you testing in throughput? Was it Win2K/XP or 9X-based OSs? The more modern ones have vastly improved performance in TCP/IP, and I am not inclined to believe that NetBEUI is that much faster (if at all) than these newer implementations. What did your test entail? Was it simply copying files over, or were there many networked applications running in the background while you were checking network/CPU utilization? Was it a single large file and/or many small files? What were the results?

Quote: hey clutch, i use netbeui in a production environment and it works A LOT faster than TCP/IP does, especially when you have machines that are on different IP ranges, so don't bag on an old protocol that still out performs TCP/IP on smaller LANs (not WANs) NetBEUI used to be the protocol of choice for smaller networks because of its lower overhead and faster throughput. However, have you taken a good look at the collisions on an average network using it? How about the broadcast storms? Also, when comparing the protocols, are you comparing the two on the same OS (such as Win2K) or is this a mixed environment (such as Win95, 98, NT4, 2K)? If you are using older Win9X boxes, then those are the ones that will see the performance benefit (unless the aforementioned issues catch up depending on the network size as NetBEUI does not scale well), but if you are using a modern network that relies on network-installed and client/server applications, then you will not see a performance benefit and in reality be hurting the performance of the network. @wessss, Did you try calling MS Support and just getting the proper fix for the clients? They are pretty easy to deal with; all you have to do is tell them the Q number along with what the issues were that brought you to that conclusion, and they will email the fix to you (or a link to get it). You don't have to pay for it either, so it would definately be worth your time to check it out. Point to this article as it is the one that supercedes your earlier Q number. Also, while your clients may be pointing to your WINS server's IP, are your servers doing the same? They will need to (including the WINS box itself) so the WINS db will properly cache all the IPs and machine roles to each machine name on the network. Now, if either of those don't work for you and you still have NetBEUI installed, then make sure you have NetBEUI higher up in the binding order than TCP/IP for your NICs. If not, your systems will have to wait for your TCP/IP stack to timeout on its session(s) before moving its way to NetBEUI.

If you scroll down on this link, you should find what you are looking for: http://www.microsoft.com/technet/treevie...ity/iis4err.asp

Go to /. and claim you are hosting it on a 486. That should bring in some hits...

What ryoko is referring to is being in "Corporate/Workgroup" (as in connected to an Exchange or Lotus Notes server) or "POP" (traditional SMTP/POP mail) mode. In either case, Outlook 2K/XP will still want to use the news reader within OE since it doesn't have one of its own.

Outlook uses the OE newsreader. Go to "View>Go To>News" and you can configure it there.

Give this a shot: http://www.4guysfromrolla.com/ASPScripts/PrintFAQ.asp?FAQID=35 If you are about to try ASP.NET, the System.DateTime namespace gives you a ton more options to play with the formatting if you like.

Quote: Windows XP sucks IMHO because: *Infinite loop crashes which still haven't been fixed (Via/nvidia issue but it doesn't happen under Win2k). [/b] Actually, it seems that some have had this same issue under Win2K as well: http://www.viaarena.com/?PageID=64 Also, I did get this error once with my GeForce2 Pro on my SOYO P4S Dragon Ultra (SiS 645 Chipset) using the 23.12 drivers from the MS site. As long as I have avoided those, I seem to be fine. Never got it on an Intel chipset regardless of OS, CPU/Chipset combo, video card, or workload. Quote: *USB devices randomly being dropped (probably a Via issue but it doesn't happen under Win2k) I've got a few USB gizmos on several WinXP machines, and I haven't seen this one either. That's not to say that it doesn't happen, but I haven't heard of it either. What kind of gizmos are dropping off? Is it possible that the drivers or devices themselves aren't up to snuff? Quote: *Web view removed - okay, many people don't like it but I do and it annoys me that MS didn't give us the choice I'm lost on this one as well; please tell me what you mean by "Web View". Quote: *Explorer randomly locking media files - happens with mp3, avi, anything really, only way to delete/rename/move the files that get locked is to kill explorer and use the command window. To be fair, I have seen this one. But occasionally, I saw it in Win2K as well. It appears like whatever process you had using that file seems to hang around and keeps a lock on the file. But, when you look for the process that *would* do this, there isn't one to be found. I tend to see this more on files that I have expanded using the built-in ZIP decompressor. Quote: *Simple File Sharing and other stupid things enabled by default - okay these can be disabled, but many people don't know where the options to disable them are and so get confused (eg. a win98 user migrates to winXP and can't figure out how to password protect shares - with simple file sharing you just can't). I think the idea was to make it easier for the average Win9X user (or newbie admin rolling this out in a workgroup) to setup on a network. I dig WinXP as it is *much* easier to administer on a LAN with it's increased GP options and Terminal Services. However, it's a pig when running on slower boxes (you know the ones; the ones that you would throw out the window if you could...) but still stable. Oh, and Via sucks...

You don't have to bud. This link should take you to the hi-res version: http://starwars.apple.com/ep2/clone_war/media/gate/ep2_clone_war_p640.mov