Unable to print to Windows printer
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
After upgrading my desktop system to SuSE 8.2, I have not been able to
print to a printer on Windows ME. However, I can print from my laptop
(also SuSE 8.2).
At the present time, the /etc/samba/smb.conf files on both systems are
identical, and I restarted both the smb and nmb daemons.
smbclient shows the following (altered to protect the guilty):
gaf@gaf:~> smbclient -L //abc
added interface ip=192.168.0.xxx bcast=192.168.0.255 nmask=255.255.255.0
Password: <empty>
Sharename Type Comment
--------- ---- -------
PRINTER$ Disk
HPPSC2200 Printer xxx's Multi-Function Printer
C Disk xxx's C drive
IPC$ IPC Remote Inter Process Communication
The printer is configured with no password.
In YaST when I go to configure the printer:
Select SMB Printing
Type IP address into host field (that system has a fixed local ip
address).
Lookup finds the queue:HPPSC2200
When testing the SMB connnection, YaST reports a problem.
It was successful in pinging the other system, but it reports
"session request to 192.168.0.yyy failed (Called name not present).
- --
Jerry Feldman
After upgrading my desktop system to SuSE 8.2, I have not been able to print to a printer on Windows ME. However, I can print from my laptop (also SuSE 8.2). At the present time, the /etc/samba/smb.conf files on both systems are identical, and I restarted both the smb and nmb daemons. smbclient shows the following (altered to protect the guilty): gaf@gaf:~> smbclient -L //abc added interface ip=192.168.0.xxx bcast=192.168.0.255 nmask=255.255.255.0 Password: <empty>
Sharename Type Comment --------- ---- ------- PRINTER$ Disk HPPSC2200 Printer xxx's Multi-Function Printer C Disk xxx's C drive IPC$ IPC Remote Inter Process Communication
The printer is configured with no password.
In YaST when I go to configure the printer: Select SMB Printing Type IP address into host field (that system has a fixed local ip address).
Lookup finds the queue:HPPSC2200
When testing the SMB connnection, YaST reports a problem. It was successful in pinging the other system, but it reports "session request to 192.168.0.yyy failed (Called name not present). Since my laptop could print successfully, and the desktop could not, I compared the /etc/cups/printers.conf files. The only difference between
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 8 Sep 2003 10:03:16 -0400
Jerry Feldman
participants (1)
-
Jerry Feldman