| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 8218 | 2001-03-12 19:43:00 | Windows 2000, peer to peer network, internet connection sharing, internal email | Guest (0) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 9912 | 2001-03-12 19:43:00 | I'm setting up a peer to peer network for my wifes new law practice. Using Windows 2000 for the security and stability. Never had much to do with NT. I have heard that you can install software that will allow one workstation to act as a workgroup server as well, to share an internet connection, and to distribute email internally. However, others have said that it is tricky, and complicated to administer. My question is - is this possible, and is it worth the effort? Second question - is there any reason why shouldn't have NTFS set up as the filimng system, or stick with FAT 32? I would appreciate any help I can get. |
Guest (0) | ||
| 9913 | 2001-03-12 22:43:00 | I have a small network at home with 3 computers. The one I am writing from has a connection to Paradise cable and runs Win2K. My kids' machine is running Windows 98 and another machine is running Win NT 4.0 Server (because I have a learning edition of SQL Server on it). I found setting up the Win2K machine and the Win 98 machine to talk to one another was largely automatic. In fact, the Win2K setup did everything for me whereas the Win98 machine I had to load client software for Internet Connection Sharing. The NT Server box was a little trickier because I had to set-up TCP/IP details such as assigning an address. I have not been able to get the NT box to see the internet but I haven't tried very hard as it is just as easy to use the Win2K box and download stuff to the server. We're all happily sharing printers too. If you have any specific questions, I'm happy to answer them for you. |
Guest (0) | ||
| 9914 | 2001-03-12 22:54:00 | I forgot to add that my son and I use MSN Chat when we want to send messages to one another (as the machines are at opposite ends of the house). That might resolve your internal email problem. As for NTFS over FAT32, I run Win98 on the Win2K machine as well so I've stuck with FAT32. I understand that NTFS gives you loads of additional features over FAT32 such as encryption, logging and folder security but at a performance cost. You should check out all the features of NTFS and decide whether they are worth the performance hit. |
Guest (0) | ||
| 9915 | 2001-03-12 23:39:00 | Hi Daivd, 1: Use NTFS 2: Install TCP/IP 3: Pick an Internal IP address scope, eg 192.168.1.xxx 4: Install NetBEUI protocol 5: Disable Netbios over TCP/IP 6: Assign a unique IP address 7: Pick the ICS machine and set up a connection to the Internet 8: Enable sharing of the connection in it's properties. 9: On all other machines, set the default gateway to be the IP address of the machine running ICS 10: Set the DNS server entries to be the DNS server of your ISP There are a few ways to do the e-mail bit however. |
Guest (0) | ||
| 9916 | 2001-03-13 01:23:00 | Thanks for the help, Nick and anon. Couple of questions: Why install NetBEUI as well as TCP/IP? Its the email problem I would really like to crack - Its only 3 machines at the moment,theres only going to be one real Web user, the other two only really need email access. Are any of the solutions easy to manage? |
Guest (0) | ||
| 9917 | 2001-03-13 07:38:00 | Hey, Theres heaps of information on apcmag.com (http://apcmag.com ) Look in Workshop/Windows Workshop This has info on win 2000 and networking nothing on your question. If you really need help a Microsoft Trainging pack may help Jacz jacz@mailandnews.com |
Guest (0) | ||
| 9918 | 2001-03-14 05:26:00 | I have WinGate (www.deerfield.com) on my Win2K Prof machine to share my dial-up internet connection with my two Win98 clients using DHCP, though I will shortly be going ADLS. As for internal email, I have registered my own domain and use WorkGroupMail (www.workgroupmail.com) to provide a local POP3/MAPI server. |
Guest (0) | ||
| 1 | |||||