Day: February 18, 2008

Hotplug

by ucinfo, posted in Flaphead, Gadgets

Found this on Bruce’s blog (http://www.schneier.com/blog/archives/2008/02/hotplug_1.html)

Check it out! http://www.wiebetech.com/products/HotPlug.php

With HotPlug, you can move a computer without powering it down!

We created this product for our Government/Forensic customers – but it has IT uses as well. Need to move a server without powering it down? HotPlug can do it.

Bottom line: WiebeTech’s HotPlug LT allows hot seizure and removal of computers from the field to anywhere else on the planet. HotPlug LT keeps power flowing to the computer while transferring the computer’s power input from one A/C source (such as a wall outlet or power strip) to another (a portable UPS) and back again.

check out the youtube video! http://www.wiebetech.com/videos/HPLT_Demo.php

 

Windows 2003 SP2 & Exchange 2003

by ucinfo, posted in !Things2Remember, Flaphead, MsExchange

Here we go again.  So nice new DL585 G2.  Slapped Exchange 2003 on SP2 and few other fixes and then started noticing there:

Event Type:    Error
Event Source:    Application Popup
Event Category:    None
Event ID:    333
Description:
An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system’s image of the Registry.

Event Type:    Error
Event Source:    Srv
Event Category:    None
Event ID:    2019
Computer:    GBRPSMMSWM06NA
Description:
The server was unable to allocate from the system nonpaged pool because the pool was empty.

I have /3g /userva:3030.

When you open task manager, Nonpaged is 96512!

This is Windows 2003 Ent with SP2  .. any ideas?

Microsoft Exchange 2007- Error There is a Problem with the Proxy Servers Security Certificate. Outlook Client Can Not Connect to an Exchange 2007 Server

by ucinfo, posted in Flaphead, KB Articles, MsExchange

Remember this? http://blogs.flaphead.dns2go.com/archive/2007/11/13/exchange-2007-msexchangeis-9646.aspx

Interesting how HP has hidden this .. I like the final words .. “The real fix is to make sure the network card supports the new featured offered in SP1 and SP2 of Windows Server 2003. Consult the manufacture of the network card for updated drivers. ” BUT THAT IS YOU HP!

Source: http://h10025.www1.hp.com/ewfrf/wc/genericDocument?lc=en&cc=us&docname=c01141389&dlc=en&printable=yes&encodeUrl=true&

ISSUE:
Exchange 2007 Standard. No service pack. Window 2003 Standard SP1

Outlook 2007
Windows XP

Customer had a single user that can not connect to the Exchange 2007 server using Outlook. He could use OWA and connect successfully. He tried using OL 2003 and 2007 with the same error. When trying to use auto discovery after he is prompted for credentials he would get error:

There is a problem with the proxy server’s security certificate. The name on the security certificate is invalid or does not match the name of the target site Outlook is unable to connect to the proxy server (Error code:0)

When he manually configures Outlook and gave credentials he would get error: Cannot open your default email folders. You must connect to Microsoft exchange with the current profile before you can synchronize your folders with you offline folder file.

Troubleshooting:
Customer moved the mailbox to another server. This broke OWA. We then removed the exchange attributes of the mailbox by doing a remove in Exchange 2007 console. After reconnecting the mailbox OWA worked again but we still had the same problem as before. We also notice this error in the event log:
Event Type: Error   
Event Source: MSExchangeIS   
Event Category: General   
Event ID: 9646   
Description:   Closing Mapi session “/o=Organization/ou=Administrative Group/cn=Recipients/cn=Recipient” because it exceeded the maximum of 32 objects of type “session”. 

This would suggest a third party program making too many connections but this was not the case. The problem was with the network card and is described in this article although the errors we got were not documented.

http://msexchangeteam.com/archive/2007/07/18/446400.aspx

With the release of the Scalable Networking Pack that is included with Windows 2003 SP2, we in Exchange support have been seeing some connectivity issues once the new networking features are enabled. These new features are enabled by default and are only used if your network card driver supports them. Some of the new architectural additions that were introduced with the Scalable Networking Pack are TCP Chimney Offload, Receive-side Scaling

SOLUTION:
Resolution:
To Disable TCP Chimney, Navigate to the following registry key and set the value to 0. Note: You have to reboot the server after this registry change.

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters]
“EnableTCPChimney”=dword:00000000

The real fix is to make sure the network card supports the new featured offered in SP1 and SP2 of Windows Server 2003. Consult the manufacture of the network card for updated drivers.