Senin, 13 Februari 2012

windows cannot connect to the printer windows 7


Try this.....I have seen it work on machines upgraded or coming into a previous 32bit environment. Try this on the machine sharing the printer.
1) Share Permissions
1. On explorer, go to C:\windows\system32\spool\PRINTERS
2. Right click, Properties
3. Sharing tab
4. Advanced Sharing
5. Check "Share this folder"
6. Permissions
7. Grant everyone Full Control
2) NTFS Permissions
1. On explorer, go to C:\windows\system32\spool\printers
2. Right click, Properties
3. Security tab
4. Edit
5. Add
6. Advanced
7. Find Now 8. Choose "NETWORK"
9. OK
10. Grant Network full control.
You may also need this last step.
1. Go to "Printers"
2. click "Add Printer"
3. "Add a Local Printer"
4. "Create a New Port"
5. use the "Local Port" option
6. at "Enter a Port Name" enter: "\\Computername\Printername"

Minggu, 12 Februari 2012

How To Change Default Email Client


 


 

How To Change Default Email Client

To change the default e-mail client:-

1.Open Internet Explorer, click the Tools menu, select Internet Options. Click Programs tab and select your email client from the drop-down list. Once selected, click OK/Apply button.

Remote desktop connection "The local policy of this system does not permit you to logon interactively"

Let me fix it myself

To resolve this issue, add allowed users to the Remote Desktop Users list:
  1. Click Start, point to Settings, and then click Control Panel.
  2. Double-click System, and then on the Remote tab, click Select Remote Users.
  3. Click Add type in the user account name, and then click OK.

    If you are adding more than one user name, use a semicolon to separate the names.
Note: Adding users to the Remote Desktop Group requires that you are logged on through an administrator account.

Also, make sure that the Remote Desktop Users group has sufficient permissions to log on through Terminal Services. To do this, follow these steps:
  1. Click Start, click Run, type secpol.msc, and then click OK.
  2. Expand Local Policies, and then click User Rights Assignment.
  3. In the right pane, double-click Allow logon through Terminal Services. Make sure that the Remote Desktop Users group is listed.
  4. Click OK.
  5. In the right pane, double-click Deny logon through Terminal Services. Make sure that the Remote Desktop Users group is not listed, and then click OK.
  6. Close the Local Security Settings snap-in.

Kamis, 09 Februari 2012

Mengetahui Penyebab Terjadinya BlueScreen di Komputer Anda dengan BlueScreenView




Pernahkah komputer anda mengalami BlueScreen secara tiba-tiba? BlueScreen adalah kejadian dimana layar komputer anda tiba-tiba berwarna biru akibat dari sebuah crash yang terjadi di komputer anda. BlueScreen ini biasanya dikarenakan adanya driver yang sedang anda akses mengalami crash secara tiba-tiba.
Ketika BlueScreen terjadi, hal yang biasanya kita lakukan adalah merestart atau mematikan komputer kita dan menghidupkannya kembali. Kita tidak tahu apa penyebab BlueScreen tersebut dan driver mana yang mengalami crash sehingga membuat BlueScreen tersebut muncul. Akhirnya walaupun BlueScreen sering terjadi di komputer kita, kita tidak mengetahui apa penyebabnya.
Bagi anda yang ingin mengetahui apa yang menyebabkan BlueScreen tersebut terjadi, anda bisa menggunakan software BlueScreenView. Mengetahui penyebab terjadinya BlueScreen ini sangat penting karena dengan tahu apa penyebabnya, kita bisa lebih mudah mencari solusinya.
BlueScreenView adalah software yang bisa anda gunakan untuk melihat penyebab BlueScreen (BSOD / Blue Screen of Death) melalui informasi crash yang terdapat di dump files.
BlueScreenView bekerja dengan cara melakukan scanning ke semua file minidump yang terbuat ketika terjadi BlueScreen. Informasi tersebut kemudian ditampilkan dalam sebuah tabel yang berisi nama dari file minidump, tanggal dan waktu terjadinya crash, informasi dasar tentang crash yang terjadi, serta driver atau module mana yang menyebabkan crash tersebut (Nama file, Nama produk, deskripsi file serta versi file)
BlueScreenView bisa anda gunakan di komputer dengan sistem operasi Windows XP, Windows Server 2003, Windows Server 2008, Windows Vista dan Windows 7.
Ketika windows anda mengalami BlueScreen (Blue Screen of Death), maka anda bisa mengetahui penyebabnya dengan menggunakan software BlueScreen View. Software bekerja dengan cara melakukan scanning di file Minidump yang dibuat oleh windows ketika terjadi BlueScreen crash. Namun sayangnya, tidak semua komputer windows anda terkonfigurasi untuk membuat file minidump ketika bluescreen crash terjadi. Solusinya adalah mengkonfigurasinya secara manual, seperti apa caranya? Baca panduan lengkapnya berikut ini:
Bagi anda pengguna Windows XP :
1.Cukup klik “Start” -> dan klik kanan “My Computer” dan pilih “Properties”
2.Pada Tab “Advanced”, klik tombol setting yang ada di dalam sub tab “Startup and Recovery”
3.Pada sub tab “Write Debugging Information”, pilih “Small Memory Dump” kemudian klik OK
Bagi Pengguna Windows Vista :
1.Klik “Start” -> klik kanan “Computer” dan pilih “Properties”
2.Klik “Advanced System Settings”
3.Pada tab “Advanced” klik “setting” yang ada di dalam sub tab “Startup and Recovery”
4.Pada kotak “Write Debugging Information”, pilih “Small Memory Dump” dan klik OK
Bagi Pengguna Windows 7 :
1.Buka Control Panel kemudian pilih “System And Security”.
2.Klik “System” dan klik “Advanced System Settings”
3.Di tab “Advanced”, klik tombol “setting” yang ada di dalam box “Startup and Recovery”
4.Pada kotak “Write Debugging Information”, pilih “Small Memory Dump” dan klik OK
Setelah konfigurasi minidump anda benar, maka setiap kali windows mengalami BlueScreen (BSOD), sebuah file minidump akan tersimpan di windows anda. File inilah yang nanti bisa diakses oleh software BlueScreen View untuk menganalisa apa penyebab terjadinya BlueScreen di komputer anda.
Bagi anda yang ingin mendownload BlueScreenView klik image dibawah :
Setelah BlueScreenView terinstall di komputer anda dan anda buka, maka anda akan mendapati 2 panel utama dari BlueScreenView. Panel yang atas berisi semua informasi BlueScreen Crash yang tersimpan di file Minidump komputer anda. Sedangkan detailnya akan ditampilkan di panel bawah. BlueScreenView juga akan menampilkan tampilan BlueScreen yang sangat mirip dengan BlueScreen Windows saat crash terjadi.
Hal penting yang perlu anda ingat adalah bahwa agar BlueScreenView ini bisa bekerja, komputer anda sudah harus terkonfigurasi untuk bisa menyimpan minidump file ketika terjadi crash.

“The current time on this computer and the current time on the network are different. For more information about Date/Time Properties, see Help and Support. To log on, contact your system administrator.”




At first I thought that the local time on the laptop was incorrect or possibly in the wrong time zone.
That all checked out…
After reading several posts I decided to check the BIOS time settings, which again were all correct…
I also tried removing the PC from the Domain and re-adding it.  I still received the same error.
What I did to fix our issue was as follows.
1) Log on locally with the local Administrator password
2) open cmd prompt
3) NET USE \\DCNAME /user:myname entered my password
4) NET TIME \\DCNAME /SET /Y
I am now able to log into the domain with my domain account.
The entire network is in upgrade mode, so if there is an underlying issue I hope to have it resolved very soon.
ALSO NOTE! When using Sinmantec Ghost to create a Ghost image of a IBM T400 Laptop. Make sure to use the -ib when creating the image and also (was 50 /50 hit and miss here) the -ib switch when bringing the image down to a new laptop.
If you do not use those switches the MBR record gets hosed and you will have to either use a 98 boot disk to run FIXMBR, or spend a day and a half trying to work around it.

Rabu, 08 Februari 2012

Cannot start Microsoft Office Outlook. Cannot open the Outlook window


I had this problem on a customers laptop with Vista Home Premium and Microsoft office 2007 Enterprise.

I've often seen similar errors with Office including things going wrong with Word, Excel, basically any Microsoft Office application.
Nearly all of these errors can be solved by allowing Office to re-create it's profile folders. I fixed the same problem you are having with this procedure...

1. Close all office applications
2. Browse to and RENAME the following folders (do not delete them if you wish to avoid losing any emails and address books). I normally stick an _ on the end to make it "foldername_"

For Microsoft Outlook...
C:\Users\\AppData\Local\Microsoft\Outlook
C:\Users\\AppData\Roaming\Microsoft\Outlook

For other Microsoft Office Programs...
C:\Users\\AppData\Local\Microsoft\Office
C:\Users\\AppData\Roaming\Microsoft\Office

3. Open problematic application (Outlook in this case)

The next problem you will have with OUTLOOK is your Personal Folders file will be new and therfore empty (none of your old emails, calendar or contacts in there!).
Don't panic though, all you need to do is the following...

1. Open Outlook
2. Go to File>Import and Export...
3. Choose "Import from another program of file" and click next
4. Choose "Personal Folder File (.pst)" and click next
5. Click the browse button and locate the folder that you previously renamed
C:\Users\\AppData\Local\Microsoft\Outlook_ ??
6. Choose the "Outlook.pst" file (which should be more than 1KB if it contains anything) and click the "Open" Button at the bottom
7. Click "Next" and then "Finish" and watch all of your lovely emails, calendar appointments and contacts fly back into your active profile!

Hope that works for you guys.

Selasa, 07 Februari 2012

Register comdlg32.ocx on x64 Win7


Here is how to resolve comdlg32.ocx missing error.
  1. Download comdlg32.zip and extract comdlg32.ocx from zip file
  2. Move comdlg32.ocx to c:\Windows\system32 folder. For 64bit Vista/Win7, move comdlg32.ocx to c:\Windows\SysWOW64
  3. Open a command line window and run following command:
    regsvr32 c:\Windows\system32\comdlg32.ocx
    Note: a) On 64bit Vista/Win7, run this command instead:
    regsvr32 c:\Windows\SysWOW64\comdlg32.ocx
    b) For Vista/Win7 with UAC turn on, the above command needs to be run from elevated command prompt.
  4. Once comdlg32 is registered successfully, following message will prompt, DllRegisterServer in C:\WINDOWS\System32\comdlg32.ocx succeeded.
  5. Now launch the application again you should not see file missing error.
Update: Important note if you use WIN7: when registering comdlg32.ocx, it must be done as administrator, or regsvr32.exe will fail with error 0x8002801c.
To do this as administrator, Go to ‘All Programs -> Accessories -> Command Prompt’, right click on ‘Command Prompt’ icon, and click on ‘Run as administrator’ to start a command prompt, then run the regsvr32 command