Terminal Server User Access Permissions

Ketika saya sudah melakukan install Terminal Server pada OS Windows Server 2003 X64 ternyata terdapat error "To log on to this remote computer, you must have Terminal Server User Access permissions on this computer. By default, members of the Remote Desktop Users group have these permissions. If you are no a member of the Remote Desktop Users group or another group that has these permissions, or if the Remote Desktop User group does not have these permissions, you must be granted these permissions manually." dengan gambar seperti dibawah ini :

Solusinya yaitu :


1. Masuk ke Terminal Server Configuration
2. Klik kanan RDP-TCP, kemudian Properties
3. Pilih tab "Permissions"
4. Klik Add, masukan nama User / Group User yang diperbolehkan melakukan akses.
5. Check list Allow Full Control User / Group User yang baru ditambahkan.

Source: Mbah Google

Demikian, dan berhasil :)

Error Firewall IPNat.sys

Masalah ini terjadi ketika Server tidak bisa diakses oleh Computer lain, padahal melalui Server tersebut akses ke ip terdapat folder-folder yang disharing. Dan computer lain tidak bisa melakukan ping ke server.
Solusinya :
1. Klik kanan My Computer>Manager>Services and Applications>Services.
2. Disable Routing and Remote Access service
3. Setting ulang Gateway pada TCP/IP
4. Jika diperlukan lakukan "Repair"
5. Masuk CMD dan jalankan perintah "ipconfig /flushdns"
Beres deh.

Found this tidbit while researching this problem:
Can't enable windows Firewall on a RRAS server - Windows firewall cannot run because another program or service is running that might use the network address translation component (Ipnat.sys)
Situation: one of our clients could not get the windows Firewall to work. Whenever they tried to start the Windows Firewall, they received the following message: "Windows firewall cannot run because another program or service is running that might use the network address translation component (Ipnat.sys).

What they tried:

They event tried to stop the RRAS but got the same result. They finally make it work by disabling the RRAS.

Recommendation: It is not recommended to use Windows Firewall on a RRAS server. If you use the server as a router, you should enable NAT; if you use the server as VPN, you should have another firewall. If, for some reasons, you do want to enable Windows Firewall in the Windows 2003, you may need to disable the RRAS. To do that, right-click on My Computer>Manager>Services and Applications>Services. Disable Routing and Remote Access service

When I disabled RRAS, I could get into my Firewall settings. I then shut off my firewall and re-configured RRAS.

Sukses bro...

Windows Cannot Set The Password

When you are adding users to a Windows Server 2003 you receive a message

Titled: Active Directory

And the stop message:
Windows cannot set the password for because: The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.

---

Your IT experience should have taught you a few things:
1: Computers need to be more secure.
2: Users don't want to deal with security.
(More specifically they don't want to enter in difficult passwords.)

---

By default Windows Server 2003 requires passwords to meet the following criteria for strong passwords.

• Has at least 6 characters
• Does not contain "Administrator" or "Admin"
• Contains characters from three of the following categories:
  • Uppercase letters (A, B, C, and so on)
  • Lowercase letters (a, b, c, and so on)
  • Numbers (0, 1, 2, and so on)
  • Non-alphanumeric characters (#, &, ~, and so on)

Caution: Loosening password restrictions decreases security.

---

Select Domain Security Policy from Administrative Tools.

---

Click on Security Settings > Account Policies > Password Policy.

Right-click on Minimum password length in the right pane.

Click Properties from the context menu.

---

Do not remove the check from the Define this policy setting checkbox!

Enter a new minimum password length. Entering a Zero (0) will remove the password requirement.

Click the OK button.

---

Double-click on Passwords must meet complexity requirements in the right pane.

---

Do not remove the check from the Define this policy setting checkbox!

Select the Disabled option.
(This will allow simpler passwords.)

Click the OK button.

---

Close the Default Domain Security Settings window.

---

Now, you need to put the new Password Policy into effect.


Click Start > Run...

Type cmd into the Open: input box.

Click the OK button.

---

Type gpupdate /force at the Command Prompt.

Press the [Enter] key.

Type exit.

Press the [Enter] key.

---

Process complete

Source: tacktech.com


Yup sangat sukses, error dapat diatasi :)

Terminal Server User Access permissions

Sudden "...you must have Terminal Server User Access permissions on this computer." Error.

I have a Small Business Server 2003 R2 Server running Team Foundation Server tucked out of the way to conserve desk space (three servers, two clients, two desks: not much space).  I don't have it hooked up to a monitor (one: don't have that many monitors, and two: desk space).  So, I've been merrily using Remote Desktop Connection (RDC) in Windows XP to connect to this server to perform my various administration tasks (like install service packs, hot fixes, etc.).
Well, I finally had a couple of cycles to install some hotfixes for the new daylight savings time changes to various components, so I sparked up RDC to get the ball rolling on my server--as I have done many times before.  I was greeted with a message box as I logged in:

To log on to this remote computer, you must have Terminal Server User Access Permissions on this computer. By default, members of the Remote Desktop group have these permissions. If you are not a member of the Remote Desktop Users group or another group that has these permissions, or if the Remote Desktop User group does not have these permissions, you must be granted these permissions manually.

Needless to say I was dumbfounded--it worked fine yesterday.  After a bit of searching, it appears it was the 120 day anniversary of creating this server and Terminal Server (which is what is used for an application server in Small Business Server) had "expired" (i.e. its grace period for CALs had expired).  I was used to installing Windows Server and setting up Terminal Server for remote administration (there was a setting for that in Windows Server, I honestly don't remember what Small Business Server asked me when I installed; it certainly wasn't clear it was different the other Windows Server installation processes).  Apparently I missed the memo that remote administration is now called "Remote Desktop".  Clearly a WTF moment.
As it turns out, the hoops to get back to the ability of remote administration aren't clearly documented (I actually couldn't find any documentation on the process, I actually inferred the process from various non-Microsoft sources--there could be documentation somewhere, I just didn't find it).  The process requires that Terminal Server be uninstalled, the server rebooted, and Remote Desktop be re-enabled.  A point-list of the steps:

1. Run Add/Remove Programs (run "appwiz.cpl")
2. Click Add/Remove Windows Components (Alt-W)
3. Uncheck Terminal Server
4. Press Next>.
5. Follow instructions, including rebooting.
6. Open System control panel applet (run "sysdm.cpl")
7. Click Remote tab.
8. Check Enable Remote Desktop on this computer. (because removing Terminal Server disables this)
9. Click Select Remote Users...
10. Make sure administrators is in the list.
11. Click OK.
12. Click OK. for the next dialog.
13. Wait a few minutes for things to get up and running and you're no ready for remote administration again.

I hope this helps someone get back up and running faster than I did...
 
Source: PeterRitchie

Solusi untuk Not enough server storage

Pesan Error :

• Not enough server storage is available to process this command.
• Not enough memory to complete transaction. Close some applications and retry

Error ini biasanya ketika melakukan akses file ke komputer orang lain dalam satu jaringan / network, Ncomputing, Acronis, dll termasuk yang saya alami sendiri ketika komputer os windows xp kantor saya tidak bisa print dari software ms-dos prompt ke printer LPT1 atau USB. Ternyata hal ini disebabkan setting IRPStackSize yang salah.
Kebanyakan orang lain melakukan setting IRPStackSize pada nilai 50. tetapi pada kenyataannya hal ini tidak menyelesaikan masalah.
Setting yang benar adalah sebagai berikut :
1. Start > Run > Regedit
2. Cari folder
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Services
\LanmanServer
\Parameters
3. Edit jika sudah ada “IRPStackSize” ganti Base ke “Decimal” kemudian “Value data” isi angka “20″. Jika belum ada buat dengan cara klik kanan mouse > New > DWORD value > ganti New Value #1 menjadi IRPStackSize kemudian klik2x IRPStackSize kemudian lakukan langkah ke 3 (tiga).

4. Restart Windows anda.
5. Coba kembali apakah masih ada pesan “Not enough server storage …” ???

NTLDR is Missing: Menangani Pesan Error File Windows Yang Hilang

oleh salsabel pada Mar.15, 2009, dalam kategori Sistem Operasi, Windows

Mungkin Anda pernah menemukan pesan error “NTLDR is Missing” kadang ada tambahan “Press any key to restart”. Komputer tidak mau dihidup. Setelah ditekan tombol apapun cuman restart sambil terus menampilkan pesan error di atas. Apa yang terjadi?

Tenang, jangan panik. Anda dapat menanganinya dengan langkah sederhana berikut ini. Saya sudah punya dua solusi penanganan yang dapat Anda pilih sesuai keinginan Anda. Tapi sebelumnya perlu kita ketahui bersama apa sebab pesan Error tersebut muncul..
Menurut Microsoft dan beberapa sumber yang berkecimpung dalam dunia antivirus dan penyelamatan data, pesan error tersebut muncul dengan minimal salah satu sebab berikut ini:
1. Komputer melakukan booting dari media yang non-bootable
2. Harddisk tidak terdeteksi dengan baik di BIOS
3. File NTLDR dan atau NTDETECT.COM rusak/hilang
4. Konfigurasi file boot.ini yang tidak tepat
5. Upaya upgrade Windows 95, 98, atau ME yang masih menggunakan Fat32
6. Ada Harddisk baru yang baru dipasang
7. Boot sector/Master Boot Record rusak/hilang
8. File sistem Windows 2000 or Windows XP rusak atau terkorupsi
9. Kabel data Harddisk IDE/EIDE cacat atau rusak
Berikut ini langkah pemecahannya:
Pilihan 1: Menggunakan Recovery Console Windows
1. Boot komputer dari CD instalasi Windows XP
2. Pilih opsi Repair(R) dengan menekan tombol R
3. Setelah masuk pada Command Prompt Windows (Layar berubah berwarna hitam dengan tulisan putih) Pilih sistem operasi dengan menekan tombol 1 kemudian [Enter]
4. Jika ada, masukkan password Administrator. Jika tidak ada, langsung tekan [Enter]
5. Jika Anda baru saja melakukan perubahan pada master boot record atau proses booting, kembalikan file Boot.ini ke kondisi semula dengan mengetik perintah berikut:

fixmbr [Enter]
fixboot [Enter]

6. Pindah ke drive CD Anda. Misalnya saya punya CD Drive di E: maka perintanhya seperti ini:

E: [Enter]

7. Copy file ntldr dan ntdetect.com dari folder I386 di CD Drive Anda ke folder C: dengan perintah berikut:

copy E:\I386\ntldr c:
copy E:\I386\ntdetect.com c:

Jika ada konfirmasi, jawab dengan [Y]es

7. Restart Komputer.
Dalam beberapa kasus yang pernah saya tangani, langkah tersebut di atas dapat menyelesaikan masalah. Namun jika Anda belum beruntung, silakan coba Pilihan kedua berikut ini.
Pilihan 2: Menggunakan File Recovery.
File ini saya temukan dari hasil googling beberapa tahun lalu. Jadi maaf saya tidak sertakan sumbernya. Semoga amal programmernya diterima di sisi-Nya.. Amin.
Kembali ke proses recovery.. Cara ini lebih mudah karena Anda tinggal mendownload file recovery dan mengkopi ke flashdisk/disket atau burning file ISO berikut ini. File yang saya maksud dapat Anda download dari sini atau dari Gudang File di bagian kanan bawah web ini di bagian Program > Recovery.
File Recovery ini berisi file-file sebagai berikut:

1. fixntldr.exe = untuk membuat disket bootable dengan perbaikan
2. fixntldr.zip = file-file yang hilang
3. fixntldriso4w2k.zip = file iso berisi perbaikan pesan error untuk win2000/server edition
4. fixntldriso.zip = file iso berisi perbaikan pesan error untuk winxp
5. ntldrusb.zip = untuk membuat buat usb flasdisk bootable berikut perbaikan

Selanjutnya Anda tinggal pilih media yang akan Anda gunakan. Copy/Burn dan booting dengan media tersebut. Misalnya saya pilih media CD, saya download dan burn file fixntldriso.zip ke dalam sebuah CD dan booting dari CD yang barusan saya burn. Secara otomatis program di dalamnya akan mengkopy file NTLDR dan NTDETECT.COM ke drive C:
UPDATE:
Panduan menggunakan NTLDRUSB.ZIP.
- Ekstrak file ntldrusb.rar ke dalam folder ntldrusb.
- Masukkan Flashdisk USB Anda
- Klik dua kali HPUSBFW.EXE
- Centang pilihan “Create a DOS startup disk” dan “using DOS system files located at”.
- Kemudian tekan tombol abu-abu dengan tanda “…”. Ini akan membuka jendela browse dan yang meminta Anda untuk memilih folder. Arahkan ke  folder “dos system files” yang juga ada dalam di lokasi yang sama dengan file HPUSBFW.EXE
- Klik OK; Klik Start, Klik Yes,
- Tunggu beberapa saat sampai muncul jendela konfirmasi; Klik OK; Klik Close;
- Buka folder “putonusb”, copy semua file ke dalam flashdisk USB Anda.
- Eject Flashdisk USB Anda.
- Boot di PC Anda. Anda akan layar booting Windows 98 beberapa saat. Kemudian, muncul layar hitam bertuliskan “replace boot sector of the drive C: (y/n)”, tekan tombol y;
- Setelah muncul C:\ prompt, reboot komputer Anda dengan menekan Ctrl + Alt + Del.
- Selanjutnya Anda bisa memilih opsi booting 1-10.
Anda punya pengalaman lain? Saya akan sangat senang jika Anda bersedia menuangkannya dalam komentar di bawah..

Baca selengkapnya di: http://guntingbatukertas.com/sistem-operasi/windows/ntldr-missing-menangani-pesan-error-file-windows-yang-hilang/#ixzz0sUs16xni

Not enough server storage is available to process this command

Ketika mau mencoba browse folder computer lain ternyata muncul pesan :
"Not enough server storage is available to process this command"
Ini karena di Registry Computer yang me-sharing folder tidak terdapat IRPStackSize.

Maka solusinya :
1. Melalui RUN ketikkan REGEDIT
2. Cari HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters kemudian periksa apakah terdapat IRPStackSize?
3. Jika belum buat melalui klik kanan mouse pilih NEW | DWORD VALUE kemudian berikan nama IRPStackSize, kemudian klik 2x IRPStackSize kemudian pada Value data isikan angka 21.
4. Kemudian Restart ulang.
5. Selamat mencoba browse

Translate to English :

"Not enough server storage is available to process this command"
is a message that you can receive when you try to access a shared resource on a network. The Event ID: 2011 may also be written referring to the configuration parameter IRPStackSize. If the IRPStackSize is not present in the Registry the default value which may not be large enough for the server service to administer shared folders on some of the physical drives.

To solve this problem open the Registry and navigate to the key HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ lanmanserver \ parameters and check if the string IRPStackSize exists. If it does not exist create a new Dword with the name IRPStackSize.

The default value for this Dword is 18 and you should raise the value by adding 3 to it. The first value for IRPStackSize would be 21. Reboot your computer and see if that solved the problem. If you still get the error message add 3 again and reboot your computer again.