Search results for query: *

I recently received some info about AD domain naming which has cleared this up a bit, and I will probably name my domain something like home.company.com and then add a DNS record at the ISP to point home.company.com to my W2K server's IP address for remote access and/or internet printing...

(bump)

My current set up involves a non-microsoft server running my email, web page, and ftp, and it's static IP address is the one registered with the world-wide DNS for my company's www.company.com, ftp.company.com, and email@company.com functions. When I install my new Windows 2000 Server Domain...

...right now from everyone's comments, and yours helped out in that arena. I like the idea of 2 servers for mission critical, but I think I'll be *told* to go with one. I do want to configure it with RAID, tape backup, and have a quick repair turnaround so I'll have to check out all that stuff...

Oh yeah - hehe. Sorry - I was thinking that was the Compaq description. I'm thinking Dell or IBM, but need to compare specs, prices, and support on both.

Did anyone mention Dell yet? What are your thoughts on a Dell server? - Bob

Brett - Good deal. Thanks for all your help! - Bob

KingE - I like your scenario a lot. To answer your question, we have a full class C set of ip addresses assigned and they are statically assigned to all machines. Thanks for the help! - Bob

Brett - I wanted to keep the new server and workstations logically separate from the current setup, as it is to support a new project and new customer and should have nothing to do with the other machines currently on the network. However, I understand what you are saying. Just set the new...

I recall something about Quota management having to be enabled on the folder before you start copying the data into that folder so it will reflect the proper size. I'm not sure on this, but maybe it will lead you in the right direction for troubleshooting. Also, if disk compression is enabled...

(Bump) Anyone have any input on this please? - Bob

I just hoping I could just set up the new W2K Server with DNS, Active directory, and a new domain name, then have the associated workstations authenticate the that new domain controller only and point their DNS to that server. That new server would point it's DNS to the ISP's DNS for Internet...

But for a small to medium sized environment of office or database users, it's not real significant or required, is it? - Bob

Anyone like any of the IBM's? I recall they had a line called eServers or something. I don't think I need dual processors or dual nic's, but a gig of memory would be nice and definitely something to do with RAID wold help. Right now I always install (2) drives and do mirroring through the OS...

Thanks mjinks61 - Wow - that's interesting if it truly requires a network connection to see itself in the workgroup and to see/use unc paths to shared folders on itself. Not that I ever tried it without a network cabled until now. If what you are saying is true, that would be my problem. Some...

It is my understanding that LOCAL group policy applies to all local user accounts for that particular machine.

Just curious - I see these "dual" network cards for servers. What is the general strategy and implementation on how these make access to the server faster or more efficient? Thanks! - Bob

Any recommendations on hardware manufacturers/models for setting up a new Windows 2K Server? I'm talking maybe 2-5 clients initially, not growing too much for this project in the foreseeable future. We will probably run SQL Server and Access applications. Instead of building a machines from...

You may have read my note relating to adding a Win 2K Server to an existing Win NT 4 environment. We currently use a TR-4 tape drive in the Win NT server with Seagate Backup Exec for daily backups. Are tape drives a dead duck? I've heard of local shops backing up to NAS and saying how much...

We current have a Windows NT 4 Server environment, with 1 PDC and 1 BDC. I have a current domain called X. We use static ip addressing and do NOT run DHCP, WINS, or DNS on the servers. I point the workstations directly to the ISP DNS servers for name resolution for Internet access via our T1...