In Windows 7 & Windows 8 , all your printers have gone. If you have a local
printer that printer is listed as an Unspecified device.
I solved it the following way.
I found that the print spooler service had stopped. If I restarted the
service but it stopped again.
I went to "%WINDIR%\system32\spool\printers" & deleted all the files in
there.
I then started the print spooler service & it remained started.
Went to device & printers and all my printers had come back again & the local
printer was no longer an Unspecified device.
0d0325ba-944d-4148-aec9-ff44a44f5746|3|5.0
While processing a TGS request for the target server krbtgt XXXXXXXX
did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 8).
The requested etypes were 18. The accounts available etypes were 23 -133 -128 3 1.
Event Type: Error
Event Source: KDC
Event Category: None
Event ID: 27
The cause of the event is that the client requests a service ticket with a etype 18 (aes256-cts-hmac-sha1-96), which is not supported by Windows Server 2003 but supported by Windows Server 2008 R2. If the Kerberos authentication works properly, you can safely ignore the events. It just informs the clients what etypes it supports.
For more information, please refer to the following articles:
The security principals and the services that use only DES encryption for Kerberos authentication are incompatible with the default settings on a computer that is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/kb/977321
Event ID 27 — KDC Encryption Type Configuration
http://technet.microsoft.com/en-us/library/cc733974(WS.10).aspx
9e6bef18-35d3-4bfe-b4d4-12175b5d0917|5|5.0
This one drove me crazy. Many help articles start with " start adsiedit and browse to CN=Configuration CN=Services ....." . I could not see CN=Configuration to save my life.
After hours of hair pulling I found this article Thanks David
http://www.kineticcomputer.com/tips/1103-cannot-see-configuration-container-in-adsiedit.htm
If it helped would appreciate a rating star.
Ashwin
Lansend.com
Microsoft Certified Partner
0ce9d927-01d0-4230-956e-8185cd90ef7e|4|5.0
Process mad.exe () (PID=2356). Object [\Default Offline Address List]. Property [PublicFolderDatabase] is set to value [domain name /Configuration/Deleted Objects/Public Folder Database
DEL:9e3c1a6b-7c91-4fe4-b32c-cca73a355533], it is pointing to Deleted Objects container of Active Directory. This property should be fixed as soon as possible.
Solution: This worked for me
http://blog.ronnypot.nl/?p=212
277f493e-f605-4f0f-ae9e-d770218b550d|3|5.0
The issue has been resolved.
- In the Exchange MMC , under server configuration select Hub transport
- in the action menu on the right hand side select " New Receive Connector"
- Give it a name. any name will do , we call it "Application relay"
- In the next screen Local Network settings
4.a provide the fully qualified ( internal) dns name of the mail server
4b. Edit the the receive connector binding & change the port to 26
- In the next screen Remote network settings
5a. remove the default bindings of 0.0.0.0-255.255.255.255
5b. Add the IP address of the server running Backup exec, in our case 10.0.0.4
This address is often the same as that of the Exchange server especially if you are running SBS
- On the next screen New Connector you will be displayed a summary of your configuration which will look somewhat like this , click NEW to build it.
Name: Application relay
Type: Custom
IP Address(es):
(All available IPv4 addresses): Port 26
FQDN: mailserver.domainname.com
Remote IP range(s):
10.0.0.4
- IF all is well On the next screen Completion you will be informed so . click Finish
- In the Exchange MMC double click the connector you just created &
8a. select the Permission groups tab & check Exchange Server
( Note: if backupexec is not on the same server as the exchange server you may have to play around with this)
8b. select the Authentication tab & additionally check off Externally Secured
- Go to Symantec Backup Exec & select E-mail alerts and Pager notifications from the drop down menu
- Enable SMTP Configuration & fill up the information for your mail server , remember to specify port 26, Sender name & Sender email address. There is no need to Enable SMTP Authentication
That's it you are done.
If you still cannot send email alerts , you will want to set the logging for the recive connector you just created to Verbose
You will find the log in the following folder.
Receive Connector logs are located in:
Exchange 2010: C:\Program Files\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive
Exchange 2007: C:\Program Files\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive
Send Connector logs are located in:
Exchange 2010: C:\Program Files\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend
Exchange 2007: C:\Program Files\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend
images coming shortly
ba114edd-df36-4dfb-a010-14c06d058ef8|7|4.9