Networking Printer

[mmione]

Well my dad has a nice all in one lexmark printer/scanner/photocopier. WHen I clcik computers near me, his computer shows up. I was wondering how I could print using the printer on his computer instead of mine. Thanks.

[JackMDS]

Yeah you can.

On the computer with the printer open Control Panel / Printer and Fax. Right click on the printer choose properties click on the sharing Tab and make it Sharable.

You have to install the pronter drivers on your computer too.

.

[Sid]

You don't need to install the drivers on your system. Run the add printer on your system and tell it its a network printer, then find the printer and your all set. You will need to set sharing on your dad's system.

[JackMDS]

Originally posted by Sid
You don't need to install the drivers on your system If the two computers are always on at the same time you might not need the Drivers on the Printerless computer.

However, some applications like to see the drivers, thus may not work well in absence of drivers when you are not connected to the computer with the Printer.

[Sid]

Originally posted by JackMDS
If the two computers are always on at the same time you might not need the Drivers on the Printerless computer.

However, some applications like to see the drivers, thus may not work well in absence of drivers when you are not connected to the computer with the Printer.

Print data is sent to the printer host in raw data. You only need to install the drivers on the host system. I can't count how many network printer setup I've done and I have never install any drivers and any system other than the host.

[qball15j]

Originally posted by Sid
Print data is sent to the printer host in raw data. You only need to install the drivers on the host system. I can't count how many network printer setup I've done and I have never install any drivers and any system other than the host.

:nod: Only time you may run into problems is if host OS is newer then the client OS, then you would need to install the driver on the client machine.

[JackMDS]

Maintained a Bulldozer (Business Network) is not necessarily the same of as the Little Sedan of the Home peer to peer user.
.

[JackMDS]

Yeah The Pros do not care about NetBEUI in their Big Network Envioroment (and rightfully so).

However if you would have a Buck for each Modest Peer to Peer 2-3 computers Guy that was saved by installing NetBEUI after days of trying to share with no avail, you would be Rich.

.

[qball15j]

Originally posted by JackMDS
Yeah The Pros do not care about NetBEUI in their Big Network Envioroment (and rightfully so).

However if you would have a Buck for each Modest Peer to Peer 2-3 computers Guy that was saved by installing NetBEUI after days of trying to share with no avail, you would be Rich.

.

Did you post to thie wronge topic. hehe Were talking printers here not file sharing. :rotfl:

[JackMDS]

Originally posted by qball15j
Did you post to thie wronge topic. hehe Were talking printers here not file sharing. :rotfl: Yeah wrong thread. But read it anyway it is for you.

.

[qball15j]

Originally posted by JackMDS
Yeah wrong thread. But read it anyway it is for you.

.

Kind of figured that. :D

[Sid]

Originally posted by qball15j
:nod: Only time you may run into problems is if host OS is newer then the client OS, then you would need to install the driver on the client machine.

Not true, you can have the host send the drivers for the client(I have never had to do this). When I took my MCSE course's and tests, that was one area that MS really hit us on hard. Take a good look around the printer controls, man they have a lot of options.

I could take my laser printer which windows(any version) has no drivers for and tell my network that it's a web based and you would be able to print to in over the internet without installing a single driver.

[koldchillah]

Sid's right.. I never needed drivers either.. Once file/print sharing is enabled and the printer is shared on the host; simply browse the "computers near me" or workgroup. Find the host PC, double click; the shared printer should be displayed; right click printer, select "connect".. done deal.

[qball15j]

Originally posted by koldchillah
Sid's right.. I never needed drivers either.. Once file/print sharing is enabled and the printer is shared on the host; simply browse the "computers near me" or workgroup. Find the host PC, double click; the shared printer should be displayed; right click printer, select "connect".. done deal.

I've had a number of cases where that didn't work. Windows 2000 Server and 98 clients. Only way I didn't need a driver for the client machines is when I specified on the 2000 server that clients were using 98 and choosing the 98 driver to place on the server.

[YeOldeStonecat]

In my opinion....it's a mixture of several things
1) Printer drivers themselves....while most of the better printers have drivers you can usually install by browsing to the share, right clicking, and "connecting"...I've come across some that don't always do that.
2) Mixtures of OS's...what OS is sharing, what OS is connecting across the LAN.

TCP and/or NetBEUI...I don't see how that factors into this.

[qball15j]

Originally posted by YeOldeStonecat
In my opinion....it's a mixture of several things
1) Printer drivers themselves....while most of the better printers have drivers you can usually install by browsing to the share, right clicking, and "connecting"...I've come across some that don't always do that.
2) Mixtures of OS's...what OS is sharing, what OS is connecting across the LAN.

TCP and/or NetBEUI...I don't see how that factors into this.

:nod:

[Sid]

Originally posted by qball15j
I've had a number of cases where that didn't work. Windows 2000 Server and 98 clients. Only way I didn't need a driver for the client machines is when I specified on the 2000 server that clients were using 98 and choosing the 98 driver to place on the server.

I guess I should have been more clear. That is what I meant by all the options in the print drivers.

[koldchillah]

Originally posted by qball15j
I've had a number of cases where that didn't work. Windows 2000 Server and 98 clients. Only way I didn't need a driver for the client machines is when I specified on the 2000 server that clients were using 98 and choosing the 98 driver to place on the server.

I'm not going to disagree with you. :) But it sounds more like you're referring to a true network printer (we've got about 5 or 6 of those too). The necessary drivers for all varying client OS's are then placed on the server and configured as you said. But what if the printer is locally connected via USB to a 98 client PC sitting on some executive's desk?
I guess it sorta depends on the printer though.. We are all correct, just depends on the variables. :p

We have 272 computers on our win2k server domain (all win2k or winXP pro). Probably 40 or so desktop level laserjet 1000's, 1200's, Epson C60's.. etc etc.. (not by choice mind you) and a few nicer 2200's. All the printers we have used here have host based drivers that only required installation on the host PC. For our true network printers, we do as you mentioned.. install the drivers on the server and go from there; especially if you have 98 clients on your network.. (btw, I despise non NT based OS's on business level networks although I realize they are in abundance).

NetBeui? not on any network I work with.. TCP/IP should and can work on small home networks; and if it doesn't, its because its probably not configured correctly or something else is stepping on it. I'll take a routable solution over a broadcast solution just about any day.

[JackMDS]

Originally posted by koldchillah NetBeui? not on any network I work with.. TCP/IP should and can work on small home networks; and if it doesn't, its because its probably not configured correctly or something else is stepping on it. I'll take a routable solution over a broadcast solution just about any day. [/B] I am trying to Convey this message for long time, for some reason the Network Pros refuse to Get it (I guess it is a Psychological factor more than any thing else).

There are millions of Home owners that are in a process to Networking their humble family.

They are trying desperately to understand Networking and it is not easy.

Almost all of them use the Windows Network Wizard excessively because they do not know better.
As an example. After repetitive use of the Wizard the TCP/IP settings in the Registry get “Confused”, in most of the time it does not affect the capacity to use the Internet but it deem the Sharing part of the LAN unusable.

Some try to learn better, some can not, and some do not care. Installing NetBEUI makes their LAN functional. “Routable solution over a broadcast solution” is not really an important functional issue when you have 2-5 computers on a Humble Network.

Resisting the NETBEUI solution would be like not letting a person to buy one of this portable Rechargeable Battery to start their car under emergency.

Why should you buy it? Keep you Battery in Good shape and never leave any of the courtesy ON, and every thing will be a OK!!!

[koldchillah]

Originally posted by JackMDS
I am trying to Convey this message for long time, for some reason the Network Pros refuse to Get it (I guess it is a Psychological factor more than any thing else).

I hear ya man.. Your points are valid. It still doesn't change the fact that its a bandaid approach. IMHO, I'd rather go the extra mile and heal the wound so that I'm not dealing with extra variables shall another problem arise later on down the road. I have probably not worked on enough home networks (maybe a dozen or so at most) to have seen this TCP/IP registry corruption that you speak of. I work mostly on one large network. I do hate that stupid wizard though. It always turns into a configuration nightmare. :p

Sorry we got off topic mmione.. let us know how it works out for ya.. :)

[mmione]

I got it working, thanks for all the help.