clutch

I can't remember where I saw this, but I bookmarked it. Basically you are just unregistering that functionality. http://www.annoyances.org/exec/show/article03-202 HTH

Is the website being hosted on a member server, or a domain controller? Also, is the site configured to resolve accounts to a specific default domain (as a DC would)? Normally, for DCs, altering the "Default Domain Controller" policy is enough; simply add the user group that you want to have access to the secured portions of the site to the "Log on Locally" part of the policy is enough. Anybody have any other ideas?

When you say "see the server", do you mean that you just do not see it listed in Network Neighborhood, or that you can't ping it either? Is NetBIOS over TCP/IP enabled in the TCP/IP properties of the WinXP clients? Are you using DHCP or a static addressing scheme? Lastly, are you using WINS or DNS as a name resolution scheme on your network? Just making sure that NetBIOS over TCP/IP is enabled will usually fix this issue.

A friend showed me this nifty little product for logging IP traffic through his Linksys 4-Port Cable/DSL Gateway, but since I don't use my Linksys router anymore (I use ISA Server), I didn't have a need for it. I did check it out, and it seems pretty cool so I thought I would forward the link on to you guys... http://www.linklogger.com/ It's pretty cheap, and has some nice little reporting features to it.

Well, I would imagine that they are too different from each other to really be compared. For instance, I am not aware of the Sniffer Pro application being functional on the built-in switch of the Linksys unit, nor would it be particularly suited to viewing reports by date, protocol, IP, and the like. Also, you wouldn't run Sniffer Pro at startup, nor would you want to run it as a service. Also, since Sniffer Pro costs SO much (probably $5,000-$10,000 for that client range). I am under the impression that this software works by using the logging funciton of the router, but actually keeps all the data rather than being capped at a limited amount of traffic (hence the need for the DB).

Sounds like a group policy issue. Has someone setup a domain policy for your network? That person might have locked MSN messenger down. You can also create a domain policy MSC by opening a new MMC, and adding the Group Policy snap-in. When doing so, use the "Default Domain" policy (or your custom one if you see it listed or know its name) so you can see if it's being locked. If you don't know how to get to the messenger portion, check out the post by APK here: http://www.ntcompatible.com/vb/showthread.php?threadid=18303&highlight=messenger HTH

Did you try pinging the XP box? How about pinging from the XP box?

I haven't had any issues, and I am not aware of any that would draw the comment of it "badly" needing a service pack. Then again, every OS gets such comments in its first release whether or not they are deserved.

933@1085 (155MHz FSB). Idles at 28*C, full load at 41*C. Super stable, quite cool. Also note that I have been running it on my Celeron with no issues (300a@450).

Actually, the limitation should only extend to DOS and Win 3.1 (can't remember anyone pushing that share name limit using "net share") and not affect Win9x/NT 3.x or above. Now I don't know a damn thing about C coding, but one thing you might try when referencing long filenames or files/directories with spaces in their names is using quotes around the path, such as: "C:\Program Files\My Program\progfile.exe" This way, the entire string will be referenced rather than being broken at "C:\Program" and the rest being considered an argument. I can't remember the problems that you have ever showing up for me when using Win9X in any Windows network, be it Win9X peer-to-peer, NT Domain, or Win2K AD. What version of Novell were you running, v3.12? I thought that was the oldest one which was "Y2K Compliant" (haven't heard that in a while, eh?). One more thing, there was a bogus "virus" scare going around telling people to delete a specific file if found on their Win9x systems, but the file enabled use on long file names. I don't suppose you would know if anybody fell for that hoax, do you?

I like the start menu myself, along with being able to right click on items in it and getting their alternate menus rather than simple shortcut properties. Plus, I have found the OS to be faster overall on faster systems; it just seems to scale better than Win2K to me. Sand had a ton of problems, while I didn't but we have very similar hardware configurations. Plus, I have WinXP Pro installed on a Celeron 300a@450 with 640MB RAM and it *does* run faster in every way than it did with Win2K. But if you have a ton of issues and it can be traced to the OS, then there is no reason to continue running it when you have another waiting in the wings to go back to (especially one as nice as Win2K).

Atreyu switched back to Win2K, but I haven't had a reason to (he has had numerous crashes while I have not). Besides, I have been to busy working with ISA server to even be concerned with my desktop OS. Especially since I had to redo my AD because of its bizarre concept of containerization, but that's another story...

Why did you name your PC "Corona-12" anyway?

I posted here about a utility for logging IP traffic from Linksys and ZyXEL products. If you have either, you might want to check it out.

Well, you may not be out of the woods just yet. Be on the lookout for odd behavior or anything not quite normal (data corruption, spotty performance, etc). I normally watch the system for a few days *very* closely after any BIOS flash just to make sure. Also, I am typing this on Smirnoff Ice-4, but after 12 I probably wouldn't even care if the computer was plugged into a wall anymore let alone beeped...

I just wish I could get Athlon performance in a system with Intel's stability. Is that too much to ask?

OK, now for the easy answer. Log into your Linksys router (default IP is 192.168.1.1 if I remember correctly) and go to "Advanced". You should see a tab for "Forwarding", and using that tab enter your workstation's IP (it needs to be static so this will work) and "5190" for the port. Click "apply" and you should be set, but if not you might have to restart the modem by unplugging it and plugging it back in again (power cycling). The whole problem that you are seeing is that the traffic is not being permitted to route IN to your workstation (or the unit is just not aware of where to send it), whereas you are able to send because default NAT/PAT configurations on low-end units allow for all access to outgoing traffic. Let me know if you are having any issues.

I had something similar happen with a video card once, and I just reseated it and the problem went away. Other than that, I don't know what to tell ya.

You seem to have indicated that Win98 does work, but did you check all the internal connections and make sure that the CPU fan is still operational? Maybe something was loose and that little move finally made it act up. Just going for the simple stuff first.

If I were giving the award, it wouldn't be to any of the above . But the only reason they held back was due to their existing contracts which I know they will still be suffering the effects of for some time to come.

I am not sure I follow, since you are stating that the video cards are "worthy" because they are trying to better themselves. Well, ATI has to, because they have routinely screwed up every hardware release for the last few years with bad drivers. So, they NEED this to work, and they are doing everything possible (like the Quake.exe vs. Quack.exe from HardOCP, where they found that the ATI drivers were looking for the Quake.exe to run) to look good in the public eye. As for NVidia, they merely released a card that uses DX8 features and a few more enhancements. They have set a release schedule of about every 6 months with a new version in the fall and a spring "refresher" (usually clocked higher) in the following year. The i845d "betters" the view of recent motherboard releases from Intel that can use cheaper memory. Not only that, but it uses several other new features that are out (as previously mentioned) that the other vendors haven't done much with yet. The main reason why this board has been stalled so long is because of that stupid agreement with RAMBUS that essentially killed the performance of low to mid level workstations. So yes, I would say that Intel brought as much that's "new" to the table as either of the video card companies did since they are enabling the use of new technology (much like the video cards enable DX8). When you are in the "tech" (or any field, really) business, people expect you to do better, and that's fine. But I say you reserve awards for things that are new or a major improvement over previous revisions or anything else that's available.

Well, you made a good point, so I have to support that. Rock on.

I have to agree with M4Carbine on this, since the GF3 only brings a few new features (something about some strange new alchemy named "pixel shaders" ) and ATI is just now starting to enable the features with new driver releases that were promised before the cards were released. Also, why limit yourself to CPU/Mobo/Video Card when you could designate USB 2.0, OSX, Windows XP, Blade Server Technology, iPod (Apple's MP3 gizmo, it's pretty damn cool), etc? It just seems like there's a lot more deserving techno-geek toys that would be more deserving of such an accolade from anybody.

Try using any of the ATI cards from the last few years and you will find that "stability" is something to be desired when using anything 3D related (which they claim to support numerous times). For 2D, they are fine, but you might as well get Matrox and have both stability *and* performance. The only issues that I have seen with NVidia cards have been from: A. CosmosWorks cannot establish a mesh using any of the 21.xx and up drivers, but that's a limitation of the program, and... B. The infinite loop and crashing issues that seem to only affect Via chipset owners (surprise). I would have thought that the Athlon processors would be the product of the year, or that zippy MP3 player from Apple. But then again, those products are only as good as the platforms they run on, right?