Too many names

Posted: 12-20-2008, 09:47 PM
From the manifacture, the printer has a netbios name, a model number, its
driver's name, its LPD queue name

On the server, the administrator assigns a print queue name and an IP
address.

Please, what name is used for the server's print queue name and what's the
purpose of it.
On the other hand, why do we need the LPD queue name if we send the print
job to printer's IP address?

Lately, printers manufactures allow any remote queue name for LPD queue name
.... how does that work compare to the specific LPD queues names?

Thanks in advance!


Too many names


Responses to "Too many names"

Alan Morris [MSFT]
Guest
Posts: n/a
 
Re: Too many names
Posted: 12-24-2008, 05:01 AM
One can only send data over LPD/ lpr protocol on an IPv4 or IPv6 transport.

Each manufacture can designate how to implement the LPD spec, some only
accept data to a specific queue name and others will accept to any name.


So far this you are not really asking a Windows question but rather
something for the printer vendor.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"ITNews" <ITNews@net.it> wrote in message
news:%23zrdPyuYJHA.760@TK2MSFTNGP02.phx.gbl...
> From the manifacture, the printer has a netbios name, a model number, its
> driver's name, its LPD queue name
>
> On the server, the administrator assigns a print queue name and an IP
> address.
>
> Please, what name is used for the server's print queue name and what's the
> purpose of it.
> On the other hand, why do we need the LPD queue name if we send the print
> job to printer's IP address?
>
> Lately, printers manufactures allow any remote queue name for LPD queue
> name ... how does that work compare to the specific LPD queues names?
>
> Thanks in advance!
>
>

Alan Morris [MSFT]
Guest
Posts: n/a
 
Re: Too many names
Posted: 12-24-2008, 05:01 AM
One can only send data over LPD/ lpr protocol on an IPv4 or IPv6 transport.

Each manufacture can designate how to implement the LPD spec, some only
accept data to a specific queue name and others will accept to any name.


So far this you are not really asking a Windows question but rather
something for the printer vendor.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"ITNews" <ITNews@net.it> wrote in message
news:%23zrdPyuYJHA.760@TK2MSFTNGP02.phx.gbl...
> From the manifacture, the printer has a netbios name, a model number, its
> driver's name, its LPD queue name
>
> On the server, the administrator assigns a print queue name and an IP
> address.
>
> Please, what name is used for the server's print queue name and what's the
> purpose of it.
> On the other hand, why do we need the LPD queue name if we send the print
> job to printer's IP address?
>
> Lately, printers manufactures allow any remote queue name for LPD queue
> name ... how does that work compare to the specific LPD queues names?
>
> Thanks in advance!
>
>

ITNews
Guest
Posts: n/a
 
Re: Too many names
Posted: 12-24-2008, 06:36 PM
Hello Mr. Morris.
Sorry, I realize, I asked 3 questions and thank you for answering the 2nd
one.
I also realize that the print queue name is different from the printer queue
name, which I was referring to.

Therefore, my first question is regarding the printer queue names on the
Windows environment, the printer queue names created by administrators.
" Please, what name is used for the server's printer queue name and what's
the purpose of it."

I guess I found the 2nd part of my 2nd question, the purpose of the server's
printer queue name is to resolve the name into the IP address, although I do
not understand how are the A(host) and PTR records entered/updated in the
DNS in an AD environment and if printers use ddns like workstations. On the
other hand, if this printer queue name is to resolve the printer's name into
the IP address why would we experience ghost printers? Don't DHCP and DNS
keep in touch? lol


The first part of my 2nd question though is where I need some help. Out of
so many printer names that I mentioned in my original post, which one is
used for the server's printer queue name, please. Is it the NetBIOS name of
the printer, or could it be any name?

Although it may seem like I have many questions, everything is related to
one thing only: the printer queue name.


Any help / link will be appreciated!




what is the

"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:O8ShlSYZJHA.1352@TK2MSFTNGP03.phx.gbl...
> One can only send data over LPD/ lpr protocol on an IPv4 or IPv6
> transport.
>
> Each manufacture can designate how to implement the LPD spec, some only
> accept data to a specific queue name and others will accept to any name.
>
>
> So far this you are not really asking a Windows question but rather
> something for the printer vendor.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "ITNews" <ITNews@net.it> wrote in message
> news:%23zrdPyuYJHA.760@TK2MSFTNGP02.phx.gbl...
>> From the manifacture, the printer has a netbios name, a model number, its
>> driver's name, its LPD queue name
>>
>> On the server, the administrator assigns a print queue name and an IP
>> address.
>>
>> Please, what name is used for the server's print queue name and what's
>> the purpose of it.
>> On the other hand, why do we need the LPD queue name if we send the print
>> job to printer's IP address?
>>
>> Lately, printers manufactures allow any remote queue name for LPD queue
>> name ... how does that work compare to the specific LPD queues names?
>>
>> Thanks in advance!
>>
>>
>
>

ITNews
Guest
Posts: n/a
 
Re: Too many names
Posted: 12-24-2008, 06:36 PM
Hello Mr. Morris.
Sorry, I realize, I asked 3 questions and thank you for answering the 2nd
one.
I also realize that the print queue name is different from the printer queue
name, which I was referring to.

Therefore, my first question is regarding the printer queue names on the
Windows environment, the printer queue names created by administrators.
" Please, what name is used for the server's printer queue name and what's
the purpose of it."

I guess I found the 2nd part of my 2nd question, the purpose of the server's
printer queue name is to resolve the name into the IP address, although I do
not understand how are the A(host) and PTR records entered/updated in the
DNS in an AD environment and if printers use ddns like workstations. On the
other hand, if this printer queue name is to resolve the printer's name into
the IP address why would we experience ghost printers? Don't DHCP and DNS
keep in touch? lol


The first part of my 2nd question though is where I need some help. Out of
so many printer names that I mentioned in my original post, which one is
used for the server's printer queue name, please. Is it the NetBIOS name of
the printer, or could it be any name?

Although it may seem like I have many questions, everything is related to
one thing only: the printer queue name.


Any help / link will be appreciated!




what is the

"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:O8ShlSYZJHA.1352@TK2MSFTNGP03.phx.gbl...
> One can only send data over LPD/ lpr protocol on an IPv4 or IPv6
> transport.
>
> Each manufacture can designate how to implement the LPD spec, some only
> accept data to a specific queue name and others will accept to any name.
>
>
> So far this you are not really asking a Windows question but rather
> something for the printer vendor.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "ITNews" <ITNews@net.it> wrote in message
> news:%23zrdPyuYJHA.760@TK2MSFTNGP02.phx.gbl...
>> From the manifacture, the printer has a netbios name, a model number, its
>> driver's name, its LPD queue name
>>
>> On the server, the administrator assigns a print queue name and an IP
>> address.
>>
>> Please, what name is used for the server's print queue name and what's
>> the purpose of it.
>> On the other hand, why do we need the LPD queue name if we send the print
>> job to printer's IP address?
>>
>> Lately, printers manufactures allow any remote queue name for LPD queue
>> name ... how does that work compare to the specific LPD queues names?
>>
>> Thanks in advance!
>>
>>
>
>

Alan Morris [MSFT]
Guest
Posts: n/a
 
Re: Too many names
Posted: 12-27-2008, 12:32 AM
The spooler typically connects to the printer name rather than the share
name but one can connect to the share name as well. The share name is used
by the server service to create named pipes to the spooler service.

The spooler uses the printer HOSTNAME to obtain the IP address for the
printer from WINS or DNS entries. Stale entries are always around. Most
printers get the IP from DHCP but some printers do not play well when
updating WINS and DNS. If the NIC for the printer works well with DNS leave
it DHCP. If your running into too many stale entries when the IP changes,
go for static. I'm sure there is more than one person in this forum who
will tell you always use static IP entries for the printers.

The spooler only uses the NETBIOS name of the printer when printing to Local
Ports and resolution is handed over to the network layer when writing data
or querying for valid server name. For most print server configurations,
the NETBIOS name of the printer is never used.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"ITNews" <ITNews@net.it> wrote in message
news:eDBeJafZJHA.2084@TK2MSFTNGP06.phx.gbl...
> Hello Mr. Morris.
> Sorry, I realize, I asked 3 questions and thank you for answering the 2nd
> one.
> I also realize that the print queue name is different from the printer
> queue name, which I was referring to.
>
> Therefore, my first question is regarding the printer queue names on the
> Windows environment, the printer queue names created by administrators.
> " Please, what name is used for the server's printer queue name and what's
> the purpose of it."
>
> I guess I found the 2nd part of my 2nd question, the purpose of the
> server's printer queue name is to resolve the name into the IP address,
> although I do not understand how are the A(host) and PTR records
> entered/updated in the DNS in an AD environment and if printers use ddns
> like workstations. On the other hand, if this printer queue name is to
> resolve the printer's name into the IP address why would we experience
> ghost printers? Don't DHCP and DNS keep in touch? lol
>
>
> The first part of my 2nd question though is where I need some help. Out of
> so many printer names that I mentioned in my original post, which one is
> used for the server's printer queue name, please. Is it the NetBIOS name
> of the printer, or could it be any name?
>
> Although it may seem like I have many questions, everything is related to
> one thing only: the printer queue name.
>
>
> Any help / link will be appreciated!
>
>
>
>
> what is the
>
> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
> news:O8ShlSYZJHA.1352@TK2MSFTNGP03.phx.gbl...
>> One can only send data over LPD/ lpr protocol on an IPv4 or IPv6
>> transport.
>>
>> Each manufacture can designate how to implement the LPD spec, some only
>> accept data to a specific queue name and others will accept to any name.
>>
>>
>> So far this you are not really asking a Windows question but rather
>> something for the printer vendor.
>>
>>
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/search/?adv=1
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "ITNews" <ITNews@net.it> wrote in message
>> news:%23zrdPyuYJHA.760@TK2MSFTNGP02.phx.gbl...
>>> From the manifacture, the printer has a netbios name, a model number,
>>> its driver's name, its LPD queue name
>>>
>>> On the server, the administrator assigns a print queue name and an IP
>>> address.
>>>
>>> Please, what name is used for the server's print queue name and what's
>>> the purpose of it.
>>> On the other hand, why do we need the LPD queue name if we send the
>>> print job to printer's IP address?
>>>
>>> Lately, printers manufactures allow any remote queue name for LPD queue
>>> name ... how does that work compare to the specific LPD queues names?
>>>
>>> Thanks in advance!
>>>
>>>
>>
>>
>
>

Alan Morris [MSFT]
Guest
Posts: n/a
 
Re: Too many names
Posted: 12-27-2008, 12:32 AM
The spooler typically connects to the printer name rather than the share
name but one can connect to the share name as well. The share name is used
by the server service to create named pipes to the spooler service.

The spooler uses the printer HOSTNAME to obtain the IP address for the
printer from WINS or DNS entries. Stale entries are always around. Most
printers get the IP from DHCP but some printers do not play well when
updating WINS and DNS. If the NIC for the printer works well with DNS leave
it DHCP. If your running into too many stale entries when the IP changes,
go for static. I'm sure there is more than one person in this forum who
will tell you always use static IP entries for the printers.

The spooler only uses the NETBIOS name of the printer when printing to Local
Ports and resolution is handed over to the network layer when writing data
or querying for valid server name. For most print server configurations,
the NETBIOS name of the printer is never used.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"ITNews" <ITNews@net.it> wrote in message
news:eDBeJafZJHA.2084@TK2MSFTNGP06.phx.gbl...
> Hello Mr. Morris.
> Sorry, I realize, I asked 3 questions and thank you for answering the 2nd
> one.
> I also realize that the print queue name is different from the printer
> queue name, which I was referring to.
>
> Therefore, my first question is regarding the printer queue names on the
> Windows environment, the printer queue names created by administrators.
> " Please, what name is used for the server's printer queue name and what's
> the purpose of it."
>
> I guess I found the 2nd part of my 2nd question, the purpose of the
> server's printer queue name is to resolve the name into the IP address,
> although I do not understand how are the A(host) and PTR records
> entered/updated in the DNS in an AD environment and if printers use ddns
> like workstations. On the other hand, if this printer queue name is to
> resolve the printer's name into the IP address why would we experience
> ghost printers? Don't DHCP and DNS keep in touch? lol
>
>
> The first part of my 2nd question though is where I need some help. Out of
> so many printer names that I mentioned in my original post, which one is
> used for the server's printer queue name, please. Is it the NetBIOS name
> of the printer, or could it be any name?
>
> Although it may seem like I have many questions, everything is related to
> one thing only: the printer queue name.
>
>
> Any help / link will be appreciated!
>
>
>
>
> what is the
>
> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
> news:O8ShlSYZJHA.1352@TK2MSFTNGP03.phx.gbl...
>> One can only send data over LPD/ lpr protocol on an IPv4 or IPv6
>> transport.
>>
>> Each manufacture can designate how to implement the LPD spec, some only
>> accept data to a specific queue name and others will accept to any name.
>>
>>
>> So far this you are not really asking a Windows question but rather
>> something for the printer vendor.
>>
>>
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/search/?adv=1
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "ITNews" <ITNews@net.it> wrote in message
>> news:%23zrdPyuYJHA.760@TK2MSFTNGP02.phx.gbl...
>>> From the manifacture, the printer has a netbios name, a model number,
>>> its driver's name, its LPD queue name
>>>
>>> On the server, the administrator assigns a print queue name and an IP
>>> address.
>>>
>>> Please, what name is used for the server's print queue name and what's
>>> the purpose of it.
>>> On the other hand, why do we need the LPD queue name if we send the
>>> print job to printer's IP address?
>>>
>>> Lately, printers manufactures allow any remote queue name for LPD queue
>>> name ... how does that work compare to the specific LPD queues names?
>>>
>>> Thanks in advance!
>>>
>>>
>>
>>
>
>

IT News
Guest
Posts: n/a
 
Re: Too many names
Posted: 12-27-2008, 06:26 PM
Thanks Mr. Morris,

You seem to be the most knowledgeable person about printing in the
newsgroups.
I am just confused with so many names in printing,
printer name, print name, share name, printer Hostname, printer Netbios
name, queue name, etc.

Happy holidays!


"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:OSv4cq7ZJHA.1336@TK2MSFTNGP02.phx.gbl...
> The spooler typically connects to the printer name rather than the share
> name but one can connect to the share name as well. The share name is
> used by the server service to create named pipes to the spooler service.
>
> The spooler uses the printer HOSTNAME to obtain the IP address for the
> printer from WINS or DNS entries. Stale entries are always around. Most
> printers get the IP from DHCP but some printers do not play well when
> updating WINS and DNS. If the NIC for the printer works well with DNS
> leave it DHCP. If your running into too many stale entries when the IP
> changes, go for static. I'm sure there is more than one person in this
> forum who will tell you always use static IP entries for the printers.
>
> The spooler only uses the NETBIOS name of the printer when printing to
> Local Ports and resolution is handed over to the network layer when
> writing data or querying for valid server name. For most print server
> configurations, the NETBIOS name of the printer is never used.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "ITNews" <ITNews@net.it> wrote in message
> news:eDBeJafZJHA.2084@TK2MSFTNGP06.phx.gbl...
>> Hello Mr. Morris.
>> Sorry, I realize, I asked 3 questions and thank you for answering the 2nd
>> one.
>> I also realize that the print queue name is different from the printer
>> queue name, which I was referring to.
>>
>> Therefore, my first question is regarding the printer queue names on the
>> Windows environment, the printer queue names created by administrators.
>> " Please, what name is used for the server's printer queue name and
>> what's the purpose of it."
>>
>> I guess I found the 2nd part of my 2nd question, the purpose of the
>> server's printer queue name is to resolve the name into the IP address,
>> although I do not understand how are the A(host) and PTR records
>> entered/updated in the DNS in an AD environment and if printers use ddns
>> like workstations. On the other hand, if this printer queue name is to
>> resolve the printer's name into the IP address why would we experience
>> ghost printers? Don't DHCP and DNS keep in touch? lol
>>
>>
>> The first part of my 2nd question though is where I need some help. Out
>> of so many printer names that I mentioned in my original post, which one
>> is used for the server's printer queue name, please. Is it the NetBIOS
>> name of the printer, or could it be any name?
>>
>> Although it may seem like I have many questions, everything is related to
>> one thing only: the printer queue name.
>>
>>
>> Any help / link will be appreciated!
>>
>>
>>
>>
>> what is the
>>
>> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
>> news:O8ShlSYZJHA.1352@TK2MSFTNGP03.phx.gbl...
>>> One can only send data over LPD/ lpr protocol on an IPv4 or IPv6
>>> transport.
>>>
>>> Each manufacture can designate how to implement the LPD spec, some only
>>> accept data to a specific queue name and others will accept to any name.
>>>
>>>
>>> So far this you are not really asking a Windows question but rather
>>> something for the printer vendor.
>>>
>>>
>>>
>>> --
>>> Alan Morris
>>> Windows Printing Team
>>> Search the Microsoft Knowledge Base here:
>>> http://support.microsoft.com/search/?adv=1
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> "ITNews" <ITNews@net.it> wrote in message
>>> news:%23zrdPyuYJHA.760@TK2MSFTNGP02.phx.gbl...
>>>> From the manifacture, the printer has a netbios name, a model number,
>>>> its driver's name, its LPD queue name
>>>>
>>>> On the server, the administrator assigns a print queue name and an IP
>>>> address.
>>>>
>>>> Please, what name is used for the server's print queue name and what's
>>>> the purpose of it.
>>>> On the other hand, why do we need the LPD queue name if we send the
>>>> print job to printer's IP address?
>>>>
>>>> Lately, printers manufactures allow any remote queue name for LPD queue
>>>> name ... how does that work compare to the specific LPD queues names?
>>>>
>>>> Thanks in advance!
>>>>
>>>>
>>>
>>>
>>
>>
>
>

IT News
Guest
Posts: n/a
 
Re: Too many names
Posted: 12-27-2008, 06:26 PM
Thanks Mr. Morris,

You seem to be the most knowledgeable person about printing in the
newsgroups.
I am just confused with so many names in printing,
printer name, print name, share name, printer Hostname, printer Netbios
name, queue name, etc.

Happy holidays!


"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:OSv4cq7ZJHA.1336@TK2MSFTNGP02.phx.gbl...
> The spooler typically connects to the printer name rather than the share
> name but one can connect to the share name as well. The share name is
> used by the server service to create named pipes to the spooler service.
>
> The spooler uses the printer HOSTNAME to obtain the IP address for the
> printer from WINS or DNS entries. Stale entries are always around. Most
> printers get the IP from DHCP but some printers do not play well when
> updating WINS and DNS. If the NIC for the printer works well with DNS
> leave it DHCP. If your running into too many stale entries when the IP
> changes, go for static. I'm sure there is more than one person in this
> forum who will tell you always use static IP entries for the printers.
>
> The spooler only uses the NETBIOS name of the printer when printing to
> Local Ports and resolution is handed over to the network layer when
> writing data or querying for valid server name. For most print server
> configurations, the NETBIOS name of the printer is never used.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "ITNews" <ITNews@net.it> wrote in message
> news:eDBeJafZJHA.2084@TK2MSFTNGP06.phx.gbl...
>> Hello Mr. Morris.
>> Sorry, I realize, I asked 3 questions and thank you for answering the 2nd
>> one.
>> I also realize that the print queue name is different from the printer
>> queue name, which I was referring to.
>>
>> Therefore, my first question is regarding the printer queue names on the
>> Windows environment, the printer queue names created by administrators.
>> " Please, what name is used for the server's printer queue name and
>> what's the purpose of it."
>>
>> I guess I found the 2nd part of my 2nd question, the purpose of the
>> server's printer queue name is to resolve the name into the IP address,
>> although I do not understand how are the A(host) and PTR records
>> entered/updated in the DNS in an AD environment and if printers use ddns
>> like workstations. On the other hand, if this printer queue name is to
>> resolve the printer's name into the IP address why would we experience
>> ghost printers? Don't DHCP and DNS keep in touch? lol
>>
>>
>> The first part of my 2nd question though is where I need some help. Out
>> of so many printer names that I mentioned in my original post, which one
>> is used for the server's printer queue name, please. Is it the NetBIOS
>> name of the printer, or could it be any name?
>>
>> Although it may seem like I have many questions, everything is related to
>> one thing only: the printer queue name.
>>
>>
>> Any help / link will be appreciated!
>>
>>
>>
>>
>> what is the
>>
>> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
>> news:O8ShlSYZJHA.1352@TK2MSFTNGP03.phx.gbl...
>>> One can only send data over LPD/ lpr protocol on an IPv4 or IPv6
>>> transport.
>>>
>>> Each manufacture can designate how to implement the LPD spec, some only
>>> accept data to a specific queue name and others will accept to any name.
>>>
>>>
>>> So far this you are not really asking a Windows question but rather
>>> something for the printer vendor.
>>>
>>>
>>>
>>> --
>>> Alan Morris
>>> Windows Printing Team
>>> Search the Microsoft Knowledge Base here:
>>> http://support.microsoft.com/search/?adv=1
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> "ITNews" <ITNews@net.it> wrote in message
>>> news:%23zrdPyuYJHA.760@TK2MSFTNGP02.phx.gbl...
>>>> From the manifacture, the printer has a netbios name, a model number,
>>>> its driver's name, its LPD queue name
>>>>
>>>> On the server, the administrator assigns a print queue name and an IP
>>>> address.
>>>>
>>>> Please, what name is used for the server's print queue name and what's
>>>> the purpose of it.
>>>> On the other hand, why do we need the LPD queue name if we send the
>>>> print job to printer's IP address?
>>>>
>>>> Lately, printers manufactures allow any remote queue name for LPD queue
>>>> name ... how does that work compare to the specific LPD queues names?
>>>>
>>>> Thanks in advance!
>>>>
>>>>
>>>
>>>
>>
>>
>
>

30515
Guest
Posts: n/a
 
RE: Too many names
Posted: 03-20-2009, 03:38 PM


"ITNews" wrote:
> From the manifacture, the printer has a netbios name, a model number, its
> driver's name, its LPD queue name
>
> On the server, the administrator assigns a print queue name and an IP
> address.
>
> Please, what name is used for the server's print queue name and what's the
> purpose of it.
> On the other hand, why do we need the LPD queue name if we send the print
> job to printer's IP address?
>
> Lately, printers manufactures allow any remote queue name for LPD queue name
> .... how does that work compare to the specific LPD queues names?
>
> Thanks in advance!
>
>
>
 
LinkBack Thread Tools Display Modes
 


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
file names and folder names have been changed into some values automatically harish9999 Windows Vista File Management 3 12-01-2008 03:51 AM
setting to remember names and places, like e-bay names...etc. John K Windows XP Help & Support 0 01-26-2004 02:51 AM
document directory names no longer match names of user owners habiru Windows XP Security & Administration 1 09-15-2003 02:22 AM
erase the names of the downloaded files in the file names proposition scroll-men Kelly Customize Windows XP 0 08-01-2003 12:29 AM
Machine names v. User names Pete Bradshaw Windows XP Security & Administration 1 07-15-2003 03:18 PM