clutch

NP.

You might need to simply reclaim ownership, and then reapply your access rights to it. Sometimes a previous permissions assignment can go haywire, and you'll get prompted with something like "the permissions on this object are out of order, please click 'ok' to fix this" or similar.

No, I am right. I have done this on many servers that sit on the perimeter. There is ZERO reason to have NetBIOS enabled on an outside NIC, unless you are using a nested domain (a domain housed inside another domain) where you want to have replication of WINS info between multiple domains. It seems to me that it would be hard to pass judgement on an opinion where you are not familiar with the topic. NetBIOS is simply a core protocol heavily used in MS (SMB as well) systems, and was the foundation for NetBEUI (a very small, very fast broadcast-based protocol). When MS decided to ditch the effort on NetBEUI (I saw this mostly around '97-'98, but probably sooner with their gradual push into DNS and TCP/IP) and go into TCP/IP, they really pushed WINS as a solution for name and resource resolution. NetBIOS handles RPC information, such as using remote consoles for user and system management on remote systems, and should NEVER be left bound to a controller that is not used for this purpose. When you remove the ability for an OS to "listen" for commands, you are closing a potentially large hole. So what I do is just unbind NetBIOS over TCP/IP from the external NIC, and I also remove "File and Printer Sharing" along with "Client for MS Networks" if possible. This will keep the OS from using that NIC for most authentication purposes. Basically, you are stripping that NIC down to core functionality which is equivalent to a *nix/BSD system, and they have been working on networks for years, right?

What folder is it?

The proc issues aren't so much Apple's fault, as Motorolla's. They haven't had a strong desire to push the design envelope, so they don't. Their design has a *very* shallow pipeline, while AMD's is longer and Intel's in longer still. However, Apple's systems started having problems in the performance world back when the P3 450s started showing up and some application vendors (*cough* adobe *cough*) actually put a bit of time and money into designing their apps to run on x86 systems, and not just doing a fairly shoddy "port" of their app. So, I would have to say that "going the Apple way" would have to be moronic at best. AMD just sticks with a shallow pipeline and has a fairly minor investment in chipsets (very bad idea) whereas Intel goes with a longer pipeline, more processing tricks (heavier branch prediction and "Hyper-Threading"), and puts a good deal of cash into chipsets that showcase their CPUs.

Disable NetBIOS over TCP/IP on the offending NIC.

Did you look on the CD that came with the motherboard for drivers for your NIC? My ASUS P4PE CD has drivers for Linux to activate both Broadcom chips that they used with it.

First, a good place to start is here: http://www.linux-on-laptops.com/compaq.html Second, while getting info on my new Dell Inspiron 8200 I thought I saw some info on your laptop in Google searches. You might want to try both sources.

Here is another link that I posted before, and it might be simpler to follow. http://www.iisanswers.com/articles/dns_for_iis.htm But essentially, it sounds like you are close. Just so you know, AD is designed to work with 2 or more DCs, and can be quirky when running solo. Also, as a side note, you can setup a DNS server in Linux or BSD to handle those duties. I haven't done this, but it is feasible from what I have read. Just remember, you want all of the of the internal workstations and servers to point to your internal DNS server for name resolution, and this includes the NIC on the server itself.

Look down a couple of threads for the same topic.

It's obvious to most people only after they have done it. First, you have to understand that any machine that has an outside DNS server's IP setup as a DNS box can contaminate its name resolution. For example, let's say you had yada.yada.local as a real name on the outside world, and as your LAN domain (not gonna happen, but this is just for theory). Now, on a given client you have your internal DNS box as DNS server one, and an outside DNS server box as DNS server two. Now, when the client needs to authenticate, the first thing it's gonna do is try to resolve the current domain that it's in, and find the first available DC to authenticate it. It will try the first DNS server, and hopefully get in contact with it. Now, in a low demand environment where the server is ALWAYS available, the problem would never manifest, but you will see the "rub" soon enough. Now, let's say it's booting up, and the first server isn't available. Well, since it's a fresh boot there will not be any sort of DNS resolver cache to fall back on, so it will hit the DNS boxes. Next, the first is a no-show, so it goes for number two. Number says that yada.yada.local is your *outside* (real) IP, and it will hand that info back to your client. Now, the client will keep hitting the outside IP thinking it has the proper information for your domain, and will keep hitting your outside IP (probably on the other end of a router or NAT system, right?) until it gives up, then moves down the resolution chain. Unfortunately, this is where you see a lot of AD errors and timeouts; simple name resolution. So, what do I do about it you ask? Simple, you setup internal DNS box(es) that handle all name resolution for your clients, and only those clients. The forwarders are there so the DNS server that you setup can get info on other domains besides the one setup locally on it (it doesn't mystically pickup every single domain ever listed unless you try to sync it with a root server, and you *really* don't want that) and can then help clients get to where they are going. Normally, I suggest putting your ISP's DNS servers on there, as they are faster to get to (hop-wise). You can use root hints to bypass the ISP's servers and go straight to the source, but I never bother. This is what I do. I setup the DNS box for my domain, and enter static assignments for my servers and other fixed IPs (printers and such). I also enter WWW, FTP, SMTP, and MX records as needed. Then, I enter all the official DNS boxes on my network into the DNS Servers tab, and then instruct them to only replicate with servers listed on that tab (that way your boxes don't arbitrarily receive traffic from the outside and try to replicate junk data from your non-routable IPs to the outside world). I also enable WINS and WINS-R lookups and point them to my WINS server (yeah, it's supposed to be dead but sometimes you still need it). If you need more info, let me know. But, this should be enough to get you going. You can also do a search here using my name and "DNS" for other explanations on this.

Disabling the pagefile does help speedwise, but Photoshop complains about not having one (at least PS6 did) and some other apps might too. Also, Windows is a little slower about releasing RAM when requested, so while you might "see" that you have extra RAM available, Windows may not agree with you and proclaim that you are out of resources. The best way to know is to use a performance counter and check to see how much swap file usage there is over about a week. Then, you can either resize it or remove it completely. This has worked fine for me with systems of 512MB RAM or more. This behavior with *needing* a pagefile seems limited to Windows and its apps more than anything else, as various Linux distros I have used (RH, Debian, etc) never even bother with it on my systems with 512MB and 1GB of RAM.

Quote: Apparently you can run Dual Athlon XP, so maybe this is an idea rather than Dual Athlon MP. A pair of Athlon XP 2100+ and the Asus A7M266-D board will be cheaper than a P4 2.53 and the Asus P4B533-E board How is the chipset performance between both systems? How is hardware compatibility? What about memory controller performance? Also, does it support any future hardware upgrades you might be looking for (SATA, USB 2.0, etc) out of the box without giving up PCI slots? Has there been any further development for dual AMD cpus? You might find yourself trying to get the most out of 2 fast procs when the mobo can barely keep up with one.

Well, if you don't have NetBIOS installed at all (by default, it is installed and would have to be removed) then just set that to "disabled" there as well. And yes, Windows is indeed "looking" for something, namely an autheticating server/workstation. So, if you're just using a single workstation attached to an Internet connection that hands out IPs via DHCP, then just leave the DNS settings along other than "Disable NetBIOS over TCP/IP."

I'm not sure how I missed this before, but oh well . This is an issue that's been confirmed by MS (at least with an AD tech I spoke to) with regards to ridiculously long logons and network services taking forever to start up on servers. Since your system is configured to be in a workgroup, it is going to *look* for it all over the place, and try to hit as many NetBIOS sources as it can. The MS tech told me to just disconnect the network connection if it ever happened to me (which it hasn't, as I run internal domains and name resolution), so that's a quick patch for you. The only other thing I could think of is to simply disable NetBIOS if you aren't using it and see if that will speed things up. If you have only one box that you are using, then you really shouldn't have NetBIOS bound to your NIC anyway, so just deselect it in your network properties and see what happens.

Have you actually disabled them completely? It could be that it is still running and not reporting it properly. Setting it to manual still allows the service to be launched.

I don't have a guide for you, but installation isn't that hard. However, I can tell you that vmware is going to have a bit of a performance hit in both OSs. I used RH and Gentoo on my WinXP box at work (dual Xeon 2.0GHz with a gig of RDRAM) and you can definately feel the hit in speed. So if you just want to get familiar with the OS or run simple things (like small compilers, office apps, etc) in the guest OS then go for. But, I wouldn't suggest running high-demand applications in the guest OS and then make a judgement as to its performance afterward. Mostly, you just use it for evaluating simple compatibility.

If it was me, I would get an ASUS P4PE with the 3.06GHz P4, this way I would have hyper-threading to behave like a dual cpu box. That way you get high performance, stability, and compatibility.

Debian is awesome, but if you have a bit of change to fork out, go for Xandros: www.xandros.com It's based on Debian woody, and has all of Debian's strong points but it easier to manage, has a patched/updated kernel, and a better hardware detection and installation routine. It also looks somewhat similar to a Windows 2000 install, but is all Linux. It also comes with Codeweavers Office and CrossOver plugin to support some Windows-only apps and utilities.

Kinda sorta. It appears that you only need SR1 to make the jump to SP3. http://office.microsoft.com/downloads/2000/o2ksp3.aspx

The disks are a little bit different, so I think the installs would be too. I have tried using our volume key with retail disks, and it didn't work (and vice versa). So I would think that the installations might have a file or two that are different as well and would prohibit that kind of key swap.

Well, while never being a big fan of Tom's Hardware (I used to be a long time ago), this review does show a fair amount of data with respect to enabling HT: http://www.tomshardware.com/cpu/02q4/021114/index.html This does behave a lot like a normal dual-cpu system. I think something like this will payoff for the majority of users in this forum as we tend to run *many* applications at the same time. BTW, the video clip is worth watching if you have broadband to get it.

Hey, it happened once to a coworker a long time ago. He would get on, and the other guy would get bounced off, and vice-versa. Finally, the ISP checked out the logs and put it together. Now, there is a major longshot of it happening, but yes it can and has happened. There are several components of the address that let it get created, but that shouldn't affect the performance of it (I have a soyo mb that lets you reflash the onboard NIC to whatever MAC you want, which is handy for some apps that are licensed against MAC addresses). So yeah, knock yourself out, but I would suggest using something less obvious as all "0"s since either RR might have that blocked (thinking it could be an error) or someone else might be using it.

Um, format? Outside of that, it's going to be a pain. I know that modified versions of IE can sometimes leave parts behind and make upgrades fussy. I wouldn't know of any "clean" ways to remove AOL from a box other than formatting.

Since I just got Xandros (very nice setup, by the way), I thought I would pass this along to other current and future Xandros users. It turns out that there is a fairly simple way to get new fonts to work in it. Here's the link to the Xandros forums, and at the bottom is a post from one of their techs on how to do it. This is the first time that I have seen a font install where it takes place system wide, and immediately. The fonts come up in Mozilla, OpenOffice.org, etc. http://forums.xandros.com/viewtopic.php?...4b3511c8b9a23eb