Printing over a network in Win2k

[WPKenny]

Ello again!

Okay. Is comeone able to explain to me in really simple, step-by-step terms how I can get a computer using win2k to print to a printer that is shared on a WinME machine?

I've made a real arse of it so far and tried local printer ports and creating new ports and all sorts but it just seems to cock up somewhere along the line.

I can SEE the printer (there's two actually on the WinMe machine) and when I tell Win2k where the printer is it goes "Ah! That's a HP XXXX printer! Would you like to install the right drivers for it?" etc etc.

All seems to go smoothly. But as soon as I try to print to it, it tells me there's an error printing. :/

If anyone knows of a site with pictures and stuff in how to go about setting it up correctly, I'd be very grateful cos at the mo, I've got to save all my files to a shared directory and kick whoever is on the machine with the printers attached while I print my documents. Not exactly business like.

 

[Summo]

Sounds like you've done it, but what's the error?

 

[Scouse]

Aye - it's a good thing for anyone here to post the EXACT error on this board.

You got any firewall software? Can't really see it being a problem but....

 

[S-Gray]

Is it a communications error or somethin?

 

[WPKenny]

It's all sorts of errors depending on set ups I try. I've tried it so many ways now.

I get communication errors. Sometimes it looks like it's printing okay but it never arrives at the printer. Other times it just simply says "there was an error printing" blah blah blah.

I find it odd that Win2k can see the printer and even identify which printer it is over the network, yet when it tries to communicate with it, it just falls over.

There's no firewall between the two computers.

Any other suggestions?

Perhaps I am doing something wrong? Is someone able to point me in the direction of a step by step guide of setting up a printer over a network from Win2k?

 

[Scouse]

Should be dead easy.

1) On your 98 box enable file and printer sharing.

When you set up your printer give it a meaningful name.
(Eg. if it's a HP laserjet 4 call it that).

2) On your Win2k box you can probably browse to the printer if it's in the same workgroup/domain otherwise you'll have to do it the long way.

3) It'll ask for drivers - and auto-install them.

4) Bob should be your mother's sister's husband.

Failing that - can you not just whack it on your 2k box? The sharing of printers FROM 2k is more reliable than from 9x.

and give us a *selection* of your errors then m8

 

[Scouse]

Also. Dead easy mistake to make >

When you set up the printer on the machine you're going to share it FROM you set it up as connected to my computer.

When you go to find the printer from the other machine you set it up as a network printer.


Not trying to insult you - I've just seen lots of people try to set things up this way (believe it or not!)

 

[Scooba Da Bass]

Every network printer I've set up over win2k has been as easy as finding the printer, and that's it. How has been on a server based network, although it shouldn't be any different on a peer to peer. I know XP has the option of installing the drivers locally for all versions of Windows to save the other computer having to find them itself, maybe ME has this option?

The only other option I can think of is to supply the IP of the printer and try to access it via port capture

 

[Scooba Da Bass]

Oh, have you tried adding them by browsing to the computer then right clicking the shared printer, this should give you an install option.

You may also want to try deleting the spool files for the printer on the local machine (*.shd *spl)

 

[WPKenny]

According to what you guys have said I've tried all that apart from deleting those files. What will that do?

I tried browsing for the computer via the network and connecting to it that way.
It seems to think it's actually sent it but it's not arriving now at the other printer.

I can't connect the printers directly to either of the win2k machines cos they're laptops and aren't always there.

Hmmm. No errors messages recently so I can't quote any directly. The print jobs just seem to disappearing into the void.

 

[Scooba Da Bass]

I remember reading an Ms knowledgebase articale about networkprinter problems. Deleting the spool files was one of the solutions

 

[Scouse]

Make sure you update the drivers on your 2k box with the most recent W2k drivers for the printer - that may help.

You haven't told us if you've connected the printer via a parallel port or on a jet direct box or whatever.

Be more specific please.

 

[WPKenny]

There are two printers. A LaserJet 1100 and a Deskjet 845c. The deskjet is attached via a USB cable and the Laserjet is attached via a standard parralel printer cable.

I've done a search on both machines (WinME with the printers on it, and win2k laptop) and found no such "spool" files.

 

[Scouse]

Off the top of my head have a look (on your Win2k machine) under c:\winnt\system32\spool

I could be wrong tho.

Never tried sharing a USB printer. Should theoretically be the same as your other one.

SO. You've (theoretically) got 2 PC's.

One (the 98 box) is called fred
Two (win2k) called blogs.

From blogs go Start>Run and type in: \\fred

and tell us what you see - you should see anything and everything that's shared (it'll bring up a window).

If your printers are shared properly you should see 'em.

 

[Insane]

normally the spools folder doesnt help..

try this good 'old trick..

download the Corporate Drivers on the Win2K box, those drivers commonly disable bi-directional support on client machines, since the drivers trying to find the printer it wont pass the info through till it gets an ACK from the printer... which it wont across the network anyway.

if not, then move the USB printer to Win2K where it'll work better, and is a lot better at sharing out

does this happen both with the laserjet AND the deskjet? or is it only the deskjet?