FreeBSD Reset or Recover Root Password (save my day)!

With FreeBSD version 5.4 and above the booting procedure is slightly changed. The older version of FreeBSD uses the boot -s option at Ok prompt. However, with FreeBSD version FreeBSD 5.4+ you don’t have to type any commands. Here is the procedure to boot FreeBSD into a single user mode to reset root password.

In this tip I will explain how to boot FreeBSD into a single user mode to reset root password.

Procedure: Reset FreeBSD root user password

Step # 1: Start FreeBSD server/workstation.

Step # 2: Press Enter key at boot loader.

At Welcome to FreeBSD! boot menu press spacebar key to pause default booting

Type number 4 key (type 4 number) to boot into single user mode

(click to enlarge)

Next you will see the following prompt from system:
When prompted Enter full pathname of shell or RETURN for /bin/sh:

Press Enter key to boot into a single user mode. Next, you will be immediately dropped into a single user mode without a root password.

You need to remount / (root) file system in read and write mode with mount command, type the following commands:
# mount -u /
# mount -a

Setup a new password with the passwd command for root user:
# passwd

Next type exit command to boot FreeBSD into multi-user mode environment:
# exit
OR You can just reboot the system:
# sync;sync
# reboot

For more information see man pages of passwd and mount commands.

Advertisements

Shutting down interface eth1: Error: Device ‘eth1′ NetworkManager/Devices/1 disconnecting failed: This device is not active

On Centos 6.2, while restarting the network service, I got the following error,

# service network restart
Shutting down interface eth0:  Device state: 3 (disconnected)
[  OK  ]
Shutting down interface eth1:  Error: Device ‘eth1′ (/org/freedesktop/NetworkManager/Devices/1) disconnecting failed: This device is not active
[FAILED]
Shutting down interface eth2:  Error: Device ‘eth2′ (/org/freedesktop/NetworkManager/Devices/2) disconnecting failed: This device is not active
[FAILED]
Shutting down interface eth3:  Error: Device ‘eth3′ (/org/freedesktop/NetworkManager/Devices/3) disconnecting failed: This device is not active

Fix :

Please stop the NetworkManager and restart network service

[root@proxy network-scripts]# service NetworkManager stop
Stopping NetworkManager daemon: [ OK ]
[root@proxy network-scripts]# chkconfig NetworkManager off
[root@proxy network-scripts]# chkconfig network on
[root@proxy network-scripts]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
[root@proxy network-scripts]#

Cant see what you are looking for.. Try Google for more information

Source: http://linuxwindows.net/2013/04/22/shutting-down-interface-eth1-error-device-eth1-orgfreedesktopnetworkmanagerdevices1-disconnecting-failed-this-device-is-not-active/

How to change the listening port for Remote Desktop

 
System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you.Visit the Windows 8 Solution Center
This article was previously published under Q306759
Expand all | Collapse all
This article describes how to change the port that Remote Desktop listens on.

Note The Remote Desktop Connection Client for the Mac supports only port 3389. 3389 is the default port.

You can use the Remote Desktop feature in Microsoft Windows XP Professional to connect to your computer from another remote computer.

Warning The Remote Assistance feature in Microsoft Windows XP may not work correctly if you change the listening port.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

307711 Remote Assistance invitation file does not contain correct port number

To have us change the port that Remote Desktop listens, go to the “Fix it for me” section. If you prefer to fix this problem yourself, go to the “Let me fix it myself” section.

Fix it for me

To fix this problem automatically, click the Fix it button or link. Click Run in the File Download dialog box, and follow the steps in the Fix it wizard.

Fix this problem
Microsoft Fix it 50595


Notes

  • Please type the new integer port number between 1025 and 65535 in the PortNumber text box during the installation of the Fix it solution. Make sure the new port number is not in use by other application.
  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Then, go to the “Did this fix the problem?” section.

 

Let me fix it myself

To change the port that Remote Desktop listens on, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows
  1. Start Registry Editor.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
  3. On the Edit menu, click Modify, and then click Decimal.
  4. Type the new port number, and then click OK.
  5. Quit Registry Editor.
  6. Restart the computer.

Note When you try to connect to this computer by using the Remote Desktop connection, you must type the new port. Maybe you have to set the firewall to allow the new port number before you connect to this computer by using the Remote Desktop connection.

304304 How to configure the Remote Desktop client to connect to a specific port when you use Windows XP

 

Did this fix the problem?

  • Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.
  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the “Fix it for me” blog or send us an email.

Collapse imageProperties

Article ID: 306759 – Last Review: May 4, 2011 – Revision: 4.0
APPLIES TO
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows Remote Desktop Connection for Macintosh
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Windows Server 2008 Enterprise
  • Windows Vista Enterprise
  • Windows Vista Enterprise 64-bit Edition
  • Windows Server 2008 R2 Enterprise
  • Windows 7 Enterprise
  • Windows 7 Professional
Keywords:
kbregistry kbsyssettings kbenv kbhowto kbnetwork kbfixme kbmsifixme KB306759