--------------- FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: F3300011 Date: 03/01/98 From: FRANK RAMSEY Time: 07:59pm \/To: CHRIS HOLTEN (Read 2 times) Subj: Administrative shares Chris Holten wrote in a message to Frank Ramsey: FR> Chris Holten wrote in a message to Steve Quarrella: CH> administrative shares. You don't have to be a part of a CH> domain to have access to domain resources. FR> If the domain guest account is disabled (the default), FR> you must be part of the domain to access domain FR> resources. CH> Hmm..I never noticed that. However I can log on remotely to CH> a different domain than what I am in using an administrator CH> account for that domain and have domain privals. If there is CH> no guest account, then I can't do that? If the domain A trusts domain B and you're part of domain B, the admins of domain A can grant you privs to domain A resources. The default privs for a trusted domain to a trusting domain are access to domain resources would not be available to workstations not part of the domain by default. There was not a suggestion that the workstation belonged to a domain; quite the contrary, the workstation would be kept out of domains to protect the security of admin shares. I jumped in to point out your answer was correct, but to work as described would require the guest account in the domain to be changed from the default. If there are no trust relationships between domains and the guest account is disabled, attempts to access domain resources will result in access denied. I seem to recall the issue was how disable the admin shares. You responded a choice would be to keep the workstation out of the domain and therefore keeping the admin shares unavailable to domain admin. 100% true. If a workstation is not part of the domain, only accounts defined in the workstation SAM has access to workstation resources. Because it's not part of the domain, domain admins are not part of the workstation SAM. I believe you then suggested the workstation does not have to be part of the domain to access domain resources. Because the guest account is disabled by default, by default the workstation will not be able to access domain resources. To access domain resources, the guest account in the domain must be enabled. Or the workstation be made part of the domain, which means the admin shares on the workstation are available to domain admins. Frank PE, CNE, MCSE, MCP+I, MCP framsey@goodyear.com, frank.ramsey@fallsbbs.com --- * Origin: A Point on Pine Lake, Uniontown, Ohio (1:157/110.70) --------------- FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: F3300012 Date: 03/02/98 From: JEFF GUERDAT Time: 07:14am \/To: CHRIS HOLTEN (Read 2 times) Subj: Print Processor unknown e On 02-17-98, CHRIS HOLTEN said to ANYONE WHO HAS SEEN THIS: CH>This is one that I've never seen before. Hopefully I'm just overlooking CH>something real simple. In NT 4.0 workstation I get the following Error CH>when I try install a printer and test print it: CH>"Operation could not be completed. Print Processor is unknown". All I could find in Technet was this: --------------------------------------------- The print processor is unknown. [Kernel32] The print processor is a dynamic-link library (DLL) which calls the printer driver. An application has tried to use a print processor which has not been installed on your computer. Contact your system administrator to check the software that has been installed on your computer. If the required DLL cannot be installed on your system, you may have to contact the supplier of the running application. --------------------------------------------- And this from the web site search: --------------------------------------------- Error Message: "Print Processor Is Unknown" Last reviewed: January 5, 1998 Article ID: Q153355 The information in this article applies to: Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0 Microsoft Windows NT Server versions 3.5, 3.51, and 4.0 SYMPTOMS When you attempt to print or connect to a print queue, the following error message may appear: Could not connect to the printer because the print processor is unknown. CAUSE This error message may be caused by either of the following: The default print processor Winprint.dll is missing on the computer. This file should be located in the following directory: %Systemroot%\System32\Spool\Prtprocs\W32x86 -or- The winprint key is corrupted or missing from the registry in the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\ Environments\Windows NT x86\Print Processors\ RESOLUTION If the Winprint.dll file is missing, expand Winprint.dl_ from the Windows NT installation CD to the %Systemroot%\System32\Spool\Prtprocs\W32x86 directory. If the winprint key is missing from the registry. you must use Registry Editor to add it. Use the steps below to add the winprint key to the registry: WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. 1.Run Regedt32.exe 2.Navigate to the following registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print \Environments\Windows NT x86\Print Processors\ 3.Click to select the Print Processors key. 4.On the Edit menu, click Add Key, and then type "winprint" (without the quotation marks) in the Key Name field of the Add Key dialog box (leave the Class field blank). 5.Click to select the winprint key. On the Edit menu, click Add Value. 6.Type the following values in the Add Value dialog box and then click OK: Value Name: Driver Data Type: REG_SZ 7.For the String Value, type "winprint.dll" (without the quotation marks), and click OK. 8.Restart the computer. After the computer restarts, you should be able to add printers. --- *Durango b200 #NR* DurangoMail for Windows NT/95 --- QScan/PCB v1.17b / 01-0406 * Origin: Knight Moves - Rochester,NY 716-865-2106 (1:2613/313) --------------- FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: F3300013 Date: 03/02/98 From: GARY GILMORE Time: 06:58pm \/To: ALL (Read 2 times) Subj: New in the Windows32 FDN New Windows95 releases, from the Windows32 File Distribution Network. (W32_FDN) (Announcement made with moderator permission) --------------------------------------------------------------------------- Area : W32_INT - W32_FDN: Internet & Web Related --------------------------------------------------------------------------- MAILBEAM.ZIP 733,215 MailBeamer 3.14, a SMTP and POP3 Gateway for Microsoft Mail. MailBeamer is a drop-in-replacement for the MS SMTP Gateway. --------------------------------------------------------------------------- Area : W32_MISC - W32_FDN: Win32 Misc --------------------------------------------------------------------------- ASAWIN95.EXE 1,330,583 AsEasyAs v1.60, powerful spreadsheet pgm with over 130 math, financial, scientific, stat, string functions. Superb graphics.