Few days ago I got a error of undeliverable message on exchange 2003.

Undeliverable error

Possible Cause:

• The e-mail account does not exist at the organization the message was sent to. This issue may occur if there was a problem when users were moved between sites. For example, if a former Administrative_Group_1 user moves to Administrative_Group_2 and then replies to an old e-mail message, or if the user does not re-create his or her Outlook profile, an old Administrative Group style LegDN address will be used, and an NDR is generated.
• The message was sent to obsolete personal address book entries.
• The categorizer rejected delivery because you configured your SMTP contact with see comment SMTP RFC821 characters.

Troubleshooting: Verify the recipient address and resend the message. Verify that the recipient address is formatted correctly and that the categorizer was able to correctly resolve the recipient.

After resending to proper recipient I got the problem solved.

Few days ago I got the following error on a pc.

The problem occurs because Microsoft Data Access Components (MDAC) is not installed on the computer. The .NET application uses MDAC to access the data from the database.

To resolve this problem, I installed MDAC on the computer. I downloaded MDAC from the following Microsoft Developer Network (MSDN) Web site:Data Access downloads
http://msdn2.microsoft.com/en-us/data/aa937695.aspx

And now the problem is solved.

Few days ago I got a problem on MS outlook that it could not view images. I solved the error on following way.

1. Go to run from start menu

2. Type regedit

3.Go to HKEY_USER\Software\Microsoft\Office\11.0\Outlook\Security\OutlookSecureTempFolder

4. In right pane Navigate to the value of this key %USERPROFILE%\LocalSettings\Temporary Internet Files\OLK3D where OLK3D Value change in different values

2 dyas ago I found that there is some lines on desktop “Thayet Myo Hacking Day”. It was a virus/worm. It slow down the pc. I removed the virus on following way.

1.  Open My Computer, click on tools and select Folder option.

2. Go to View Tab, and select “Show Hidden files and folder” and uncheck “Hide extensions for known file system” and “Hide protected operating system files (recommended)”.

3. Start the pc on Safe mode.

4. Delete the explorer.exe files in C:\recycler, C:\Windows\Backup and C:\.

5. Open regedit and delete explorer file in hkey_local_machine/software/microsoft/windows/current version/run .

6. Restart the pc. Update the AV installed on your pc and scan whole HDD.

I have done it for Debian. Trusted HTTPS configuration is the last page. I took help from the URL:
http://www.debianhelp.co.uk/apachetomcat.htm
http://www.debianhelp.co.uk/selfcert.htm
Requirements:
Apache2, mod_jk, apache tomcat 5.5.16,  JDK, openssl, libapache-mod-ssl

Step by step Configuration:
1. Install apache2. For tomcat we have to change some from the normal configuration. (I folowed the URL http://www.debianhelp.co.uk/apachetomcat.htm )

How To Download And Install The VSFTP Package:

RedHat and Fedora software is installed using RPM packages. As of this writing, the most recent Fedora version used a VSFTP RPM file is named:

# vsftpd-1.2.0-5.i386.rpm

Now download the file to a directory such as /tmp and install it using the rpm command:

[root@bigboy tmp]# rpm -Uvh vsftpd-1.2.0-5.i386.rpm
Preparing… ########################################## [100%]
1:vsftpd     ########################################## [100%]

[root@bigboy tmp]#

How To Get VSFTP Started

Redhat Version 9, Fedora Core 1And Newer

You can start/stop/restart vsftpd after booting by using the following commands:

[root@bigboy tmp]# /etc/init.d/vsftpd start
[root@bigboy tmp]# /etc/init.d/vsftpd stop
[root@bigboy tmp]# /etc/init.d/vsftpd restart

To get vsftpd configured to start at boot:

[root@bigboy tmp]# chkconfig –level 345 vsftpd on

Testing To See If VSFTP Is Running

[root@bigboy root]# netstat -a | grep ftp
tcp        0        0        *:ftp         *:*        LISTEN
[root@bigboy root]#

Configuring The VSFTP as anonymous:

# vi /etc/vsftpd/vsftpd.conf

anonymous_enable=YES
local_enable=YES
write_enable=YES
anon_upload_enable=YES
anon_mkdir_write_enable=YES
xferlog_enable=YES

Other vsftpd.conf Options

There are many other options you can add to this file including:

Limiting the maximum number of client connections (max_clients)

Limiting the number of connections by source IP address (max_per_ip)

The maximum rate of data transfer per anonymous login. (anon_max_rate)

The maximum rate of data transfer per non-anonymous login. (local_max_rate)

Descriptions on this and more can be found in the vsftpd.conf man pages.

The /etc/vsftpd.ftpusers File

For added security you may restrict FTP access to certain users by adding them to the list of users in this file. Do not delete entries from the default list, it is best to add.

Anonymous Upload

If you want remote users to write data to your FTP server then it is recommended you create a write-only directory within /var/ftp/pub. This will allow your users to upload, but not access other files uploaded by other users. Here are the commands to do this:

[root@bigboy tmp]# mkdir /var/ftp/pub/upload
[root@bigboy tmp]# chmod 733 /var/ftp/pub/upload

FTP Greeting Banner

Change the default greeting banner in the vsftpd.conf file to make it harder for malicious users to determine the type of system you have.

ftpd_banner= New Banner Here

Configuring The VSFTP as Sucure Users:

# vi /etc/vsftpd/vsftpd.conf

# anonymous_enable=YES
local_enable=YES
write_enable=YES
# anon_upload_enable=YES
# anon_mkdir_write_enable=YES
xferlog_enable=YES

FTP Users With Only Read Access To A Shared Directory:

Create a user group and shared directory. In this case well use “/home/ftp-users” and a user group name of “ftp-users” for the remote users.

[root@bigboy tmp]# groupadd ftp-users
[root@bigboy tmp]# mkdir /home/ftp-docs

Make the directory accessible to the ftp-users group.

[root@bigboy tmp]# chmod 750 /home/ftp-docs
[root@bigboy tmp]# chown root:ftp-users /home/ftp-docs

Add users, and make their default directory /home/ftp-docs

[root@bigboy tmp]# useradd -g ftp-users -d /home/ftp-docs user1
[root@bigboy tmp]# useradd -g ftp-users -d /home/ftp-docs user2
[root@bigboy tmp]# useradd -g ftp-users -d /home/ftp-docs user3
[root@bigboy tmp]# useradd -g ftp-users -d /home/ftp-docs user4
[root@bigboy tmp]# passwd user1
[root@bigboy tmp]# passwd user2

[root@bigboy tmp]# passwd user3
[root@bigboy tmp]# passwd user4

Change the permissions of the files in the /home/ftp-docs directory for read only access by the group

[root@bigboy tmp]# touch /home/ftp-docs/abc
[root@bigboy tmp]# chown root:ftp-users /home/ftp-docs/*
[root@bigboy tmp]# chmod 740 /home/ftp-docs/*

Users should now be able to log in via ftp to the server using their new user names and passwords. If you absolutely don’t want any FTP users to be able to write to any directory then you should comment out the write_enable line in your vsftpd.conf file like this:

#write_enable=YES

Restart vsftp for the configuration file changes to take effect.

Sample Login Session To Test Funtionality

Check for the presence of a test file on the ftp client server.

[root@smallfry tmp]# ls
total 1
-rw-r–r– 1 root root 0 Jan 4 09:08 testfile

[root@smallfry tmp]#

Now we have to keep the file in location:

# cd /home/ftp-docs/ that will be downloaded.

Hello, today some while ago i configured a DNS on Debian successfully. I ma writting this post using my DNS. Here is the configuration method of DNS.

Step1. At the very beginning I installed the package bind9 that is used for configuring DNS at Debian. I just write down the command,

apt-get install bind9

It will install the package bind9 within few minutes and now, we are ready to configure our DNS server.

Edit file named.conf in directory /etc/bind . And in this tutor, the domain is test.com.

vi /etc/bind/named.conf

Here we have to add the following lines at the end last ‘Zone’ paragraph.

zone “test.com” {
type master;
file “/etc/bind/test”;
};

zone “1.62.10.in-addr.arpa.” {
type master;
file “/etc/bind/reverse”;
};

after it, save and exit with type “:wq!”

and now we have to make the zone file and reverse zone file, in directory as we edited in file named.conf

vi /etc/bind/test
and you have to put some configuration like this;

$TTL 604800
1.62.10.in-addr.arpa. IN SOA debian. root.test.com. (
1 ;

Serial 604800 ;

Refresh 86400 ;

Retry 2419200 ;

Exipire 604800 ) ;

Negative Cache TTL
;
@ IN NS debian.test.com.
@ IN MX 10 debian.test.com.
debian IN A 10.62.1.100
www IN CNAME debian.test.com.

then save and exit, with type “:wq!“

after it, you must create reverse zone file

vi /etc/bind/reverse
then put some configuration like this;

test’s zone file :
$TTL 64800
@ IN SOA debian root.test.com (
1 ;

serial 7200 ;

refresh 7200 ;

retry 36000 ;

expire 7200 ) ;

mimimum
;
@ IN NS debian.test.com.

debian IN A 10.62.1.100

100 IN PTR debian.test.com.

then save and exit, with type “:wq!“

and now you should configure dns resolver.

Edit file of directory /etc/resolv.conf
and put some configuration there!

vi /etc/resolv.conf

And add the following lines.

search test.com
nameserver 10.62.1.100
then save and exit with type “:wq!“

and now you should configure the host file.

vi /etc/hosts

put some configuration there!

127.0.0.1 localhost
10.62.1.100 debian.test.com debian

Note: IP address in that domain is 10.62.1.100
and that host has domain test.com
Hope to get suggestion from you.

Few days ago, I faced problem at remote desktop connection. I could could connect to the remote pc through RDC but it was getting hanged after logging in. Later we found that there was change at remote server at firewall. I had to change adjust the TCP MTU to 1300 to get the connection properly. To adjust the TCP MTU I had to do the following things.

To modify the PPPoE MTU size, create the following registry key:

Then add the following registry entries.

To do this:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Ndiswan\Parameters
3. On the Edit menu, point to New, and then click Key.
4. Type Protocols, and then press ENTER.
5. On the Edit menu, point to New, and then click Key.
6. Type 0, and then press ENTER.
7. On the Edit menu, point to New, and then click DWORD Value.
8. Type ProtocolType, and then press ENTER.
9. On the Edit menu, click Modify.
10. Type 800, and then click OK.
11. On the Edit menu, point to New, and then click DWORD Value.
12. Type PPPProtocolType, and then press ENTER.
13. On the Edit menu, click Modify.
14. Type 21, and then click OK.
15. On the Edit menu, point to New, and then click DWORD Value.
16. Type ProtocolMTU, and then press ENTER.
17. On the Edit menu, click Modify.
18. Type the appropriate MTU size (decimal value), and then click OK.
    

    Tuning TCP MTU image 1

19. 19.   Browse to the TCP/IP registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parametersby expanding successive folders on the left panel and scrolling down as needed.
20. Create a MTU value according to this.
    

    MTU

    Key: Tcpip\Parameters\Interfaces\interfaceGUID

    Value Type: REG_DWORD—number

    ValidRange: 88–the MTU of the underlying network

    Default: 0xFFFFFFFF

    

    Adjusting TCP MTU at client pc image 2

    Description: This parameter overrides the default Maximum Transmission Unit (MTU) for a network interface. The MTU is the maximum IP packet size, in bytes, that can be transmitted over the underlying network. For values larger than the default for the underlying network, the network default MTU is used. For values smaller than 88, the MTU of 88 is used. I insert the MTU value 1300.

And Finally I could log in at the remote server through RDC successfully.

Actually I do not know much about this. Any comment or suggestion regarding this topic will be highly appriciated. Waiting to hear from you.

You can run the following commands to directly open these programs

appwiz.cpl >>Add/Remove Programs
desk.cpl >> Display Properties
firewall.cpl >> Firewall Settings
inetcpl.cpl >> Internet Options
mmsys.cpl >> Sound and Audio
ncpa.cpl >> Network Connections
nusrmgr.cpl >> User Accounts
powercfg.cpl >> Power Options
sysdm.cpl >>System Properties
wscui.cpl >> Security Center
wuaucpl.cpl >> Automatic Updates Configuration

Sometimes we get problem after installing windows besides linux. Fresh installation of windows sets boot loading directly from MBR. So, Grub boot loader does not work. We can recover Grub boot loader very easily. To do so, we can follow the following steps.

1. Start the pc on linux rescue mode.

2. In rescue mode do chroot/mnt/sysimage.

3. Then do grub-install /dev/hda

4. Restart the pc.

Now you will find Grub boot loader.