Problems with KB967723 in windows update. Error code: 80070490

In Windows 2008, when you do a windows update you can receive a error code 80070490  when apply the update KB967723.

If you experience this problem, download the patch manually and install it.

Download i386 from here:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=35c1d5a9-a953-4fc6-90c0-d2358c7b89e6

Download X64 from here:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6e46822e-f79d-492d-ad01-ee680ad324f5

Dell openmanage and Nimbus monitoring – SNMP Traps

Start Dell openmange.

Goto System -> Alert Management -> SNMP Traps.

Select all the information you want sent to Nimbus

Now startup services in adminsitration tools, and right click on SNMP Services and choice Properties.
Go to Traps, and type community name, in my example it is appmanager, and the traps destionations should be the nimbus server or where you are going to install the snmptd agents in nimbus.

No go into nimbus and install snmptd and dom_traps on the host where you will monitoring the Dell openmanage hardware.
And then go to host, and right click on snmptd agents, and choice configure.

Press the last icon, “User/Security Manager” and put in the community name from last step, in my example that will be appmanager.

Now you should be running

Sponsor link: http://www.it-århus.dk

Pureftpd (Ubuntu / Debian)

Setting up Pure ftpd to run on certains port is very simple.
Log on to you linux box and run this command:

echo “60010 60030” > /etc/pure-ftpd/conf/PassivePortRange
/etc/init.d/pure-ftpd restart

or if you run mysql as a backend

/etc/init.d/pure-ftpd-mysql restart

Now you just need to forward port 60010 to 60030, to you linux box.

ipsec Services: Only one usage of each socket address protocol network address port is normally permitted.

I have a servers that would not connect to the Internet, if I ping the gateway it says that:

Destination unreachable.

i found that the IPSec service was not stated. And if I start it it say: Only one usage of each socket address protocol network address port is normally permitted.

i found that there have been some problems after install

After Installing MS08-037 (951746 and 951748)

The solution was to reserved som port in the TCP/IP protocol

Here is the list of ports that we have seen conflicts with services on the machine.

  • 1645-1646 – Used by IAS
  • 1701-1701 – Used by L2TP
  • 1812-1813 – Used by IAS
  • 2883-2883 – Used by AUTD
  • 4500-4500 – Used by IPSEC

For now we are suggesting customers be proactive and modify the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ReservedPorts

I also found this in my event viewer

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 7/12/2008
Time: 6:38:37 PM
User: N/A
Computer: SERVER
Description:  The IPSEC Services Service terminated with the following error:  Only one usage of each socket address (protocol/network address/port) is normally permitted.

Event Type: Error
Event Source: IPSec
Event Category: None
Event ID: 4292
Date: 7/15/2008
Time: 2:53:14 PM
User: N/A
Computer:    SERVER
Description:  The IPSec driver has entered Block mode. IPSec will discard all inbound and outbound TCP/IP network traffic that is not permitted by boot-time IPSec Policy exemptions. User Action: To restore full unsecured TCP/IP connectivity, disable the IPSec services, and then restart the computer.  For detailed troubleshooting information, review the events in the Security event log.

Thanks to http://blogs.technet.com/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-properly-after-installing-ms08-037-951746-and-951748.aspx

Min ønskeliste

Byggemarked:
Glasfiber flagstang.
Askespand
Brændespand til gildesal
Rive til havetraktor
AEG 18V Stiksav (Batteri)
Kompresser
Støvsuger til værksted, gerne med mulighed for at tilslutte sav. (Så den suger nå saven er i brug)
Kabeltromle 40 meter ledning
Mefa Postkasse (630) (Sort med en sølv bølge)
Skruer til torks (30mm / 40mm / 50mm / 60mm)
Lagerreol. Til udehuset, til opbevaring af div. redskaber, kasser og andet.
Haveslange vogn.
Nordlux outdoor discos væglamper i sort (Fåes i uge 49 til 399 pr. stk)

IT:
WD TV Live

Isenkræmmer:

Perfection Ølglas (holmegaard).
Zwilling Pizzaskærer.
Raclette (Skal fordel varmen godt, evt Tefal Harmony Pierrade).
Barbermaskine (Gerne med selvvask og sådan den kan holde til vand)

Film:
24 timer sæson 4 og 5.
Klovn DVD (Hele samling er udgivet i en boks.

Spil
Settlers (Brætspil) også gerne div. udvidelser til spillet.

Musik
D-A-D: The overmuch Box – set her: http://www.gaffashop.dk/shop/d-a-d-the-overmuch-46223p.html

A significant number of invalid certificates have been provided by remote IP address 205.188.153.55 / 64.12.162.248

AOL has change there Root Certificate.
You can download them at https://pki-info.aol.com/AOL/

These 2 need to be imported in all Office Communication Server T – rusted Root Certification Authorities

You can see a video on howto import these 2 certificates here: http://simsbury.members.winisp.net/Update-AOL-Root-CA.wmv

There errors is belov

Multiple invalid incoming certificates.

In the past 1185 minutes the server received 12 invalid incoming certificates. The last one was from host 64.12.162.248.
Cause: This can happen if a remote server presents an invalid certificate due to an incorrect configuration or an attacker.
Resolution:
No action needed unless the number of failures is large. Contact the administrator of the host sending the invalid certificate and resolve this problem.

Over the past 0 minutes Office Communications Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80090325 (The certificate chain was issued by an authority that is not trusted.) while trying to connect to the host “sip.oscar.aol.com”.

Cause: Wrong principal error could happen if the peer presents a certificate whose subject name does not match the peer name. Certificate root not trusted error could happen if the peer certificate was issued by remote CA that is not trusted by the local machine.

In the past 0 minutes the server received 1 invalid incoming certificates. The last one was from host 64.12.162.248.

Cause: This can happen if a remote server presents an invalid certificate due to an incorrect configuration or an attacker.

Remote principal name is not configured in trusted server list.

After buying a CA sign certificate from Geotrust i got this in my Event viewer:

Remote principal name is not configured in trusted server list.

The subject name sip.XXX.com of the certificate assigned to process AVMCUSvc(1788) was not found in the trusted server list.
Certificate serial number: OU=Equifax Secure Certificate Authority, O=Equifax, C=US
Certificate issuer name: 0DA2A3.
Cause: Incorrect setup of the pool. Should never happen.
Resolution:
Verify that the Subject Name of the certificate presented by the remote peer is configured in the trusted server list.

For more information, see Help and Support Center at

I fix this problem by typing:

c:
cd \
cd “C:\Program Files\Microsoft Office Communications Server 2007 R2\ResKit”
cscript OCSTrustEntry.vbs /action:add /FQDN:sip.XXXX.com /type:TrustedServer

Sponsor link: http://www.it-århus.dk / http://www.it-aarhus.dk