[dba-Tech] Re: [] Wireless network (sort of)

   I conclude that your server first spools the print jobs on the server
first?!

	 
	You would need to create a different ip range for that second
nic and printers. That would make thing more complicated. Furthermore
when your server first spools the job, that means that a print job is
send twice over the network once from the client to the server and once
from the server to the printer.
	 
	You could change the clients to print directly to the IP
printer. This is great for the switch and bandwith but has a
disadvantage. The printjob is queqed on the client pc and has to be on
during printing.
	This can be a problem when people start large job overnight. It
also charges the client pc more.
	If your printers have a hard disk they will store the job on to
their disk and you don't have that issue.
	But most networkprinter do not have a hard disk (in my
customerbase).
	 
	 
	You could however buy a swithch whre you can team up two network
cards.
	It is posible with some brands to combine two ports on the
switch with two nics on the server.
	This for fault tolerancy and/or combined bandwith, resulting in
a 200Mb pipe between server and switch.
	Both nics are seen as one nic to the os.
	 
	I believe the cost of a 1Gb link between switch and server will
not be much more expensive.
	A switch with 1 or 2 1Gb ports are not that uncommon anymore on
swithches.
	All other ports may be 100Mb
	 
	Please note that I'm not saying this will resolve your problem.
	Network problems and bandwith can be very complicated and even
be different depending on the time of day.
	for example, if your current server is today not powerfull
enough a switch will not help much or nothing at all.
	Erwin
	 
	 
	 
	 

		-----Oorspronkelijk bericht----- 
		Van: dba-tech-bounces at databaseadvisors.com namens
Francisco H Tapia 
		Verzonden: di 4/11/2003 19:25 
		Aan: Discussion of Hardware and Software issues 
		CC: 
		Onderwerp: Re: [dba-Tech] Re: [] Wireless network (sort
of)
		
		

		Would it be helpful to add a 2nd Nic and bind all print
job request
		trough it, and leave the original nic for standard file
server access? 
		I don't know how to do this, but I can only imagine that
it could be
		done.  throw a Switch in there in place of the hub and
you've updated
		your network w/ 1 nic + the number of switches required.
		
		John Colby wrote:
		
		>Erwin,
		>
		>A collision is when one computer is transmitting and
another starts
		>transmitting over the top of the first.  The result of
a collision is that
		>the data is corrupted and has to be retransmitted.
		>
		>This can happen in a hub because ALL computers share a
single physical
		>electrical connection.  This simply cannot happen with
a switch because the
		>electronics set up a unique electrical connection from
computer to computer
		>using a cross point switch.
		>
		>With an eight port switch you could under ideal
circumstances have four 100
		>mbit conversations going on simultaneously.  There
would be no collisions at
		>all, four perfectly completed communications.
		>
		>Now obviously if a server is on one port and all the
other ports want to
		>talk to that port then only one at a time can do so,
but you still NEVER
		>have collisions since the electronics simply don't
connect port A to port B
		>unless port B is not in use.
		>
		>So yes, you have a bottleneck, all communications needs
to go through a
		>single port to get to the server, but NO, true
collisions (one computer
		>transmitting on top of and corrupting data of another
computer) NEVER happen
		>with a switch.
		>
		>John W. Colby
		>www.colbyconsulting.com
		>
		>-----Original Message-----
		>From: dba-tech-bounces at databaseadvisors.com
		>[mailto:dba-tech-bounces at databaseadvisors.com]On Behalf
Of Erwin Craps
		>Sent: Tuesday, November 04, 2003 2:07 AM
		>To: Discussion of Hardware and Software issues
		>Subject: RE: [dba-Tech] Re: [] Wireless network (sort
of)
		>
		>
		>Thats not to