No access to Shared Printer

G

Guest

Recently rolled out Windows 2000 Pro (SP4 and all post SP4 patches) within a
mixed NT/2K environment. No showstoppers as of yet with the exception of
printers (print devices). Under NT, providing the "box" was switched on and
the printer was shared, the device was always available to print regardless
of who or no-one logged on. However, under 2000 my users have to be
physically logged on before I can use their printer, otherwise I get "access
is denied" or "unable to connect". Is this just the norm with 2000 or have I
configured the printer incorrectly?

Many Thanks in advance. Chris.
 
S

Shilpa Sinha [MSFT]

Hi

Maybe this will help:

Reference Link:
==============
http://support.microsoft.com/default.aspx?scid=kb;en-us;161734&Product=win20
00

Windows NT and Windows 2000 Print Browsing Architecture

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 - Description of the Microsoft Windows Registry
http://support.microsoft.com/default.aspx?scid=kb;EN-US;256986

SUMMARY
=============
Windows NT and Windows 2000 leverage the familiar browsing mechanism found
in File Manager to enumerate printers for remote printing. This article
describes the mechanism used for print browsing in a Windows environment
and the registry keys that effect its behavior.

MORE INFORMATION
==============
How Shared Printers Are Found

When a user chooses to browse for a printer in the domain, a remote
procedure call (RPC) (EnumPrinters) is made to the browse master.
EnumPrinters returns only the computers in the browse list that have set
the printer flag (SV_TYPE_PRINT) in their host announcements.

For additional information about how the master browser is selected, click
the following article number to view the article in the Microsoft Knowledge
Base:

102878 - Information on Browser Operation
http://support.microsoft.com/default.aspx?scid=kb;EN-US;102878

Below is a network trace fragment that illustrates a client browsing a
Windows NT print server.

Client Request
===============
FRAME: Base frame properties
ETHERNET: 802.3 Length = 1042
LLC: UI DSAP=0xE0 SSAP=0xE0 C
IPX: NetBIOS Packet - 6112.08003E3046DE.455 -> 6112.02608C3F3E55.455 - 0
Hops
NBIPX: Session Data
SMB: C transact TransactNmPipe, FID = 0x80a
MSRPC: c/o RPC Request: call 0x1 opnum 0x0 context 0x0 hint 0x364
R_WINSPOOL: RPC Client call winspool:RpcEnumPrinters(..)
R_WINSPOOL: DWORD Flags = 64 (0x40)
R_WINSPOOL: STRING_HANDLE Name = \\NTSERVER
R_WINSPOOL: DWORD Level = 1 (0x1)
R_WINSPOOL: LPBYTE pPrinterEnum [..] = 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00...
R_WINSPOOL: DWORD cbBuf = 804 (0x324)


Server Response
===============
FRAME: Base frame properties ETHERNET: 802.3 Length = 970LLC: UI DSAP=0xE0
SSAP=0xE0 CIPX: NetBIOS Packet - 6112.02608C3F3E55.455 ->
6112.08003E3046DE.455 - 0 Hops
NBIPX: Session Data
SMB: R transact TransactNmPipe (response to frame 89)
MSRPC: c/o RPC Response: call 0x1 context 0x0 hint 0x338 cancels 0x0
R_WINSPOOL: RPC Server response winspool:RpcEnumPrinters(..)
R_WINSPOOL: LPBYTE pPrinterEnum [..] = 08 00 00 00 DA 02 00 00 B4 02 00 00
B2 02 00 00 08 00 00 00 58 02 00...
R_WINSPOOL: LPDWORD pcbNeeded = 460 (0x1CC)
R_WINSPOOL: LPDWORD pcReturned = 3 (0x3)
R_WINSPOOL: Return Value = 0 (0x0)


The network trace above shows the network client receiving back a response
from the server containing information from the RPC call EnumPrinters.
(Additional information on this function is available in the Win32 SDK.)

How Existing Printers Get Enumerated to the Print Browse Master
=================================================================
Windows NT Server and Workstation computers update the browse master by
default every 10 minutes with print share information. This is done via the
Win32 AddPrinter function.

Below is a network trace fragment that demonstrates a client enumerating
shared resources to the print browse master:

FRAME: Base frame properties ETHERNET: 802.3 Length = 458LLC: UI DSAP=0xE0
SSAP=0xE0 CIPX: NetBIOS Packet - 6112.08003E3046DE.455 ->
6112.02608C3F3E55.455 - 0 Hops
NBIPX: Session Data
SMB: C transact TransactNmPipe, FID = 0x200c
MSRPC: c/o RPC Request: call 0x1 opnum 0x5 context 0x0 hint 0x11C
R_WINSPOOL: RPC Client call winspool:RpcAddPrinter(..)
R_WINSPOOL: STRING_HANDLE pName = \\NTSERVER
R_WINSPOOL: PPRINTER_CONTAINER pPrinterContainer {..}
R_WINSPOOL: DWORD Level = 1 (0x1)
R_WINSPOOL: (Untyped 1) PrinterInfo {..}
R_WINSPOOL: Switch Value = 1 (0x1)
R_WINSPOOL: LPPRINTER_INFO_1W pPrinterInfo1 {..}
R_WINSPOOL: DWORD Flags = 24 (0x18)
R_WINSPOOL: LPWSTR pDescription = 35780264 (0x221F6A8)
R_WINSPOOL: LPWSTR pName = 35781864 (0x221FCE8)
R_WINSPOOL: LPWSTR pComment = 12163832 (0xB99AF8)
R_WINSPOOL: LPWSTR pDescription = \\NTCLIENT\Lexmark Optra PS,Lexmark Optra
PS,
R_WINSPOOL: LPWSTR pName = \\NTCLIENT\Lexmark Optra PS
R_WINSPOOL: LPWSTR pComment =
R_WINSPOOL: PDEVMODE_CONTAINER pDevModeContainer {..}
R_WINSPOOL: DWORD cbBuf = 0 (0x0)
R_WINSPOOL: LPBYTE pDevMode = 0 (0x0)
R_WINSPOOL: PSECURITY_CONTAINER pSecurityContainer {..}
R_WINSPOOL: DWORD cbBuf = 0 (0x0)
R_WINSPOOL: LPBYTE pSecurity = 0 (0x0)


Registry Entries
================
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.

Below is a list of registry entries that will manipulate client and server
behavior in regard to print browsing.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print

DisableServerThread REG_DWORD
Range: 0 or 1
Default: 0 (false)

Set this to 1 (true) to disable the browse thread on the current computer.
This thread is used to call other print servers to notify them that this
printer exists.

ServerThreadTimeout REG_DWORD

Range: Milliseconds

Default: 36,000 (36 seconds)

Specifies the amount of time the ServerThread sleeps for before it calls
all the other print servers to notify them of the printers on this
computer.

NetPrinterDecayPeriod REG_DWORD

Range: Milliseconds

Default: 3,600,000 (1 hour)

Specifies how long to cache a network printer. The cache is used to
present the list of printers when the browse dialog is used.

RefreshTimesPerDecayPeriod REG_DWORD

Range: 1 - 5

Default: 2

Specifies how many times to inform the browse masters and backup servers
per decay period. Default value is two times per hour. Do not set a zero
value if you specify both RefreshTimesPerDecayPeriod and
ServerThreadTimeout; the system will wait for the maximum of either the
ServerThreadTimeout or the RefreshTimesPerDecayPeriod.

Non-Printing Registry Changes
=============================
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

SizReqBuf REG_DWORD

Range: 512 - 65535 (bytes in decimal, or 200 - FFFF in hexadecimal)

Default: 4356

Note: In Windows 2000, the minimum setting is 1024. Small buffers use less
memory, and large buffers can improve performance. The exact value that
works best in a specific environment will depend on the specific
configuration of that environment. For an optional value, try 4410
(hexadecimal). This value has been shown to work well in a standard
Ethernet environment. By default, this setting is 4356 bytes on computers.
On servers that have more than 512 MB of memory, this value is increased to
16 KB. A receive buffer that is larger can improve performance on query
directory and similar commands, but at the price of more memory per work
item.
EnableBroadcastSpoolerStatus REG_DWORD

Range: 0 or 1

Default: 0 (false)

Forces the broadcast of WM_SPOOLERSTATUS messages on Windows 2000; ignored
by other platforms. By default, Windows 2000 does not broadcast
WM_SPOOLERSTATUS messages. Set this registry value to 1 if you have a
program that is designed for earlier versions of Windows that rely on
receipt of the WM_SPOOLERS ATUS messages. Note that the WM_SPOOLERSTATUS
message does not have guaranteed delivery semantics, so programs should not
rely upon its receipt.

The information in this article applies to:
===========================================

o Microsoft Windows 2000 Server
o Microsoft Windows 2000 Advanced Server
o Microsoft Windows 2000 Professional
o Microsoft Windows 2000 Datacenter Server
o Microsoft Windows NT Workstation 3.51
o Microsoft Windows NT Workstation 4.0
o Microsoft Windows NT Server 3.51
o Microsoft Windows NT Server 4.0


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

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top