RE: adding a printer to a CNAME
From: James Wong (Wong_at_discussions.microsoft.com)
Date: 07/28/04
- Next message: Jen: "Message for Shilpa Sinha"
- Previous message: Alan Morris\(MSFT\): "Re: Queue redirection & traffic compression"
- In reply to: Shilpa Sinha [MSFT]: "RE: adding a printer to a CNAME"
- Next in thread: Shilpa Sinha [MSFT]: "RE: adding a printer to a CNAME"
- Reply: Shilpa Sinha [MSFT]: "RE: adding a printer to a CNAME"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 28 Jul 2004 11:06:02 -0700
Shilpa,
Tthanks for the reply, but since we're going to have to rescope the DHCP addressing as well as institute VLANs, adding a printers to CNAME is really the best bet (7500 users, distributed over 1000 sq miles). I really do not want ot have to go to every user and change their printers location after we move the printserver to another IP address (and name).
If I upgrade to W2K3, would that allow we to add printers via the printerserver's CNAME?
"Shilpa Sinha [MSFT]" wrote:
> Hi
>
> Maybe this will help:
>
> You Cannot Add a Printer by Using the CNAME
>
> SYMPTOMS
> ==============
> If you are use the Add Printer Wizard to add a new printer, the new printer
> is not added if you use the printer's canonical name (CNAME) instead of the
> server name. You receive the following error message:
>
> Connect to Printer:
> Could not connect to the printer. You either entered a printer name that
> was incorrect or the specified printer is no longer connected to the server.
> Check Help for more information.
>
> If you capture a network trace, you receive the following error message
> from remote procedure call (RPC):
>
> NERR_DeviceNotShared "0x907"
>
> CAUSE
> =========
> CNAMEs are not used in managing the local server name cache.
>
> RESOLUTION
> =============
> Service Pack Information
>
> To resolve this problem, obtain the latest service pack for Microsoft
> Windows 2000. For additional information, click the following article
> number to view the article in the Microsoft Knowledge Base:
>
> 260910 - How to Obtain the Latest Windows 2000 Service Pack
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;260910
>
> Hotfix Information
>
> A supported fix is now available from Microsoft, but it is only intended to
> correct the problem that is described in this article. Apply it only to
> computers that are experiencing this specific problem. This fix may receive
> additional testing. Therefore, if you are not severely affected by this
> problem, Microsoft recommends that you wait for the next Windows 2000
> service pack that contains this fix.
>
> To resolve this problem immediately, contact Microsoft Product Support
> Services to obtain the fix. For a complete list of Microsoft Product
> Support Services phone numbers and information about support costs, visit
> the following Microsoft Web site:
>
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
>
> NOTE: In special cases, charges that are ordinarily incurred for support
> calls may be canceled if a Microsoft Support Professional determines that a
> specific update will resolve your problem. The typical support costs will
> apply to additional support questions and issues that do not qualify for
> the specific update in question.
>
> The English version of this fix has the file attributes (or later) that are
> listed in the following table. The dates and times for these files are
> listed in coordinated universal time (UTC). When you view the file
> information, it is converted to local time. To find the difference between
> UTC and local time, use the Time Zone tab in the Date and Time tool in
> Control Panel.
>
> Date Time Version Size File name
> --------------------------------------------------------
> 26-Aug-2002 17:31 5.0.2195.6030 250,640 Localspl.dll
> 26-Aug-2002 17:31 5.0.2195.6030 79,632 Spoolss.dll
>
>
> WORKAROUND
> ==================
> To work around this problem, use the server name or Internet Protocol (IP)
> address instead of the CNAME.
>
> STATUS
> =========
> Microsoft has confirmed that this is a problem in the Microsoft products
> that are listed at the beginning of this article. This problem was first
> corrected in Microsoft Windows 2000 Service Pack 4.
>
> MORE INFORMATION
> ==========================
> For additional information about how to obtain a hotfix for Windows 2000
> Datacenter Server, click the article number below to view the article in
> the Microsoft Knowledge Base:
>
> 265173 - The Datacenter Program and Windows 2000 Datacenter Server Product
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;265173
>
> The information in this article applies to:
>
> o Microsoft Windows 2000 Server SP1
> o Microsoft Windows 2000 Server SP3
> o Microsoft Windows 2000 Server SP2
> o Microsoft Windows 2000 Advanced Server SP1
> o Microsoft Windows 2000 Advanced Server SP2
> o Microsoft Windows 2000 Advanced Server SP3
> o Microsoft Windows 2000 Professional SP1
> o Microsoft Windows 2000 Professional SP2
> o Microsoft Windows 2000 Professional SP3
>
> Reference Link:
> =============
> http://support.microsoft.com/default.aspx?scid=kb;en-us;298692&Product=win20
> 00
>
> Shilpa Sinha
> This posting is provided "AS IS" with no warranties, and confers no rights
- Next message: Jen: "Message for Shilpa Sinha"
- Previous message: Alan Morris\(MSFT\): "Re: Queue redirection & traffic compression"
- In reply to: Shilpa Sinha [MSFT]: "RE: adding a printer to a CNAME"
- Next in thread: Shilpa Sinha [MSFT]: "RE: adding a printer to a CNAME"
- Reply: Shilpa Sinha [MSFT]: "RE: adding a printer to a CNAME"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|