clutch

Either way, that doesn't stop you from getting probed. It's just annoying as hell to me.

Could be worse.

Nice post ghayes, very informative.

Also, try www.samba.org for general info, and http://us6.samba.org/samba/GUI/ for GUI stuff.

I can give you a start. The main issue between SAMBA and Windows OSs is the fact that all the modern ones communicate in an encrypted manner. You will see this in the "HOW-TOs" on the subject that accompanies SAMBA. Windows NT4 (Pre SP3) and Win95 (pre version "C" I think) would communicate via encryption on the first try, then would try plain text afterward. Now, plaintext was great for *nix platforms since that is (was?) their default methodology. What you will have to decide on, is whether you want to "cripple" Win2K and have it broadcast in plain text (please, no ) or make SAMBA use encryption. SAMBA does work perfectly fine in encrypted mode, so try to use that one first. Also, use SWAT, the HTML based front end for SAMBA to get your shares up and running, it's pretty nice to work with. Linux has a lot going for it on the networking front, so stick with it. You can learn a lot that way.

www.speedguide.net

Unfortunately, I have none with respect to binding NICs. Also, I have never felt that great about the network underpinnings of Win98, so any effort bind multiple cards under that OS would seem questionable at best. BTW, do you really think my hand is pretty? Who told you that?

Just thought I would drop in on this one person conversation...

I think Hellbringer was interested in the idea of binding multiple NICs for increased download capacity. Well, here's an app that will do that. http://www.ipmetrics.com/ It looks like it explains loadbalancing a bit as well.

Cool, I thought I was going crazy for a moment there.

So whatcha get? Any cool new toys? If not, buy yourself something, you have my permission...

That's odd, Toby. I patched 5 servers running Win2K SP2, and none of them needed the reboot. Also, you will be getting an email from me.

Ouch. Still kinda hard to believe that so much havoc can be averted with a patch that doesn't even require a reboot (at least in Win2K anyway).

Office XP works fine with Win2K. Now, I don't know about importing settings, but you can import all of your mail, calendar entries, journal entries, etc. by exporting your personal folder file into a pst. This is all covered here. Just make sure not to forget any archive files you may still have there.

Windows Professional only hosts up to 10 concurrent connections. This may be a problem for your layout. As for the hardware under Win2K server, that should be fine (though I think I would opt for 256MB of RAM myself).

I only deal with NTFS, so it's never been an issue for me. And CUViper is right about Zip files, they are pretty easy to crack. If I see anything else, I'll post it.

Tnx.

http://support.microsoft.com/support/kb/articles/Q230/5/20.ASP That should do it. Make sure you are using NTFS first though.

Does anybody here have experience with this component? I am trying to get it to show a calendar in a public folder, but I can't seem to get the thing to do it. I can display the calendar, email, tasks, etc. for the logged on user, but I can't get to public folders. Tnx.

Your description sounds more like middle management, rather than being a "guru".

Anybody here ever mess with that? Any info to offer?

Yeah, he more than likely meant "deny" in his earlier posts (unless the UK version uses "decline" rather than "deny"). As for being a guru, I have no idea. I can tell you this though, most of the more advanced people here have had more than a few years under their respective belts not only using various versions of Windows, but administering them in business situations. Earlier, I wasn't so much attacking you (I am sorry if you got that impression) as illustrating what most people really need to do before they start handling server-class operating systems. When I tried to use Linux, I went through about a dozen "how-tos" before I could get anywhere with it. After a while, I was able to move around in a somewhat pathetic manner . I got Samba working with NT while retaining encryted authentication, and I did mess with Apache for a brief amount of time. I had a couple of friends that knew Linux quite well, and they gave me some assistance. However, the main source of information came from reading books (I bought QUE's "Using Linux" and Sam's "Teach Yourself Samba in 24 Hours") to get myself off the ground. Now while I know using books like this may not be particularly attractive, it is far better than getting bits and pieces of information from dozens of sources and then patching it all together. In that scenario, you rarely get an accurate picture of what is going on. So many people manage to get their hands on NT/2K server, and start setting up boxes with little or no idea what they are doing. Most of them install IIS in full default trim, and then wonder why their machines are used as "zombies" for DoS attacks. Learning to use an OS is something requires temperment, and a great deal of patience. I just feel that this is getting pushed aside in favor of quickly picking up some commonly used tasks, and then trying to land a job as an admin somewhere. I mean, for those who don't know, Win2K server can do more than host game and w4rez servers...

Here is something I found on Technet regarding this issue http://support.microsoft.com/support/kb/articles/Q266/4/16.ASP You may be able to find more at this link http://search.microsoft.com/us/itresources/default.asp

Here's the deal bud, you are probably being used as a relay to pass email hence the NDRs (Non Delivery Reports) showing up. Configure your server like this: http://www.exchangeadmin.com/Articles/Index.cfm?ArticleID=7696 and you should be fine. You will note that having routing turned "off" is what generates the NDRs to begin with. Test your server as is outlined in the article, and you will be all set.