clutch

Unfortunately, Philipp requested that there would be no popup BS in his advertising, but they still get sent to him anyway. This isn't intentional.

It would be cool for burning presentation CDs and such for companies, or document control as well.

Cool, just keep an eye on the logs to make sure that any group policies will propogate properly.

You pretty much have it bud. When you setup your domain controllers, go ahead and let the install DNS for you, but remember that you will have to configure it to some extent on your own. I would also try to have the child domain controllers forward their unknown DNS requests to your ISP (or use root hints, which may help you out as you stated) to speed up the process, but if you have any resolution issues (like clients stating that they can't get group policies) then setup the child domain forwarders to point to the parent domain DNS boxes.

You are a sad little man. You have my pity...

Looks like a Code-Red style attack. If you install IISLockdown (or at least URLScan) from MS that will harden IIS to that type of attack and reject those URLs. IISLockdown http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/tools/tools/locktool.asp URLScan (my fav) http://support.microsoft.com/default.aspx?scid=KB;EN-US;q307608&id=307608&sd=tech

Sure man. So you're a lurker that's just now starting to pipe up? And I have no information to provide to anyone at all. That's what you're saying right? If anyone else wants to agree and thinks that my posts are a waste, then please speak up. If this is the general consensus, then I'll leave. How's that grab ya, sparky?

This thing? http://www.yamaha.com/yec/multimedia/customer/features/feat_prodsCRWF1_1.html That's pimpy. Must be a big hit at LAN parties.

Quote: The thing is that RH has crippled KDE. I have used the Fontinstaller in KDE (Mandrake too) before but in this release RH has removed it. I think that RH8 works with fonts in another way, not supported with the availble tools. At least I hope so, coz this method is not very strightforward Anyway, if you are using RH8 check out that Mozilla build. [edit] will add some screenshots tomorrow... [/edit] Hey Toby, where's our screencaps?

I would think so, as I have done this on my systems with 1280x1024 resolutions and not had any issues. Also, I haven't had any need to "undo" that, so I am of little use there.

Umm, ok. It simply sounding like you could expand on that point. And actually, the flaw was with NT4, not Windows 2000 (as I said earlier). Now, seeing as that is your second post, you seem to be monitoring this board fairly aggressively for your first day afterall. So, was that witty enough for you?

Actually, there was a flaw at one point in NT that allowed for users to generate other users and add them to the admins group (oops ). A friend that's a sysadmin at a rather large network caught someone doing that a long time ago, but it was fixed since then (right? ). As for the domain permissions, I must admit that I am not sure what you are addressing BN. Please explain.

Actually, no, I am *not* an MCSE+I due to the certifications I have. If I had picked up Proxy Server or Exchange Server, then I would, in fact, have been an MCSE+I. Try not to make assumptions, as you are simply making an a$$ of yourself. I only have two of the qualifying "+I" criteria, and am therefore an MCP+I in addition to being an MCSE. If you like, I could scan in transcript...no, wait, your opinion does not really concern me. Next, no one ever stated that he (nor you) did something wrong, I was presenting a more common approach to it that also resolves future issues that he might encounter. Also, as there are many posts, I might not see *every* single post shown. But, if you think that someone making alternate option to your post being known is a personal attack, then you are in for a rough time as many people here are quite opinionated and will be offering all kinds of options.

Quote: Quote: MS went back and said... "ok, here is what we did wrong, lets optimize this and take it to the next level". I thought that was the general idea behind service packs?! Well, bugfixes, at least. Service packs rarely optimize and MS got out of adding features via them a while ago (at least officially.) So, for the most part tweaked is correct on that statement.

Right click on "My Computer", select "Manage", and then expand "Shared Folders" and open "Sessions". That should show all the current connections and let you disconnect them. Also, you can manage remote systems by right clicking on "Computer Management", select "Connect to Another Computer..." and then entering the name of the target computer.

However, if you actually pay attention to the link (read the page), this can apply to *anyone* that is needing to manage .NET servers and/or Windows 2000 servers from an XP box. It also details solutions to possible problems that he might experience in the future. This post might come up in future searches, so having a link that exposes the newest file and explains version conflicts might be fairly helpful.

You could also go here: http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q304718& and get the adminpak for .NET Server RC1, which should work just fine. Bear in mind that the DCs might have to be upgraded to SP3, although you'll see a link that will show you how to modify the registries of SP2 and earlier Win2K boxes to allow the adminpak to connect to them.

If you plan on having them as distributed management (where each child domain can have its own admin but that admin can't manage the enterprise), then the nomenclature would be: root = parent.com child1 = child1.parent.com child2 = child2.parent.com child3 = child3.parent.com In this respect, you would setup your root domain first, and then have at least 2 domain controllers in it. On those controllers, install your DNS services and setup your forwarders to point to the "real" DNS servers from your ISP (this can be the tricky part, as with proper replication the DNS system should have a local cache of all the info from *.parent.com servers and only go to the outside when using outside resources). Once they are up, stable, and not reporting any errors, then try child1.parent.com. On that one, setup the DC's DNS to only replicate traffic with the servers on its nameservers tab, and on that tab list parent.com's DNS servers. You want to do this so that your DNS server doesn't spend all day replicating traffic with anyone that will listen. You will want to do the same thing for parent.com and make sure that they sync properly afterward (it might take 5 minutes or so). Now, on child1.parent.com, try gettting to the internet. If, for some reason, it doesn't allow you to get out, put parent.com's DNS boxes in the forwarders tab of child1.parent.com's DNS server. The main rule that you really want to focus on is *keep your internal DNS internal*. Make sure that none of the client systems get contaminated with outside data, or they might resolve parent.com as the external IP to your webserver and never get info from your DCs. Once the sync works well between child1.parent.com and parent.com, do the same for child2.parent.com. Rinse and repeat. One more thing, if you have pre-Windows 2000 machines having WINS around isn't such a bad idea. So, if your DNS system has slow resolution times or you have apps that only want to use \\machinename... then simply setup a single WINS box with your DNS boxes in each domain (or more if you like) and then have your DNS perform WINS and WINS-R lookups. Once a system (like Windows NT 4.0) comes online, it will pick up its IP from DHCP, and register with WINS. Then, if someone does a ping for nt4.child1.parent.com, the DNS system will look locally first for nt4, and when it doesn't find it it will scan the WINS DB. Once that's done, it will return the info as nt4.child1.parent.com, appending the proper DNS suffix auto-magically. The process is very fast, so don't be too concerned about this. Just keep this in mind if DDNS registration doesn't work as advertised for you (it rarely did for me).

Who cares, anyone that makes judgements about a game from a leaked alpha is a dumba$$ anyway. The leaked build of UT2003 ran OK, but the retail version ran a lot better with more features enabled. I expect the same to happen here.

It's "double-pumped", just like how the P4s are "quad-pumped" from a real 100MHz FSB to 400MHz (or 133 to 533). It actually isn't called "double-pumped" as AMD has some other stupid name for it. But basically it's another multiplier that is irrespective of the memory speed. So, the CPU can have a 266FSB while the RAM is still at 133. That's why you can see all kinds of crazy dividers and asynchronous operation of RAM vs. CPU.

I am going to bed right now, but list how many subdomains you are hosting and how many systems in each one. I can give you a quick rundown on how I would do it, and see if that meets your needs.

I used the SiS 645 in my Soyo Dragon, and it was pretty nice. The only issues that I had with it were usually in loading their IDE/AGP drivers (which sucked), and Debian not finding my burner properly on that box.

I saw this link in a reply to a ZDNet column, and I thought I would pass it along for people looking for office/RDBMS integration in Linux. http://www.unixodbc.org/doc/OOoMySQL.pdf

Annoying. Seems people just have too much time on their hands.

Quote: If its broken outta the box then they should replace it, i mean why shoudnt they replace it? You paid good money for something that doesnt work ;( People do it all the time. Have you ever bought software?