tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Burgess <>
Subject RE: N/w Problem (Puneet Sachar)
Date Wed, 03 Apr 2002 11:32:53 GMT
Hi Puneet

This is off topic but....
If your structured cabling is already connected to the panel (usually called
a patch panel) then its all very easy on the hardware side.
Just make sure that the switching hub you are using is an UNMANAGED one --
if the ADCOM is managed then it requires setting up and will be a total pain
for a tiny network like yours -- a 24 port unmanaged switching hub should
only cost around £60 for a 10Mbs one, maybe £120 for a 10/100 autosensing
one that will work with both 10Mbs and 100Mbs network interface card.
Assuming you have an unmanaged hub then no setup is required.  All you need
are short patch cables (i.e. 40cm say lengths of cable with an rj45 jack at
each end).  You can buy tools for making the cables up but its a serious
pain and quite expensive when you can buy them ready made for £1 or less
each.  You just take a patch cable from each socket on the patch panel into
a socket on the switch and all is done.  

All the client machines need is a similar cable (but longer - 2M is probably
good) to go from their network interface card (NIC) to the wall or floor box
where each length of structured cabling comes out.

If the panel isn't wired up or if you don't have any floor boxes wired up
then the simplest thing is just to forget it and simply use an unmanaged
switch on its own.  All you need is a length of network cable for each
machine and you just connect the machine's NIC to any port on the hub.
That's it!  The only problem with this is getting the cable neatly arranged
and then working out which cable is which when machines move around --
structured cabling helps by hiding all the mess under the floor :(

To begin with why not start simply peer to peer with the built in windows
networking- you can add a dedicated server and make it Primary Domain
Controller (PDC) later, once you're happy with the cabling etc..

Setting up the client machines could be as simple as installing the netbeui
protocol on each one, giving it a unique name and setting the workgroup name
to be the same for all machines (by default, windows uses a workgroup name
of WORKGROUP -- there's no reason why you shouldn't stick with that. )  If
however, you want shared internet access or to set up a workgroup web
browser then you will have to use TCP/IP.  You can use both TCP/IP and
Netbeui but its probably better to just install tcp/ip in this case.  The
simplest way of doing this is then to create a text file called hosts with
no suffix and put in it one line for each machine giving its name and a
unique tcp/ip address.  There are a number of ranges of numbers available
for use by internal networks that you should choose from for example
192.168.x.y  where x and y are arbitrary numbers between 1 and 222. So,
assuming you use planets as your machine names, the file might look like	localhost ##always a good idea	mercury venus earth mars jupiter


Then set up each machine by installing tcp/ip protocol and configuring it to
not use DNS and not use WINS and to have a fixed ip address, using the
address for each machine assigned in the hosts file.  Give the machine the
correct name and put it in the workgroup.  Then copy the hosts file to
c:\winnt\system32\drivers\etc  (for NT, 2000 and XP)
or to
c:\windows  (for 95, 98, and ME)

At a command prompt you should then be able to type
ping localhost 
and see a list of replies received from the machine you typed the command
on.  Then try
ping venus
and you should see text to the effect of

Pinging venus[] with 32 bytes of data
Reply from bytes=32 time<10ms TTL=128
Reply from bytes=32 time<10ms TTL=128
Reply from bytes=32 time<10ms TTL=128
Reply from bytes=32 time<10ms TTL=128

If so, then all should be well....

If not, promise your network knowledgeable friend a large drink if he'll
help you out!!!  Or start by uninstalling tCP/IP and installing netbeui
which will almost certainly just work and let people use that for a time
while you read up on simple tcp/ip installations.. It's really not

Best Wishes
John Burgess
Tel: 01865 718666 
Fax: 01865 718600

-----Original Message-----
From: puneet sachar []
Sent: Wednesday, April 03, 2002 10:50 AM
To: Tomcat Users List; Tom Drake
Subject: N/w Problem (Puneet Sachar)

Hi friends

Plz find with the word file along with this mail(virus
scanned ....)

and help me if u have solutions for this 


Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax

Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.343 / Virus Database: 190 - Release Date: 22/03/02

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.343 / Virus Database: 190 - Release Date: 22/03/02

To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

View raw message