On Sun, Feb 27, 2005 at 05:37:27PM -0500, SOTL wrote:
> Hi All
>
> Help !!!!!!!!!!!!!
>
> Sorry for screaming but I do feel a bit better now.
>
> I have a small network with 3 computers which mostly does not work:
>
> MSI with name of Reality_Check @ 192.168.2.7 with Mandrake 10.1
> HP with name Meatloaf_Night @ 192.168.2.9 with Mandrake 9.2
> IBM with name Big_Nate @ 192.168.2.2 with Mandrake 10.1
>
> I do not have the ability to install 10.1 on the HP with out replacing the CD
> reader with a DVD reader.
>
> >From any one box I can ping either [or both at the same time] of the
> other two
> boxes. For example from the IBM box I can ping MSI by using 192.168.2.7
> and/or HP by using 192.168.2.9.
>
> I can not ping either of the other boxes by using names. For example I
> can not
> ping MSI or HP by using the names Reality_Check or Meatloaf_Night nor can I
> ping the IBM box from either MSI or HP using Big_Nate.
>
> So, numbers work; names do not work. I believe this issue will be solved when
> I configure /etc/hosts or my firewall router so for this posting that issue
> is not relevant.
Um, no. If you're going the /etc/hosts route, the /etc/hosts file on
_each_ machine must contain the names and IP numbers of all the other
boxes on the LAN. Unless, of course, you're running DNS on your
firewall.
>
> I was able to access the MSI box from both the HP box and the IBM box
> by using
> the following:
> fish://username@ip_address/path/to/directory
> or fish://trunk@192.168.2.7
>
Hmm. I never heard of "fish" before. But firing it up on my box, I see
it's a way of ssh-ing into a box from a browser. Interesting. You learn
something new every day.
> After performing the above plus actions I departed and returned.
>
> Firing up all 3 computers the 2 which I was not able to access by fish
> came up
> normal and functioned normal.
>
> The MSi box which I was able to access by fish came up with video up to 3/4
> way through KDE boot at which time it lost video and maybe key and mouse too
> as they did not appear to be functioning either.
>
> I shut the box down by turning power off [bad practice] since I appear
> to have
> no control of box.
>
> I repeated the above several times with identical results.
>
> I attempted to access box by fish and was able to do so.
>
> I placed Mandrake 10.1 disk in DVD drive and did an upgrade.
>
> Booting box after upgrade I still got blank screen and most possible no mouse
> and no keyboard.
>
> My personal belief at this point is that the box is confused by my not
> logging
> out of SSH - I saw no way to do such so I just closed Konqueror on the box I
> was SSHing from.
>
Don't think so. After you reboot, all such confusions should go away.
The machine shouldn't even know you were in a ssh session before, so
long as the other machines are not trying to continually create a SSH
connection with it.
There all kinds of guesses possible about what's going on. Marginal
hardware finally ceased to be marginal and hosed itself. Bit(s) got
flipped or media became corrupted in some of your startup software
(kernel, init scripts, libraries, etc.). Some configuration got changed,
perhaps inadvertantly, by you.
Here's something I'd be curious about. You're probably coming up in X at
startup. Can you get to a console? Try Ctrl-Alt-F2 when the system
appears to hang in X, and see if that puts you in a console. (You can
substitute some other function key up to F6, if you like.) If so, your
machine (and keyboard) actually works, but your X is somehow hosed. If
you're sitting at a console, there are all kinds of troubleshooting
things you can do to debug a system, though many may be beyond your
expertise.
Paul
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:44:33 EDT