Re: More Samba headaches
> Brian Morgan wrote:
> > Here's a tricky one for ya. I'm using debian 2.0 / samba to connect
> > several jet direct box printers via ip addresses so that hundreds of
> > laptops on our campus can print via ip using MS networking. Works
> > great.
> >
> Ok. Can you explain your setup a bit more? I will assume that the HP
> printers have the builtin JetDiret, and the Debian box is just
> accepting the SMB printer connections and printing them to the HPs
> with lpr.
Yes, except we have some external jetdirect boxes, each configured with an ip
address.
>
>
> > 1 problem now: All of a sudden, nobody can print with the existing
> > windows printer setup. If I recreate the same printer, same samba
> > network que, etc., I can print again. In looking at the properties of
> > the new printer and the old printer, they are identical, but the old one
> > comes up with a windows error "cannot connect to this network printer.
> > Check to make sure . . . blah blah blah." This error occurs on all the
> > laptops: even ones that have just been burned with a fresh hard drive
> > image containing the appropriate printer setups.
> >
> Interesting. What do you see if you browse the Network Neighborhood on one
> of the laptops and look at your Debian box(es)? Is it the same as what you
> see with a ``smbclient -L boxname''? Can you connect to the printer shares
> on your Debian box(es) with smbclient? Can you look at the printers on the
> Debian box(es) thru the Network Neighborhood on the laptops?
If I browse through network neighborhood, I can see the debian boxes. I have
it setup so that the users that connect to the debian boxes just have limited
access to the printer queues, though, so I don't see much else in network
neighborhood. When I do a printer setup, I can see the debian server, and
connect to the appropriate printer with no problem.
>
>
> > The only other thing I can think of that would relate is that last week
> > the debian servers each had an ip conflict. That has been resolved now,
> > and the boxes have all been restarted.
> >
> IP conflict with what? Each other or a laptop? How did you resolve it?
IP conflict was with another win95 desktop machine on campus. Changed ip
address for the win95 boxes.
>
>
> > Any thoughts? Is this something anyone else has experienced, or is this
> > just another part of the ever growing list of problems associated with
> > the Bill Gates Virus?
> >
> Sounds weird, but we need more information on your setup.
Again, this all worked fine a couple of weeks ago. Very strange.
>
>
> --
> ______________________________________________________________
> | ian eure, network admin, freelance security consultant, and |
> | manically depressed paranoid schizophrenic, at your service. |
> ; <ieure@minion.org> - http://minion.org ;
> : raw speed = 105.6 wpm with 4.5% errors :
> . . . . . . . . . . . . . . . . . . . . . .
Reply to: