Dark Developments Where Knowledge Meets Power

26Mar/120

BBOX – Belgacom BBOX Bridge

Posted by Dark#Basics

BBOX - Belgacom BBOX Bridge
It's quite easy to set-up a B-BOX into Bridge mode once you know it.

Bridging is a forwarding technique used in packet-switched computer networks. Unlike routing, bridging makes no assumptions about where in a network a particular address is located. Instead, it depends on flooding and examination of source addresses in received packet headers to locate unknown devices. Once a device has been located, its location is recorded in a table where the source address is stored so as to avoid the need for further flooding. The utility of bridging is limited by its dependence on flooding, and is thus only used in local area networks.

1. Connect to the router and login into the Admin Interface. By default the interface can be found by surfing to 192.168.1.1.

2. Select Advanced Settings, ‘Network Interfaces’ in the Menu.


3. Select WAN PPPoE, select Disable and apply the changes by selecting OK.

Once the b-box has disabled the Network Interface the modem will be in bridging mode. Do note that the device after the modem will need to provide the PPPoE authentication by using the username and password provided by the ISP.

Filed under: Networking No Comments
7Mar/120

IIS – Could not load file or assembly…

Posted by Dark#Basics

Could not load file or assembly 'Microsoft.Web.Extensions'
When adding a new website to IIS it is possible that you receive the following error message when browsing to the site.

Select All Code:
1
Could not load file or assembly 'Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

In my case the solution was to change the application mode the classic instead of integrated (Default). This can be done by going to IIS Manager > Application Pools > Select Site > Edit Application Pool > Basic Settings... and changing the Managed Pipeline mode to Classic.

6Mar/120

WSUS – Move WSUS Database Files to a Different Volume

Posted by Dark#Basics

WSUS - Move WSUS Database Files to a Different Volume

  1. Launch SQL Server Management Studio Express console as an administrator. It is located under Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express.
  2. Fill in the following information and then click Connect
    • Server type: Database Engine
    • Servername: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
    • Authentication: Windows Authentication

    clip_image004

  3. Expand Databases and right-click on SUSDB and select Tasks > Detach... from the context menu.
  4. clip_image006

  5. Select the "Drop Connection" checkbox and click OK. It is possible that you receive an error message that the database can't be detached. This is because the services IIS Admin Server and Update Services are still running. Make sure that the services are stopped and try to detach the SQL database again.
  6. clip_image008

  7. Open explorer and move the C:\WSUS\SUSDB folder to the <new drive>:\WSUS directory.
  8. To reattach the database, right-click on Database and select Attach… from the context menu.
  9. clip_image010

  10. On the Attach Databases page select the Addbutton.
  11. clip_image012

  12. Browse to the new location of the SUSDB.mdf database and select OK twice to complete the move.

www.geeklab.info/2010/05/how-to-move-your-susdb-wsus/

blogs.technet.com/b/sbs/archive/2009/09/23/how-to-move-wsus-content-and-database-files-to-a-different-partition.aspx

6Mar/120

BACKUPEXEC – ERROR: Failed to install SQL Express BKUPEXEC Instance

Posted by Dark#Basics

"ERROR: Failed to install SQL Express BKUPEXEC Instance"

When doing a fresh install of BackupExec I've encountered the following error: ERROR: Failed to install SQL Express BKUPEXEC Instance". When doing the system diagnostics from BackupExec it mentioned that the WMI check failed. The KnowledgeBase of BackupExec gave me a possible workaround for the WMI issue. It was running the following commands through the CLI.

Select All Code:
1
2
3
4
5
6
7
8
9
10
11
12
net stop winmgmt
cd /d %windir%\system32\wbem
for %i in (*.dll) do RegSvr32 -s %i
scrcons.exe /RegServer
unsecapp.exe /RegServer
wbemtest.exe /RegServer
winmgmt.exe /RegServer
wmiadap.exe /RegServer
wmiapsrv.exe /RegServer
wmic.exe /RegServer
wmiprvse.exe /RegServer
net start winmgmt

In my case this didn't helped. But what I did notice that it was an error when creating the SQL Instance, what if we can create this instance in advance and instruct BackupExec to install the database there?
This is possible by running the SQL setup and by creating a new SQL-instance. After that the instance is created and running, verify that the service SQL (INSTANCENAME) is running, we'll be able to install the BackupExec database to the created instance by running the 'Advanced'-setup feature.

Filed under: BackupExec No Comments