Can't find NT Box and Printer with YaST
Because of a very specialized medical program that requires Windows NT 4.0, I have had to attach this NT box to my SuSE 9.0 network. The problem is that I can not see the printer from YaST, nor can I see the NT box from SAMBA. Here is what I have tried: * Printer setup using SMB Printer. * Printer setup using IPP setup under CUPS server. * Printer setup using SAMBA (as supplied with SuSE 9.0) I am out of ideas here. The application in question is old enough that it does not support networking and must talk to a local printer, otherwise I would have set things up under SuSE 9.0 and forced a share into play into the NT 4.0 box. Before I forget, NT 4.0 is running service pack 6. Anyone seen this kind of problem before? Sugestions? Thanks in advance, ...Paul -- Managing good programmers/engineers is tantamount to herding cats...
On Mon, 2004-02-16 at 23:34, Paul Penrod wrote:
Because of a very specialized medical program that requires Windows NT 4.0, I have had to attach this NT box to my SuSE 9.0 network. The problem is that I can not see the printer from YaST, nor can I see the NT box from SAMBA
Do you have File and Print Sharing configured in NT? If you don't, the linux box will never see the printer.
Here is what I have tried:
* Printer setup using SMB Printer. * Printer setup using IPP setup under CUPS server. * Printer setup using SAMBA (as supplied with SuSE 9.0)
I am out of ideas here. The application in question is old enough that it does not support networking and must talk to a local printer, otherwise I would have set things up under SuSE 9.0 and forced a share into play into the NT 4.0 box.
Would the application work if you captured the printer port from the network? Marshall
At 04:40 AM 2/17/2004, Marshall Heartley wrote:
On Mon, 2004-02-16 at 23:34, Paul Penrod wrote:
Because of a very specialized medical program that requires Windows NT 4.0, I have had to attach this NT box to my SuSE 9.0 network. The problem is that I can not see the printer from YaST, nor can I see the NT box from SAMBA
Do you have File and Print Sharing configured in NT? If you don't, the linux box will never see the printer.
I am not sure what you mean here. I have the printer set up as a shared device. Is there another setting I need to adjust ?
Here is what I have tried:
* Printer setup using SMB Printer. * Printer setup using IPP setup under CUPS server. * Printer setup using SAMBA (as supplied with SuSE 9.0)
I am out of ideas here. The application in question is old enough that it does not support networking and must talk to a local printer, otherwise I would have set things up under SuSE 9.0 and forced a share into play into the NT 4.0 box.
Would the application work if you captured the printer port from the network?
It probably would - except the printer in use is an HP 6MP and does not have network support built in.
Marshall
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Managing good programmers/engineers is tantamount to herding cats...
<snip>
Do you have File and Print Sharing configured in NT? If you don't, the linux box will never see the printer.
I am not sure what you mean here. I have the printer set up as a shared device. Is there another setting I need to adjust ?
We could use a bit more info. Is the NT machine in a domain or in a workgroup? If SAMBA is installed on SuSE 9, see what does the output of smbclient -L <host> say? Replace <host> with the netbios name of the machine.
Here is what I have tried:
Would the application work if you captured the printer port from the network?
It probably would - except the printer in use is an HP 6MP and does not have network support built in.
Ok I was assuming that the printer may have been on a print server. If the printer was on a server, then the suggestion that Ken suggested should work. Please answer the questions above and we will see if we can help you. Also try and post to the list so that others can help you. I may not have all the answers to help you. Marshall
At 07:05 AM 2/17/2004, Men in grey suits forced Marshall Heartley to type:
<snip>
Do you have File and Print Sharing configured in NT? If you don't, the linux box will never see the printer.
I am not sure what you mean here. I have the printer set up as a shared device. Is there another setting I need to adjust ?
We could use a bit more info.
Is the NT machine in a domain or in a workgroup?
The NT box is in a workgroup (ROSES). TCP/IP is the default protocol. NetBUI is not enabled. IPX/SPX is not enabled. The box is set up with a static IP address: 192.168.0.13, and connected to a hub, which is connected to a Router/Gateway (192.168.0.1). DNS resolution is provided externally by Verizon and the DNS IP's have been entered manually.
If SAMBA is installed on SuSE 9, see what does the output of smbclient -L <host> say? Replace <host> with the netbios name of the machine.
Here is what I have tried:
Would the application work if you captured the printer port from the network?
It probably would - except the printer in use is an HP 6MP and does not have network support built in.
Ok I was assuming that the printer may have been on a print server. If the printer was on a server, then the suggestion that Ken suggested should work.
Please answer the questions above and we will see if we can help you.
Also try and post to the list so that others can help you. I may not have all the answers to help you.
Marshall
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Managing good programmers/engineers is tantamount to herding cats...
<snip>
Is the NT machine in a domain or in a workgroup?
The NT box is in a workgroup (ROSES). TCP/IP is the default protocol. NetBUI is not enabled. IPX/SPX is not enabled. The box is set up with a static IP address: 192.168.0.13, and connected to a hub, which is connected to a Router/Gateway (192.168.0.1). DNS resolution is provided externally by Verizon and the DNS IP's have been entered manually.
What does smbclient -L 192.168.0.13 say?? Marshall
At 09:20 AM 2/17/2004, Marshall Heartley wrote:
<snip>
Is the NT machine in a domain or in a workgroup?
The NT box is in a workgroup (ROSES). TCP/IP is the default protocol. NetBUI is not enabled. IPX/SPX is not enabled. The box is set up with a static IP address: 192.168.0.13, and connected to a hub, which is connected to a Router/Gateway (192.168.0.1). DNS resolution is provided externally by Verizon and the DNS IP's have been entered manually.
What does smbclient -L 192.168.0.13 say??
Marshall
First, I need to apologize for some bad information. smbclient DOES see the NT box. Here is the output from the last run: Here is the output: axler@voodoo2:~> smbclient -L brandy added interface ip=192.168.0.10 bcast=192.168.0.255 nmask=255.255.255.0 Got a positive name query response from 192.168.0.13 ( 192.168.0.13 ) Password: session setup failed: NT_STATUS_LOGON_FAILURE axler@voodoo2:~> smbclient -L brandy added interface ip=192.168.0.10 bcast=192.168.0.255 nmask=255.255.255.0 Got a positive name query response from 192.168.0.13 ( 192.168.0.13 ) Password: Domain=[ROSES] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] Sharename Type Comment --------- ---- ------- D Disk Brandy Drive D: HP6MP Printer HP LaserJet 6MP PS ADMIN$ Disk Remote Admin HP6MP-PCL Printer HP LaserJet 6P/6MP - Standard HP6MP-B2 Printer \\BRANDY2\HP6MP IPC$ IPC Remote IPC C$ Disk Default share D$ Disk Default share print$ Disk Printer Drivers Server Comment --------- ------- BRANDY BRANDY2 Samba Server on Brandy2 Workgroup Master --------- ------- ROSES BRANDY axler@voodoo2:~> axler@voodoo2:~>
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Managing good programmers/engineers is tantamount to herding cats...
On Tuesday 17 February 2004 2:30 pm, Paul Penrod wrote:
First, I need to apologize for some bad information. smbclient DOES see the NT box.
I'll simply repost something I posted a while ago, which may get you through this: There are two separate configuration challenges: Windows client/Linux server, and Linux client/Windows server. To keep things straight, the server machine is the one that has the printer and the client machine is the one that wants to print something. I'm working with Windows ME, but I assume that most of this works for other Wins also. Linux client is the easier case, assuming that the Windows printer is working correctly within Windows. On the Windows side, you have to bring it up in Control Panel and give it a share name (WINPRINT, say). Now supposedly that should make it available for Linux printing without further ado under the name WINPRINT@HOST, but I have not been able to get that to work. So what you need to do is to create an appropriate printer (let's call it WPR) on the Linux client such that printing to that printer will cause the print file to print on the Windows server. There are three ways to create the printer: using the CUPS configurator via the local webpage http:// localhost:631/admin, using Yast2 via Hardware / Printer, or adding the necessary entries to the file /etc/cups/printers.conf. Using Yast2, you choose to add a printer named WPR. The critical choice is the next one, where you select to print via an SMB network server; the following choices are straightforward. Using the CUPS configurator, you choose Add Printer, then set the name as WPR and the location as the hostname of the Windows machine (I'm not sure if that's really necessary, though). For the device, choose Windows Printer via Samba. For the Device URI, choose smb://workgroup/HOST/WINPRINTER (you can usually omit the workgroup, though). The rest is straightforward. For the case of a Linux server and a Windows client, the configuration is best done via the Samba configuration program SWAT, available as a webpage at http://localhost:901. (Bug: you may need to run /etc/init.d/xinit restart to get SWAT to work.) You should create a spooling directory at /var/spool/ samba with all permissions turned on and the sticky bit (t) set, though /tmp can also be used for the spooling directory. Now go to the PRINTERS section and create a printer with the same name as the Linux printer you want to print on. Using any other name won't work. (The name is the same one you'd use in an lpr command.) Set the path to /var/spool/samba. Note that this is the path of the spool directory, not of the printer itself; /dev/lp0 will *not* work here. Set "guest OK", "printable", "browseable", and "available" all to "yes" and "printing to "CUPS". Now you can create the printer. Next, go to the GLOBALS section of SWAT and under Printing Options, set the printcap name to CUPS and printing to cups. Confirm the changes and you're ready to print to your new printer. To do all this under Yast2 (not possible in pre-9.0 versions of Yast2), you go to the Samba Server section of Network Services, then Next, then Advanced, then Add. Then add the new printer, again with the same name as the Linux printer you want to print on. The path should be /var/spool/samba as with SWAT. Now for the Windows side. Bring up Network Neighborhood, then look at the available hosts. One of them should be your Linux machine. Click on that to see what's available. The name of your printer should appear. Right-click on that, then choose Install. The rest should be straightforward, and you'll have a new printer in the Printers section of Control Panel. Paul Abrahams
Paul, First, a very big thank you for the help you and Marshall have provided thus far. The box in question I am working with is about 1000 miles away from me at the moment, so much of the information I have gleaned has been by phone and e-mail as folks in CA are helping me work though the problem. I wanted to take the time to apply your suggestions and advice before coming back to the forum with my results. I was hoping to come back with an "it works" statement and some details on how. Unfortunately, I have not made progress on that front, except that I have more data that I can submit for consideration. First attempt of the day involved clearing out samba, removing all print configurations from the SuSE box, and starting from a clean slate. Using smbclient, we pinged the NT box with both the netbios name and the IP address to see what we would get back. The NT box responded the same way each time showing all shared resources, including the printer shares labeled HP6MP (postscript driver) and HP6MP-PCL. Next we setup a simple share with SAMBA and attempted to copy a file from the NT box to the share. The shared directory BTW was left full open (777) so there were no permission issues, at least from the file system, to get in the way. In SAMBA we set the netmask to 0x111 so that we would have full read/write to the share, made the share Available, Browseable , Printable to FALSE, Read Only to FALSE, and set Guest OK to TRUE. We invoked the Network Neighborhood and found the SuSE box, then the shared directory. After opening the directory, we attempted to copy a file from the NT box to the new share. The copy failed for "Access Denied". We tried several different ways to convince the file to copy to the SuSE box, including destroying and re-creating the share, resetting permissions, forcing SAMBA to restart, etc. Nothing worked until, out of a whim, we rebooted the NT box, and viola! The share was not only visible but would accept the copy as well. Evidently, NT does a lousy job of updating it's network connections when things change. Armed with that observation, we started two copies of Konquerer and attempted to go the other direction by copying a file from SuSE to the NT box. The first window we pointed it at smb://ROSES/brandy and found our data drive (D:). Then we successfully copied a file to the D: drive on the NT box and copied back again to SuSE. Next we attempted to use YaST / Hardware / Printer to configure an SMB connection. The Host lookup did not show the NT box, so we entered in the IP address instead. Lookup on the queues returned nothing as well, so we entered the share name HP6MP in the hopes that it might get through anyway. Press the TEST button returned an error "Connection to ROSES failed!". Next we tried to establish an IPP connection with URI. We used the entry, the test did not prove successful. We also tried multiple combinations with CUPS to see if any of them would work. No joy. The person helping me with the test did not want to switch the printer cable to the SuSE box, as the NT box is stuffed into a cabinet that would require about 45 minutes of work to extricate and swap things around (very crowded). So, it appears the NT->Linux Printer Server option is not available to me at the moment. One final test we ran was with a Fedora Core machine. It found the printer and printed right to it with no hassles at all. Out of curiosity I went poking around to see what might be different about Fedora vs SuSE 9.0 in regards to SAMBA. It appears that Fedora is running SAMBA 3.0.2 while SuSE 9.0 is running 2.2.8a. I did not see anything in the release notes that would explain why SuSE should be having a hard time, but though it would be worth mentioning. Again, thanks in advance for you help and suggestions. ...Paul At 12:40 PM 2/17/2004, Paul W. Abrahams wrote:
On Tuesday 17 February 2004 2:30 pm, Paul Penrod wrote:
First, I need to apologize for some bad information. smbclient DOES see the NT box.
I'll simply repost something I posted a while ago, which may get you through this:
There are two separate configuration challenges: Windows client/Linux server, and Linux client/Windows server. To keep things straight, the server machine is the one that has the printer and the client machine is the one that wants to print something. I'm working with Windows ME, but I assume that most of this works for other Wins also.
Linux client is the easier case, assuming that the Windows printer is working correctly within Windows. On the Windows side, you have to bring it up in Control Panel and give it a share name (WINPRINT, say). Now supposedly that should make it available for Linux printing without further ado under the name WINPRINT@HOST, but I have not been able to get that to work.
So what you need to do is to create an appropriate printer (let's call it WPR) on the Linux client such that printing to that printer will cause the print file to print on the Windows server. There are three ways to create the printer: using the CUPS configurator via the local webpage http:// localhost:631/admin, using Yast2 via Hardware / Printer, or adding the necessary entries to the file /etc/cups/printers.conf.
Using Yast2, you choose to add a printer named WPR. The critical choice is the next one, where you select to print via an SMB network server; the following choices are straightforward.
Using the CUPS configurator, you choose Add Printer, then set the name as WPR and the location as the hostname of the Windows machine (I'm not sure if that's really necessary, though). For the device, choose Windows Printer via Samba. For the Device URI, choose
smb://workgroup/HOST/WINPRINTER
(you can usually omit the workgroup, though). The rest is straightforward.
For the case of a Linux server and a Windows client, the configuration is best done via the Samba configuration program SWAT, available as a webpage at http://localhost:901. (Bug: you may need to run /etc/init.d/xinit restart to get SWAT to work.) You should create a spooling directory at /var/spool/ samba with all permissions turned on and the sticky bit (t) set, though /tmp can also be used for the spooling directory. Now go to the PRINTERS section and create a printer with the same name as the Linux printer you want to print on. Using any other name won't work. (The name is the same one you'd use in an lpr command.) Set the path to /var/spool/samba. Note that this is the path of the spool directory, not of the printer itself; /dev/lp0 will *not* work here. Set "guest OK", "printable", "browseable", and "available" all to "yes" and "printing to "CUPS". Now you can create the printer.
Next, go to the GLOBALS section of SWAT and under Printing Options, set the printcap name to CUPS and printing to cups. Confirm the changes and you're ready to print to your new printer.
To do all this under Yast2 (not possible in pre-9.0 versions of Yast2), you go to the Samba Server section of Network Services, then Next, then Advanced, then Add. Then add the new printer, again with the same name as the Linux printer you want to print on. The path should be /var/spool/samba as with SWAT.
Now for the Windows side. Bring up Network Neighborhood, then look at the available hosts. One of them should be your Linux machine. Click on that to see what's available. The name of your printer should appear. Right-click on that, then choose Install. The rest should be straightforward, and you'll have a new printer in the Printers section of Control Panel.
Paul Abrahams
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Managing good programmers/engineers is tantamount to herding cats...
On 02/20/2004 07:23 AM, Paul Penrod wrote:
It appears that Fedora is running SAMBA 3.0.2 while SuSE 9.0 is running 2.2.8a.
Check out ftp://ftp.sernet.de/pub/samba if you think it might be samba. You can get 9.0 samba packages there. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
<snip>
Armed with that observation, we started two copies of Konquerer and attempted to go the other direction by copying a file from SuSE to the NT box. The first window we pointed it at smb://ROSES/brandy and found our data drive (D:). Then we successfully copied a file to the D: drive on the NT box and copied back again to SuSE.
This is a good sign.
Next we attempted to use YaST / Hardware / Printer to configure an SMB connection. The Host lookup did not show the NT box, so we entered in the IP address instead. Lookup on the queues returned nothing as well, so we entered the share name HP6MP in the hopes that it might get through anyway. Press the TEST button returned an error "Connection to ROSES failed!".
Did you make sure that the correct workgroup was entered in the workgroup box? What is the NT permissions on the printer? You may need to use a username and password in order to connect.
Next we tried to establish an IPP connection with URI. We used the entry, the test did not prove successful. We also tried multiple combinations with CUPS to see if any of them would work. No joy.
If this is NT4, I do not think that it natively does IPP. IPP came about with W2K I believe. I do not remember setting up IPP in NT4. I do remember that NT did have Print Services for Unix which should allow you to print to the printer via LPD. But you probably do not want another service running on this machine.
The person helping me with the test did not want to switch the printer cable to the SuSE box, as the NT box is stuffed into a cabinet that would require about 45 minutes of work to extricate and swap things around (very crowded). So, it appears the NT->Linux Printer Server option is not available to me at the moment.
OK we will see about getting it to work with the original plan A
One final test we ran was with a Fedora Core machine. It found the printer and printed right to it with no hassles at all. Out of curiosity I went poking around to see what might be different about Fedora vs SuSE 9.0 in regards to SAMBA. It appears that Fedora is running SAMBA 3.0.2 while SuSE 9.0 is running 2.2.8a. I did not see anything in the release notes that would explain why SuSE should be having a hard time, but though it would be worth mentioning.
Was there any differences in the smb.config files between the one from SuSE and the one from Fedora?
Again, thanks in advance for you help and suggestions.
Welcome Marshall
Hello, I didn't read the whole mail thread in detail but it seems http://portal.suse.com/sdb/en/2003/11/jsmeix_print-smb-90.html was not yet mentioned. Kind regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Mon, 2004-02-16 at 23:34, Paul Penrod wrote:
Because of a very specialized medical program that requires Windows NT 4.0, I have had to attach this NT box to my SuSE 9.0 network. The problem is that I can not see the printer from YaST, nor can I see the NT box from SAMBA.
Here is what I have tried:
* Printer setup using SMB Printer. * Printer setup using IPP setup under CUPS server. * Printer setup using SAMBA (as supplied with SuSE 9.0)
I am out of ideas here. The application in question is old enough that it does not support networking and must talk to a local printer, otherwise I would have set things up under SuSE 9.0 and forced a share into play into the NT 4.0 box.
Before I forget, NT 4.0 is running service pack 6.
Anyone seen this kind of problem before? Sugestions?
Thanks in advance,
...Paul
Put the printer on the network and use it on the NT box as follows: net use lpt1: \\computer\sharename_of_printer The application will think the printer is local. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Monday 16 February 2004 11:34 pm, Paul Penrod wrote:
Because of a very specialized medical program that requires Windows NT 4.0, I have had to attach this NT box to my SuSE 9.0 network. The problem is that I can
not
see the printer from YaST, nor can I see the NT box from SAMBA.
Here is what I have tried:
* Printer setup using SMB Printer. * Printer setup using IPP setup under CUPS server. * Printer setup using SAMBA (as supplied with SuSE 9.0)
The first question is what smbclient sees on the NT machine. If smbclient sees the printer, then the investigation path is different than if it does not. Paul Abrahams
At 07:28 AM 2/17/2004, Paul W. Abrahams wrote:
On Monday 16 February 2004 11:34 pm, Paul Penrod wrote:
Because of a very specialized medical program that requires Windows NT
4.0,
I have had to attach this NT box to my SuSE 9.0 network. The problem is that I can not see the printer from YaST, nor can I see the NT box from SAMBA.
Here is what I have tried:
* Printer setup using SMB Printer. * Printer setup using IPP setup under CUPS server. * Printer setup using SAMBA (as supplied with SuSE 9.0)
The first question is what smbclient sees on the NT machine. If smbclient sees the printer, then the investigation path is different than if it does not.
Paul Abrahams
The smbclient does not see the NT box at all. The NT box, however, can see the SuSE box and can reference a directory I published as a test. What has me puzzled is that a test Win2000 box I have setup has no problem seeing SAMBA shares on Fedora, SuSE, RedHat 9.0, or Mandrake. The only issue until this one was I had to make sure that I set "PRINTABLE" to false, otherwise the Win2000 box would treat the link like a printer.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Managing good programmers/engineers is tantamount to herding cats...
On Tuesday 17 February 2004 10:54 am, Paul Penrod wrote:
The smbclient does not see the NT box at all. The NT box, however, can see the SuSE box and can reference a directory I published as a test.
Unless you're somehow using smbclient incorrectly, which is probably not the case, that suggests that the problem is entirely on the NT side. If smbclient can't see the NT box, I doubt if there's a single useful thing you can do on the Linux side to get past it. So you've got an NT problem, not a Linux problem. Of course, once you have smbclient viewing the NT box, you may again have a LInux problem. If anyone else disagrees with this analysis, I can learn something. Paul Abrahams
participants (6)
-
Joe Morris (NTM) -
Johannes Meixner -
Kenneth Schneider -
Marshall Heartley -
Paul Penrod -
Paul W. Abrahams