|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] Samba Printing to an HP Deskjet
|
I'd start with a tcpdump on the samba server to see what the client is trying
to connect to (assuming that is the problem). For standard file shares I
only needed to open port 445 (I believe, I forgot the precise number, but it
was the only port needed for a basic file share). Perhaps you have some port
blocked and the clients are expecting to at least contact some NMBD server,
or something similarly wacky? We had experience with an SMB client trying to
access port 80(!) as if it wanted to check WEBDAV availability even after it
successfully found the SMB share. Symptoms were as you described.
P.S. for mounting the shares I used IP address. If I used the name, of
course it needed to look up the name, hence extra traffic on other ports.
Dan W.
On Tue, Dec 19, 2006 at 10:21:09AM -0500, Andrew M. Lauppe wrote:
> Geneva Global Inc - Performance Philanthropy
> ____________________________________________
>
>
> Hey everyone..
>
> So, I have a CentOS 4.4 machine running as a samba server. All users
> have appropriate usernames and passwords in the appropriate groups (I
> know this because they all have working connections to the file share on
> the same machine with appropriate permissions on the folders, etc.)
>
> The printer works. You send a job to it, it prints the job; that's not
> the problem. The problem is two-fold;
> 1. Everything takes longer than it should, even printing. You
> hit properties in windows and querying the printer settings takes 2
> minutes. Meanwhile the end-user's computer looks like its locked up.
> After a couple minutes, the properties screen comes up, so you hit
> 'printing preferences' and it takes another 2 minutes to come up. You
> make your setting changes, and then hit apply - you guessed it, two
> minutes to apply.
> 2. In Details view of the printers and faxes window in windows,
> regardless what username you've entered, it says something like 'unable
> to connect, authorization failed.' Or 'access denied' or something,
> though if you print to it, it spits out your job just fine.
>
> Any suggestions?
> Andy
> ___________________________________________________________________________
> Philadelphia Linux Users Group -- http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|