Often when trying to connect to samba user from Windows client, we received error “Multiple connection to a server or shared resource by the same user, using more than one user name, are not allowed” . To successfully reconnect to samba server we have to terminate the previous session first. So, how to do this without need to reboot the server?.

First, we check the existing connection with.

Second, terminate the connection to the resource.

Then reconnect to samba server

Ariyossss

What the F… I’ve created one new sub domain for new test web site last night but until now (12 hours) it still cannot be resolved. !@#$$. Why tmnet, mynic, jaring & etc so slow?. Other nameserver already resolved this correctly lor.

TMNET nameserver 202.188.1.5

———————————
> web.xx.my
Server:         202.188.1.5
Address:        202.188.1.5#53

** server can’t find web.xx.my: NXDOMAIN

FREE nameserver  208.94.147.150

————————————

> web.xx.my
Server:         208.94.147.150
Address:        208.94.147.150#53

Non-authoritative answer:
web.xx.my  canonical name = www.xx.my.
Name:   www.xx.my
Address: 60.xx.xx.xx

Already 4:13am now but I’m still busy doing some clean up for my office VMs. Well it’s become a challenge lately to monitor & control all the VMs when most of engineers having at least one VM. The difficult part is, I discovered that 5 of the VMs with Logmein client installed and some of you just leave it happily downloading up to 5GB files. Come on dude, I have to upgrade my Fedora before it’s go to production as required by your Boss(My Boss too) but with the current speed, it will take a year to finish. Block Logmein will not solve the problem because I know some of you will require to Logmein to customer site to do remote support. Yehh educate you, sent email and I even provided you all with SSLVPN access but there is no guarantee this headache will not happen again isn’t it?. Sigh…

Although this is not recommended, for emergency cases you can set the vyatta root password using vyatta user account as below :

• #configure
• #set system login user root authentication plaintext-password mynewpassword
• #commit
• #save
• #exit

ariyossss

Might useful to some of you :

• $yum install make (407KB)
• $yum install gcc (34M) -> path -> /usr/bin/gcc
• $yum install kernel-devel (20M) –> path –> /usr/src/kernels/2.6.33.3-85.fc13.x86_64/include/
• $mkdir /tmp/vmware
• $cd /tmp/vmware
• $tar -zxvf /media/VMware\ Tools/VMwareTools-8.3.2-257589.tar.gz
• $cd vmware-tools-distrib/
• $./vmware-install.pl
• $/usr/bin/vmware-user
• Logout & login back
• Restart x server

Notes : New initrd will be created during this Vmware Tools installation. I Recommend you to take a snapshot for roll-back purpose before you are going to install it.

Give myself a minute to try the installation of Fedora 13 on ESXi 4.1. Wondering if I can find anything special on this release compare to the other distro. Once VM created, I just set the memory to 1024MB and 1 vCPU for this 64bit Fedora and ready to give ago.

At the beginning of the installation I discovered that, there is an option (storage) for you to install Fedora image onto SAN & DAS. Well, this  sound good to someone who want to try to boot up their OS image from other than normal storage (vmdk). Default partition layout is nothing much different from Redhat default installation. One default LVM volume is enough and ext4 remain as Fedora default file system type. The rest of configurations are very similar to Redhat. What surprised me was, the installation only took less than a minute to complete. Read more

Sigh, due to general support for ESX 3.5 U3 and vCenter 2.5 U3 already finished, me and my colleague (Mr.Lai) have to work tonight. We are going to upgrade all four ESX 3.5 U3 to U5 and vCenter 2.5 U3 to U6 at the same time. Hopefully both HP blade 460c and FalconStor NSS storage doesn’t cause me anything after we upgrade it. BTW, I’m thinking, why not we go for vSphere 4.0 or 4.1 right?
Nevertheless, I’m going to take my sahur at Kg.Baru “Nasi Lemak Antarabangsa” later. Read more