GoodMorning all,
I am having some problems with the tasklist /s [servername] -u [user] -p [password]
I am on an windows 7 machine and i whant to view the tasks on my windows xp.
So i do this
tasklist /s \192.168.1.105 -u Administrator -p MyPass
The error i am recieving is unknown user or invalid password.
I am 100% positive that the username and password is correct cause i also log in with those credentials on my windows xp pc.
When i am on my windows xp and willing to do tasklist to my windows 7 pc its working fine.
Both PC's dont have an domein but are in the same WORKGROUP
Services are started on win xp. No firewall is active.
I also tried PSTools but also that one is not connecting to the windows XP machine.
Any help will be appriciated.
Related
Couldn't connect to a remote machine because of my password?
My problem here :
I can connect remotely with the normal method like "mstsc", so my user and password are working fine.
I do not understand why the password didn't work on powershell.
Could you help me for that please?
WinRM is enable on the remote machine.
Add your full command to the post for review.
You should run your powershell session as an account that has proper access to the server.
enter-pssession -computername "your PC Name" is the command.
Powershell version will matter here to the device you are trying to connect to needs to be on powershell 3.0
What is password for Windows 10 IOT Core Dashboard if i installed the Windows 10 IOT Core ( 10.0.16299.15) through the NOOBS?
I found following password is useful.
p#ssw0rd
p#ssw[zero]rd
if you had not set any password initially while installing Windows IoT to your flash SD card, it would remain as the defaults, i.e.,
Username: Administrator
Password: p#ssw0rd
If you had entered any password initially while installing Windows IoT using the Windows IoT dashboard utility, then the password would change to that,
Username: Administrator
Password: xxxx_your_set_password_xxxx
OK, Found the solution! You need to connect with the computername in front of the username...like this...
Enter-PsSession -ComputerName minwinpc -Credential minwinpc\Administrator
Yes, the command line should be in this form:
Enter-PsSession -ComputerName <machine-name or IP Address> -Credential Administrator
Please also note that the default password is: p#ssw0rd
The zero can easily be mistaken as an 'O' so calling that part out.
I found User Name : Administrator
and Pass Word: (as I fill in on Windows 10 IOt core Dashboards) ,could not use p#ssw0rd .
I tried to reset administrator password from following steps is below but unable to change administrator password.
Set the server computer to boot from USB Bootable drive, and boot the server from Windows server bootable image.
2.When install options appear, I select repair windows by command.
3.When command prompt appears, I type in command prompt "net user administrator password123" to reset the new password to the administrator user.
4.And reboot the computer after reboot I tried to login with new password but unable to login.
So please help me.
You can use offline nt password and registry editor. Here http://pogostick.net/~pnh/ntpasswd/ is the original source.
I'm trying to successfully run a batch file located on a server pc (Windows Server 2008 R2) from my Windows 7 client PC. But its not working and the command prompt shows the following error information message.
When I run
psexec \\199.219.21.141 -u admin /c "C:\Compile.bat"
I'm prompted for password, and when I enter the password and press I get
Make sure that the default admin$ share is enabled on 199.219.21.141
(which is my machine ipaddress)
The user admin is part of the Local administrators on the server machine
Things I tried,
Turning off the UAC Turning OFF the Windows Firewall
Setting the LocalAccountTokenFilterPolicy DWORD to 1 in, HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Caching the user credentials using
cmdkey.exe /add:MACHINE_NAME_HERE /user:199.219.21.141\admin /pass:PASSWORD_HERE
psexec.exe \199.219.21.141 -i notepad
cmdkey.exe /delete:199.219.21.141
After trying to connect for some time, it again displays
Make sure that the default admin$ share is enabled on 199.219.21.141
Any ideas what am I doing wrong?
I have disabled the remote desktop firewall rule in a Windows Azure virtual machine.As you would expect, I can no longer remote desktop in to the server.
Does anyone know if it is possible to re-enable the Remote Desktop Windows firewall rule?
What I have tried
As a long shot, I have downloaded the Windows Azure CLI but can't see anything in there that would do it but have not found anything.
I have also tried to execute the following command against the MSSQL server:
EXEC xp_cmdshell 'netsh advfirewall firewall set rule group="remote desktop" new enable=Yes';
GO
I am getting the following message from the query:
The requested operation requires elevation (Run as administrator).
Please tell me I don't have to re-create the site (which is backed up).
If you're using a VM inside a resource group with the new azure portal, you can do this:
Click reset password
Change mode to "Reset configuration only"
Click update and wipe your sweat off :)
It turns out that all I needed to do was to PowerShell into the Azure VM.
Steps:
Make sure PowerShell is enabled in the Endpoints section of the Azure portal.
Get the server's certificate (PowerShell needs this for remote commands). You can get the server certificate by going to your domains' URL: https://yourdomaing.cloudapp.net:12345 (where :12345 is the port that PowerShell uses).
Export the SSL certificate of the site as a .CER file and install it on your local machine.
Save it to the "Trusted Root Certification Authorities" store on your machine.
Open PowerShell with administrative privileges on your local machine and type:
Enter-PSSession -ComputerName yourdomain.cloudapp.net -Port 5986 -Credential YourUserName -UseSSL
A login popup will appear, enter your VM's login credentials here.
You will now be able to execute commands against the Azure VM. In my case, I ran netsh advfirewall firewall set rule group="remote desktop" new enable=Yes and exited the PowerShell session and was able to remotely connect to my machine.