Re: Can not connect to Active Directory Printer

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"Christian Lamparth" <ChristianLamparth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:DC45145C-7410-4E40-B024-335784BC6B6A@xxxxxxxxxxxxxxxx
Hi Herb
Thank you for your help I double check the permissions the everyone group
has print rights and when I click on the share tab for the printer the
printer is shared as
SGBSRDP0003 and list in directory is checked.
The user can also see the object when they search for the printer in the
add
network printer wizzard, however when they double click on it to install
it
they are getting the error message:"windows cannot connect to the printer"

Please advise

I am not 100% certain but those symptoms are somewhat indicative of
a Name Resolution problem.

Possibly the AD is depending on DNS, and the direct share method is
using NetBIOS name resolution.

I would start by confirming the name resolution (NSLookup, NBTStat,
net use \\SHARENAME\printerName etc)

Use both the DNS name, the NetBIOS name, AND the IP address in
those tools (like Net Use) which support that type.

You likely have a Name Resolution problem since you CAN print to
that Print Share through some method (thus eliminating name resolution
as the likely problem)

"Herb Martin" wrote:


"Christian Lamparth" <ChristianLamparth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:EF81B972-CA27-44F7-B8A6-50928AB807E1@xxxxxxxxxxxxxxxx
We have a multi server Active Directory Domain Domain (one tree) all
our
Servers are WIndows Server 2003 R2 running Vital QIP for DNS and DHCP.
In
England we are using a Windows 2000 Server for our File and Print
Server,
all
printers are registered in Active Directory.

Users (who print) still need Permission on the Print SHARE -- the AD
"printer object" is merely for searching and finding the printer, it has
nothing
to do with permissions for actually PRINTING.

On the other hand, for the users to use that Printer Object in AD, they
must
have READ on the Printe and the enclosing (parent) OUs to ensure they can
search for it and FIND it (like finding a file.)

When we try to add the printer through the Printer Wizzard using
"Find a
printer in the directory" option we get the following error message:
"Windows cannot connect to this Printer. Make sure that you have typed
the
name correctly; and that the printer is connected to the network."

The printers however work fine when we connect directly to the server
using
the \\servername\printer name command.







.

Relevant Pages

  • RE: SBS 2003 Outoging Fax Problem w/Error 32028 (Cannot send - fatal error)
    ... 1.Reduce the baud rate of the incoming fax modem and see how it goes. ... Click Permissions and verify that the user attempting to fax has at ... 3.If you have configured the fax client on the Windows XP computer ... On the "Additional Server Types" page, ...
    (microsoft.public.windows.server.sbs)
  • RE: Userenv Error
    ... Microsoft Windows Small Business Server 2003 Service Pack 1 ... Please check both the Share Permissions of the Group folder, ...
    (microsoft.public.windows.server.sbs)
  • Re: Workgroup server to domain
    ... Microsoft MVP - Windows NT Server ... >>may have to add permissions for domain users to access ... >>Scott Harding ... >>Microsoft MVP - Windows NT Server ...
    (microsoft.public.windows.server.migration)
  • Re: login/logoff Report
    ... located both the cmd files in the correct place now. ... Make sure you have hotfix 842933 applied to the SBS server ... truncated" error message when you try to modify or to view GPOs in Windows ... Make sure the "logging folder" share has Share Permissions: ...
    (microsoft.public.windows.server.sbs)
  • Re: Log on Interactively
    ... The server is a Windows 2003 Enterprise Edition Server ... I added the Remote Desktop Users group to the permissions tab with the User ... I then added the Terminal Services User group that I had ...
    (microsoft.public.windows.terminal_services)