If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Standalone network printer doesn't appear in network places
Hi,
Windows XP Pro, SP2. OKI C7300N printer. I've installed a standalone network printer (i.e. not connected to a particular computer). Its IP address (assigned by DHCP on my router) is 192.168.0.7. I've put it in the same MSHOME workgroup as the 3 computers on the network. I can ping it by IP address and by name fine from all 3 PCs. I've also run the Add Printer wizard by specifying a network printer and the URL http://192.168.0.7/ipp (the printer supports IPP - Internet Printing Protocol) and the printer now appears in Printers and Faxes as 'OKI C7300N on http://192.168.0.7.' I can print to it with no problem, however I have several questions: 1. Despite it being in the MSHOME workgroup, it doesn't appear in My Network Places - Entire Network - Microsoft Windows Network - MSHOME. Any ideas why? 2. What if DHCP assigns a different IP address the next time the printer is switched on? Will its current internet port http://192.168.0.7/ipp then be incorrect and printing therefore fail? 3. On the printer's Network Summary web page, the NetBEUI Status is shown as: Computer Name : OKI Workgroup Name : MSHOME Master Browser : ????? Is Master Browser being '?????' the problem? My aim, if at all possible, is to get the printer to appear in the MSHOME workgroup so I could then run the Add Printer wizard and browse for it by name instead of using the URL IPP method. Hope someone can help - thanks for any info or tips. |
Ads |
#2
|
|||
|
|||
On Tue, 29 Mar 2005 22:31:08 +0100, "J Williams" *email_address_deleted*
wrote: Hi, Windows XP Pro, SP2. OKI C7300N printer. I've installed a standalone network printer (i.e. not connected to a particular computer). Its IP address (assigned by DHCP on my router) is 192.168.0.7. I've put it in the same MSHOME workgroup as the 3 computers on the network. I can ping it by IP address and by name fine from all 3 PCs. I've also run the Add Printer wizard by specifying a network printer and the URL http://192.168.0.7/ipp (the printer supports IPP - Internet Printing Protocol) and the printer now appears in Printers and Faxes as 'OKI C7300N on http://192.168.0.7.' I can print to it with no problem, however I have several questions: 1. Despite it being in the MSHOME workgroup, it doesn't appear in My Network Places - Entire Network - Microsoft Windows Network - MSHOME. Any ideas why? 2. What if DHCP assigns a different IP address the next time the printer is switched on? Will its current internet port http://192.168.0.7/ipp then be incorrect and printing therefore fail? 3. On the printer's Network Summary web page, the NetBEUI Status is shown as: Computer Name : OKI Workgroup Name : MSHOME Master Browser : ????? Is Master Browser being '?????' the problem? My aim, if at all possible, is to get the printer to appear in the MSHOME workgroup so I could then run the Add Printer wizard and browse for it by name instead of using the URL IPP method. Hope someone can help - thanks for any info or tips. Is the actual name "OKI C7300N"? What operating system is on the other 3 computers? http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/print_choosing_a_printer_name.mspx Are you running NetBEUI, or NetBIOS Over TCP/IP? -- Cheers, Chuck Paranoia comes from experience - and is not necessarily a bad thing. My email is AT DOT actual address pchuck sonic net. |
#3
|
|||
|
|||
Hi Chuck,
Thanks for your reply. The 3 computers are all running XP Pro. The actual name (DNS host name) of the printer (listed as 'Computer Name' in the NetBEUI status mentioned in OP) is OKI. I can ping OKI and get replies. The name in 'OKI C7300N on http://192.168.168.7' (assigned by XP when I run the Add Printer wizard) comes from the System Name on the printer's General Network Settings page. I changed this to OKI but it made no difference. Protocols TCP/IP and NetBEUI are enabled on the printer. I'm not sure if I'm running NetBEUI or NetBIOS over TCP/IP ON the computers - Local Area Connection properties on 1 PC shows the following enabled: Client for Microsoft Networks File and Printer Sharing for Microsoft Networks QoS Packet Scheduler Internet Protocol (TCP/IP) I tried adding NWLink NetBIOS protocol but it didn't seem to make any difference. "Chuck" wrote in message ... On Tue, 29 Mar 2005 22:31:08 +0100, "J Williams" *email_address_deleted* wrote: Hi, Windows XP Pro, SP2. OKI C7300N printer. I've installed a standalone network printer (i.e. not connected to a particular computer). Its IP address (assigned by DHCP on my router) is 192.168.0.7. I've put it in the same MSHOME workgroup as the 3 computers on the network. I can ping it by IP address and by name fine from all 3 PCs. I've also run the Add Printer wizard by specifying a network printer and the URL http://192.168.0.7/ipp (the printer supports IPP - Internet Printing Protocol) and the printer now appears in Printers and Faxes as 'OKI C7300N on http://192.168.0.7.' I can print to it with no problem, however I have several questions: 1. Despite it being in the MSHOME workgroup, it doesn't appear in My Network Places - Entire Network - Microsoft Windows Network - MSHOME. Any ideas why? 2. What if DHCP assigns a different IP address the next time the printer is switched on? Will its current internet port http://192.168.0.7/ipp then be incorrect and printing therefore fail? 3. On the printer's Network Summary web page, the NetBEUI Status is shown as: Computer Name : OKI Workgroup Name : MSHOME Master Browser : ????? Is Master Browser being '?????' the problem? My aim, if at all possible, is to get the printer to appear in the MSHOME workgroup so I could then run the Add Printer wizard and browse for it by name instead of using the URL IPP method. Hope someone can help - thanks for any info or tips. Is the actual name "OKI C7300N"? What operating system is on the other 3 computers? http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/print_choosing_a_printer_name.mspx Are you running NetBEUI, or NetBIOS Over TCP/IP? -- Cheers, Chuck Paranoia comes from experience - and is not necessarily a bad thing. My email is AT DOT actual address pchuck sonic net. |
#4
|
|||
|
|||
I can avoid a potential problem if the printer's IP address changes by
specifying URL http://oki/ipp in Add Printer. I'd still like to understand why I can't browse the printer in Network Places. "J Williams" wrote in message ... Hi Chuck, Thanks for your reply. The 3 computers are all running XP Pro. The actual name (DNS host name) of the printer (listed as 'Computer Name' in the NetBEUI status mentioned in OP) is OKI. I can ping OKI and get replies. The name in 'OKI C7300N on http://192.168.168.7' (assigned by XP when I run the Add Printer wizard) comes from the System Name on the printer's General Network Settings page. I changed this to OKI but it made no difference. Protocols TCP/IP and NetBEUI are enabled on the printer. I'm not sure if I'm running NetBEUI or NetBIOS over TCP/IP ON the computers - Local Area Connection properties on 1 PC shows the following enabled: Client for Microsoft Networks File and Printer Sharing for Microsoft Networks QoS Packet Scheduler Internet Protocol (TCP/IP) I tried adding NWLink NetBIOS protocol but it didn't seem to make any difference. "Chuck" wrote in message ... On Tue, 29 Mar 2005 22:31:08 +0100, "J Williams" *email_address_deleted* wrote: Hi, Windows XP Pro, SP2. OKI C7300N printer. I've installed a standalone network printer (i.e. not connected to a particular computer). Its IP address (assigned by DHCP on my router) is 192.168.0.7. I've put it in the same MSHOME workgroup as the 3 computers on the network. I can ping it by IP address and by name fine from all 3 PCs. I've also run the Add Printer wizard by specifying a network printer and the URL http://192.168.0.7/ipp (the printer supports IPP - Internet Printing Protocol) and the printer now appears in Printers and Faxes as 'OKI C7300N on http://192.168.0.7.' I can print to it with no problem, however I have several questions: 1. Despite it being in the MSHOME workgroup, it doesn't appear in My Network Places - Entire Network - Microsoft Windows Network - MSHOME. Any ideas why? 2. What if DHCP assigns a different IP address the next time the printer is switched on? Will its current internet port http://192.168.0.7/ipp then be incorrect and printing therefore fail? 3. On the printer's Network Summary web page, the NetBEUI Status is shown as: Computer Name : OKI Workgroup Name : MSHOME Master Browser : ????? Is Master Browser being '?????' the problem? My aim, if at all possible, is to get the printer to appear in the MSHOME workgroup so I could then run the Add Printer wizard and browse for it by name instead of using the URL IPP method. Hope someone can help - thanks for any info or tips. Is the actual name "OKI C7300N"? What operating system is on the other 3 computers? http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/print_choosing_a_printer_name.mspx Are you running NetBEUI, or NetBIOS Over TCP/IP? -- Cheers, Chuck Paranoia comes from experience - and is not necessarily a bad thing. My email is AT DOT actual address pchuck sonic net. |
#5
|
|||
|
|||
On Wed, 30 Mar 2005 00:38:47 +0100, "J Williams"
wrote: I can avoid a potential problem if the printer's IP address changes by specifying URL http://oki/ipp in Add Printer. I'd still like to understand why I can't browse the printer in Network Places. "J Williams" wrote in message ... Hi Chuck, Thanks for your reply. The 3 computers are all running XP Pro. The actual name (DNS host name) of the printer (listed as 'Computer Name' in the NetBEUI status mentioned in OP) is OKI. I can ping OKI and get replies. The name in 'OKI C7300N on http://192.168.168.7' (assigned by XP when I run the Add Printer wizard) comes from the System Name on the printer's General Network Settings page. I changed this to OKI but it made no difference. Protocols TCP/IP and NetBEUI are enabled on the printer. I'm not sure if I'm running NetBEUI or NetBIOS over TCP/IP ON the computers - Local Area Connection properties on 1 PC shows the following enabled: Client for Microsoft Networks File and Printer Sharing for Microsoft Networks QoS Packet Scheduler Internet Protocol (TCP/IP) I tried adding NWLink NetBIOS protocol but it didn't seem to make any difference. OK, if the list of protocols just includes the 4 above, that is NBT, not NetBEUI. Please, keep things simple, don't add NetBEUI or IPX/SPX, unless you have ONE special configuration which we will get to. Please start by making sure that only those four protocols are present. I've worked with networked printers, lots of them, but mostly they were network connected under TCP/IP, and the share (and printer queue) was managed by a server (actual computer) running NBT, and providing the named share. I've never heard of a network connected printer that runs NetBIOS Over TCP/IP, nor one that does its own queue management. How is the printer physically connected to the network? I Googled and Yahooed (and never found a link to the manufacturer Oki - I wonder why?), but all the articles referred to it as a Personal Printer (ie to be connected to a computer for queue management and sharing). And this PC World article: http://www.pcworld.com/reviews/article/0,aid,109563,src,ov,00.asp Oki provides comprehensive printed and on-screen documentation, including a 500-page manual on the printer hardware and a 230-page manual on network management, both in PDF format. However, based on the difficulties we encountered, only experienced network administrators should attempt to install the C7300n on a Windows print server with Oki's PrintSuperVision management software. I wonder why they wrote that? -- Cheers, Chuck Paranoia comes from experience - and is not necessarily a bad thing. My email is AT DOT actual address pchuck sonic net. |
#6
|
|||
|
|||
Chuck thought carefully and wrote on 3/29/2005 4:19 PM: How is the printer physically connected to the network? I Googled and Yahooed (and never found a link to the manufacturer Oki - I wonder why?), but all the articles referred to it as a Personal Printer (ie to be connected to a computer for queue management and sharing). 'cuse me Chuck while I butt in: http://www.okidata.com/mkt/html/nf/C7300-C7500Home.html The C7300N comes with Ethernet, firewire and parallel ports and it's own internal print server and web-based printer manager. Lance ***** |
#7
|
|||
|
|||
On Tue, 29 Mar 2005 22:00:35 -0800, Lance *email_address_deleted* wrote:
Chuck thought carefully and wrote on 3/29/2005 4:19 PM: How is the printer physically connected to the network? I Googled and Yahooed (and never found a link to the manufacturer Oki - I wonder why?), but all the articles referred to it as a Personal Printer (ie to be connected to a computer for queue management and sharing). 'cuse me Chuck while I butt in: http://www.okidata.com/mkt/html/nf/C7300-C7500Home.html The C7300N comes with Ethernet, firewire and parallel ports and it's own internal print server and web-based printer manager. Lance ***** Thanks for the link, Lance. So the printer has Ethernet. And it supports IPP - which IIRC is a TCP/IP protocol. TCP/IP does not provide named shares. For a named share (something visible in Network Neighborhood), my guess is you have to set up a print queue on a Windows XP server, which then provides the share. I have worked with HP Laserjets (not Deskjets - those are another story) which will let you configure IPX/SPX for named discovery by the HP Printer Management client. But that is simply to display printer status, manage print cartridge replacement, etc. For named shares, named print queue management, etc, you still have to configure the printer on a Windows server, and the printer queue seen in Network Neighborhood, by all the client workstations, will be a component of the Windows server. It sounds to me like you installed it on the one Windows XP Pro computer, as "http://192.168.0.7", with the Oki IPP driver. If you want to see the printer as a named share, you'll have to share it from the Windows XP computer. Will the IPP driver deal successfully with its possibly changing ip address (a result of using DHCP for address assignment)? You may need to read the printer manual to find out how that works. If you don't want to share the printer from the one Windows XP computer, my guess is that you'll have to install the IPP client on each computer, and refer to the printer as "OKI C7300N on http://192.168.0.7". That's not a named share, so you won't see it in Network Neighborhood. -- Cheers, Chuck Paranoia comes from experience - and is not necessarily a bad thing. My email is AT DOT actual address pchuck sonic net. |
#8
|
|||
|
|||
"Chuck" wrote in message ... On Tue, 29 Mar 2005 22:00:35 -0800, Lance *email_address_deleted* wrote: Chuck thought carefully and wrote on 3/29/2005 4:19 PM: How is the printer physically connected to the network? I Googled and Yahooed (and never found a link to the manufacturer Oki - I wonder why?), but all the articles referred to it as a Personal Printer (ie to be connected to a computer for queue management and sharing). 'cuse me Chuck while I butt in: http://www.okidata.com/mkt/html/nf/C7300-C7500Home.html The C7300N comes with Ethernet, firewire and parallel ports and it's own internal print server and web-based printer manager. Lance ***** Thanks for the link, Lance. So the printer has Ethernet. And it supports IPP - which IIRC is a TCP/IP protocol. TCP/IP does not provide named shares. For a named share (something visible in Network Neighborhood), my guess is you have to set up a print queue on a Windows XP server, which then provides the share. I have worked with HP Laserjets (not Deskjets - those are another story) which will let you configure IPX/SPX for named discovery by the HP Printer Management client. But that is simply to display printer status, manage print cartridge replacement, etc. For named shares, named print queue management, etc, you still have to configure the printer on a Windows server, and the printer queue seen in Network Neighborhood, by all the client workstations, will be a component of the Windows server. It sounds to me like you installed it on the one Windows XP Pro computer, as "http://192.168.0.7", with the Oki IPP driver. If you want to see the printer as a named share, you'll have to share it from the Windows XP computer. Will the IPP driver deal successfully with its possibly changing ip address (a result of using DHCP for address assignment)? You may need to read the printer manual to find out how that works. If you don't want to share the printer from the one Windows XP computer, my guess is that you'll have to install the IPP client on each computer, and refer to the printer as "OKI C7300N on http://192.168.0.7". That's not a named share, so you won't see it in Network Neighborhood. Hi Chuck, And thanks for your help. You are right about the IPP method - that's the one I've used. The printer is connected by Ethernet to a switch box which is connected to my router. From what you say, I now understand why the printer won't appear in Network Neighbourhood unless I install it as a local/network printer attached to one of my computers. But then it's dependent on that computer being on. Thinking logically, a standalone network printer won't appear in 'Microsoft Windows Network' because it isn't a Windows machine! The OKI installation CD1 allows me to set up the printer as a Windows share name, or directly as a network printer. The latter also installs 'OKI LPR' which is a system tray utility for TCP/IP printing, plus network drivers and spool directories. Because the printer supports IPP, I can add it by IP address http://198.168.0.7/ipp, or better still name http://oki/ipp. The client machines adding the printer just need access to the PCL Driver (Network) file downloaded from http://my.okidata.com/PP-C7300n.nsf?opendatabase. So overall this method is easier more lightweight than using OKI LPR. |
#9
|
|||
|
|||
On Wed, 30 Mar 2005 13:03:49 +0100, "J Williams"
wrote: "Chuck" wrote in message .. . On Tue, 29 Mar 2005 22:00:35 -0800, Lance *email_address_deleted* wrote: Chuck thought carefully and wrote on 3/29/2005 4:19 PM: How is the printer physically connected to the network? I Googled and Yahooed (and never found a link to the manufacturer Oki - I wonder why?), but all the articles referred to it as a Personal Printer (ie to be connected to a computer for queue management and sharing). 'cuse me Chuck while I butt in: http://www.okidata.com/mkt/html/nf/C7300-C7500Home.html The C7300N comes with Ethernet, firewire and parallel ports and it's own internal print server and web-based printer manager. Lance ***** Thanks for the link, Lance. So the printer has Ethernet. And it supports IPP - which IIRC is a TCP/IP protocol. TCP/IP does not provide named shares. For a named share (something visible in Network Neighborhood), my guess is you have to set up a print queue on a Windows XP server, which then provides the share. I have worked with HP Laserjets (not Deskjets - those are another story) which will let you configure IPX/SPX for named discovery by the HP Printer Management client. But that is simply to display printer status, manage print cartridge replacement, etc. For named shares, named print queue management, etc, you still have to configure the printer on a Windows server, and the printer queue seen in Network Neighborhood, by all the client workstations, will be a component of the Windows server. It sounds to me like you installed it on the one Windows XP Pro computer, as "http://192.168.0.7", with the Oki IPP driver. If you want to see the printer as a named share, you'll have to share it from the Windows XP computer. Will the IPP driver deal successfully with its possibly changing ip address (a result of using DHCP for address assignment)? You may need to read the printer manual to find out how that works. If you don't want to share the printer from the one Windows XP computer, my guess is that you'll have to install the IPP client on each computer, and refer to the printer as "OKI C7300N on http://192.168.0.7". That's not a named share, so you won't see it in Network Neighborhood. Hi Chuck, And thanks for your help. You are right about the IPP method - that's the one I've used. The printer is connected by Ethernet to a switch box which is connected to my router. From what you say, I now understand why the printer won't appear in Network Neighbourhood unless I install it as a local/network printer attached to one of my computers. But then it's dependent on that computer being on. Thinking logically, a standalone network printer won't appear in 'Microsoft Windows Network' because it isn't a Windows machine! The OKI installation CD1 allows me to set up the printer as a Windows share name, or directly as a network printer. The latter also installs 'OKI LPR' which is a system tray utility for TCP/IP printing, plus network drivers and spool directories. Because the printer supports IPP, I can add it by IP address http://198.168.0.7/ipp, or better still name http://oki/ipp. The client machines adding the printer just need access to the PCL Driver (Network) file downloaded from http://my.okidata.com/PP-C7300n.nsf?opendatabase. So overall this method is easier more lightweight than using OKI LPR. I think you're getting the idea. You appear to have 3 choices. 1) Use IPP for all 4 computers. Install the IPP client on all 4 computers, and you will see the printer under "Printers and Faxes" on all 4 computers. 2) Use IPP for one computer. Install the IPP client on the main XP computer, and share the printer out from the main computer. See the printer under Network Neighborhood on 3 client computers. 3) Use Windows Networking on the printer, and setup a named share there. See the printer under Network Neighborhood on all 4 client computers. Option 1 is the simplest. Install a driver on each client computer, see the printer under Printers and Faxes, and use it as a network printer. Option 2 is the choice which PC World recommends "... only experienced network administrators should attempt to install the C7300n on a Windows print server with Oki's PrintSuperVision management software." Sharing a printer from a print server isn't magical. The sharing has to be supported by the vendor, and has to work with all the variances of the operating system. And we all know how variant Windows is. Option 3 is the one that intrigues me, though. The printer specs (link provided by Lance, thanks Lance) mentions an optional 10G hard drive. Does the printer operating system come with some portion of Windows? Again, Windows share names are Windows functions, so there has to be some Windows component in the printer operating system. Please let us know what you decide to do. -- Cheers, Chuck Paranoia comes from experience - and is not necessarily a bad thing. My email is AT DOT actual address pchuck sonic net. |
#10
|
|||
|
|||
In article ,
Chuck wrote: On Wed, 30 Mar 2005 00:38:47 +0100, "J Williams" wrote: I can avoid a potential problem if the printer's IP address changes by specifying URL http://oki/ipp in Add Printer. I'd still like to understand why I can't browse the printer in Network Places. "J Williams" wrote in message ... Hi Chuck, Thanks for your reply. The 3 computers are all running XP Pro. The actual name (DNS host name) of the printer (listed as 'Computer Name' in the NetBEUI status mentioned in OP) is OKI. I can ping OKI and get replies. The name in 'OKI C7300N on http://192.168.168.7' (assigned by XP when I run the Add Printer wizard) comes from the System Name on the printer's General Network Settings page. I changed this to OKI but it made no difference. Protocols TCP/IP and NetBEUI are enabled on the printer. I'm not sure if I'm running NetBEUI or NetBIOS over TCP/IP ON the computers - Local Area Connection properties on 1 PC shows the following enabled: Client for Microsoft Networks File and Printer Sharing for Microsoft Networks QoS Packet Scheduler Internet Protocol (TCP/IP) I tried adding NWLink NetBIOS protocol but it didn't seem to make any difference. OK, if the list of protocols just includes the 4 above, that is NBT, not NetBEUI. Please, keep things simple, don't add NetBEUI or IPX/SPX, unless you have ONE special configuration which we will get to. Please start by making sure that only those four protocols are present. I've worked with networked printers, lots of them, but mostly they were network connected under TCP/IP, and the share (and printer queue) was managed by a server (actual computer) running NBT, and providing the named share. I've never heard of a network connected printer that runs NetBIOS Over TCP/IP, nor one that does its own queue management. My favorite way to set up a shared printer is with with the lpr/lprd (TCP) protocol, which every jetdirect card and printserver appliance I've ever seen supports. All versions of windows can play but the setup is different for 98, NT4, w2k, and XP. Thank you, Bill. There is no server computer. All the machines talk directly to the printer. Each of the computers queue their own files on their local disk. It's great in a mixed Windows/Unix environment. It's nice in a small office with a workgroup LAN but no server. XP suppert is great. I can imagine that a really, really fast laser printer would justify a local computer as server to stage work and keep the printer 100% busy but if you've got that budget then one more computer isn't a big expense. -- a d y k e s @ p a n i x . c o m Don't blame me. I voted for Gore. |
#12
|
|||
|
|||
In article ,
Chuck wrote: On 30 Mar 2005 11:46:34 -0500, (Al Dykes) wrote: In article , Chuck wrote: On Wed, 30 Mar 2005 00:38:47 +0100, "J Williams" wrote: I can avoid a potential problem if the printer's IP address changes by specifying URL http://oki/ipp in Add Printer. I'd still like to understand why I can't browse the printer in Network Places. "J Williams" wrote in message ... Hi Chuck, Thanks for your reply. The 3 computers are all running XP Pro. The actual name (DNS host name) of the printer (listed as 'Computer Name' in the NetBEUI status mentioned in OP) is OKI. I can ping OKI and get replies. The name in 'OKI C7300N on http://192.168.168.7' (assigned by XP when I run the Add Printer wizard) comes from the System Name on the printer's General Network Settings page. I changed this to OKI but it made no difference. Protocols TCP/IP and NetBEUI are enabled on the printer. I'm not sure if I'm running NetBEUI or NetBIOS over TCP/IP ON the computers - Local Area Connection properties on 1 PC shows the following enabled: Client for Microsoft Networks File and Printer Sharing for Microsoft Networks QoS Packet Scheduler Internet Protocol (TCP/IP) I tried adding NWLink NetBIOS protocol but it didn't seem to make any difference. OK, if the list of protocols just includes the 4 above, that is NBT, not NetBEUI. Please, keep things simple, don't add NetBEUI or IPX/SPX, unless you have ONE special configuration which we will get to. Please start by making sure that only those four protocols are present. I've worked with networked printers, lots of them, but mostly they were network connected under TCP/IP, and the share (and printer queue) was managed by a server (actual computer) running NBT, and providing the named share. I've never heard of a network connected printer that runs NetBIOS Over TCP/IP, nor one that does its own queue management. My favorite way to set up a shared printer is with with the lpr/lprd (TCP) protocol, which every jetdirect card and printserver appliance I've ever seen supports. All versions of windows can play but the setup is different for 98, NT4, w2k, and XP. Thank you, Bill. There is no server computer. All the machines talk directly to the printer. Each of the computers queue their own files on their local disk. It's great in a mixed Windows/Unix environment. It's nice in a small office with a workgroup LAN but no server. XP suppert is great. I can imagine that a really, really fast laser printer would justify a local computer as server to stage work and keep the printer 100% busy but if you've got that budget then one more computer isn't a big expense. Peer-peer queue management is a good idea, in a mixed environment where everybody plays fair, and nobody needs special priority. How do the multiple queues get merged on the printer? LPR/LPD (TCP/IP Native) or Named Shares (Windows Networking) both have advantages and disadvantages. LPR/LPD is not unique to Windows platforms, so it is useful for generating reports on servers and mainframes of numerous brands, and printing reports locally in a Windows centric network. But native LPR/LPD doesn't provide named shares, so folks can't see the printers in Network Neighborhood. And some small printers don't support LPR/LPD. Nor are all software products capable of formatting reports for LPR/LPD printing. Once set up it's a standard WIndows GUI printer. I can't imaging anything that would print to a locally-attached printer that wouldn't work on an LPR printer. DOS apps have the same pronblem they have on any networked printer. It shows up as an icon in the printer group. There may be some printers with fancy management/status capabilities that LPR clients can't see but I've never compe across them myself. -- a d y k e s @ p a n i x . c o m Don't blame me. I voted for Gore. |
#13
|
|||
|
|||
"Chuck" wrote in message ... On Wed, 30 Mar 2005 13:03:49 +0100, "J Williams" wrote: "Chuck" wrote in message . .. On Tue, 29 Mar 2005 22:00:35 -0800, Lance *email_address_deleted* wrote: Chuck thought carefully and wrote on 3/29/2005 4:19 PM: How is the printer physically connected to the network? I Googled and Yahooed (and never found a link to the manufacturer Oki - I wonder why?), but all the articles referred to it as a Personal Printer (ie to be connected to a computer for queue management and sharing). 'cuse me Chuck while I butt in: http://www.okidata.com/mkt/html/nf/C7300-C7500Home.html The C7300N comes with Ethernet, firewire and parallel ports and it's own internal print server and web-based printer manager. Lance ***** Thanks for the link, Lance. So the printer has Ethernet. And it supports IPP - which IIRC is a TCP/IP protocol. TCP/IP does not provide named shares. For a named share (something visible in Network Neighborhood), my guess is you have to set up a print queue on a Windows XP server, which then provides the share. I have worked with HP Laserjets (not Deskjets - those are another story) which will let you configure IPX/SPX for named discovery by the HP Printer Management client. But that is simply to display printer status, manage print cartridge replacement, etc. For named shares, named print queue management, etc, you still have to configure the printer on a Windows server, and the printer queue seen in Network Neighborhood, by all the client workstations, will be a component of the Windows server. It sounds to me like you installed it on the one Windows XP Pro computer, as "http://192.168.0.7", with the Oki IPP driver. If you want to see the printer as a named share, you'll have to share it from the Windows XP computer. Will the IPP driver deal successfully with its possibly changing ip address (a result of using DHCP for address assignment)? You may need to read the printer manual to find out how that works. If you don't want to share the printer from the one Windows XP computer, my guess is that you'll have to install the IPP client on each computer, and refer to the printer as "OKI C7300N on http://192.168.0.7". That's not a named share, so you won't see it in Network Neighborhood. Hi Chuck, And thanks for your help. You are right about the IPP method - that's the one I've used. The printer is connected by Ethernet to a switch box which is connected to my router. From what you say, I now understand why the printer won't appear in Network Neighbourhood unless I install it as a local/network printer attached to one of my computers. But then it's dependent on that computer being on. Thinking logically, a standalone network printer won't appear in 'Microsoft Windows Network' because it isn't a Windows machine! The OKI installation CD1 allows me to set up the printer as a Windows share name, or directly as a network printer. The latter also installs 'OKI LPR' which is a system tray utility for TCP/IP printing, plus network drivers and spool directories. Because the printer supports IPP, I can add it by IP address http://198.168.0.7/ipp, or better still name http://oki/ipp. The client machines adding the printer just need access to the PCL Driver (Network) file downloaded from http://my.okidata.com/PP-C7300n.nsf?opendatabase. So overall this method is easier more lightweight than using OKI LPR. I think you're getting the idea. You appear to have 3 choices. 1) Use IPP for all 4 computers. Install the IPP client on all 4 computers, and you will see the printer under "Printers and Faxes" on all 4 computers. 2) Use IPP for one computer. Install the IPP client on the main XP computer, and share the printer out from the main computer. See the printer under Network Neighborhood on 3 client computers. 3) Use Windows Networking on the printer, and setup a named share there. See the printer under Network Neighborhood on all 4 client computers. Option 1 is the simplest. Install a driver on each client computer, see the printer under Printers and Faxes, and use it as a network printer. Option 2 is the choice which PC World recommends "... only experienced network administrators should attempt to install the C7300n on a Windows print server with Oki's PrintSuperVision management software." Sharing a printer from a print server isn't magical. The sharing has to be supported by the vendor, and has to work with all the variances of the operating system. And we all know how variant Windows is. Option 3 is the one that intrigues me, though. The printer specs (link provided by Lance, thanks Lance) mentions an optional 10G hard drive. Does the printer operating system come with some portion of Windows? Again, Windows share names are Windows functions, so there has to be some Windows component in the printer operating system. Please let us know what you decide to do. Hi Chuck, I went with Option 1. Option 3 is interesting, I agree. According to the doco, the optional hard drive is for local spooling and storage of documents for printing on demand. The printer's OS doesn't come with Windows and installing some sort of OS - Windows, MacOS or Netware - on the hard drive would be an interesting exercise (for a rainy day). The C7300N has TCP/IP, NetBEUI, NetWare, EtherTalk and IPP protocols as standard so getting it to run one of these OS's might be possible. It even has Telnet and ftp! |
#14
|
|||
|
|||
On Wed, 30 Mar 2005 23:44:40 +0100, "J Williams"
wrote: "Chuck" wrote in message .. . On Wed, 30 Mar 2005 13:03:49 +0100, "J Williams" wrote: "Chuck" wrote in message ... On Tue, 29 Mar 2005 22:00:35 -0800, Lance *email_address_deleted* wrote: Chuck thought carefully and wrote on 3/29/2005 4:19 PM: How is the printer physically connected to the network? I Googled and Yahooed (and never found a link to the manufacturer Oki - I wonder why?), but all the articles referred to it as a Personal Printer (ie to be connected to a computer for queue management and sharing). 'cuse me Chuck while I butt in: http://www.okidata.com/mkt/html/nf/C7300-C7500Home.html The C7300N comes with Ethernet, firewire and parallel ports and it's own internal print server and web-based printer manager. Lance ***** Thanks for the link, Lance. So the printer has Ethernet. And it supports IPP - which IIRC is a TCP/IP protocol. TCP/IP does not provide named shares. For a named share (something visible in Network Neighborhood), my guess is you have to set up a print queue on a Windows XP server, which then provides the share. I have worked with HP Laserjets (not Deskjets - those are another story) which will let you configure IPX/SPX for named discovery by the HP Printer Management client. But that is simply to display printer status, manage print cartridge replacement, etc. For named shares, named print queue management, etc, you still have to configure the printer on a Windows server, and the printer queue seen in Network Neighborhood, by all the client workstations, will be a component of the Windows server. It sounds to me like you installed it on the one Windows XP Pro computer, as "http://192.168.0.7", with the Oki IPP driver. If you want to see the printer as a named share, you'll have to share it from the Windows XP computer. Will the IPP driver deal successfully with its possibly changing ip address (a result of using DHCP for address assignment)? You may need to read the printer manual to find out how that works. If you don't want to share the printer from the one Windows XP computer, my guess is that you'll have to install the IPP client on each computer, and refer to the printer as "OKI C7300N on http://192.168.0.7". That's not a named share, so you won't see it in Network Neighborhood. Hi Chuck, And thanks for your help. You are right about the IPP method - that's the one I've used. The printer is connected by Ethernet to a switch box which is connected to my router. From what you say, I now understand why the printer won't appear in Network Neighbourhood unless I install it as a local/network printer attached to one of my computers. But then it's dependent on that computer being on. Thinking logically, a standalone network printer won't appear in 'Microsoft Windows Network' because it isn't a Windows machine! The OKI installation CD1 allows me to set up the printer as a Windows share name, or directly as a network printer. The latter also installs 'OKI LPR' which is a system tray utility for TCP/IP printing, plus network drivers and spool directories. Because the printer supports IPP, I can add it by IP address http://198.168.0.7/ipp, or better still name http://oki/ipp. The client machines adding the printer just need access to the PCL Driver (Network) file downloaded from http://my.okidata.com/PP-C7300n.nsf?opendatabase. So overall this method is easier more lightweight than using OKI LPR. I think you're getting the idea. You appear to have 3 choices. 1) Use IPP for all 4 computers. Install the IPP client on all 4 computers, and you will see the printer under "Printers and Faxes" on all 4 computers. 2) Use IPP for one computer. Install the IPP client on the main XP computer, and share the printer out from the main computer. See the printer under Network Neighborhood on 3 client computers. 3) Use Windows Networking on the printer, and setup a named share there. See the printer under Network Neighborhood on all 4 client computers. Option 1 is the simplest. Install a driver on each client computer, see the printer under Printers and Faxes, and use it as a network printer. Option 2 is the choice which PC World recommends "... only experienced network administrators should attempt to install the C7300n on a Windows print server with Oki's PrintSuperVision management software." Sharing a printer from a print server isn't magical. The sharing has to be supported by the vendor, and has to work with all the variances of the operating system. And we all know how variant Windows is. Option 3 is the one that intrigues me, though. The printer specs (link provided by Lance, thanks Lance) mentions an optional 10G hard drive. Does the printer operating system come with some portion of Windows? Again, Windows share names are Windows functions, so there has to be some Windows component in the printer operating system. Please let us know what you decide to do. Hi Chuck, I went with Option 1. Option 3 is interesting, I agree. According to the doco, the optional hard drive is for local spooling and storage of documents for printing on demand. The printer's OS doesn't come with Windows and installing some sort of OS - Windows, MacOS or Netware - on the hard drive would be an interesting exercise (for a rainy day). The C7300N has TCP/IP, NetBEUI, NetWare, EtherTalk and IPP protocols as standard so getting it to run one of these OS's might be possible. It even has Telnet and ftp! Option 1 would be my choice too. I would maybe go with TCP/IP, or IPP, but not NetBEUI or Netware - those are extra protocols that you don't need cluttering up your LAN. IPP and individual drivers on each computer should be stable and make each computer access equally. I'd still wonder what portion of Windows is on the printer to provide NetBEUI (NetBIOS Over TCP/IP maybe?). Knowing that there has recently been an alert for HP PCL / JetAdmin, I'm not sure I'd want a piece of Windows on a printer if I didn't know what piece is there and how to secure it. So option 1 definitely would be my choice. -- Cheers, Chuck Paranoia comes from experience - and is not necessarily a bad thing. My email is AT DOT actual address pchuck sonic net. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Divide by zero error on printer access 0xC0000094 | Franz Regensburger | Printing and Faxing with Windows XP | 1 | March 21st 06 04:41 PM |
Installing default network printer for all users | Gilles | Printing and Faxing with Windows XP | 2 | April 8th 05 07:53 AM |
Network Printer Problem | [email protected] | Networking and the Internet with Windows XP | 16 | October 23rd 04 05:22 PM |
wireless network..but Printer is not sharing nor can create wo | Rajmahal | Printing and Faxing with Windows XP | 2 | July 24th 04 07:08 AM |
wireless network..but Printer is not sharing nor can create wo | Rajmahal | Printing and Faxing with Windows XP | 1 | July 24th 04 07:08 AM |