Solaris

duke - exactly what i thought with the no keyboard thing. however, i've got a ps/2 keyboard i'm going to bring it into work and give it a go there. i've got term servers up the @#$ and a million cables. hahaha.

the serial connection gives me nothing. no output. seems lom is the only choice at the moment.

jesus... for such a small server, its a real pain to get into. i can get into a m9000 a million different ways. no problems. o well... gotta love sun!

Check that the hardware flow control is set to "off" in your terminal emulator.

ok well it's figured out. i grab another solaris 10 server and hooked up a console cable from term port to lom port. issued a tip hardwire and got in with no problems. everything was already good in /etc/remote.

I know I'm a little late to the party, but the "no keyboard" message just indicates that there isn't a Sun keyboard plugged into the server. It doesn't have anything to do with your PC's keyboard.

This is how the Sun server decides whether to use a graphical console or the serial port. No keyboard = serial console.

This might have changed with LOM. I'm not 100% sure about that, but it's true for older hardware.

exactly. i just didn't have the ability to hook up a keyboard to the server. but still... i'm really curious as why a term connection from my xp desktop won't push input to the server? i even tried another laptop and same thing. all were connected to the LOM.

now i just got to look into figuring out why the serial port on the t1 won't work. not sure what someone did to this server but it seems beat up to me! hahaha.

Somebody could have mucked with the console settings or there could be a connection problem with the cable or console port itself.

I seem to remember having this exact same problem once. Could read from, but not write to the console. I think it was a broken pin or wire in the cable.

i thought about a broken pin or something of that sort so i tried another roll over and same thing. happened on two separate xp desktops. also interesting was the fact that hyperterm didn't show me anything. i needed to use teraterm and/or secureCRT to actually get output.

before i ran outta the house for work i noticed when i initiate vi on a file... it doesn't display correctly. didn't get a good chance to mess with it but i'm wondering if the console connection to the LOM is whats causing the strange formatting.