🚀 go-pugleaf

[previous posting]

AL>In article <1993Sep23.183048.29485@rat.csc.calpoly.edu> jowalker@polyslo.csc
AL>poly.edu writes:
AL>>
AL>>In <BILLY@SJUVM.BITNET>'s bar room soliliquy, he muttered:
AL>>>Hello
AL>>>My company is running on ethernet (Thin net) using Lantastic.
AL>>>We have about 28 computers on this network all on one bus with
AL>>>
AL>>>My problem is HARDWARE. I know Ethernet has a limit of 607 feet of cable
AL>>>(I've recently discovered we have 887 ft;thats one of the causes of our
AL>>>downtime) and a limit of 30 computers per segment.
AL>>>
AL>>>Question: How can we get more than 30 computers on the network?
AL>>>          Can we use a HUB or a Repeater with the existing cables?
AL>>
AL>>I had this same problem, in that I had exceeded the 600 plus some
AL>>odd feet limit per segment. What I did was divide our network
AL>>into two segments by putting another network card in the server.
AL>>It was fairly easy, inexpensive, and gave the network a lot more
AL>>stability in that if one segment had problems, the other segment
AL>>ran happily along. I used this to divide up departments within my
AL>>company so that people who did development and sent strange
AL>>packets out of their machines that might cause problems were on a
AL>>segment isolated from the accountants and marketing people who
AL>>relied on the network for printing and standard apps.
AL>>
AL>>I am not sure if the 30 station limit is per segment as well but
AL>>I think it is, so this would solve both of your problems. Of
AL>>course this is not really a great long term solution if your
AL>>company is going to do a lot of growing. It is just a cheap, easy
AL>>fixit for a small company with a small budget.

AL>Wouldn't a repeater do the same job???  You should be able to insert the
AL>repeater in the middle of the network and then treat each side as another
AL>segment.

AL>Now here's a question...If I divide the network into two segments by
AL>putting a second adapter into the server, then if I am running a client
AL>server app with the client on one segment and the db server on another
AL>segment, will the client-server app still work?????  In other words, will
AL>the ipx/netbios calls made by the client still reach the server even though
AL>its on a different segment???


AL>---------------------------------------------------------------------------
AL>Alex Lee
AL>Managing Director
AL>QUEUE Systems                       E-Mail:  ALEX@QUEUE.PCI.ON.CA
AL>60 Columbia Way, Suite 300           Voice:  (416) 940-8132
AL>Markham, Ontario, Canada               Fax:  (416) 940-9234
AL>L3R 0C9
AL>===========================================================================

A repeater will solve your length problem.  However, it gives you no
relief on the bandwidth limits.  A repeater makes all traffic additive.
If you make two seperate ethernets then you get bandwidth relief.

Is the db server the same as the file server?  If the db server is
seperate then you are right, the server will need to route that traffic.
The router function will work with the normal protocols.  If your
netbios is true IBM netbios then it won't work because that is not
routeable.  If its netbios emulation via IPX it will route fine.

If the server must route a lot of traffic that will demand server
resources.

Good Luck
DR
---
 � OLX 2.1 TD � The Methodist Medical Center of Illinois