Headless server - Revision history

90.157.164.244 at 19:53, 15 June 2008

2008-06-15T19:53:48Z

Dave at 02:41, 25 July 2005

2005-07-25T02:41:29Z

68.154.130.47: another typo

2005-07-08T17:11:38Z

another typo

68.154.130.47: typo fixes

2005-07-08T17:11:03Z

typo fixes

Dave at 21:52, 26 December 2004

2004-12-26T21:52:56Z

Dave at 00:32, 23 December 2004

2004-12-23T00:32:12Z

Dave at 00:27, 23 December 2004

2004-12-23T00:27:53Z

Dave at 00:27, 23 December 2004

2004-12-23T00:27:30Z

Dave at 00:27, 23 December 2004

2004-12-23T00:27:02Z

Dave at 00:25, 23 December 2004

2004-12-23T00:25:10Z

New page

Slang for running a server with no monitor or other peripherals attached. Some computers may '''need''' to have a keyboard attached in order to boot up, but that can often be disabled in the [[BIOS]]. Once you've got a headless server set up, you'll either control it remotely via [[ssh]] or [[webmin]] or locally by using a serial console cable attached to another computer. This is sometimes necessary if you've hosed the connectivity to the headless server (e.g., you killed [[ssh]] or you misconfigured your IP information with [[ifconfig]].

For this you will need:
- a null modem serial cable (or USB to serial, etc)
- a serial port on your headless server
- a serial port on the computer you're connecting ''from''
- a terminal program on your working computer. In Microsoft Windows, you can use Tera Term Pro SSH (putty doesn't do serial consoles,) or the built-in MS Windows program HyperTerm. Unixes (and unix-alikes,) can use [[cu]] or [[tip]].

Quick and dirty instructions:
1. Connect the cable from your computer to the server -- serial ports. Make SURE it's a null modem cable.
2. start up your terminal program and tell it to use the serial COM port on your PC and change the connection settings to 9600 bps, 8-n-1, Hardware flow control.
3. press enter once the program says it's connected.
4. You should now be at your login prompt -- locally, as if you had a full monitor and keyboard attached to your headless server -- so you can login and fix your network problems.

@@ Line 7: / Line 7: @@
   - a terminal program on your working computer.
-In Microsoft Windows, you can use Tera Term Pro SSH (putty doesn't do serial consoles), or the built-in MS Windows program HyperTerm for your terminal program. Unixes (and unix-alikes), can use [[cu]] or [[tip]].
+In Microsoft Windows, you can use Tera Term Pro SSH, putty, or the built-in MS Windows program HyperTerm for your terminal program. Unixes (and unix-alikes), can use [[cu]] or [[tip]].
 Quick and dirty instructions:

← Older revision		Revision as of 02:41, 25 July 2005
Line 26:		Line 26:

	[[Category:Configuring FreeBSD]]		[[Category:Configuring FreeBSD]]
		+	[[Category:FreeBSD for Servers]]

← Older revision		Revision as of 17:11, 8 July 2005
Line 1:		Line 1:
−	Slang for running a server with no monitor or other peripherals attached. Some computers may '''need''' to have a keyboard attached in order to boot up, but that can often be disabled in the [[BIOS]]. Once you've got a headless server set up, you'll either control it remotely via [[ssh]] or [[webmin]] or locally by using a serial console cable attached to another computer. This is sometimes necessary if you've hosed the connectivity to the headless server (e.g., you killed [[ssh]] or you misconfigured your IP information with [[ifconfig]].	+	Slang for running a server with no monitor or other peripherals attached. Some computers may '''need''' to have a keyboard attached in order to boot up, but that can often be disabled in the [[BIOS]]. Once you've got a headless server set up, you'll either control it remotely via [[ssh]] or [[webmin]] or locally by using a serial console cable attached to another computer. This is sometimes necessary if you've hosed the connectivity to the headless server (e.g., you killed [[ssh]] or you misconfigured your IP information with [[ifconfig]]).

	For this you will need:		For this you will need:

@@ Line 7: / Line 7: @@
   - a terminal program on your working computer.
-In Microsoft Windows, you can use Tera Term Pro SSH (putty doesn't do serial consoles,) or the built-in MS Windows program HyperTerm for your terminal program. Unixes (and unix-alikes,) can use [[cu]] or [[tip]].
+In Microsoft Windows, you can use Tera Term Pro SSH (putty doesn't do serial consoles), or the built-in MS Windows program HyperTerm for your terminal program. Unixes (and unix-alikes), can use [[cu]] or [[tip]].
 Quick and dirty instructions:
@@ Line 18: / Line 18: @@
      keyboard attached to your headless server -- so you can login and fix your network problems.
-If you're using Window's HyperTerm program, you settings should look like this:
+If you're using Window's HyperTerm program, your settings should look like this:
 [[Image:Hyperterm.jpg]]
-For more info on how to do this from a FreeBSD box to another, check out the FreeBSD Manual page http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/serial.html
+For more info on how to do this from one FreeBSD box to another, check out the FreeBSD Manual page http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/serial.html
 [[Category:Configuring FreeBSD]]

@@ Line 20: / Line 20: @@
 If you're using Window's HyperTerm program, you settings should look like this:
-[[Image:Hyperterm.jpg|thumb|HyperTerm settings example picture]]
+[[Image:Hyperterm.jpg]]
 For more info on how to do this from a FreeBSD box to another, check out the FreeBSD Manual page http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/serial.html

← Older revision		Revision as of 00:32, 23 December 2004
Line 21:		Line 21:

	[[Image:Hyperterm.jpg\|thumb\|HyperTerm settings example picture]]		[[Image:Hyperterm.jpg\|thumb\|HyperTerm settings example picture]]
		+
		+	For more info on how to do this from a FreeBSD box to another, check out the FreeBSD Manual page http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/serial.html

@@ Line 10: / Line 10: @@
 Quick and dirty instructions:
-. Connect the cable from your computer to the server -- serial ports. Make SURE it's a null modem cable.
+. Connect the cable from your computer to the server -- serial ports.
-. Start up your terminal program and tell it to use the serial COM port on your PC and change the connection settings to 9600 bps, 8-n-1, Hardware flow control.
+    Make SURE it's a null modem cable.
 . Press enter once the program says it's connected.
-. You should now be at your login prompt -- locally, as if you had a full monitor and keyboard attached to your headless server -- so you can login and fix your network problems.
+. You should now be at your login prompt -- locally, as if you had a full monitor and
 If you're using Window's HyperTerm program, you settings should look like this:
 [[Image:Hyperterm.jpg|thumb|HyperTerm settings example picture]]

@@ Line 5: / Line 5: @@
   - a serial port on your headless server
   - a serial port on the computer you're connecting ''from''
-  - a terminal program on your working computer. In Microsoft Windows, you can use Tera Term Pro SSH (putty doesn't do serial consoles,) or the built-in MS Windows program HyperTerm. Unixes (and unix-alikes,) can use [[cu]] or [[tip]].
+  - a terminal program on your working computer.
 Quick and dirty instructions: