Showing posts with label System and Network Admin. Show all posts
Showing posts with label System and Network Admin. Show all posts

Tuesday, 22 April 2008

Install ntop3.3 onto Ubuntu linux v7 - a brief guide

So now, it seems you have Ubuntu linux working on a PC (or VirtualPC as I am doing now). The next step is to install ntop-3.3 onto it.

Why I like ntop, because I want to see what kind of network traffic my network have. And it seems a good open source tool and many people on the net have discussed about it.

Unfortunately, to install it successfully is not very simple. You might need to download 16~17 packages for it.

There are:

ntop-3.3
automake-1.6.3
autoconf-2.53
libtool-1.5.10
libpng-1.2.26
libtool-1.5.10
openssl-0.9.8g
zlib-1.2.3
rrdtool-1.2.27
freetype-2.1.10
pkg-config-0.23
libart_lgpl-2.3.20
m4-1.4.9
libpcap-0.9.8
flex-2.5.35
bison-2.3
gawk-3.1.6

All of these packages can be searched in Google. And basically you only need to do is just unpack them (except ntop), "./configure", "make", "make install" (as root).

Now you might spent 3 hours for all of these. Before you start to install ntop, you might need to edit configure.in file. Search for the rrd direction and you might have to modify it from default value.

Then you can just use "./autogen.sh", "make" then "make install" to install ntop onto your PC.

Alright, now ntop is on your system under "/user/local/var/ntop". Then you need to create a group and a user to use ntop.

# groupadd ntop

# useradd -m -s /bin/false -d /var/lib/ntop -c "ntop user" -g ntop ntop

For the first run, you need to type this command to change the password for administrator:

# ntop -A

now, you can start ntop:

# ntop -p /var/lib/ntop -u ntop

To check if it is running, you can type "http://localhost:3000" in to web browser.

Monday, 6 August 2007

Exchange Server 2007 Installation Marathon Day 2 - Why does it only support 64bit OS?

Basically 4GB memory limitation is the bottleneck of 32bit OS. When the hardware become cheaper and cheaper, also users with faster network speed (are you still using dial-up internet?) need faster response from server side.
So in an enterprise environment with thousands clients, 4 GB RAM is much less than neccesary for spooling, scanning virus and filtering spams.


Thursday, 26 July 2007

Exchange Server 2007 Installation Marathon Day 1 - Windows Server 2003, AD and IIS

* Hardware Platform:
Core 2 Duo E6320 CPU,
Intel P965 Motherboard,
1GB DDRII 667 RAM,
250GB SATAII HDD,
Intergraded LAN/VGA

* Software Environment:
Windows XP Pro x64 (Host Operating Sytem)
VMWare Server 1.0.2
Windows Server 2003 x64 R2 (Guest Operating system)
Exchange Server 2007


Step 1 - AD, IIS installation

Computer Name: Server01
Domain Name: CONTOSO (just as same as in MSCE training course)
IP Address: xxx.xxx.xxx.8/24
Default Gateway: xxx.xxx.xxx.2 (which is controlled by VMWare to rout your network traffic to internet.)
Primary DNS Server: xxx.xxx.xxx.8 (Which is WinServer 2003, but firstly it isn't been configured. To setting this IP as primary DNS is to avoid error messenge during installing Exchange 2007)
Secondary DNS Server: xxx.xxx.xxx.2 (which is the real one)

After you install AD on your server, you need to raise the Domain functional level to "Windows 2000 native"

Step 2 - Exchange 2007 Installation

The instructuction of Exchange 2007 Installation Wizzard is very clear. Only thing I did is just follow it until get it done.


Friday, 29 June 2007

"netsh" Scripting -- Changing IP settings

"netsh" is a powerful command-line tool for network admin.

If you are tired to click your mouse button to open and close several windows to change IP settings on your laptop between your office and your home, then try this and save them into .VBS format on your desktop.

For network A (by manually assigned):

netsh int ip set address name=”Local Area Connection” source=static addr=192.168.0.xxx mask=255.255.255.0
netsh int ip set address name=”Local Area Connection” source=static gateway=192.168.0.xxx gwmetric=1
netsh int ip set dns name=”Local Area Connection” source=static addr=192.168.1.xxx

NOTE: you might need to check the name of your network connection.

For network B (by DHCP):

netsh int ip set address name=”Local Area Connection” source=dhcp
netsh int ip set dns name=”Local Area Connection” source=dhcp