Senin, 23 Januari 2017

cmdkey /add:IP /user:administrator /pass:123
net use h: \\IP\NamaFolder \persistent:yes

 Make all future connections persistent (auto-reconnect at login)
 NET USE /Persistent:Yes
or 
 NET USE /P:Yes
CMDKEYPerintah cmdkey digunakan untuk menampilkan , membuat, dan menghapus user dan password disimpan
 run batch
Batch File

How To Create A Windows Batch File To Map Multiple Drives At Once

11
winlogo.jpgMapping a drive to a share on a remote computer can be a big time saver when you need to access files and folders remotely. UsingWindows Explorer, you can easily map the drive to the share on a remote computer when needed.
But what if you need to map multiple drives at once, or you want to always map the drive when you logon to your computer?
The best solution is to create a batch file that you can click on, when you need to map the drives, or copy it to your Windows user account Startup folder so the drives are mapped automatically during logon.
To map drives using a batch file, we'll need to use the net use command. At it's simplest form, the command looks like this:
net use [devicename | *] [\\computername\sharename
where:
devicename = the dive letter for the map drive
computername = is the computeer wher the share exists
sharename = is the name of the share
So to create a batch file that will map a drive to different computers that are sharing folders, we'll use the following commands:
net use W: \\computer1\MP3 
net use X: \\computer2\Photos
Note: you can asssign any drive letter you want, as long as it is not in use by your computer (for example A or drives).

What About Authentication?
Using the commands above to map drives, assumes that the account you are logged on as, exists on the remote computer where the shared folder is located, or if you are at work, is part of a Windows Domain.
If you need to authenticate when mapping the drive, we'll need to use an account that exists on the remote computer or in a Windows Domain, and add it onto the net use command as shown below:
net use [devicename | *] [\\computername\sharename password  /USER:username
Therefore the command will look like this when used in a batch file:
net use W: \\computer1\MP3 mypassword /USER:mary
net use X: \\computer2\Photos mypassword /USER:bob
If an error occurs (unknown user name), you will need to use the /USER switch with thedomainname option as follows:
net use W: \\computer1\MP3 mypassword /USER:mydomain\mary
If the remote computer is not part of a Domain, and is part of a Workgroup, then substitute the Domain for the name of the remote computer (where the user account resides).
net use W: \\computer1\MP3 mypassword /USER:computer1\mary

Creating The Batch File
Ok, now that we know how to use the net use command, let's create the batch file.
  • First, open up Notepad or your favorite text editor.
  • Next, copy the commands as shown below and paste them into the file. Don't forget to modify the net usecommand with the drive letter you want to use, the name of the Computer and share you want to map a drive to, and password and account name (if needed).
ECHO Begin Mapping Drivesnet use W: \\computer1\MP3 mypassword /USER:mary 
net use X: \\computer2\Photos myrealpassword /USER:bob 

exit
  • Then save the file with any name and a .bat extension (make sure it's NOT saved using .txt as the file type extension), to a location where you can easily access it (such as your Desktop).
  • When you need to map the drive(s), just double click on it.
  • http://onunqisa.blogspot.co.id/2012_12_01_archive.html 
  • http://blog.guardrex.com/

Minggu, 22 Januari 2017

tidak bisa scan fotocopy

Configure SMB Security in Windows Server 2012

Posted on June 20, 2013 by Russell Smith in Security with 0 Comments

How do I configure SMB Security in Windows Server 2012?

Windows Server 2012 (and Windows 8) introduce a new version of the Server Message Block (SMB) protocol for transferring files across a network. One of the most interesting new features is the ability to encrypt files over the wire between two supported clients. SMB 2.1 in Windows Server 2008 R2 (and Windows 7) was able to sign SMB packets to prevent spoofing, but not encrypt the actual data. Prior to Windows Server 2012, the only way to encrypt file data in transit was to configure IPsec. SMB 3.0 encryption can be enabled, either per share or file server, without any special planning.
Sponsored

Fight Off the Bandwidth Bandits

Critical business apps taking a backseat to bandwidth-sucking streaming media, apps, or users? Sniffing out bandwidth bandits is quick and easy with SolarWinds® NetFlow Bandwidth Analyzer Pack (BAP).
Download Free 30-Day Trial

Disable SMB 1.o

Microsoft recommends that unless you have clients running Windows XP or earlier, you should disable SMB 1.0. Do this in a preproduction lab environment before rolling out the change to your production systems. However, there are still certain scenarios where SMB 1.0 is still required, such as when the computer browser service is enabled in Vista (or later).
Windows Server 2012 has a new PowerShell command that makes it easy to get the configuration status of SMB protocols on the server, and optionally enable or disable SMB protocol support.
To get the current SMB protocol status on Windows Server 2012: Logon to the server as a local administrator, open a PowerShell prompt from the Start screen or icon on the desktop Taskbar, and run the following command:
Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol
Check SMB protocol configuration in Windows Server 2012
Note that there’s no separate command to enable or disable SMB 3.0, as it cannot operate independently of SMB 2.1.
Now, run the following command to disable SMB 1.0 and confirm the action when prompted:
Set-SmbServerConfiguration -EnableSMB1Protocol $false
After that, run the first command again. You should see that SMB 1 has been successfully disabled.
Sponsored

Enable SMB 3.0 Encryption

You can enable encryption per file share or for the entire server. SMB 3.0 uses the AES-CCM algorithm for both encryption and signing. Using the same PowerShell cmdlet as above, run the following command to enable SMB 3.0 Encryption for all file shares:
Set-SmbServerConfiguration –EncryptData $true
To enable encryption for a specific file share, run the following PowerShell command, replacing <sharename> with name of the file share for which you want to enable encryption:
Set-SmbShare –Name <sharename> -EncryptData $true
When enabled, SMB 3.0 encryption will encrypt file data between devices that support SMB 3.0. Clients that don’t support SMB 3.0 will not be able to connect to the file server or share where encryption is turned on. While not recommended, this behavior can be changed by running the Set-SmbServerConfiguration –RejectUnencryptedAccess $false PowerShell command.
https://www.petri.com/configure-smb-security-windows-server-2012