Cannot Publish Post to Blogger using Internet Explorer 9

Description:

You can edit/create your post in blogger.com, however you cannot click the publish post button. You are using Internet Explorer 9.

Resolution:

There are two options:

• First, you can enable Compatibility View as a workaround. At Internet Explorer 9, please go to Tools > Compatibility View Settings. Add blogger.com to the list. Click Close and restart your IE 9. Open your post again and you should be able to publish it now. However you may still encounter issue with font sizes, etc.
• Second is to change the setting at the blogger site. Please go to Settings > Select Post Editor > choose Updated Editor > click save settings. Open your post again and you should be able to create/edit/post to your blog again. You will also gain new editing feature such us improved image handling and new preview window.

Blank Live Communication Server (LCS) 2005 MMC Snap-In

Description

You have successfully install your Live Communication Server (LCS) 2005 or LCS 2005 with SP1. However when you start the Live Communication Server Administration tool you got blank page only.
There's nothing appear at the left hand side of the mmc window. The account that you are using already have the correct permission.

Resolution

Create a new MMC snap-in to manage the Live Communication Server 2005.

> Click Start, click Run, type mmc, and then click OK.
> In the Console1 MMC snap-in, click Add/Remove Snap-in on the File menu.
> In the Add/remove Snap-in dialog box, click Add, click Live Communications Server 2005 in the Add Standalone Snap-in dialog box, click Add, click Close, and then click OK.
> On the File menu, click Save As.
> In the Save As dialog box, locate the %WINDIR%\System32 folder.
> In the File name box, type wrtcsnap2.msc, and then click Save.
> Click Yes when you are prompted to overwrite the existing wrtcsnap2.msc file.

For details, please see http://support.microsoft.com/kb/926921

Email being block by att.net

Description:

Users are having issue when sending email to certain domain. From the undeliverable message, you could see, " is blocked. For information see http://att.net/blocks'>". You've check with known blacklist provider and none of them have your IP listed.

Resolution:

To remove your IP from their list is through their website http://att.net/blocks. Choose Tools for administrators of mail systems whose messages have been blocked. Fill in your IP address, name, contact number, and the error message that you received. After that click submit. It would take a couple of days for them to remove your IP.

Email being block by 88.blackzap.net – Frontbridge

Description:

Users are having problem sending email to some domain. From the error message you could see “smtp; 550 Service unavailable; Client host [xxx.xxx.xxx.xxx] blocked using 88.blacklist.zap; Mail From IP Banned To request removal from this list please forward this message to delist@frontbridge.com>”. You’ve check with known blacklist provider and none of them have your public IP listed.

Resolution:

The only way to get your public IP remove from their blacklist is through email. The list is proprietary and not open for public. You need to send them email asking for delisting and they will reply back to you in one business day. This is the case if you get listed the first time. But if you IP get listed again, the process would be more difficult and take much longer time.

Frontbridge is owned by Microsoft and its part of their Exchange Hosted Services. However the support seems only available on US working hour’s time. Other than that, there’re some false positive that could make good legitimate email being blocked.

Cannot start IPSEC service error. The system cannot find the file specified.

Description:
Suddenly you cannot logon to the domain from a server. You cannot ping it, even though the network card is connected to the network and functioning normally. You can ping to self from the server. No firewall blocks the connection. When looking through event viewer, you notice 2 errors were log; Event ID 7023 and Event ID 4292 (IPSec driver has entered Block mode). Both are related to IPSEC. You check the IPSEC services and found that you cannot start it. There’s “The system cannot find the file specified” error.

Resolution:
The problem occurs when there’s corrupted file in the policy store. The file may become corrupted if an interruption occurs when the policy being written to the disk. To solve it, please go to HKEY_LOKAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\IPSec\Policy\Local. Delete this subkey (if exist). After that, rebuild the new local policies store. To do that, click Start > Run > type regsvr32 polstore.dll. Try starting the IPSEC services again. All issue should work well now.