Nt Networking

[DavidClark]

&lt;gulp&gt;<br>
I am about to build my 1 st network.<br>
There are 8 clients and I've built a server. I've got several years benind me- but this is sort of like my first date all over again.<br>
Which model - domain or workgroup? <br>
What about TCP/IP numbers since this is a closed network ?<br>
Should I use DHCP and take the easy way out?<br>
We're going to use Wingate the give the clients Web acess- and secuity issues are minimal since ADMIN will not allow any dial ins.<br>
<br>
HELP !!!! You may email me directly at <A HREF="mailto:davidclark@davidclark.org">davidclark@davidclark.org</A> if you wish !<br>

 

[MasterRacker]

1. Definitely go with a domain model.<br>
2. Set up DHCP on your server. I'm not familiar with Wingate, but I assume it's a combination proxy server/gateway/firewall, etc.... If so, you will have a static real world IP with your ISP and internally, you can use any addressing you want. You may still have some static addresses, so make sure you get everything on the same subnet. <p> Jeff<br><a href=mailto: masterracker@hotmail.com> masterracker@hotmail.com</a><br><a href= > </a><br> Of all the things I've lost in life, I miss my mind the most ...

 

[Ianco]

Have you considered using Windows 2000.&nbsp;&nbsp;You might even get away with using Windows 2000 Professional, the workstation version rather than the server?&nbsp;&nbsp;It has Internet Connection Sharing built in and works great.&nbsp;&nbsp;I am using it will my home network, dial-up to my ISP, with 4 mixed 9x clients.<br>All depends on what you plan to use the server for.&nbsp;&nbsp;If you require SQL server, or any other Back Office products then you will definitely need to go server version, either NT4 or 2000.<br>Good Luck<br>Ianco

 

[thorswolf]

Agree definitely with a domain model.<br>DHCP also is much easier. There is a specific addressing range available for a &quot;home&quot; I believe. You can get this from the Microsoft site by looking up their &quot;Internet Connection Sharing&quot; (ICS) description under Windows 98. I remember it specifies the addressing ranges available.<br>I don't know Wingate, but most of those Internet sharing apps usually work well.<br>Dial-ins shouldn't be what you're worried about. Hackers is a more likely problem on the side exposed to the Internet. You may want to consider a gatekeeper software like BlackIce on that machine.<br><br>Best of luck.<br><br>Yves

 

[pmkincaid]

First of all I agree with everyone else in a Domain structure is your best bet.&nbsp;&nbsp;Its not that difficult to set up and allows for future expansion if you so desire.<br><br>Now is where I disagree, somewhat...&nbsp;&nbsp;One question that comes into play with whethter to use DHCP or Static IP addresses is concerning the Proxy Server (Wingate).&nbsp;&nbsp;Is there going to be any filtering done on the Proxy server (ie is there a chance you don't want JoeUserA access to espn.com cause he surfs it all day long, but the boss wants it to follow his favorite team?)&nbsp;&nbsp;Or any sort of logging of traffic?&nbsp;&nbsp;Granted you may not think this is a concern right now, however when (and its never a matter of if these days...) your connection to the internet gets congested, you are going to want to do some traffic monitoring to see where the bottlenecks are, and you see that 192.168.0.6 surfs to xyz.com on this day and 192.168.0.8 surfs to xyz.com on another day and is taking 75% of your band width as they listen to streaming audio over your connection -- is it the same person, machine, etc, etc, etc.<br><br>Now I am not familiar with Wingate but most other Proxy servers will report the IP address and if you are DHCP assigning them, you MIGHT have a problem tracking something like this down...&nbsp;&nbsp;Bob's desk is always assigned 192.168.0.6 statically and you can go to Bob and tell him to stop accessing streaming audio to help with your bandwidth problem.<br><br>Having said that, the internal IP addresses you can use on your private network are:<br>&nbsp;&nbsp;&nbsp;10.0.0.0 to 10.255.255.255<br>&nbsp;&nbsp;&nbsp;172.20.16.0 to 172.20.31.255<br>&nbsp;&nbsp;&nbsp;192.168.0.0 to 192.168.255.255<br><br>Hope this helps a bit,<br>Paul Kincaid