Outlook 2003 / 2007 Interface not registered

So I installed Office 2007 and rolled it back to Office 2003, Outlook decided I can no longer send email. Whenever I hit send I get an error from Microsoft Word saying “Interface not registered” but then there was the internet… and I found the solution…Solution is here at the MS site

“You receive the “Interface not registered” error message when you try to send or to save an e-mail message to the Drafts folder in Outlook 2002View products that this article applies to.
Article ID : 870707
Last Review : August 10, 2004
Revision : 1.0

SYMPTOMS
If you use Microsoft Word as your e-mail editor in Microsoft Office Outlook 2002, and you try to send e-mail messages or to save e-mail messages to the Drafts folder, you may receive the following error message:
Interface not registered
Or, you may experience the following symptoms:
You receive an error message.
The e-mail message is not sent.
The e-mail message is not saved to the Drafts folder.

CAUSE
This behavior occurs if the Ole32.dll file that is located in the %Windir%\System32 folder is not registered correctly in the registry.

RESOLUTION
To resolve this problem, register the Ole32.dll file. To do this, follow these steps:
1. Click Start, click Run, type the following command in the Open box, and then click OK:
Regsvr32.exe %Windir%\System32\Ole32.dll
2. In the RegSvr32 dialog box, click OK.”

In microsoft outlook, interface not registered = a most sucky error

your ads here (468x60) - after 1st post.

Throttle Bandwidth Based on the Time of Day

Saw this little goodie over on ciscoblog.com

Step 1: Create an access-list that matches my file server (172.30.100.11), but only during the day.

Router(config)# time-range DAY (creates a new time range)
Router(config-time-range)# periodic weekdays 6:00 to 22:00 (matches weekdays from 6:00am to 10:00pm)
Router(config-time-range)# periodic weekend 6:00 to 22:00 (matches weekends from 6:00am to 10:00pm)
Router(config-time-range)# exit
Router(config)# ip access-list extended SERVER
Router(config-ext-nacl)# permit ip host 172.30.100.11 any time-range DAY (matches my server during the time-range I specified above)
Router(config-ext-nacl)# exit
Router(config)#

Step 2: Create a class-map (used for QoS) that matches the SERVER access-list we just created.

Router(config)# class-map MATCH_SERVER (MATCH_SERVER is just the name)
Router(config-class-map)# match access-group name SERVER (ties in the access-list above)
Router(config-class-map)# exit
Router(config)#

Step 3: Create a policy-map (used for QoS) that throttles the bandwidth.

Router(config)# policy-map LIMIT_SERVER (creates the policy)
Router(config-pmap)# class MATCH_SERVER (applies policy to this class)
Router(config-pmap-c)# police 80000 (limits bandwidth to 80Kbps)
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)#

Step 4: Apply the new policy to the incoming interface (the one connected to my LAN, not the Internet).

Router(config)# interface fa0/0
Router(config-if)# service-policy input LIMIT_SERVER 

Cisco - Simple policy to block skype.

Skype can be blocked in a similar way as we use to block kazza,limewire and other p2p applications.

NBAR configuration to drop Skype packets

class−map match−any p2p
match protocol skype

policy−map block−p2p
class p2p
drop

int dialer0
description Internet interface
service−policy input block−p2p

If you are unsure about the bandwidth eating applications being used in your organisation. you can access the interface connected to the Internet and configure following command

ip nbar protocol-discovery.

This will enable nbar discovery on your router.

Use following command

show ip nbar protocol-discovery stats bit-rate top-n 10

it will show you top 10 bandwidth eating applications being used by the users. Now you will be able to block/restrict traffic with appropriate QoS policy.

we can also use ip nbar port-map command to look for the protocol or protocol name, using a port number or numbers other than the well-known Internet Assigned Numbers Authority (IANA)-assigned) port numbers.

You can also create custom definitions using this command.

ip nbar port-map protocol-name [tcp | udp] port-number

Up to 16 ports can be specified with this command. Port number values can range from 0 to 65535

TPG Cisco PPPoE Config

Had some fun getting a 877 working on TPG today.

TPG require you to use PPPoE and PAP not CHAP for authentication.
Also you are required to use the full tpg username ***@L2TP.tpg.com.au

Relivant parts of the config are below.

interface ATM0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
pvc 8/35
encapsulation aal5snap
protocol pppoe
!
!
interface Dialer0
ip address negotiated
encapsulation ppp
dialer pool 1
no cdp enable
ppp authentication pap callin optional
ppp pap sent-username ***@L2TP.tpg.com.au password ***