General discussion

Locked

New Print Server problems

By robert.graham ·
I am recreating (Not transferring) new print queue's on a Win2K server based on print share names from our current WinNT print server. The new ports were created as LPR, and given the same name (all under 12 characters) as on the current WinNT print server. As far as I can tell, all shares were created by the same method.

The problem is that 12 of the 68 print shares created on the new W2K server are not being seen from Win9X clients. It seems to be random, as different type of printers, such as Lexmark, Canon, and HP's are being affected.

I have tried to unshare the printer, stop the spooler, and remove the Reg Key HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares\<Sharename>, and all the above \Security\<Sharename>, and restart the spooler, and recreate the share without any improvement. Any help would be appreciated.

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

New Print Server problems

by Stillatit In reply to New Print Server problems

When you install the printers on the print server and share them out, are you remembering in all cases to specify all the versions of the OS that will use each printer, and supplying all appropriate versions of the drivers for each printer?

If you try to install a printer that does not show in the list, can you type in the name and have it work?

Good luck.

Collapse -

New Print Server problems

by robert.graham In reply to New Print Server problems

All enterprise OS drivers have been installed to each printer.

When trying to type in a UNC path to the share, the error message "Access to specified device, path, or file is denied"

Collapse -

New Print Server problems

by Curacao_Dejavu In reply to New Print Server problems

give permissions to the guests account.
win98 clients dont really login on a domain, enabling the guest accounts permits other os's using the object.
Is it a large organization, what about giving it a 8 character name.


Leopold

Collapse -

New Print Server problems

by Shanghai Sam In reply to New Print Server problems

Adding Domain Guests to the permissions did not enable the printer to be seen by Win9x clients. The problem is affecting a printer with a share name with less than 8 characters as well.
One thing that we dicovered, by adding a printer through the Add Printer Wizard, even though it could not be seen by a Win 9x client, it would install in Win9x without error. You just need to know the server and queue name. In the past, we had been in the habit of accessing and installing prnters by going to Start>Run>\\PrintServer and loading the printer by double clicking on the share. Have not yet compared registries using both methods.

Collapse -

New Print Server problems

by Curacao_Dejavu In reply to New Print Server problems

Can the win9x see shared folders on the w2k ?
the problems lies between:
since you can connect to the queue without "seeing the printer" means that or netbios communication between the win9x and the w2k is nor working properly.
on the w2k I wouldlook for the newest drivers, check if all bindings are properly and reapply the service pack.
On the win9x look for the newest drivers and check the bindings also.
It's a netbios problem, only thing I can not pinpoint the problem yet.

Collapse -

New Print Server problems

by Shanghai Sam In reply to New Print Server problems

Yes, Win9x can see shared folders on the print server.
Re-Applying the service pak was the first thing we did when the problem was identified.

Win9x bindings look OK, the problem is consistant on all enterprise Win9x systems, and all other network functions working normally.

The Print Server OS was just installed, and all lastest drivers downloaded when print queue's were created.

We took the old server off-line, removed old instance with server manager, and named new server the same as the old one, and brought it back into the domain.

Also, just by adding one character to the share name, but using the same port, would allow the adjusted share name to be seen. We are using WINS, and I'm wondering if some of the share names have been cached with a different GUID causing a conflict in the permissions.

Collapse -

New Print Server problems

by ccsbz In reply to New Print Server problems

win98se has a problem seeing win2000.
write a script useing NET USE command.

Collapse -

New Print Server problems

by robert.graham In reply to New Print Server problems

HHmmmmmm.....???!! Thanks

Collapse -

New Print Server problems

by robert.graham In reply to New Print Server problems

This question was closed by the author

Back to Networks Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums