Maybe this can help you. It's the first time I post it here so comments
or suggestions are welcome!
========================================================================
This article is not meant as a step by step or how to guide for setting
up or troubleshooting peer networks. Rather, it is meant to provide
basic knowledge that should help the reader understand network concepts
and make it easier to setup and troubleshoot peer network installations.
Reading the articles suggested here should provide helpful information
that anyone trying to set up or troubleshoot a network should have. The
article is a compendium, or collection of articles which I attempt to
present in a somewhat logical order.
I didn't know where in the article I should put the following advice but
it is so important that I have decided to put it here at the beginning.
One word only, FIREWALLS! Setting up a network can be complicated and
troublesome enough so you should take every step possible to make the
job easier. I not only recommend that you disable your firewall, I
recommend that you completely uninstall it. Get it out of the picture
before you begin, once your network is up and running properly then you
can reinstall the firewall. This will allow you to properly install and
configure the network, plus it will force new network discovery by your
firewall thus ensuring that the firewall is also properly configured.
While your computers are unprotected you should take basic precautions
to avoid unwanted guests. With modem dial up there is no problem as
long as you don't dial out. With high speed and "always on" broadband
connections you need to be careful, best to simply physically disconnect
your computers from outside networks. Before you remove the firewall
disconnect the cable to outside networks.
Readers who see errors or incorrect information, or who feel that the
article might be improved with additional content are encouraged to post
their comments. The article is intended to be posted to Microsoft
newsgroups only. I have not asked specific permission from the owners
of the links in the article but I don't think they will object having
their links provided. If you own any of the links and you object or
otherwise do not want them in the article please let me know and I will
remove them.
A final note before we begin. The articles below may be written for any
or for particular Windows versions, WFW, Windows 95/98/ME, Windows
NT/2000/XP, or the Windows Server System family. While each Windows
version may have different means or ways of implementing the concepts or
technology, the basic information provided by the articles apply to all
Windows versions. Of course, don't expect Windows 95 to have Windows
2003 Advanced Server features. Advanced Server Documentation may
contain information beyond the scope of peer networks but the articles
may be posted for other reasons. Links to Advanced Server Documentation
are identifiable by leading and ending ***. Don't assume that all the
documentation in these articles apply to your situation or Windows version.
Now let's begin with the basics. You should read this first and
familiarize yourself with network architecture. This will help you
understand other concepts later on. This is the foundation for all
networks, without the fundamental knowledge contained in the article you
will lack in essential network skills. Reading time: about 30 minutes.
Networks, Networks Everywhere
By JoAnne Woodcock
Chapter 3 from Step Up to Networking, published by Microsoft Press
http://www.microsoft.com/technet/itsolutions/network/evaluate/technol/networks.mspx
So now you have the big picture, let us zoom-in on peer networks, which
is what is of concern to us for our small network. Reading time: a few
minutes or less.
Windows 2000 Professional on Microsoft Networks
http://www.microsoft.com/resources/...0/server/reskit/en-us/prork/prcf_omn_vcgd.asp
HARDWARE
Most peer networks today are connected with Network Interface Cards and
Category 5 cable but wireless devices are gaining in popularity.
Whichever hardware you use make sure it is properly installed and
configured. Read the installation and user manuals for your hardware.
Familiarize yourself with the testing and diagnostic utilities provided
by your hardware manufacturer. You can't properly install a network on
faulty or improperly configured hardware. There is a Go/No-Go process
to setting up networks, make sure that the hardware is a Go.
Wired or Wireless - What Kind of Network is Right for Me?
http://www.linksys.com/edu/page2.asp
Hubs, switches and routers explained
http://pcplus.co.uk/tips/?pagetypeid=2&articleid=15950&subsectionid=383&subsubsectionid=91
Appendix F - Routers and Switches
http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/appbaynt.mspx
Category 5 cable
http://en.wikipedia.org/wiki/Category_5_cable
If you connect only two computers together with Network Interface Cards
you have to use a "Crossover" cable. If you connect more than two
computers together you should use "straight-through" cables as mentioned
in some of the above articles, Auto-Sensing switches can differentiate
and use both types and even have mixed cables but you should still try
to use all straight-through cables on a switch.
Don't buy a hub, buy an Auto-Sensing, Auto-Negotiating switch or a
router. Switches are cheap, fast, and more than adequate for most peer
networks. A good router has the advantage of also being a hardware
firewall, but you will still need a software firewall installed on each
of your workstations to properly protect your network. Switches are
faster than routers, makes a big difference when you move large files
across the network or when you have more than 2 users on the network.
If you use wireless devices make sure that you properly secure them, you
don't want your neighbours on your network!
TRANSPORT PROTOCOL
For your computers to be able to communicate with each other they need a
common transport protocol. The golden rule is: The fewer protocols the
better. Usually there is only one needed protocol, TCP/IP. Remove ALL
unneeded protocols. The NetBEUI protocol it is almost never needed in
todays networked environment, remove it. Unnecessary protocols cause
network collisions and can significantly affect network speed and overall
performance.
A Description of Windows 95 and Windows 98 Network Protocols
http://support.microsoft.com/default.aspx?scid=kb;en-us;294945
Chapter 15 - Network Adapters and Protocols
http://www.microsoft.com/resources/documentation/windows/98/all/reskit/en-us/part3/wrkc15.mspx
Windows 2000 Professional on Microsoft Networks
http://www.microsoft.com/resources/...skit/en-us/prork/prcf_omn_hmjp.asp?frame=true
IP ADDRESSING
You may be able (or not) to use automatic IP addressing or DHCP
addressing. While Dynamic addressing might be a bit or seem to be
simpler I don't recommend using it on small peer networks. It's just as
easy to use static IP addresses. Static addressing needs no additional
service running in the background, unlike Dynamic addressing which
requires services to obtain IP leases. You could use any* address in
the Class A range, example:
Computer 1 - 10.20.30.1
Computer 2 - 10.20.30.2
Print Server - 10.20.30.6
The subnet mask 255.0.0.0 would be the same for all the above addresses.
You can also use certain IP addresses in the Class B or C range.
*Your IP addresses cannot start with the number 127. The number 127 in
class A address is reserved for internal loopback functions.
Don't confuse IP address with hardware MAC address. If you have a
router it can be used as a DHCP server. The workstations will have to
obtain IP leases from the router and the router will dish them out.
Routers can also work with static addressing thus eliminating IP leasing.
Introduction to TCP/IP
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbb_tcp_PNMZ.asp
Choosing an IP Address Assignment Method
http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prjj_ipa_hkhg.asp
TCP/IP in Windows 2000 Professional
http://www.microsoft.com/resources/...0/server/reskit/en-us/prork/prcc_tcp_blhc.asp
Understanding TCP/IP addressing and subnetting basics
http://support.microsoft.com/default.aspx?scid=kb;en-us;164015
Checklist: Installing and configuring TCP/IP
***Windows 2000 Advanced Server Documentation.***
http://www.microsoft.com/windows200.../advanced/help/sag_TCPIPchecklist.htm?id=2109
What is DHCP?
http://www.microsoft.com/resources/...v/2003/all/techref/en-us/w2k3tr_dhcp_what.asp
How DHCP Works
http://www.microsoft.com/Resources/.../techref/en-us/W2K3TR_dhcp_how.asp?frame=true
How to Remotely Reconfigure IP from Static Addressing to DHCP
http://support.microsoft.com/kb/q194407/
Static IP address setup
Converting from a DHCP based LAN configuration
http://www.homenethelp.com/web/howto/static-ip-address.asp
MS TCP/IP and Windows 95 Networking
http://www.microsoft.com/technet/archive/win95/mstcpip.mspx
(Reference Material only)
TCP/IP NETWORK COMMANDS
Tip: For help on any command use the /? switch, example: ping /? will
show available options and syntax for the ping command.
To test a TCP/IP configuration by using the ping command
***Windows 2000 Advanced Server Documentation.***
http://www.microsoft.com/windows200...s2000/en/advanced/help/sag_TCPIP_pro_Ping.htm
(Basic Ping command information, applies to all Windows version)
To test TCP/IP connections by using the ping and net view commands
***Windows 2000 Advanced Server Documentation.***
http://www.microsoft.com/windows200...n/advanced/help/sag_TCPIP_pro_PingConnect.htm
Command-line utilities
http://www.microsoft.com/resources/...roddocs/en-us/sag_tcpip_tro_usingcommands.asp
TCP/IP Troubleshooting
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cnbd_trb_dfln.asp
Using PING.EXE with Windows for Workgroups
http://support.microsoft.com/default.aspx?scid=kb;en-us;90475
(An example of when the NetBEUI protocol might be needed)
MICROSOFT NETWORKS
How To Install the Client for Microsoft Networks
http://compnetworking.about.com/cs/windowsnetworkin1/ht/client4msnet.htm
Set Up a Workgroup
http://www.microsoft.com/hardware/broadbandnetworking/10_concept_workgroups.mspx
File and Printer Sharing for Microsoft Networks
http://www.microsoft.com/windowsxp/...e/using/productdoc/en/fileandprintsharing.asp
Set Up File Sharing
http://www.microsoft.com/hardware/broadbandnetworking/10_concept_file_share_setup.mspx
Set Up Printer Sharing
http://www.microsoft.com/hardware/broadbandnetworking/10_concept_printer_share.mspx
Troubleshooting Browsing with Client for Microsoft Networks
http://support.microsoft.com/default.aspx?scid=kb;en-us;134304
Workgroup network Troubleshooting:
http://www.pctechnicians.ca/help/workgroup.html
Tip: Authenticated logons and user credentials. You need proper
credentials to have access to shared resources on a network. If you get
"access denied" messages make sure that you have an identical username
and password setup on each of the machines sharing the resource. Use
authenticated or network logons. If you don't use authenticated logon
then you may need to supply a valid username and password when you try
to connect to shared resources.
Chapter 18 - Logon, Browsing, and Resource Sharing
http://www.microsoft.com/resources/documentation/windows/98/all/reskit/en-us/part3/wrkc18.mspx
How to Use the NET VIEW Command to View Shared Resources
http://support.microsoft.com/default.aspx?scid=kb;en-us;141229
BROWSER
The Browser service is probably one of the least known and understood
service with many network users. Yet this is one of the most important
part of your network. No network is properly setup until Browser duties
are properly assigned across your network. Browser conflicts are a
major cause of network errors or problems. Take time to familiarize
yourself with the Browser service and its purpose.
Windows NT Server Resource Kit
Chapter 3 - Windows NT Browser Service
http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx
Browser Issue on Microsoft Networks
http://www.microsoft.com/technet/archive/winntas/tips/platinum/ptbimsn.mspx
Troubleshooting the Microsoft Computer Browser Service
http://support.microsoft.com/default.aspx?scid=kb;en-us;188305
Browsing the Network
http://www.wown.com/j_helmig/browse.htm
Windows 2000 Pro - Windows 98 Peer to Peer Networking,
Sharing Files with Win2000, and Fixing the "slow browsing" Problem
http://users.bigpond.net.au/hutch/win2k/win982kptpnet.htm
ON-LINE HELP
Sites by Johannes Helmig
http://www.helmig.com/
http://www.wown.com/
Network, Internet, Remote Access, VPN Tips & Troubleshooting
http://www.chicagotech.net/
Carey Holzman's Free Computer Tips and Information Page
http://www.careyholzman.com/
Home computer networking and Internet connection sharing
http://www.homenethelp.com/
http://www.microsoft.com/hardware/broadbandnetworking/default.mspx
How to Set Up a Small Network with Windows 98 Second Edition (PART 1)
http://support.microsoft.com/kb/814235
(An easy to follow 8 part guide that shows you all the steps. You can
use it as a basic guide for other Windows versions).
Microsoft Community Newsgroups
Networking Technologies Newsgroups
http://www.microsoft.com/windowsserver2003/community/newsgroups/networking/default.mspx
And finally, your pc help files contain information specific to your
Windows version.
HTH
John
