Пропадают принтера при подключении к другой сети

Пропадают принтера при подключении к другой сети

au_fomin

Новый участник

Сообщения: 1
Благодарности: 0

Доброе утро, Коллеги

Проблема заключается в следующем:

Имеется два офиса, в каждом здании есть принтера.
Когда сотрудник приезжает в один офис (№1 \\prn21ae)), у него по политике добавляются все принтера этого офиса(№1 \\prn21ae) (автоматом для аутентифицированных пользователей), всё работает, пользователь печатает. Но когда он возвращается в свой офис (№2 \\prn11ae) (тоже подключается по политике для аутентифицированных пользователей) остаются только принтера офиса №1, а старые принтера пропадают. Принтерная подсеть офиса №1 10.126.9.ххх, офис №2 172.22.200.xxx. Офис №1 и №2 находятся в одном домене. Прошу помочь разобраться. Так как каждый раз приходиться цеплять принтера вручную.

Log:

- The user 'LME_RT_24_Color_HP6040' preference item in the 'LME_AE_RT_Printers_Deployment {1B2C94EB-A2DC-4563-BE83-6679F9E298B3}' Group Policy object did not apply because it failed with error code '0x800703eb Cannot complete this function.' This error was suppressed.

- The user 'LME_RT_24_Color_HP6040' preference item in the 'LME_AE_RT_Printers_Deployment {1B2C94EB-A2DC-4563-BE83-6679F9E298B3}' Group Policy object did not apply because it failed with error code '0x800706ba The RPC server is unavailable.' This error was suppressed.

- Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.

Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events".

Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID. This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO. To resolve this event, contact an administrator in the domain to perform the following actions:

1. Identify accounts that could not be resolved to a SID:

From the command prompt, type: FIND /I "Cannot find" %SYSTEMROOT%\Security\Logs\winlogon.log

The string following "Cannot find" in the FIND output identifies the problem account names.

Example: Cannot find JohnDough.

In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").

2. Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts:

a. Start -> Run -> RSoP.msc
b. Review the results for Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment and Computer Configuration\Windows Settings\Security Settings\Local Policies\Restricted Groups for any errors flagged with a red X.
c. For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors.

3. Remove unresolved accounts from Group Policy

a. Start -> Run -> MMC.EXE
b. From the File menu select "Add/Remove Snap-in..."
c. From the "Add/Remove Snap-in" dialog box select "Add..."
d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add"
e. In the "Select Group Policy Object" dialog box click the "Browse" button.
f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab
g. For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1.

-Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
7 user registry handles leaked from \Registry\User\S-1-5-21-2025429265-1972579041-1417001333-49058:
Process 688 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-2025429265-1972579041-1417001333-49058
Process 688 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-2025429265-1972579041-1417001333-49058
Process 784 (\Device\HarddiskVolume2\Windows\System32\winlogon.exe) has opened key \REGISTRY\USER\S-1-5-21-2025429265-1972579041-1417001333-49058
Process 688 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-2025429265-1972579041-1417001333-49058\Software\Microsoft\SystemCertificates\Disallowed
Process 1284 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2025429265-1972579041-1417001333-49058\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Process 688 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-2025429265-1972579041-1417001333-49058\Software\Microsoft\SystemCertificates\My
Process 688 (\Device\HarddiskVolume2\Windows\System32\lsass.exe) has opened key \REGISTRY\USER\S-1-5-21-2025429265-1972579041-1417001333-49058\Software\Microsoft\SystemCertificates\CA

Отправлено: 10:49, 29-08-2013

alef2474

Ветеран

Сообщения: 1630
Благодарности: 220

Профиль | Отправить PM | Цитировать

Надо смотреть скрипты в sysvol, которые подключают пользователю принтера нужного офиса.
Эти скрипты видимо запускаются в групповых политиках.

Вы же групповых политик не привели и скриптов тоже. Только ошибку групповой политики про НР6040,
а принтеров - не один, судя по всему.
Возможно этому пользователю не даны разрешения на этот принтер.

Отправлено: 21:06, 30-08-2013 | #2