ssh in network

[Michael Havens]

Okay I figured out why the virtual (debian) couldn't ssh to the host
(mint). I didn't have openssh-server installed in the mint. Now they are
talking with each other nicely! Unfortunately I can't go from the either of
those to the print-server (ubuntu). The errors given from both computers is
'connection timed out'.
I can ssh from the ubuntu to  to the debian and the mint with no problem.
When I verified that openssh-server was installed on the ubuntu with apt it
said:

 openssh-server is already the newest version.
 openssh-server set to manually installed.

So I'm not too sure what that means. I think that is saying that the
downloaddd package is the newest version but it isn't installed! If I'm
correect on that point how do I install it and another question I have is
how do I get it to load on boot? I think that installing it will take care
of that but I just want to make sure.
-- 
:-)~MIKE~(-:
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Mike Ballon]

I don't have an ubuntu box to show output exactly, hopefully this will
get you what you need just the same...

type "netstat -a | grep ssh" on the print server host, you should get
something like this:

tcp0  0 *:ssh   *:*
 LISTEN

If you don't see the output above, then ssh is not listen and you'll
need to type "sudo /etc/init.d/sshd start"

Try the netstat command again...

If, in the first time running netstat you DID see the output, check
your firewall by typing "sudo /sbin/iptables -L | grep ssh", you
should see something like this:

ACCEPT tcp  --  10.0.0.0/8   anywherestate NEW
tcp dpt:ssh

If all that is correct the last thing to check is tcp wrappers, which
probably are not as common as you once where, just cat out
/etc/hosts.allow and /etc/hosts.deny for any related content.

Cheers!

On Tue, Mar 27, 2012 at 7:19 PM, Michael Havens  wrote:
> Okay I figured out why the virtual (debian) couldn't ssh to the host
> (mint). I didn't have openssh-server installed in the mint. Now they are
> talking with each other nicely! Unfortunately I can't go from the either of
> those to the print-server (ubuntu). The errors given from both computers is
> 'connection timed out'.
> I can ssh from the ubuntu to  to the debian and the mint with no problem.
> When I verified that openssh-server was installed on the ubuntu with apt it
> said:
>
>  openssh-server is already the newest version.
>  openssh-server set to manually installed.
>
> So I'm not too sure what that means. I think that is saying that the
> downloaddd package is the newest version but it isn't installed! If I'm
> correect on that point how do I install it and another question I have is
> how do I get it to load on boot? I think that installing it will take care
> of that but I just want to make sure.
> --
> :-)~MIKE~(-:
>
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

Thanks for the help Mike. But it didn't work.

 bmike1@Michaels-PC:~$ sudo /etc/init.d/sshd start
 sudo: /etc/init.d/sshd: command not found

I'm pretty dure that is because openssh-server Doesn't seem to be
installed. I tried installing it but it won't install. I think it because
it can't remove

 linux-image-3.0.0-15-generic
 linux-image-3.0.0-16-generic
 linux-image-3.0.0-17-generic


On Thu, Mar 29, 2012 at 5:54 AM, Mike Ballon  wrote:

> I don't have an ubuntu box to show output exactly, hopefully this will
> get you what you need just the same...
>
> type "netstat -a | grep ssh" on the print server host, you should get
> something like this:
>
> tcp0  0 *:ssh   *:*
> LISTEN
>
> If you don't see the output above, then ssh is not listen and you'll
> need to type "sudo /etc/init.d/sshd start"
>
> Try the netstat command again...
>
> If, in the first time running netstat you DID see the output, check
> your firewall by typing "sudo /sbin/iptables -L | grep ssh", you
> should see something like this:
>
> ACCEPT tcp  --  10.0.0.0/8   anywherestate NEW
> tcp dpt:ssh
>
> If all that is correct the last thing to check is tcp wrappers, which
> probably are not as common as you once where, just cat out
> /etc/hosts.allow and /etc/hosts.deny for any related content.
>
> Cheers!
>
> On Tue, Mar 27, 2012 at 7:19 PM, Michael Havens  wrote:
> > Okay I figured out why the virtual (debian) couldn't ssh to the host
> > (mint). I didn't have openssh-server installed in the mint. Now they are
> > talking with each other nicely! Unfortunately I can't go from the either
> of
> > those to the print-server (ubuntu). The errors given from both computers
> is
> > 'connection timed out'.
> > I can ssh from the ubuntu to  to the debian and the mint with no problem.
> > When I verified that openssh-server was installed on the ubuntu with apt
> it
> > said:
> >
> >  openssh-server is already the newest version.
> >  openssh-server set to manually installed.
> >
> > So I'm not too sure what that means. I think that is saying that the
> > downloaddd package is the newest version but it isn't installed! If I'm
> > correect on that point how do I install it and another question I have is
> > how do I get it to load on boot? I think that installing it will take
> care
> > of that but I just want to make sure.
> > --
> > :-)~MIKE~(-:
> >
> > ---
> > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change your mail settings:
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



-- 
:-)~MIKE~(-:
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Mike Ballon]

I spun up an ubuntu-desktop VM. At least the desktop distro does not
have sshd installed.

Try "sudo apt-get install openssh--server"

I also noticed the ubuntu doesn't use v5 init scripts so I guess it's
"service ssh start", although after I installed it with the apt
command above it was already running.



On Thu, Mar 29, 2012 at 1:43 PM, Michael Havens  wrote:
> Thanks for the help Mike. But it didn't work.
>
>  bmike1@Michaels-PC:~$ sudo /etc/init.d/sshd start
>  sudo: /etc/init.d/sshd: command not found
>
> I'm pretty dure that is because openssh-server Doesn't seem to be installed.
> I tried installing it but it won't install. I think it because it can't
> remove
>
>  linux-image-3.0.0-15-generic
>  linux-image-3.0.0-16-generic
>  linux-image-3.0.0-17-generic
>
>
> On Thu, Mar 29, 2012 at 5:54 AM, Mike Ballon  wrote:
>>
>> I don't have an ubuntu box to show output exactly, hopefully this will
>> get you what you need just the same...
>>
>> type "netstat -a | grep ssh" on the print server host, you should get
>> something like this:
>>
>> tcp        0      0 *:ssh                       *:*
>>     LISTEN
>>
>> If you don't see the output above, then ssh is not listen and you'll
>> need to type "sudo /etc/init.d/sshd start"
>>
>> Try the netstat command again...
>>
>> If, in the first time running netstat you DID see the output, check
>> your firewall by typing "sudo /sbin/iptables -L | grep ssh", you
>> should see something like this:
>>
>> ACCEPT     tcp  --  10.0.0.0/8           anywhere            state NEW
>> tcp dpt:ssh
>>
>> If all that is correct the last thing to check is tcp wrappers, which
>> probably are not as common as you once where, just cat out
>> /etc/hosts.allow and /etc/hosts.deny for any related content.
>>
>> Cheers!
>>
>> On Tue, Mar 27, 2012 at 7:19 PM, Michael Havens  wrote:
>> > Okay I figured out why the virtual (debian) couldn't ssh to the host
>> > (mint). I didn't have openssh-server installed in the mint. Now they are
>> > talking with each other nicely! Unfortunately I can't go from the either
>> > of
>> > those to the print-server (ubuntu). The errors given from both computers
>> > is
>> > 'connection timed out'.
>> > I can ssh from the ubuntu to  to the debian and the mint with no
>> > problem.
>> > When I verified that openssh-server was installed on the ubuntu with apt
>> > it
>> > said:
>> >
>> >  openssh-server is already the newest version.
>> >  openssh-server set to manually installed.
>> >
>> > So I'm not too sure what that means. I think that is saying that the
>> > downloaddd package is the newest version but it isn't installed! If I'm
>> > correect on that point how do I install it and another question I have
>> > is
>> > how do I get it to load on boot? I think that installing it will take
>> > care
>> > of that but I just want to make sure.
>> > --
>> > :-)~MIKE~(-:
>> >
>> > ---
>> > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>> > To subscribe, unsubscribe, or to change your mail settings:
>> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>> ---
>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
>
>
> --
> :-)~MIKE~(-:
>
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Dazed_75]

Make that:
Try "sudo apt-get install openssh-server"

On Fri, Mar 30, 2012 at 6:07 AM, Mike Ballon  wrote:

> I spun up an ubuntu-desktop VM. At least the desktop distro does not
> have sshd installed.
>
> Try "sudo apt-get install openssh--server"
>
> I also noticed the ubuntu doesn't use v5 init scripts so I guess it's
> "service ssh start", although after I installed it with the apt
> command above it was already running.
>
>
>
> On Thu, Mar 29, 2012 at 1:43 PM, Michael Havens  wrote:
> > Thanks for the help Mike. But it didn't work.
> >
> >  bmike1@Michaels-PC:~$ sudo /etc/init.d/sshd start
> >  sudo: /etc/init.d/sshd: command not found
> >
> > I'm pretty dure that is because openssh-server Doesn't seem to be
> installed.
> > I tried installing it but it won't install. I think it because it can't
> > remove
> >
> >  linux-image-3.0.0-15-generic
> >  linux-image-3.0.0-16-generic
> >  linux-image-3.0.0-17-generic
> >
> >
> > On Thu, Mar 29, 2012 at 5:54 AM, Mike Ballon 
> wrote:
> >>
> >> I don't have an ubuntu box to show output exactly, hopefully this will
> >> get you what you need just the same...
> >>
> >> type "netstat -a | grep ssh" on the print server host, you should get
> >> something like this:
> >>
> >> tcp0  0 *:ssh   *:*
> >> LISTEN
> >>
> >> If you don't see the output above, then ssh is not listen and you'll
> >> need to type "sudo /etc/init.d/sshd start"
> >>
> >> Try the netstat command again...
> >>
> >> If, in the first time running netstat you DID see the output, check
> >> your firewall by typing "sudo /sbin/iptables -L | grep ssh", you
> >> should see something like this:
> >>
> >> ACCEPT tcp  --  10.0.0.0/8   anywherestate NEW
> >> tcp dpt:ssh
> >>
> >> If all that is correct the last thing to check is tcp wrappers, which
> >> probably are not as common as you once where, just cat out
> >> /etc/hosts.allow and /etc/hosts.deny for any related content.
> >>
> >> Cheers!
> >>
> >> On Tue, Mar 27, 2012 at 7:19 PM, Michael Havens 
> wrote:
> >> > Okay I figured out why the virtual (debian) couldn't ssh to the
> host
> >> > (mint). I didn't have openssh-server installed in the mint. Now they
> are
> >> > talking with each other nicely! Unfortunately I can't go from the
> either
> >> > of
> >> > those to the print-server (ubuntu). The errors given from both
> computers
> >> > is
> >> > 'connection timed out'.
> >> > I can ssh from the ubuntu to  to the debian and the mint with no
> >> > problem.
> >> > When I verified that openssh-server was installed on the ubuntu with
> apt
> >> > it
> >> > said:
> >> >
> >> >  openssh-server is already the newest version.
> >> >  openssh-server set to manually installed.
> >> >
> >> > So I'm not too sure what that means. I think that is saying that the
> >> > downloaddd package is the newest version but it isn't installed! If
> I'm
> >> > correect on that point how do I install it and another question I have
> >> > is
> >> > how do I get it to load on boot? I think that installing it will take
> >> > care
> >> > of that but I just want to make sure.
> >> > --
> >> > :-)~MIKE~(-:
> >> >
> >> > ---
> >> > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> >> > To subscribe, unsubscribe, or to change your mail settings:
> >> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >> ---
> >> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> >> To subscribe, unsubscribe, or to change your mail settings:
> >> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> >
> >
> >
> > --
> > :-)~MIKE~(-:
> >
> > ---
> > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change your mail settings:
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



-- 
Dazed_75 a.k.a. Larry

Please protect my address like I protect yours. When sending messages to
multiple recipients, always use the BCC: (Blind carbon copy) and not To: or
CC:. Remove all addresses from the message body before sending a Forwarded
message. This can prevent spy programs capturing addresses from the
recipient list and message body.
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

> Try sudo apt-get install openssh-server
I've tried that and it won't install. I think it is because their are three
packages in there that won't install (linux-image-3.0.0-15-generic,
linux-image-3.0.0-16-generic, and linux-image-3.0.0-17-generic). How do I
remove those packages?

I just got a message from the gui update manager with instructions on maybe
how to fix it (but it didn't) (a). The update manager was also talking
about a distribution upgrade and needing to update three packages. I
canceled out of that because the packages are all different versions and I
don't want to do a distribution upgrade.

-a-
bmike1@Michaels-PC:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  linux-image-3.0.0-15-generic linux-image-3.0.0-16-generic
  linux-image-3.0.0-17-generic
0 upgraded, 0 newly installed, 3 to remove and 3 not upgraded.
3 not fully installed or removed.
After this operation, 351 MB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 246431 files and directories currently installed.)
Removing linux-image-3.0.0-15-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.0.0-15-generic
/boot/vmlinuz-3.0.0-15-generic
update-initramfs: Deleting /boot/initrd.img-3.0.0-15-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.0.0-15-generic
/boot/vmlinuz-3.0.0-15-generic
/etc/default/grub: 1: GNU: not found
run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
Failed to process /etc/kernel/postrm.d at
/var/lib/dpkg/info/linux-image-3.0.0-15-generic.postrm line 328.
dpkg: error processing linux-image-3.0.0-15-generic (--remove):
 subprocess installed post-removal script returned error exit status 1
No apport report written because MaxReports is reached already
  Removing
linux-image-3.0.0-16-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.0.0-16-generic
/boot/vmlinuz-3.0.0-16-generic
update-initramfs: Deleting /boot/initrd.img-3.0.0-16-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.0.0-16-generic
/boot/vmlinuz-3.0.0-16-generic
/etc/default/grub: 1: GNU: not found
run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
Failed to process /etc/kernel/postrm.d at
/var/lib/dpkg/info/linux-image-3.0.0-16-generic.postrm line 328.
dpkg: error processing linux-image-3.0.0-16-generic (--remove):
 subprocess installed post-removal script returned error exit status 1
No apport report written because MaxReports is reached already
  Removing
linux-image-3.0.0-17-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.0.0-17-generic
/boot/vmlinuz-3.0.0-17-generic
update-initramfs: Deleting /boot/initrd.img-3.0.0-17-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.0.0-17-generic
/boot/vmlinuz-3.0.0-17-generic
/etc/default/grub: 1: GNU: not found
run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
Failed to process /etc/kernel/postrm.d at
/var/lib/dpkg/info/linux-image-3.0.0-17-generic.postrm line 328.
dpkg: error processing linux-image-3.0.0-17-generic (--remove):
 subprocess installed post-removal script returned error exit status 1
No apport report written because MaxReports is reached already
  Errors were
encountered while processing:
 linux-image-3.0.0-15-generic
 linux-image-3.0.0-16-generic
 linux-image-3.0.0-17-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
bmike1@Michaels-PC:~$


On Fri, Mar 30, 2012 at 7:47 AM, Dazed_75  wrote:

> Make that:
> Try "sudo apt-get install openssh-server"
>
>
> On Fri, Mar 30, 2012 at 6:07 AM, Mike Ballon wrote:
>
>> I spun up an ubuntu-desktop VM. At least the desktop distro does not
>> have sshd installed.
>>
>> Try "sudo apt-get install openssh--server"
>>
>> I also noticed the ubuntu doesn't use v5 init scripts so I guess it's
>> "service ssh start", although after I installed it with the apt
>> command above it was already running.
>>
>>
>>
>> On Thu, Mar 29, 2012 at 1:43 PM, Michael Havens  wrote:
>> > Thanks for the help Mike. But it didn't work.
>> >
>> >  bmike1@Michaels-PC:~$ sudo /etc/init.d/sshd start
>> >  sudo: /etc/init.d/sshd: command not found
>> >
>> > I'm pretty dure that is because openssh-server Doesn't seem to be
>> installed.
>> > I tried installing it but it won't install. I think it because it can't
>> > remove
>> >
>> >  linux-image-3.0.0-15-generic
>> >  linux-image-3.0.0-16-generic
>> >  linux-image-3.0.0-17-generic
>> >
>> >
>> > On Thu, Mar 29, 2012 at 5:54 AM, Mike Ballon 
>> wrote:
>> >>
>> >> I don't have an ubuntu box to show output exactly, hopefully this wil

Re: ssh in network

[Mike Ballon]

Lets try the other route; what is your output to "dpkg
--get-selections | grep openssh" ?

Also post the output of dpkg --get-selections | grep linux-image" just for fun.

On Fri, Mar 30, 2012 at 11:49 AM, Michael Havens  wrote:
>> Try sudo apt-get install openssh-server
> I've tried that and it won't install. I think it is because their are three
> packages in there that won't install (linux-image-3.0.0-15-generic,
> linux-image-3.0.0-16-generic, and linux-image-3.0.0-17-generic). How do I
> remove those packages?
>
> I just got a message from the gui update manager with instructions on maybe
> how to fix it (but it didn't) (a). The update manager was also talking about
> a distribution upgrade and needing to update three packages. I canceled out
> of that because the packages are all different versions and I don't want to
> do a distribution upgrade.
>
> -a-
> bmike1@Michaels-PC:~$ sudo apt-get install -f
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
>   linux-image-3.0.0-15-generic linux-image-3.0.0-16-generic
>   linux-image-3.0.0-17-generic
> 0 upgraded, 0 newly installed, 3 to remove and 3 not upgraded.
> 3 not fully installed or removed.
> After this operation, 351 MB disk space will be freed.
> Do you want to continue [Y/n]?
> (Reading database ... 246431 files and directories currently installed.)
> Removing linux-image-3.0.0-15-generic ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.0.0-15-generic
> /boot/vmlinuz-3.0.0-15-generic
> update-initramfs: Deleting /boot/initrd.img-3.0.0-15-generic
> run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.0.0-15-generic
> /boot/vmlinuz-3.0.0-15-generic
> /etc/default/grub: 1: GNU: not found
> run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
> Failed to process /etc/kernel/postrm.d at
> /var/lib/dpkg/info/linux-image-3.0.0-15-generic.postrm line 328.
> dpkg: error processing linux-image-3.0.0-15-generic (--remove):
>  subprocess installed post-removal script returned error exit status 1
> No apport report written because MaxReports is reached already
>   Removing
> linux-image-3.0.0-16-generic ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.0.0-16-generic
> /boot/vmlinuz-3.0.0-16-generic
> update-initramfs: Deleting /boot/initrd.img-3.0.0-16-generic
> run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.0.0-16-generic
> /boot/vmlinuz-3.0.0-16-generic
> /etc/default/grub: 1: GNU: not found
> run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
> Failed to process /etc/kernel/postrm.d at
> /var/lib/dpkg/info/linux-image-3.0.0-16-generic.postrm line 328.
> dpkg: error processing linux-image-3.0.0-16-generic (--remove):
>  subprocess installed post-removal script returned error exit status 1
> No apport report written because MaxReports is reached already
>   Removing
> linux-image-3.0.0-17-generic ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.0.0-17-generic
> /boot/vmlinuz-3.0.0-17-generic
> update-initramfs: Deleting /boot/initrd.img-3.0.0-17-generic
> run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.0.0-17-generic
> /boot/vmlinuz-3.0.0-17-generic
> /etc/default/grub: 1: GNU: not found
> run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
> Failed to process /etc/kernel/postrm.d at
> /var/lib/dpkg/info/linux-image-3.0.0-17-generic.postrm line 328.
> dpkg: error processing linux-image-3.0.0-17-generic (--remove):
>  subprocess installed post-removal script returned error exit status 1
> No apport report written because MaxReports is reached already
>   Errors were
> encountered while processing:
>  linux-image-3.0.0-15-generic
>  linux-image-3.0.0-16-generic
>  linux-image-3.0.0-17-generic
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> bmike1@Michaels-PC:~$
>
>
> On Fri, Mar 30, 2012 at 7:47 AM, Dazed_75  wrote:
>>
>> Make that:
>> Try "sudo apt-get install openssh-server"
>>
>>
>> On Fri, Mar 30, 2012 at 6:07 AM, Mike Ballon 
>> wrote:
>>>
>>> I spun up an ubuntu-desktop VM. At least the desktop distro does not
>>> have sshd installed.
>>>
>>> Try "sudo apt-get install openssh--server"
>>>
>>> I also noticed the ubuntu doesn't use v5 init scripts so I guess it's
>>> "service ssh start", although after I installed it with the apt
>>> command above it was already running.
>>>
>>>
>>>
>>> On Thu, Mar 29, 2012 at 1:43 PM, Michael Havens  wrote:
>>> > Thanks for the help Mike. But it didn't work.
>>> >
>>> >  bmike1@Michaels-PC:~$ sudo /etc/init.d/sshd start
>>> >  sudo: /etc/init.d/sshd: command not found
>>> >
>>> > I'm pretty dure th

Re: ssh in network

[Michael Havens]

 dpkg --get-selections | grep openssh
openssh-clientinstall
openssh-serverdeinstall
dpkg --get-selections | grep linux-image
linux-image-3.0.0-12-genericinstall
linux-image-3.0.0-14-genericinstall
linux-image-3.0.0-15-genericdeinstall
linux-image-3.0.0-16-genericdeinstall
linux-image-3.0.0-17-genericdeinstall


On Fri, Mar 30, 2012 at 9:08 AM, Mike Ballon  wrote:

> Lets try the other route; what is your output to "dpkg
> --get-selections | grep openssh" ?
>
> Also post the output of dpkg --get-selections | grep linux-image" just for
> fun.
>
> On Fri, Mar 30, 2012 at 11:49 AM, Michael Havens  wrote:
> >> Try sudo apt-get install openssh-server
> > I've tried that and it won't install. I think it is because their are
> three
> > packages in there that won't install (linux-image-3.0.0-15-generic,
> > linux-image-3.0.0-16-generic, and linux-image-3.0.0-17-generic). How do I
> > remove those packages?
> >
>
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

you know... I am having such problems that I think I should just reinstall
everything. What do you think?

On Fri, Mar 30, 2012 at 10:07 AM, Michael Havens  wrote:

>  dpkg --get-selections | grep openssh
> openssh-clientinstall
> openssh-serverdeinstall
> dpkg --get-selections | grep linux-image
> linux-image-3.0.0-12-genericinstall
> linux-image-3.0.0-14-genericinstall
> linux-image-3.0.0-15-genericdeinstall
> linux-image-3.0.0-16-genericdeinstall
> linux-image-3.0.0-17-genericdeinstall
>
>
>
> On Fri, Mar 30, 2012 at 9:08 AM, Mike Ballon wrote:
>
>> Lets try the other route; what is your output to "dpkg
>> --get-selections | grep openssh" ?
>>
>> Also post the output of dpkg --get-selections | grep linux-image" just
>> for fun.
>>
>> On Fri, Mar 30, 2012 at 11:49 AM, Michael Havens 
>> wrote:
>> >> Try sudo apt-get install openssh-server
>> > I've tried that and it won't install. I think it is because their are
>> three
>> > packages in there that won't install (linux-image-3.0.0-15-generic,
>> > linux-image-3.0.0-16-generic, and linux-image-3.0.0-17-generic). How do
>> I
>> > remove those packages?
>> >
>>
>


-- 
:-)~MIKE~(-:
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Mike Ballon]

I'd say yes, not sure why there are two linux-image packages. Of
course I'm not an ubuntu expert  You can try to download the deb
package yourself and install with dpkg with a --force for a last ditch
effort. There is always grabbing the tarball and installing from
source as well :)

On Fri, Mar 30, 2012 at 2:25 PM, Michael Havens  wrote:
> you know... I am having such problems that I think I should just reinstall
> everything. What do you think?
>
>
> On Fri, Mar 30, 2012 at 10:07 AM, Michael Havens  wrote:
>>
>>  dpkg --get-selections | grep openssh
>> openssh-client                    install
>> openssh-server                    deinstall
>> dpkg --get-selections | grep linux-image
>> linux-image-3.0.0-12-generic            install
>> linux-image-3.0.0-14-generic            install
>> linux-image-3.0.0-15-generic            deinstall
>> linux-image-3.0.0-16-generic            deinstall
>> linux-image-3.0.0-17-generic            deinstall
>>
>>
>>
>> On Fri, Mar 30, 2012 at 9:08 AM, Mike Ballon 
>> wrote:
>>>
>>> Lets try the other route; what is your output to "dpkg
>>> --get-selections | grep openssh" ?
>>>
>>> Also post the output of dpkg --get-selections | grep linux-image" just
>>> for fun.
>>>
>>> On Fri, Mar 30, 2012 at 11:49 AM, Michael Havens 
>>> wrote:
>>> >> Try sudo apt-get install openssh-server
>>> > I've tried that and it won't install. I think it is because their are
>>> > three
>>> > packages in there that won't install (linux-image-3.0.0-15-generic,
>>> > linux-image-3.0.0-16-generic, and linux-image-3.0.0-17-generic). How do
>>> > I
>>> > remove those packages?
>>> >
>
>
>
>
> --
> :-)~MIKE~(-:
>
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Lisa Kachold]

Hi Mike,

On Fri, Mar 30, 2012 at 6:58 PM, Mike Ballon  wrote:

> I'd say yes, not sure why there are two linux-image packages. Of
> course I'm not an ubuntu expert  You can try to download the deb
> package yourself and install with dpkg with a --force for a last ditch
> effort. There is always grabbing the tarball and installing from
> source as well :)
>

Don't reinstall.

What is your error now?

/etc/init.d/sshd start
ssh localhost

What are your permissions on your home directory?

sudo ls -al $HOME

>
> On Fri, Mar 30, 2012 at 2:25 PM, Michael Havens  wrote:
> > you know... I am having such problems that I think I should just
> reinstall
> > everything. What do you think?
> >
> >
> > On Fri, Mar 30, 2012 at 10:07 AM, Michael Havens 
> wrote:
> >>
> >>  dpkg --get-selections | grep openssh
> >> openssh-clientinstall
> >> openssh-serverdeinstall
> >> dpkg --get-selections | grep linux-image
> >> linux-image-3.0.0-12-genericinstall
> >> linux-image-3.0.0-14-genericinstall
> >> linux-image-3.0.0-15-genericdeinstall
> >> linux-image-3.0.0-16-genericdeinstall
> >> linux-image-3.0.0-17-genericdeinstall
> >>
> >>
> >>
> >> On Fri, Mar 30, 2012 at 9:08 AM, Mike Ballon 
> >> wrote:
> >>>
> >>> Lets try the other route; what is your output to "dpkg
> >>> --get-selections | grep openssh" ?
> >>>
> >>> Also post the output of dpkg --get-selections | grep linux-image" just
> >>> for fun.
> >>>
> >>> On Fri, Mar 30, 2012 at 11:49 AM, Michael Havens 
> >>> wrote:
> >>> >> Try sudo apt-get install openssh-server
> >>> > I've tried that and it won't install. I think it is because their are
> >>> > three
> >>> > packages in there that won't install (linux-image-3.0.0-15-generic,
> >>> > linux-image-3.0.0-16-generic, and linux-image-3.0.0-17-generic). How
> do
> >>> > I
> >>> > remove those packages?
> >>> >
> >
> >
> >
> >
> > --
> > :-)~MIKE~(-:
> >
> > ---
> > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change your mail settings:
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



-- 
(503) 754-4452 Android
(623) 239-3392 Skype
(623) 688-3392 Google Voice
**
it-clowns.com
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

>You don't need openssh-server, it's already installed.

What does it mean when it says 'set to manually installed' when I type in
'apt-get install openssh-server'?

and then tried to install openssh-server. Well I guess it kinda worked. I
>> think it installed ssh-server because when I type in apt-get install
>> ssh-server it says:
>>
>>   openssh-server is already the newest version.
>>   openssh-server set to manually installed.
>>
>

>
>> but when I try ssh:
>>
>> sudo ssh 192.168.0.4
>> root@192.168.0.4's password: <-laptop
>> Welcome to Linux Mint 12 Lisa (GNU/Linux 3.0.0-12-generic i686)
>>
>> Welcome to Linux Mint
>>  * Documentation:  http://www.linuxmint.com
>>
>> Last login: Wed Mar 28 16:20:36 2012
>> Michaels-Laptop ~ # ssh 192.168.0.2  <-
>> computer in question
>> ssh: connect to host 192.168.0.2 port 22: No route to host
>>
>
> Michael, in Linux troubleshooting, "the error is the answer".  So that
> means there is NO ROUTE TO HOST.
> Is the machine on the same network?
>
> # traceroute 192.168.0.4
> # ping 192.168.0.4
>

Yes, they are in the same network. /24.
Michaels-Laptop ~ # traceroute 192.168.0.3
traceroute to 192.168.0.3 (192.168.0.3), 30 hops max, 60 byte packets
 1  * * *
 ...
 30  * * *
Michaels-Laptop ~ # ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_req=1 ttl=64 time=1.70 ms
^C
--- 192.168.0.3 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 1.422/1.551/1.722/0.135 ms
Michaels-Laptop ~ # ip addr show
1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether 44:1e:a1:c8:89:4b brd ff:ff:ff:ff:ff:ff
3: wlan0:  mtu 1500 qdisc mq state UP qlen
1000
link/ether 94:39:e5:11:b8:84 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.4/24 brd 192.168.0.255 scope global wlan0
inet6 fe80::9639:e5ff:fe11:b884/64 scope link
   valid_lft forever preferred_lft forever
Michaels-Laptop ~ #
bmike1@Michaels-PC:~$ traceroute 192.168.0.4
traceroute to 192.168.0.4 (192.168.0.4), 30 hops max, 60 byte packets
 1  Michaels-Laptop (192.168.0.4)  1.693 ms  1.623 ms  2.344 ms
bmike1@Michaels-PC:~$ ping 192.168.0.4
PING 192.168.0.4 (192.168.0.4) 56(84) bytes of data.
^C
--- 192.168.0.4 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.421/1.662/2.175/0.267 ms
bmike1@Michaels-PC:~$ ip addr show
1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast state
UP qlen 1000
link/ether 00:09:6b:78:ab:f0 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.3/24 brd 192.168.0.255 scope global eth0
inet6 fe80::209:6bff:fe78:abf0/64 scope link
   valid_lft forever preferred_lft forever
bmike1@Michaels-PC:~$


>>
> Michaels-Laptop ~ #
>>  The synaptic report is at 'a'.
>>
>>
>>   bmike1@Michaels-PC:~$ /etc/init.d/sshd start
>>   bash: /etc/init.d/sshd: No such file or directory
>>   bmike1@Michaels-PC:~$ ssh localhost
>>   ssh: connect to host localhost port 22: Connection refused
>>   bmike1@Michaels-PC:~$
>>
>
> # cd /etc/init.d/
> # ls -al ssh*
>
> It's called /etc/init.d/ssh in Ubuntu
> https://help.ubuntu.com/10.04/serverguide/C/openssh-server.html
>

bmike1@Michaels-PC:~$  cd /etc/init.d/
bmike1@Michaels-PC:/etc/init.d$  ls -al ssh*
-rwxr-xr-x 1 root root 4194 2011-07-29 09:02 ssh
bmike1@Michaels-PC:/etc/init.d$ cd ssh
bash: cd: ssh: Not a directory
bmike1@Michaels-PC:/etc/init.d$ sudo ssh start
[sudo] password for bmike1:  sat for five minutes
^Cbmike1@Michaels-PC:/etc/init.d$

why did the sound stop working?
>>Another problem that just started is the sound on the print server
stopped working. I clicked on the speaker icon >>to turn it up and I see it
is maxed. So then I clicked 'sound settings' and the output volume is maxed
so I >>investigate the tabs. The first tab (hardware) has nothing in the
'choose a device to configure' window. So >>somehow the driver was removed
(I guess).
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Lisa Kachold]

On Sat, Mar 31, 2012 at 11:38 AM, Michael Havens  wrote:

> >You don't need openssh-server, it's already installed.
>
> What does it mean when it says 'set to manually installed' when I type in
> 'apt-get install openssh-server'?
>

That means you "manually installed it".

>
>  and then tried to install openssh-server. Well I guess it kinda worked.
>>> I think it installed ssh-server because when I type in apt-get install
>>> ssh-server it says:
>>>
>>>   openssh-server is already the newest version.
>>>   openssh-server set to manually installed.
>>>
>>
>
>>
>>> but when I try ssh:
>>>
>>> sudo ssh 192.168.0.4
>>> root@192.168.0.4's password: <-laptop
>>> Welcome to Linux Mint 12 Lisa (GNU/Linux 3.0.0-12-generic i686)
>>>
>>> Welcome to Linux Mint
>>>  * Documentation:  http://www.linuxmint.com
>>>
>>> Last login: Wed Mar 28 16:20:36 2012
>>> Michaels-Laptop ~ # ssh 192.168.0.2  <-
>>> computer in question
>>> ssh: connect to host 192.168.0.2 port 22: No route to host
>>>
>>
>> Michael, in Linux troubleshooting, "the error is the answer".  So that
>> means there is NO ROUTE TO HOST.
>> Is the machine on the same network?
>>
>> # traceroute 192.168.0.4
>> # ping 192.168.0.4
>>
>
> Yes, they are in the same network. /24.
> Michaels-Laptop ~ # traceroute 192.168.0.3
> traceroute to 192.168.0.3 (192.168.0.3), 30 hops max, 60 byte packets
>  1  * * *
>  ...
>  30  * * *
> Michaels-Laptop ~ # ping 192.168.0.3
> PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
> 64 bytes from 192.168.0.3: icmp_req=1 ttl=64 time=1.70 ms
> ^C
> --- 192.168.0.3 ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 4005ms
> rtt min/avg/max/mdev = 1.422/1.551/1.722/0.135 ms
> Michaels-Laptop ~ # ip addr show
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet6 ::1/128 scope host
>valid_lft forever preferred_lft forever
> 2: eth0:  mtu 1500 qdisc pfifo_fast
> state DOWN qlen 1000
> link/ether 44:1e:a1:c8:89:4b brd ff:ff:ff:ff:ff:ff
> 3: wlan0:  mtu 1500 qdisc mq state UP
> qlen 1000
> link/ether 94:39:e5:11:b8:84 brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.4/24 brd 192.168.0.255 scope global wlan0
> inet6 fe80::9639:e5ff:fe11:b884/64 scope link
>valid_lft forever preferred_lft forever
> Michaels-Laptop ~ #
> bmike1@Michaels-PC:~$ traceroute 192.168.0.4
> traceroute to 192.168.0.4 (192.168.0.4), 30 hops max, 60 byte packets
>  1  Michaels-Laptop (192.168.0.4)  1.693 ms  1.623 ms  2.344 ms
> bmike1@Michaels-PC:~$ ping 192.168.0.4
> PING 192.168.0.4 (192.168.0.4) 56(84) bytes of data.
> ^C
> --- 192.168.0.4 ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 4006ms
> rtt min/avg/max/mdev = 1.421/1.662/2.175/0.267 ms
> bmike1@Michaels-PC:~$ ip addr show
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet6 ::1/128 scope host
>valid_lft forever preferred_lft forever
> 2: eth0:  mtu 1500 qdisc pfifo_fast state
> UP qlen 1000
> link/ether 00:09:6b:78:ab:f0 brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.3/24 brd 192.168.0.255 scope global eth0
> inet6 fe80::209:6bff:fe78:abf0/64 scope link
>valid_lft forever preferred_lft forever
> bmike1@Michaels-PC:~$
>

Mike it looks like one of you systems is on the wireless and the other on
the Wired.

Can you run on both servers:
# apt-get install nmap
Then on each server:
# nmap -PN 192.168.0.3
# nmap -PN 192.168.0.4

and post that?


>
>
>>>
>> Michaels-Laptop ~ #
>>>  The synaptic report is at 'a'.
>>>
>>>
>>>   bmike1@Michaels-PC:~$ /etc/init.d/sshd start
>>>   bash: /etc/init.d/sshd: No such file or directory
>>>   bmike1@Michaels-PC:~$ ssh localhost
>>>   ssh: connect to host localhost port 22: Connection refused
>>>   bmike1@Michaels-PC:~$
>>>
>>
>> # cd /etc/init.d/
>> # ls -al ssh*
>>
>> It's called /etc/init.d/ssh in Ubuntu
>> https://help.ubuntu.com/10.04/serverguide/C/openssh-server.html
>>
>
> bmike1@Michaels-PC:~$  cd /etc/init.d/
> bmike1@Michaels-PC:/etc/init.d$  ls -al ssh*
> -rwxr-xr-x 1 root root 4194 2011-07-29 09:02 ssh
> bmike1@Michaels-PC:/etc/init.d$ cd ssh
> bash: cd: ssh: Not a directory
> bmike1@Michaels-PC:/etc/init.d$ sudo ssh start
> [sudo] password for bmike1:  sat for five minutes
> ^Cbmike1@Michaels-PC:/etc/init.d$
>

Okay that's possibly a path issue.

if you are in the directory you would enter:

# sudo ./ssh start

otherwise

# sudo /etc/init.d/ssh start


>
> why did the sound stop working?
>
> >>Another problem that just started is the sound on the print server
> stopped working. I clicked on the speaker icon >>to turn it up and I see it
> is maxed. So then I clicked 'sound settings' and the output volume is maxed
> so I >>investigate the tabs. The first tab (hardware) has nothing in the
> 'choose a device to configure' window. So >>som

Re: ssh in network

[Michael Havens]

> That means you "manually installed it".
>

I did?

>Mike it looks like one of you systems is on the wireless and the other on
the Wired.
Yes, that is correct. Both connected to the modem

>Can you run on both servers:
># apt-get install nmap
>Then on each server:
># nmap -PN 192.168.0.3
># nmap -PN 192.168.0.4
>and post that?

bmike1@Michaels-PC:/etc/init.d$ sudo nmap -PN 192.168.0.3

Starting Nmap 5.21 ( http://nmap.org ) at 2012-03-31 12:38 MST
Nmap scan report for 192.168.0.3
Host is up (0.45s latency).
Not shown: 992 closed ports
PORT STATE SERVICE
22/tcp   open  ssh
80/tcp   open  http
139/tcp  open  netbios-ssn
443/tcp  open  https
445/tcp  open  microsoft-ds
631/tcp  open  ipp
5800/tcp open  vnc-http
5900/tcp open  vnc

Nmap done: 1 IP address (1 host up) scanned in 0.80 seconds
bmike1@Michaels-PC:/etc/init.d$ sudo nmap -PN 192.168.0.4

Starting Nmap 5.21 ( http://nmap.org ) at 2012-03-31 12:38 MST
Nmap scan report for Michaels-Laptop (192.168.0.4)
Host is up (0.0076s latency).
Not shown: 999 closed ports
PORT   STATE SERVICE
22/tcp open  ssh
MAC Address: 94:39:E5:11:B8:84 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 1.94 seconds
bmike1@Michaels-PC:/etc/init.d$



>>

>>> Michaels-Laptop ~ #
  The synaptic report is at 'a'.


   bmike1@Michaels-PC:~$ /etc/init.d/sshd start
   bash: /etc/init.d/sshd: No such file or directory
   bmike1@Michaels-PC:~$ ssh localhost
   ssh: connect to host localhost port 22: Connection refused
   bmike1@Michaels-PC:~$

>>>
>>> # cd /etc/init.d/
>>> # ls -al ssh*
>>>
>>> It's called /etc/init.d/ssh in Ubuntu
>>> https://help.ubuntu.com/10.04/serverguide/C/openssh-server.html
>>>
>>
>> bmike1@Michaels-PC:~$  cd /etc/init.d/
>> bmike1@Michaels-PC:/etc/init.d$  ls -al ssh*
>> -rwxr-xr-x 1 root root 4194 2011-07-29 09:02 ssh
>> bmike1@Michaels-PC:/etc/init.d$ cd ssh
>> bash: cd: ssh: Not a directory
>> bmike1@Michaels-PC:/etc/init.d$ sudo ssh start
>> [sudo] password for bmike1:  sat for five minutes
>> ^Cbmike1@Michaels-PC:/etc/init.d$
>>
>
> Okay that's possibly a path issue.
>
> if you are in the directory you would enter:
>
> # sudo ./ssh start
>
> otherwise
>
>
# sudo /etc/init.d/ssh start
>

Oh... I forgot the './' Bummer!  I thought this might make the ubuntu so
that other machines could ssh into it but still connection times out.



>> why did the sound stop working?
>>
>> >>Another problem that just started is the sound on the print server
>> stopped working. I clicked on the speaker icon >>to turn it up and I see it
>> is maxed. So then I clicked 'sound settings' and the output volume is maxed
>> so I >>investigate the tabs. The first tab (hardware) has nothing in the
>> 'choose a device to configure' window. So >>somehow the driver was removed
>> (I guess).
>>
>>
> Which distro?
>
> Ubuntu (print server).
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Lisa Kachold]

On Sat, Mar 31, 2012 at 12:58 PM, Michael Havens  wrote:

>
> That means you "manually installed it".
>>
>
> I did?
>

Just remove it:

# apt-get remove openssh-server
# apt-get add openssh-server
# /etc/init.d/ssh start

>Mike it looks like one of you systems is on the wireless and the other on
> the Wired.
> Yes, that is correct. Both connected to the modem
>
>
> >Can you run on both servers:
> ># apt-get install nmap
> >Then on each server:
> ># nmap -PN 192.168.0.3
> ># nmap -PN 192.168.0.4
> >and post that?
>
> bmike1@Michaels-PC:/etc/init.d$ sudo nmap -PN 192.168.0.3
>
> Starting Nmap 5.21 ( http://nmap.org ) at 2012-03-31 12:38 MST
> Nmap scan report for 192.168.0.3
> Host is up (0.45s latency).
> Not shown: 992 closed ports
> PORT STATE SERVICE
> 22/tcp   open  ssh
> 80/tcp   open  http
> 139/tcp  open  netbios-ssn
> 443/tcp  open  https
> 445/tcp  open  microsoft-ds
> 631/tcp  open  ipp
> 5800/tcp open  vnc-http
> 5900/tcp open  vnc
>
> Nmap done: 1 IP address (1 host up) scanned in 0.80 seconds
> bmike1@Michaels-PC:/etc/init.d$ sudo nmap -PN 192.168.0.4
>
> Starting Nmap 5.21 ( http://nmap.org ) at 2012-03-31 12:38 MST
> Nmap scan report for Michaels-Laptop (192.168.0.4)
> Host is up (0.0076s latency).
> Not shown: 999 closed ports
> PORT   STATE SERVICE
> 22/tcp open  ssh
> MAC Address: 94:39:E5:11:B8:84 (Unknown)
>
> Nmap done: 1 IP address (1 host up) scanned in 1.94 seconds
> bmike1@Michaels-PC:/etc/init.d$
>
>
>
>>>
>
 Michaels-Laptop ~ #
>  The synaptic report is at 'a'.
>
>
>   bmike1@Michaels-PC:~$ /etc/init.d/sshd start
>   bash: /etc/init.d/sshd: No such file or directory
>   bmike1@Michaels-PC:~$ ssh localhost
>   ssh: connect to host localhost port 22: Connection refused
>   bmike1@Michaels-PC:~$
>

 # cd /etc/init.d/
 # ls -al ssh*

 It's called /etc/init.d/ssh in Ubuntu
 https://help.ubuntu.com/10.04/serverguide/C/openssh-server.html

>>>
>>> bmike1@Michaels-PC:~$  cd /etc/init.d/
>>> bmike1@Michaels-PC:/etc/init.d$  ls -al ssh*
>>> -rwxr-xr-x 1 root root 4194 2011-07-29 09:02 ssh
>>> bmike1@Michaels-PC:/etc/init.d$ cd ssh
>>> bash: cd: ssh: Not a directory
>>> bmike1@Michaels-PC:/etc/init.d$ sudo ssh start
>>> [sudo] password for bmike1:  sat for five minutes
>>> ^Cbmike1@Michaels-PC:/etc/init.d$
>>>
>>
>> Okay that's possibly a path issue.
>>
>> if you are in the directory you would enter:
>>
>> # sudo ./ssh start
>>
>> otherwise
>>
>>
> # sudo /etc/init.d/ssh start
>>
>
> Oh... I forgot the './' Bummer!  I thought this might make the ubuntu so
> that other machines could ssh into it but still connection times out.
>

That means that the connection times out.   Are you trying to ssh as root?
Sometimes root is excluded from connecting via /etc/ssh/sshd_config?

# grep Root /etc/ssh/sshd_config

Okay, you can do (verify ssh):
# /etc/init.d/ssh status
or
# netstat -antp |grep ssh
or
# ps -ef |grep ssh

Try your connection again!

# ssh yourname@targetprintserverip

If the connection is seen on the host (but has some problem due to FQN
(/etc/hosts) or /etc/hosts.allow files, it will be logged in either:

# tail /var/log/messages
# tail /var/log/secure

Okay we see the ports open, so we don't have a firewall in the way.

What is in your /etc/hosts.allow and /etc/hosts.deny on the ssh target?

>
>
>
>>> why did the sound stop working?
>>>
>>> >>Another problem that just started is the sound on the print server
>>> stopped working. I clicked on the speaker icon >>to turn it up and I see it
>>> is maxed. So then I clicked 'sound settings' and the output volume is maxed
>>> so I >>investigate the tabs. The first tab (hardware) has nothing in the
>>> 'choose a device to configure' window. So >>somehow the driver was removed
>>> (I guess).
>>>
>>>
>> Which distro?
>>
>> Ubuntu (print server).
>

Okay you can post to the Ubuntu boards, or google the exact *distro
version*[uname -a] with your question and find a great number of
people who have
already answered your question.

>
>
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



-- 
(503) 754-4452 Android
(623) 239-3392 Skype
(623) 688-3392 Google Voice
**
it-clowns.com
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

On Sat, Mar 31, 2012 at 1:21 PM, Lisa Kachold wrote:

>
>
> On Sat, Mar 31, 2012 at 12:58 PM, Michael Havens  wrote:
>
>>
>> That means you "manually installed it".
>>>
>>
>> I did?
>>
>
> Just remove it:
>
> # apt-get remove openssh-server
> # apt-get add openssh-server
> # /etc/init.d/ssh start
>
>
I just tried and those linux kernel updates  for
   linux-image-3.0.0-15-generic
   linux-image-3.0.0-16-generic
   linux-image-3.0.0-17-generic
still show up (and make me wait about 5 minutes for it to complete). (see
'a' at the end) After I removed it I tried the second command you gave me
and it said 'command not found'.
Then I tried to ssh out of the ubuntu but got the connection refused error,
so I reinstalled it and could again..


> >Mike it looks like one of you systems is on the wireless and the other on
>> the Wired.
>> Yes, that is correct. Both connected to the modem
>>
>>
> That means that the connection times out.   Are you trying to ssh as
> root?  Sometimes root is excluded from connecting via /etc/ssh/sshd_config?
>

I thought that was the only way to run ssh.


>
> # grep Root /etc/ssh/sshd_config <--- 'root' not in file
>
> Okay, you can do (verify ssh):
> # /etc/init.d/ssh status
> or
> # netstat -antp |grep ssh
> or
> # ps -ef |grep ssh <-- happily running
>

 ps -ef |grep ssh
bmike11750  1717  0 Mar27 ?00:00:01 /usr/bin/ssh-agent
/usr/bin/dbus-launch --exit-with-session /usr/bin/gnome-session
--session=ubuntu
root  2607 1  0 13:51 ?00:00:00 /usr/sbin/sshd -D
root  2942 29774  0 14:01 pts/300:00:00 grep --color=auto ssh
root@Michaels-PC:/etc/init.d#


> Try your connection again!  < I can only ssh out of the
> ubuntu, (this is the step I figured out 'apt-get remove openssh-server'
> broke things
>
> # ssh yourname@targetprintserverip
>
> If the connection is seen on the host (but has some problem due to FQN
> (/etc/hosts) or /etc/hosts.allow files, it will be logged in either:
>
> # tail /var/log/messages <--- no such file or directory
> # tail /var/log/secure  <--- no such file or directory
>
> Okay we see the ports open, so we don't have a firewall in the way.
>
> What is in your /etc/hosts.allow and /etc/hosts.deny on the ssh target?
>

 all lines are commented out., (see 'b' at end) Perhaps I should create an
allowed range?

from my investigation of the man page that would look like this:

192.168.0.0/255.255.255.245 (to allow for 10 units)

is that correct?

then I guess uncomment 'paranoid' in the deny file



>
>>
>>
 why did the sound stop working?

 >>Another problem that just started is the sound on the print server
 stopped working. I clicked on the speaker icon >>to turn it up and I see it
 is maxed. So then I clicked 'sound settings' and the output volume is maxed
 so I >>investigate the tabs. The first tab (hardware) has nothing in the
 'choose a device to configure' window. So >>somehow the driver was removed
 (I guess).


>>> Which distro?
>>>
>>> Ubuntu (print server).
>>
>
> Okay you can post to the Ubuntu boards, or google the exact *distro
> version* [uname -a] with your question and find a great number of people
> who have already answered your question.
>
>>
>>
>>
Thanks... I'll do just that!


>
> -a-
>  apt-get remove openssh-server
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
>   openssh-server ssh
> 0 upgraded, 0 newly installed, 2 to remove and 3 not upgraded.
> 3 not fully installed or removed.
> After this operation, 938 kB disk space will be freed.
> Do you want to continue [Y/n]?
> Abort.
> root@Michaels-PC:/etc/init.d# apt-get remove openssh-server
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
>   openssh-server ssh
> 0 upgraded, 0 newly installed, 2 to remove and 3 not upgraded.
> 3 not fully installed or removed.
> After this operation, 938 kB disk space will be freed.
> Do you want to continue [Y/n]? y
> (Reading database ... 259861 files and directories currently installed.)
> Removing ssh ...
> Removing openssh-server ...
> ssh stop/waiting
> Processing triggers for ureadahead ...
> Processing triggers for ufw ...
> Processing triggers for man-db ...
> Setting up linux-image-3.0.0-15-generic (3.0.0-15.26) ...
> Running depmod.
> update-initramfs: deferring update (hook will be called later)
> Examining /etc/kernel/postinst.d.
> run-parts: executing /etc/kernel/postinst.d/dkms 3.0.0-15-generic
> /boot/vmlinuz-3.0.0-15-generic
> run-parts: executing /etc/kernel/postinst.d/initramfs-tools
> 3.0.0-15-generic /boot/vmlinuz-3.0.0-15-generic
> update-initramfs: Generating /boot/initrd.img-3.0.0-15-generic
> /etc/initramfs-tools/conf.d/resume.new: 1: GNU: not found
> run-parts: executing /etc/kernel/postinst.d/pm-uti

Re: ssh in network

[Lisa Kachold]

Mike:

On Sat, Mar 31, 2012 at 2:44 PM, Michael Havens  wrote:

>
>
> On Sat, Mar 31, 2012 at 1:21 PM, Lisa Kachold wrote:
>
>>
>>
>> On Sat, Mar 31, 2012 at 12:58 PM, Michael Havens wrote:
>>
>>>
>>> That means you "manually installed it".

>>>
>>> I did?
>>>
>>
>> Just remove it:
>>
>> # apt-get remove openssh-server
>> # apt-get add openssh-server
>> # /etc/init.d/ssh start
>>
>>
> I just tried and those linux kernel updates  for
>linux-image-3.0.0-15-generic
>linux-image-3.0.0-16-generic
>linux-image-3.0.0-17-generic
> still show up (and make me wait about 5 minutes for it to complete). (see
> 'a' at the end) After I removed it I tried the second command you gave me
> and it said 'command not found'.
>
Okay sorry it's

# apt-get install openssh-server


> Then I tried to ssh out of the ubuntu but got the connection refused
> error, so I reinstalled it and could again..
>
>
>> >Mike it looks like one of you systems is on the wireless and the other
>>> on the Wired.
>>> Yes, that is correct. Both connected to the modem
>>>
>>>
>> That means that the connection times out.   Are you trying to ssh as
>> root?  Sometimes root is excluded from connecting via /etc/ssh/sshd_config?
>>
>
> I thought that was the only way to run ssh.
>
>
You run a ssh server and you use a ssh client as a user.

# ssh myusername@targetserverIP

>
>> # grep Root /etc/ssh/sshd_config <--- 'root' not in file
>>
>
Make sure you used "Root" like
# sudo grep Root /etc/ssh/sshd_config

You should see it (after openssh-server is installed) just look if it says
yes or no.

>
>>
>> Okay, you can do (verify ssh):
>> # /etc/init.d/ssh status
>> or
>> # netstat -antp |grep ssh
>> or
>> # ps -ef |grep ssh <-- happily
>> running
>>
>
>  ps -ef |grep ssh
> bmike11750  1717  0 Mar27 ?00:00:01 /usr/bin/ssh-agent
> /usr/bin/dbus-launch --exit-with-session /usr/bin/gnome-session
> --session=ubuntu
> root  2607 1  0 13:51 ?00:00:00 /usr/sbin/sshd -D
> root  2942 29774  0 14:01 pts/300:00:00 grep --color=auto ssh
> root@Michaels-PC:/etc/init.d#
>
>
>> Try your connection again!  < I can only ssh out of the
>> ubuntu, (this is the step I figured out 'apt-get remove openssh-server'
>> broke things
>>
>> Okay:

# apt-get install openssh-server
/etc/init.d/ssh start

>
>> # ssh yourname@targetprintserverip
>>
>> If the connection is seen on the host (but has some problem due to FQN
>> (/etc/hosts) or /etc/hosts.allow files, it will be logged in either:
>>
> Hmmm?  Go look in var log and see what this system logs to:

# sudo tail /var/log/messages
# sudo tail /var/log/syslog

>
>> # tail /var/log/messages <--- no such file or directory
>> # tail /var/log/secure  <--- no such file or directory
>>
>>
>> Okay we see the ports open, so we don't have a firewall in the way.
>>
>> What is in your /etc/hosts.allow and /etc/hosts.deny on the ssh target?
>>
>
>  all lines are commented out., (see 'b' at end) Perhaps I should create an
> allowed range?
>
> from my investigation of the man page that would look like this:
>
> 192.168.0.0/255.255.255.245 (to allow for 10 units)
>
> is that correct?
>
> then I guess uncomment 'paranoid' in the deny file
>

Add this to /etc/hosts.allow:

  /etc/hosts.allow looks:

ALL : 127.0.0.1
sshd : 192.168.0.0/24, 78.207.132.32

This example shows an external address you might want to use to connect
from outside your internal network (once you open or port forward port 22).

Now the /etc/hosts.deny file:

ALL : ALL


>
>
>>
>>>
>>>
> why did the sound stop working?
>
> >>Another problem that just started is the sound on the print server
> stopped working. I clicked on the speaker icon >>to turn it up and I see 
> it
> is maxed. So then I clicked 'sound settings' and the output volume is 
> maxed
> so I >>investigate the tabs. The first tab (hardware) has nothing in the
> 'choose a device to configure' window. So >>somehow the driver was removed
> (I guess).
>
>
 Which distro?

 Ubuntu (print server).
>>>
>>
>> Okay you can post to the Ubuntu boards, or google the exact *distro
>> version* [uname -a] with your question and find a great number of people
>> who have already answered your question.
>>
>>>
>>>
>>>
> Thanks... I'll do just that!
>
> Do this and your apt-get/aptitude will be fixed:

# sudo apt-get install make



>
>>
>> -a-
>>  apt-get remove openssh-server
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> The following packages will be REMOVED:
>>   openssh-server ssh
>> 0 upgraded, 0 newly installed, 2 to remove and 3 not upgraded.
>> 3 not fully installed or removed.
>> After this operation, 938 kB disk space will be freed.
>> Do you want to continue [Y/n]?
>> Abort.
>> root@Michaels-PC:/etc/init.d# apt-get remove openssh-server
>> Reading package lists... Done
>> Buildi

Re: ssh in network

[Michael Havens]

I was googling the 'no route to host' and found a suggestion to add a route
that poimts to the routerr with the command 'sudo ip route add
192.168.1.0/24 dev eth0'. So I thought that sounded good  but after I did
not only could I not ssh out of the computer but I could no longer ssh into
the computer. I then tried to remove the route with the command 'sudo ip
route del 192.168.1.0/24 dev eth0', but that didn't help any. I just
realized that the ip address is wrong my router is 192.168.0.1 but:

  sudo ip route add 192.168.0.1/24 dev eth0
  RTNETLINK answers: Invalid argument

On Sat, Mar 31, 2012 at 4:36 PM, Lisa Kachold wrote:

>
> # apt-get install openssh-server
>

sudo apt-get install openssh-server
. . .
openssh-server is already the newest version.
openssh-server set to manually installed.



> You run a ssh server and you use a ssh client as a user.
>
> # ssh myusername@targetserverIP
>
>>
>>> # grep Root /etc/ssh/sshd_config <--- 'root' not in file
>>>
>>
> Make sure you used "Root" like
> # sudo grep Root /etc/ssh/sshd_config
>

there it is. PermitRootLogin yes

If the connection is seen on the host (but has some problem due to FQN
>>> (/etc/hosts) or /etc/hosts.allow files, it will be logged in either:
>>>
>> Hmmm?  Go look in var log and see what this system logs to:
>
> # sudo tail /var/log/messages
> # sudo tail /var/log/syslog
>
>>
>>> bmike1@Michaels-PC:~$ sudo tail /var/log/messages;sudo tail
/var/log/syslog
tail: cannot open `/var/log/messages' for reading: No such file or directory
Apr  1 13:09:46 Michaels-PC ddclient[1763]: WARNING:  file
/etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Apr  1 13:14:46 Michaels-PC ddclient[1763]: WARNING:  file
/etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Apr  1 13:17:01 Michaels-PC CRON[8219]: (root) CMD (   cd / && run-parts
--report /etc/cron.hourly)
Apr  1 13:19:46 Michaels-PC ddclient[1763]: WARNING:  file
/etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Apr  1 13:24:46 Michaels-PC ddclient[1763]: WARNING:  file
/etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Apr  1 13:29:46 Michaels-PC ddclient[1763]: WARNING:  file
/etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Apr  1 13:34:46 Michaels-PC ddclient[1763]: WARNING:  file
/etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Apr  1 13:39:46 Michaels-PC ddclient[1763]: WARNING:  file
/etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Apr  1 13:44:46 Michaels-PC ddclient[1763]: WARNING:  file
/etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
Apr  1 13:49:46 Michaels-PC ddclient[1763]: WARNING:  file
/etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
bmike1@Michaels-PC:~$


> Add this to /etc/hosts.allow:
>>>
>>>   /etc/hosts.allow looks:
>>>
>>> ALL : 127.0.0.1
>>> sshd : 192.168.0.0/24, 78.207.132.32
>>>
>>> This example shows an external address you might want to use to connect
>>> from outside your internal network (once you open or port forward port 22).
>>>
>>> This is the hosts.allow file that I added. Does this look right?

ALL : 127.0.0.1
sshd : 192.168.0.0/24, 192.168.0.1/24, 192.168.0.2/24, 192.168.0.3/24,
192.168.$ 
#shows address to use from outside of network#, 78.207.132.32




>  Now the /etc/hosts.deny file:
>>>
>>> ALL : ALL
>>>
>>>
>>
>> Do this and your apt-get/aptitude will be fixed:
>
> # sudo apt-get install make
>
>
>
make is already its current version


-- 
:-)~MIKE~(-:
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Lisa Kachold]

Reboot

On Sun, Apr 1, 2012 at 3:25 PM, Michael Havens  wrote:

> I was googling the 'no route to host' and found a suggestion to add a
> route that poimts to the routerr with the command 'sudo ip route add
> 192.168.1.0/24 dev eth0'. So I thought that sounded good  but after I did
> not only could I not ssh out of the computer but I could no longer ssh into
> the computer. I then tried to remove the route with the command 'sudo ip
> route del 192.168.1.0/24 dev eth0', but that didn't help any. I just
> realized that the ip address is wrong my router is 192.168.0.1 but:
>
>   sudo ip route add 192.168.0.1/24 dev eth0
>   RTNETLINK answers: Invalid argument
>
> On Sat, Mar 31, 2012 at 4:36 PM, Lisa Kachold wrote:
>
>>
>> # apt-get install openssh-server
>>
>
> sudo apt-get install openssh-server
> . . .
> openssh-server is already the newest version.
> openssh-server set to manually installed.
>
>
>
>> You run a ssh server and you use a ssh client as a user.
>>
>>
>> # ssh myusername@targetserverIP
>>
>>>
 # grep Root /etc/ssh/sshd_config <--- 'root' not in file

>>>
>> Make sure you used "Root" like
>> # sudo grep Root /etc/ssh/sshd_config
>>
>
> there it is. PermitRootLogin yes
>
>  If the connection is seen on the host (but has some problem due to FQN
 (/etc/hosts) or /etc/hosts.allow files, it will be logged in either:

>>> Hmmm?  Go look in var log and see what this system logs to:
>>
>> # sudo tail /var/log/messages
>> # sudo tail /var/log/syslog
>>
>>>
 bmike1@Michaels-PC:~$ sudo tail /var/log/messages;sudo tail
> /var/log/syslog
> tail: cannot open `/var/log/messages' for reading: No such file or
> directory
> Apr  1 13:09:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:14:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:17:01 Michaels-PC CRON[8219]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Apr  1 13:19:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:24:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:29:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:34:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:39:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:44:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:49:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> bmike1@Michaels-PC:~$
>
>
>>  Add this to /etc/hosts.allow:

   /etc/hosts.allow looks:

 ALL : 127.0.0.1
 sshd : 192.168.0.0/24, 78.207.132.32

 This example shows an external address you might want to use to connect
 from outside your internal network (once you open or port forward port 22).

 This is the hosts.allow file that I added. Does this look right?
>
> ALL : 127.0.0.1
> sshd : 192.168.0.0/24, 192.168.0.1/24, 192.168.0.2/24, 192.168.0.3/24,
> 192.168.$ 
> #shows address to use from outside of network#, 78.207.132.32
>
>
>
>
>>   Now the /etc/hosts.deny file:

 ALL : ALL


>>>
>>> Do this and your apt-get/aptitude will be fixed:
>>
>> # sudo apt-get install make
>>
>>
>>
> make is already its current version
>
>
> --
> :-)~MIKE~(-:
>
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



-- 
(503) 754-4452 Android
(623) 239-3392 Skype
(623) 688-3392 Google Voice
**
it-clowns.com
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Lisa Kachold]

I was googling the 'no route to host' and found a suggestion to add a route
> that poimts to the routerr with the command 'sudo ip route add
> 192.168.1.0/24 dev eth0'. So I thought that sounded good  but after I did
> not only could I not ssh out of the computer but I could no longer ssh into
> the computer. I then tried to remove the route with the command 'sudo ip
> route del 192.168.1.0/24 dev eth0', but that didn't help any. I just
> realized that the ip address is wrong my router is 192.168.0.1 but:
>
>   sudo ip route add 192.168.0.1/24 dev eth0
>   RTNETLINK answers: Invalid argument
>

A route add command is not persistent past a reboot or network restart.

Mike, ONE of your systems is on your Wireless and the other is on the
wired?  Sometimes wireless to wired connections take longer than the
timeout values for ssh or scp.  Try putting them both on either wireless or
wired and see if that's more successful?

Timeouts could be why you get a no route to host.

Verify that both boxes have a default route:

# sudo netstat -rn

Verify that both boxes have a listening ssh daemon:

# sudo netstat -antp | grep 22

Make sure you haven't installed DenyHosts or iptables that limits your
connections:

# locate Deny |more
# sudo iptables-save |more

If you don't understand the output post it to the list.

>
> # apt-get install openssh-server
>>
>
> sudo apt-get install openssh-server
> . . .
> openssh-server is already the newest version.
> openssh-server set to manually installed.
>
>
>> You run a ssh server and you use a ssh client as a user.
>>
>> # ssh myusername@targetserverIP
>>
>>>
 # grep Root /etc/ssh/sshd_config <--- 'root' not in file

>>>
>> Make sure you used "Root" like
>> # sudo grep Root /etc/ssh/sshd_config
>>
>
> there it is. PermitRootLogin yes
>

Good! You can ssh to this host with root.

>
>  If the connection is seen on the host (but has some problem due to FQN
 (/etc/hosts) or /etc/hosts.allow files, it will be logged in either:

>>> Hmmm?  Go look in var log and see what this system logs to:
>>
>> # sudo tail /var/log/syslog
>>
>>>
 bmike1@Michaels-PC:~$ sudo tail /var/log/messages;sudo tail
> /var/log/syslog
> tail: cannot open `/var/log/messages' for reading: No such file or
> directory
> Apr  1 13:09:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:14:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:17:01 Michaels-PC CRON[8219]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Apr  1 13:19:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:24:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:29:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:34:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:39:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:44:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> Apr  1 13:49:46 Michaels-PC ddclient[1763]: WARNING:  file
> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
> bmike1@Michaels-PC:~$
>

What - are you running ddclient for?
If you can't properly resolve DNS, you will not be able to ssh:

Please see this link regarding your ddclient errors:
http://www.linuxquestions.org/questions/linux-wireless-networking-41/wifi-connects-but-no-network-access-but-wired-works-880213/

>
>
>>  Add this to /etc/hosts.allow:

   /etc/hosts.allow looks:

 ALL : 127.0.0.1
 sshd : 192.168.0.0/24, 78.207.132.32

 This example shows an external address you might want to use to connect
 from outside your internal network (once you open or port forward port 22).

 This is the hosts.allow file that I added. Does this look right?
>
> ALL : 127.0.0.1
> sshd : 192.168.0.0/24, 192.168.0.1/24, 192.168.0.2/24, 192.168.0.3/24,
> 192.168.$ 
> #shows address to use from outside of network#, 78.207.132.32
>

No, you need that 78.207.132.32 on the SAME line with either ALL or sshd:
or commented out.

And 192.168.$ might cause problems.  Change it to a safe entry:
cut here
ALL : 127.0.0.1
sshd : 192.168.0.0/16, 78.207.132.32 
###end ###

Make sure you did this:

>   Now the /etc/hosts.deny file:

 ALL : ALL


>>>
>>> Do this and your apt-get/aptitude will be fixed:
>>
>> # sudo apt-get install make
>>
>>
>>
> make is already its current version
>

# sudo apt-get update

Also setup your /

Re: ssh in network

[Michael Havens]

Now, instead of the 'no route to host' error I get a 'connection refused'.
I still can't ssh to the ubuntu machine. it times out.

On Sun, Apr 1, 2012 at 4:08 PM, Lisa Kachold wrote:

> 
>
> I was googling the 'no route to host' and found a suggestion to add a
>> route that poimts to the routerr with the command 'sudo ip route add
>> 192.168.1.0/24 dev eth0'. So I thought that sounded good  but after I
>> did not only could I not ssh out of the computer but I could no longer ssh
>> into the computer. I then tried to remove the route with the command 'sudo
>> ip route del 192.168.1.0/24 dev eth0', but that didn't help any. I just
>> realized that the ip address is wrong my router is 192.168.0.1 but:
>>
>>   sudo ip route add 192.168.0.1/24 dev eth0
>>   RTNETLINK answers: Invalid argument
>>
>
> A route add command is not persistent past a reboot or network restart.
>
> Mike, ONE of your systems is on your Wireless and the other is on the
> wired?  Sometimes wireless to wired connections take longer than the
> timeout values for ssh or scp.  Try putting them both on either wireless or
> wired and see if that's more successful?
>
> Timeouts could be why you get a no route to host.
>
> Verify that both boxes have a default route:
>
> # sudo netstat -rn
>
> Verify that both boxes have a listening ssh daemon:
>
> # sudo netstat -antp | grep 22
>
> Make sure you haven't installed DenyHosts or iptables that limits your
> connections:
>
> # locate Deny |more
> # sudo iptables-save |more
>
> If you don't understand the output post it to the list.
>
>>
>> # apt-get install openssh-server
>>>
>>
>> sudo apt-get install openssh-server
>> . . .
>> openssh-server is already the newest version.
>> openssh-server set to manually installed.
>>
>>
>>> You run a ssh server and you use a ssh client as a user.
>>>
>>> # ssh myusername@targetserverIP
>>>

> # grep Root /etc/ssh/sshd_config <--- 'root' not in file
>

>>> Make sure you used "Root" like
>>> # sudo grep Root /etc/ssh/sshd_config
>>>
>>
>> there it is. PermitRootLogin yes
>>
>
> Good! You can ssh to this host with root.
>
>>
>>  If the connection is seen on the host (but has some problem due to FQN
> (/etc/hosts) or /etc/hosts.allow files, it will be logged in either:
>
 Hmmm?  Go look in var log and see what this system logs to:
>>>
>>> # sudo tail /var/log/syslog
>>>

> bmike1@Michaels-PC:~$ sudo tail /var/log/messages;sudo tail
>> /var/log/syslog
>> tail: cannot open `/var/log/messages' for reading: No such file or
>> directory
>> Apr  1 13:09:46 Michaels-PC ddclient[1763]: WARNING:  file
>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>> Apr  1 13:14:46 Michaels-PC ddclient[1763]: WARNING:  file
>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>> Apr  1 13:17:01 Michaels-PC CRON[8219]: (root) CMD (   cd / && run-parts
>> --report /etc/cron.hourly)
>> Apr  1 13:19:46 Michaels-PC ddclient[1763]: WARNING:  file
>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>> Apr  1 13:24:46 Michaels-PC ddclient[1763]: WARNING:  file
>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>> Apr  1 13:29:46 Michaels-PC ddclient[1763]: WARNING:  file
>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>> Apr  1 13:34:46 Michaels-PC ddclient[1763]: WARNING:  file
>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>> Apr  1 13:39:46 Michaels-PC ddclient[1763]: WARNING:  file
>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>> Apr  1 13:44:46 Michaels-PC ddclient[1763]: WARNING:  file
>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>> Apr  1 13:49:46 Michaels-PC ddclient[1763]: WARNING:  file
>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>> bmike1@Michaels-PC:~$
>>
>
> What - are you running ddclient for?
> If you can't properly resolve DNS, you will not be able to ssh:
>
> Please see this link regarding your ddclient errors:
>
> http://www.linuxquestions.org/questions/linux-wireless-networking-41/wifi-connects-but-no-network-access-but-wired-works-880213/
>
>>
>>
>>>  Add this to /etc/hosts.allow:
>
>   /etc/hosts.allow looks:
>
> ALL : 127.0.0.1
> sshd : 192.168.0.0/24, 78.207.132.32
>
> This example shows an external address you might want to use to
> connect from outside your internal network (once you open or port forward
> port 22).
>
> This is the hosts.allow file that I added. Does this look right?
>>
>> ALL : 127.0.0.1
>> sshd : 192.168.0.0/24, 192.168.0.1/24, 192.168.0.2/24, 192.168.0.3/24,
>> 192.168.$ 
>> #shows address to use from outside of network#, 78.207.132.32
>>
>
> No, you need that 78.207.132.32 on the SAME line with either ALL or sshd:
> or commented out.
>
> And 192.168.$ might cause problems.  Change it to a safe entry:
> cut here
> ALL : 127.0.0.1
> sshd : 1

Re: ssh in network

[Lisa Kachold]

Michael, did you follow every suggestion in the last email?

Reboot
check and verify network and ssh daemons including default routes on both
machines
verify that you have the right settings in your /etc/hosts.allow and
/etc/hosts.deny files on both servers
add /etc/hosts entries for all your machines
verify that you don't have a DenyHost or iptables running
Test your ssh again

Also:
run apt-get update
look at why you are using ddclient and why it's failing [from the link I
sent]

??

On Sun, Apr 1, 2012 at 4:18 PM, Michael Havens  wrote:

> Now, instead of the 'no route to host' error I get a 'connection refused'.
> I still can't ssh to the ubuntu machine. it times out.
>
> On Sun, Apr 1, 2012 at 4:08 PM, Lisa Kachold wrote:
>
>> 
>>
>> I was googling the 'no route to host' and found a suggestion to add a
>>> route that poimts to the routerr with the command 'sudo ip route add
>>> 192.168.1.0/24 dev eth0'. So I thought that sounded good  but after I
>>> did not only could I not ssh out of the computer but I could no longer ssh
>>> into the computer. I then tried to remove the route with the command 'sudo
>>> ip route del 192.168.1.0/24 dev eth0', but that didn't help any. I just
>>> realized that the ip address is wrong my router is 192.168.0.1 but:
>>>
>>>   sudo ip route add 192.168.0.1/24 dev eth0
>>>   RTNETLINK answers: Invalid argument
>>>
>>
>> A route add command is not persistent past a reboot or network restart.
>>
>> Mike, ONE of your systems is on your Wireless and the other is on the
>> wired?  Sometimes wireless to wired connections take longer than the
>> timeout values for ssh or scp.  Try putting them both on either wireless or
>> wired and see if that's more successful?
>>
>> Timeouts could be why you get a no route to host.
>>
>> Verify that both boxes have a default route:
>>
>> # sudo netstat -rn
>>
>> Verify that both boxes have a listening ssh daemon:
>>
>> # sudo netstat -antp | grep 22
>>
>> Make sure you haven't installed DenyHosts or iptables that limits your
>> connections:
>>
>> # locate Deny |more
>> # sudo iptables-save |more
>>
>> If you don't understand the output post it to the list.
>>
>>>
>>> # apt-get install openssh-server

>>>
>>> sudo apt-get install openssh-server
>>> . . .
>>> openssh-server is already the newest version.
>>> openssh-server set to manually installed.
>>>
>>>
 You run a ssh server and you use a ssh client as a user.

 # ssh myusername@targetserverIP

>
>> # grep Root /etc/ssh/sshd_config <--- 'root' not in file
>>
>
 Make sure you used "Root" like
 # sudo grep Root /etc/ssh/sshd_config

>>>
>>> there it is. PermitRootLogin yes
>>>
>>
>> Good! You can ssh to this host with root.
>>
>>>
>>>  If the connection is seen on the host (but has some problem due to FQN
>> (/etc/hosts) or /etc/hosts.allow files, it will be logged in either:
>>
> Hmmm?  Go look in var log and see what this system logs to:

 # sudo tail /var/log/syslog

>
>> bmike1@Michaels-PC:~$ sudo tail /var/log/messages;sudo tail
>>> /var/log/syslog
>>> tail: cannot open `/var/log/messages' for reading: No such file or
>>> directory
>>> Apr  1 13:09:46 Michaels-PC ddclient[1763]: WARNING:  file
>>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>>> Apr  1 13:14:46 Michaels-PC ddclient[1763]: WARNING:  file
>>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>>> Apr  1 13:17:01 Michaels-PC CRON[8219]: (root) CMD (   cd / && run-parts
>>> --report /etc/cron.hourly)
>>> Apr  1 13:19:46 Michaels-PC ddclient[1763]: WARNING:  file
>>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>>> Apr  1 13:24:46 Michaels-PC ddclient[1763]: WARNING:  file
>>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>>> Apr  1 13:29:46 Michaels-PC ddclient[1763]: WARNING:  file
>>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>>> Apr  1 13:34:46 Michaels-PC ddclient[1763]: WARNING:  file
>>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>>> Apr  1 13:39:46 Michaels-PC ddclient[1763]: WARNING:  file
>>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>>> Apr  1 13:44:46 Michaels-PC ddclient[1763]: WARNING:  file
>>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>>> Apr  1 13:49:46 Michaels-PC ddclient[1763]: WARNING:  file
>>> /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
>>> bmike1@Michaels-PC:~$
>>>
>>
>> What - are you running ddclient for?
>> If you can't properly resolve DNS, you will not be able to ssh:
>>
>> Please see this link regarding your ddclient errors:
>>
>> http://www.linuxquestions.org/questions/linux-wireless-networking-41/wifi-connects-but-no-network-access-but-wired-works-880213/
>>
>>>
>>>
  Add this to /etc/hosts.allow:
>>
>>   /etc/hosts.allow looks:
>>
>> ALL : 127.0.0.1
>> sshd : 192.168.0.0/24

Re: ssh in network

[Michael Havens]

I'm doing your suggestions right now. I don't know how I missed them
but after I sent the reply you are responding to I noticed them and started
the implemetation of them.  I did reboot and still ssh doesn't work. Just
wait until you get the response to your suggestion email. Sorry about the
confusion.

On Sun, Apr 1, 2012 at 4:50 PM, Lisa Kachold wrote:

> Michael, did you follow every suggestion in the last email?
>
> Reboot
> check and verify network and ssh daemons including default routes on both
> machines
> verify that you have the right settings in your /etc/hosts.allow and
> /etc/hosts.deny files on both servers
> add /etc/hosts entries for all your machines
> verify that you don't have a DenyHost or iptables running
> Test your ssh again
>
> Also:
> run apt-get update
> look at why you are using ddclient and why it's failing [from the link I
> sent]
>
> ??
>
>
> On Sun, Apr 1, 2012 at 4:18 PM, Michael Havens  wrote:
>
>> Now, instead of the 'no route to host' error I get a 'connection
>> refused'. I still can't ssh to the ubuntu machine. it times out.
>>
>> On Sun, Apr 1, 2012 at 4:08 PM, Lisa Kachold wrote:
>>
>>> 
>>>
>>> I was googling the 'no route to host' and found a suggestion to add a
 route that poimts to the routerr with the command 'sudo ip route add
 192.168.1.0/24 dev eth0'. So I thought that sounded good  but after I
 did not only could I not ssh out of the computer but I could no longer ssh
 into the computer. I then tried to remove the route with the command 'sudo
 ip route del 192.168.1.0/24 dev eth0', but that didn't help any. I
 just realized that the ip address is wrong my router is 192.168.0.1 
 but:

   sudo ip route add 192.168.0.1/24 dev eth0
   RTNETLINK answers: Invalid argument

>>>
>>> A route add command is not persistent past a reboot or network restart.
>>>
>>> Mike, ONE of your systems is on your Wireless and the other is on the
>>> wired?  Sometimes wireless to wired connections take longer than the
>>> timeout values for ssh or scp.  Try putting them both on either wireless or
>>> wired and see if that's more successful?
>>>
>>> Timeouts could be why you get a no route to host.
>>>
>>> Verify that both boxes have a default route:
>>>
>>> # sudo netstat -rn
>>>
>>> Verify that both boxes have a listening ssh daemon:
>>>
>>> # sudo netstat -antp | grep 22
>>>
>>> Make sure you haven't installed DenyHosts or iptables that limits your
>>> connections:
>>>
>>> # locate Deny |more
>>> # sudo iptables-save |more
>>>
>>> If you don't understand the output post it to the list.
>>>

 # apt-get install openssh-server
>

 sudo apt-get install openssh-server
 . . .
 openssh-server is already the newest version.
 openssh-server set to manually installed.


> You run a ssh server and you use a ssh client as a user.
>
> # ssh myusername@targetserverIP
>
>>
>>> # grep Root /etc/ssh/sshd_config <--- 'root' not in file
>>>
>>
> Make sure you used "Root" like
> # sudo grep Root /etc/ssh/sshd_config
>

 there it is. PermitRootLogin yes

>>>
>>> Good! You can ssh to this host with root.
>>>

  If the connection is seen on the host (but has some problem due to
>>> FQN (/etc/hosts) or /etc/hosts.allow files, it will be logged in either:
>>>
>> Hmmm?  Go look in var log and see what this system logs to:
>
> # sudo tail /var/log/syslog
>
>>
>>> bmike1@Michaels-PC:~$ sudo tail /var/log/messages;sudo tail
 /var/log/syslog
 tail: cannot open `/var/log/messages' for reading: No such file or
 directory
 Apr  1 13:09:46 Michaels-PC ddclient[1763]: WARNING:  file
 /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
 Apr  1 13:14:46 Michaels-PC ddclient[1763]: WARNING:  file
 /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
 Apr  1 13:17:01 Michaels-PC CRON[8219]: (root) CMD (   cd / &&
 run-parts --report /etc/cron.hourly)
 Apr  1 13:19:46 Michaels-PC ddclient[1763]: WARNING:  file
 /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
 Apr  1 13:24:46 Michaels-PC ddclient[1763]: WARNING:  file
 /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
 Apr  1 13:29:46 Michaels-PC ddclient[1763]: WARNING:  file
 /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
 Apr  1 13:34:46 Michaels-PC ddclient[1763]: WARNING:  file
 /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
 Apr  1 13:39:46 Michaels-PC ddclient[1763]: WARNING:  file
 /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
 Apr  1 13:44:46 Michaels-PC ddclient[1763]: WARNING:  file
 /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = ''
 Apr  1 13:49:46 Michaels-PC ddclient[1763]: WARNING:  file
 /etc/ddclient.conf, line 8: Invalid V

Re: ssh in network

[Michael Havens]

>A route add command is not persistent past a reboot or network restart.

It seems to have been. I rebooted and still can't ssh from the laptop to
the ubuntu.


> Mike, ONE of your systems is on your Wireless and the other is on the
>> wired?  Sometimes wireless to wired connections take longer than the
>> timeout values for ssh or scp.  Try putting them both on either wireless or
>> wired and see if that's more successful?
>>
>
okay I just connected the laptop to the router via a wire but it still
times out


> Timeouts could be why you get a no route to host.
>>
>> Verify that both boxes have a default route:
>>
>> # sudo netstat -rn
>>
>
Kernel IP routing table 
Destination Gateway Genmask Flags   MSS Window  irtt
Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG0 0  0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0
eth0
192.168.0.0 0.0.0.0 255.255.255.0   U 0 0  0
eth0

Kernel IP routing table 
Destination Gateway Genmask Flags   MSS Window  irtt
Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG0 0  0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0
wlan0
192.168.0.0 0.0.0.0 255.255.255.0   U 0 0  0
eth0
192.168.0.0 0.0.0.0 255.255.255.0   U 0 0  0
wlan0


>> Verify that both boxes have a listening ssh daemon:
>>
>> # sudo netstat -antp | grep 22
>>
> tcp0  0 0.0.0.0:22  0.0.0.0:*
LISTEN  433/sshd

tcp0  0 0.0.0.0:139 0.0.0.0:*
LISTEN  12243/smbd
tcp0  0 0.0.0.0:445 0.0.0.0:*
LISTEN  12243/smbd



>> Make sure you haven't installed DenyHosts or iptables that limits your
>> connections:
>>
>> # locate Deny |more
>> # sudo iptables-save |more
>>
>> sudo locate Deny|more <--no respose
sudo locate iptables-save|more
  /sbin/iptables-save
  /usr/share/man/man8/iptables-save.8.gz


> What - are you running ddclient for?
>> If you can't properly resolve DNS, you will not be able to ssh:
>>
>> I don't even know what ddclient is.
It must have been started automatically by something.


> Please see this link regarding your ddclient errors:
>>
>> http://www.linuxquestions.org/questions/linux-wireless-networking-41/wifi-connects-but-no-network-access-but-wired-works-880213/
>>
>
I went to the link and found nothing regarding the ddclient warning. It was
only mentioned in the output of a  poster tail command.


>>>
  Add this to /etc/hosts.allow:
>>
>>   /etc/hosts.allow looks:
>>
>> ALL : 127.0.0.1
>> sshd : 192.168.0.0/24, 78.207.132.32
>>
>> This example shows an external address you might want to use to
>> connect from outside your internal network (once you open or port forward
>> port 22).
>>
>> This is the hosts.allow file that I added. Does this look right?
>>>
>>> ALL : 127.0.0.1
>>> sshd : 192.168.0.0/24, 192.168.0.1/24, 192.168.0.2/24, 192.168.0.3/24,
>>> 192.168.$ 
>>> #shows address to use from outside of network#, 78.207.132.32
>>>
>>
>> No, you need that 78.207.132.32 on the SAME line with either ALL or
>> sshd: or commented out.
>>
>> And 192.168.$ might cause problems.  Change it to a safe entry:
>> <---that wa snly mores output to say there was more to it. it goes on
>> to x.y.z.10/24> oh. now I see the error of my ways. 192.168 is in the
>> /16 network. silly me!
>> cut here
>> ALL : 127.0.0.1
>> sshd : 192.168.0.0/16, 78.207.132.32 
>> ###end ###
>>
>
What is that 78.207.132.32 anyways? I know you say it is to connect to my
network from elsewhere but how would I do that? would it be ssh
78.207.132.32:@?

>
>> make is already its current version
>>
>> # sudo apt-get update <-it still says it is the newest
>> version
>>
>
>>
>> Also setup your /etc/hosts file on both servers following these
>> suggestions:
>> http://linux.about.com/od/commands/l/blcmdl5_hosts.htm
>>
>> Should look like this (except with all your hostnames on your network -
>> be sure to put the same one on all your linux boxes):
>>
>>  127.0.0.1   localhost
>>  192.168.1.10foo.mydomain.org   foo
>>  192.168.1.13bar.mydomain.org   bar
>>
>> already done (file existed with the proper information.
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Lisa Kachold]

Okay 

Are you colorblind?
Knowing one's limitations is good.  Now you can watch to make sure you
follow each email thread and address each item; I have noticed you miss
things frequently.  Linux troubleshooting is very specific; be careful to
read the full thread, and respond inline.

Let's address each item until we resolve things:

On Sun, Apr 1, 2012 at 5:49 PM, Michael Havens  wrote:

> >A route add command is not persistent past a reboot or network restart.
>
> It seems to have been. I rebooted and still can't ssh from the laptop to
> the ubuntu.


But you couldn't also ssh **BEFORE you did the route add so these are two
different things.

>
>
>> Mike, ONE of your systems is on your Wireless and the other is on the
>>> wired?  Sometimes wireless to wired connections take longer than the
>>> timeout values for ssh or scp.  Try putting them both on either wireless or
>>> wired and see if that's more successful?
>>>
>>
> okay I just connected the laptop to the router via a wire but it still
> times out
>
>
>> Timeouts could be why you get a no route to host.
>>>
>>> Verify that both boxes have a default route:
>>>
>>> # sudo netstat -rn
>>>
>>
> Kernel IP routing table 
> Destination Gateway Genmask Flags   MSS Window  irtt
> Iface
> 0.0.0.0 192.168.0.1 0.0.0.0 UG0 0  0
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0
> eth0
> 192.168.0.0 0.0.0.0 255.255.255.0   U 0 0  0
> eth0
>

Good you have a default route via eth0.

>
> Kernel IP routing table 
> Destination Gateway Genmask Flags   MSS Window  irtt
> Iface
> 0.0.0.0 192.168.0.1 0.0.0.0 UG0 0  0
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0
> wlan0
> 192.168.0.0 0.0.0.0 255.255.255.0   U 0 0  0
> eth0
> 192.168.0.0 0.0.0.0 255.255.255.0   U 0 0  0
> wlan0
>
> You have a default route to the 192.168.0.1 network, but you also have 2
routes to both eth0 and wlan0 (wireless and wired):

Take down your wlan (are you using wicd?)
Try first to use your Gnome or KDE to take down the wireless.

There are some known issues with wlan0 wireless slowness under Ubuntu:
http://www.hitxp.com/articles/software/ubuntu-fix-slow-wireless-internet-connection-speed-upgrading-11-04-natty-narwhal/

Essentially power management turns it down by default, so we just enter:

*# sudo iwconfig wlan0 power off*

So, let's concentrate on wired for now:

Leave it down for now, and just use your wired connection:

So after you turn off the Wireless using your Network settings by right
clicking the network wireless, enter at a terminal:

# sudo /etc/init.d/networking restart


>
>>> Verify that both boxes have a listening ssh daemon:
>>>
>>> # sudo netstat -antp | grep 22
>>>
>> tcp0  0 0.0.0.0:22  0.0.0.0:*
> LISTEN  433/sshd
> 
> tcp0  0 0.0.0.0:139 0.0.0.0:*
> LISTEN  12243/smbd
> tcp0  0 0.0.0.0:445 0.0.0.0:*
> LISTEN  12243/smbd
> 
>
Good you have sshd listening on port 22 on ubuntu.
You do NOT have sshd (daemon) listening on your laptop.

Be sure you have started it if you want to ssh to the laptop from ubuntu:

# sudo /etc/init.d/ssh start

In order to make sure ssh starts at boot in Ubuntu:

# sudo update-rc.d ssh defaults

Reference:  https://help.ubuntu.com/community/UbuntuBootupHowto

>
>>> Make sure you haven't installed DenyHosts or iptables that limits your
>>> connections:
>>>
>>> # locate Deny |more
>>> # sudo iptables-save |more
>>>
>>> sudo locate Deny|more <--no respose
> sudo locate iptables-save|more
>   /sbin/iptables-save
>   /usr/share/man/man8/iptables-save.8.gz
>
enter
# sudo iptables-save
You are looking to see if your iptables is up and configured to firewall
ssh.  Dump the response in here.

>
>
>> What - are you running ddclient for?
>>>  If you can't properly resolve DNS, you will not be able to ssh:
>>>
>>> I don't even know what ddclient is.
> It must have been started automatically by something.
>
ddclient is giving that error.

>
>
>> Please see this link regarding your ddclient errors:
>>>
>>> http://www.linuxquestions.org/questions/linux-wireless-networking-41/wifi-connects-but-no-network-access-but-wired-works-880213/
>>>
>> Oops, sorry wrong link! ddclient is for opendns dynamic dns entries, that
logs into your provider and resets a public ip when needed.  Turn it down
for now:

*# sudo /etc/init.d/ddclient stop*

Here's how to set it up (once you get ssh setup); it requires an opendns
account.
http://ubuntuforums.org/showthread.php?t=1264710

>
> I went to the link and found nothing regarding the ddclient warning. It
> was only mentioned in the output of a  poster tail command.
>
>

>  Add this to /etc/hosts.allow:
>>>
>>>   /etc/hosts.allow looks:
>>>
>>

Re: ssh in network

[Lisa Kachold]

Sorry backwards; it should be

"hosts:  files dns"


On Sun, Apr 1, 2012 at 7:28 PM, Lisa Kachold

> Check your /etc/nsswitch.conf file to be sure it has
>
> "hosts:  dns files"  wrong see above
>
> Reference:  http://www.faqs.org/docs/securing/chap6sec71.html
>
> Then ping each server before trying to reconnect with ssh.
>
> I am pretty sure that this will work now that you have them both on the same 
> network.
>
> Be sure you don't have any iptables running denying your port 22 on both 
> servers!
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>


-- 
(503) 754-4452 Android
(623) 239-3392 Skype
(623) 688-3392 Google Voice
**
it-clowns.com
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

Okay Enrique, Lisa wants me to issue some commands on the host machine. Is
this okay to do?

On Sun, Apr 1, 2012 at 7:28 PM, Lisa Kachold wrote:

> # sudo update-rc.d ssh defaults
>
> enter
> # sudo iptables-save
> You are looking to see if your iptables is up and configured to firewall
> ssh.  Dump the response in here.
>
>>

> Says your system is updated, if it runs?  Correct? < Correct
>>
>
 Check your /etc/nsswitch.conf file to be sure it has

>>> "hosts:  files dns"
>
> Reference:  http://www.faqs.org/docs/securing/chap6sec71.html
>
> Then ping each server before trying to reconnect with ssh.
>
> I am pretty sure that this will work now that you have them both on the same 
> network.
>
> Be sure you don't have any iptables running denying your port 22 on both 
> servers!
>
>
>
-- 
:-)~MIKE~(-:
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

ignore that las t message guys I have a fellow pluger who had me agree
not o modify the laptop without his knowledge because he is helping me with
something that needs the laptop to stay stable.

On Sun, Apr 1, 2012 at 9:50 PM, Michael Havens  wrote:

> Okay Enrique, Lisa wants me to issue some commands on the host machine. Is
> this okay to do?
>
>
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

On Sun, Apr 1, 2012 at 7:28 PM, Lisa Kachold 
wrote:
>Are you colorblind?
^-- only slightly

>respond inline.

^---not sure what you mean.

>Let's address each item until we resolve things:
   On Sun, Apr 1, 2012 at 5:49 PM, Michael Havens  wrote:
>>>A route add command is not persistent past a reboot or network restart.
>>It seems to have been. I rebooted and still can't ssh from the laptop to
the ubuntu.
>But you couldn't also ssh BEFORE you did the route add so these are two
different things.
Yes I could. I could ssh from the laptop to the ubuntu (printserver) until
I issued the command ' sudo ip route add
192.168.1.0/24dev eth0' on the ubuntu on the
advice of my google search. Then I tried to
delete it and add the proper route (192.168.0.1) but that didn't help any.

>Take down your wlan (are you using wicd?)

^---Wireless is now off. I don't know what Mint uses... it doesn't
say.
>>>Verify that both boxes have a listening ssh daemon:

>># sudo netstat -antp | grep 22

>>tcp0  0 0.0.0.0:22  0.0.0.0:*
LISTEN  433/sshd

>>

>>tcp0  0 0.0.0.0:139 0.0.0.0:*
LISTEN  12243/smbd

>>tcp0  0 0.0.0.0:445 0.0.0.0:*
LISTEN  12243/smbd

>>

>Good you have sshd listening on port 22 on ubuntu.

>You do NOT have sshd (daemon) listening on your laptop.

>Be sure you have started it if you want to ssh to the laptop from ubuntu:

># sudo /etc/init.d/ssh start

>In order to make sure ssh starts at boot in Ubuntu:

># sudo update-rc.d ssh defaults <-done

>Reference:  https://help.ubuntu.com/community/UbuntuBootupHowto

>>Make sure you haven't installed DenyHosts or iptables that limits your
connections:

>># locate Deny |more

>># sudo iptables-save |more

>sudo locate Deny|more <--no respose

>sudo locate iptables-save|more

>/sbin/iptables-save

>/usr/share/man/man8/iptables-save.8.gz

>enter

># sudo iptables-save

>You are looking to see if your iptables is up and configured to firewall
ssh.  Dump the response in here.

 bmike1@Michaels-PC:~$ sudo locate iptables-save
/sbin/iptables-save
/usr/share/man/man8/iptables-save.8.gz
bmike1@Michaels-PC:~$

>Oops, sorry wrong link! ddclient is for opendns dynamic dns entries, that
logs into your provider and resets a public ip when needed.  Turn it down
for now:*
# sudo /etc/init.d/ddclient stop*
^-done

>Here's how to set it up (once you get ssh setup); it requires an opendns
account.
>http://ubuntuforums.org/showthread.php?t=1264710

^--if you can remember please remind me
later

 >your system is updated,
if it runs?  Correct?
^ Correct

>Check your /etc/nsswitch.conf file to be sure it has
>"hosts: files dns" Reference:
http://www.faqs.org/docs/securing/chap6sec71.html
I'm not sure what you want here. Here is the file:
# /etc/nsswitch.conf
passwd: compat
group: compat
shadow: compat
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis

>Then ping each server before trying to reconnect with ssh.<--- they ping
both ways.
>I am pretty sure that this will work now that you have them both on the
same network. Be sure you don't
>have any iptables running denying your port 22 on both servers! iptables
-L doesn't have any deny rules in it

I don't see any deny rules in my iptables.
-- 
:-)~MIKE~(-:
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

guess what I just found out openssh-server wasn't installed  on the
laptop. So I installed it and now  netstat has the same line on it that
says port 22

  sudo netstat -antp | grep 22
  tcp0  0 0.0.0.0:22  0.0.0.0:*
LISTEN  433/sshd

However, I still can't ssh to the ubuntu. But I scan ssh from  the ubuntu
to the mint. Yipee!


On Mon, Apr 2, 2012 at 9:26 AM, Michael Havens  wrote:

> On Sun, Apr 1, 2012 at 7:28 PM, Lisa Kachold 
> wrote:
> >Are you colorblind?
> ^-- only slightly
>
> >respond inline.
>
> ^---not sure what you mean.
>
> >Let's address each item until we resolve things:
>On Sun, Apr 1, 2012 at 5:49 PM, Michael Havens 
> wrote:
> >>>A route add command is not persistent past a reboot or network restart.
> >>It seems to have been. I rebooted and still can't ssh from the laptop to
> the ubuntu.
> >But you couldn't also ssh BEFORE you did the route add so these are two
> different things.
> Yes I could. I could ssh from the laptop to the ubuntu (printserver) until
> I issued the command ' sudo ip route add 
> 192.168.1.0/24dev eth0' on the ubuntu on the advice of 
> my google search. Then I tried to
> delete it and add the proper route (192.168.0.1) but that didn't help any.
>
> >Take down your wlan (are you using wicd?)
>
> ^---Wireless is now off. I don't know what Mint uses... it doesn't
> say.
> >>>Verify that both boxes have a listening ssh daemon:
>
> >># sudo netstat -antp | grep 22
>
> >>tcp0  0 0.0.0.0:22  0.0.0.0:*
> LISTEN  433/sshd
>
> >>
>
> >>tcp0  0 0.0.0.0:139 0.0.0.0:*
> LISTEN  12243/smbd
>
> >>tcp0  0 0.0.0.0:445 0.0.0.0:*
> LISTEN  12243/smbd
>
> >>
>
> >Good you have sshd listening on port 22 on ubuntu.
>
> >You do NOT have sshd (daemon) listening on your laptop.
>
> >Be sure you have started it if you want to ssh to the laptop from ubuntu:
>
> ># sudo /etc/init.d/ssh start
>
> >In order to make sure ssh starts at boot in Ubuntu:
>
> ># sudo update-rc.d ssh defaults <-done
>
> >Reference:  https://help.ubuntu.com/community/UbuntuBootupHowto
>
> >>Make sure you haven't installed DenyHosts or iptables that limits your
> connections:
>
> >># locate Deny |more
>
> >># sudo iptables-save |more
>
> >sudo locate Deny|more <--no respose
>
> >sudo locate iptables-save|more
>
> >/sbin/iptables-save
>
> >/usr/share/man/man8/iptables-save.8.gz
>
> >enter
>
> ># sudo iptables-save
>
> >You are looking to see if your iptables is up and configured to firewall
> ssh.  Dump the response in here.
>
>  bmike1@Michaels-PC:~$ sudo locate iptables-save
> /sbin/iptables-save
> /usr/share/man/man8/iptables-save.8.gz
> bmike1@Michaels-PC:~$
>
>
> >Oops, sorry wrong link! ddclient is for opendns dynamic dns entries, that
> logs into your provider and resets a public ip when needed.  Turn it down
> for now:*
> # sudo /etc/init.d/ddclient stop*
>
> ^-done
>
>
> >Here's how to set it up (once you get ssh setup); it requires an opendns
> account.
> >http://ubuntuforums.org/showthread.php?t=1264710
> 
> ^--if you can remember please remind me 
> later
>
>  
> >your system is updated, if it runs?  Correct?
> ^ Correct
>
> >Check your /etc/nsswitch.conf file to be sure it has
> >"hosts: files dns" Reference:
> http://www.faqs.org/docs/securing/chap6sec71.html
> I'm not sure what you want here. Here is the file:
> # /etc/nsswitch.conf
> passwd: compat
> group: compat
> shadow: compat
> hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
> networks: files
> protocols: db files
> services: db files
> ethers: db files
> rpc: db files
> netgroup: nis
>
> >Then ping each server before trying to reconnect with ssh.<--- they ping
> both ways.
>
> >I am pretty sure that this will work now that you have them both on the
> same network. Be sure you don't
> >have any iptables running denying your port 22 on both servers! iptables
> -L doesn't have any deny rules in it
>
> I don't see any deny rules in my iptables.
> --
> :-)~MIKE~(-:
>



-- 
:-)~MIKE~(-:
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Dazed_75]

server needs to be installed on any and all machines you want to ssh TO.
Server is the component/daemon that listens for a request to connect.

On Mon, Apr 2, 2012 at 12:55 PM, Michael Havens  wrote:

> guess what I just found out openssh-server wasn't installed  on the
> laptop. So I installed it and now  netstat has the same line on it that
> says port 22
>
>
>   sudo netstat -antp | grep 22
>   tcp0  0 0.0.0.0:22  0.0.0.0:*
> LISTEN  433/sshd
>
> However, I still can't ssh to the ubuntu. But I scan ssh from  the ubuntu
> to the mint. Yipee!
>
>
>
> On Mon, Apr 2, 2012 at 9:26 AM, Michael Havens  wrote:
>
>> On Sun, Apr 1, 2012 at 7:28 PM, Lisa Kachold 
>> wrote:
>> >Are you colorblind?
>> ^-- only slightly
>>
>> >respond inline.
>>
>> ^---not sure what you mean.
>>
>> >Let's address each item until we resolve things:
>>On Sun, Apr 1, 2012 at 5:49 PM, Michael Havens 
>> wrote:
>> >>>A route add command is not persistent past a reboot or network restart.
>> >>It seems to have been. I rebooted and still can't ssh from the laptop
>> to the ubuntu.
>> >But you couldn't also ssh BEFORE you did the route add so these are two
>> different things.
>> Yes I could. I could ssh from the laptop to the ubuntu (printserver)
>> until I issued the command ' sudo ip route add 
>> 192.168.1.0/24dev eth0' on the ubuntu on the advice 
>> of my google search. Then I tried to
>> delete it and add the proper route (192.168.0.1) but that didn't help any.
>>
>> >Take down your wlan (are you using wicd?)
>>
>> ^---Wireless is now off. I don't know what Mint uses... it
>> doesn't say.
>> >>>Verify that both boxes have a listening ssh daemon:
>>
>> >># sudo netstat -antp | grep 22
>>
>> >>tcp0  0 0.0.0.0:22  0.0.0.0:*
>> LISTEN  433/sshd
>>
>> >>
>>
>> >>tcp0  0 0.0.0.0:139 0.0.0.0:*
>> LISTEN  12243/smbd
>>
>> >>tcp0  0 0.0.0.0:445 0.0.0.0:*
>> LISTEN  12243/smbd
>>
>> >>
>>
>> >Good you have sshd listening on port 22 on ubuntu.
>>
>> >You do NOT have sshd (daemon) listening on your laptop.
>>
>> >Be sure you have started it if you want to ssh to the laptop from ubuntu:
>>
>> ># sudo /etc/init.d/ssh start
>>
>> >In order to make sure ssh starts at boot in Ubuntu:
>>
>> ># sudo update-rc.d ssh defaults <-done
>>
>> >Reference:  https://help.ubuntu.com/community/UbuntuBootupHowto
>>
>> >>Make sure you haven't installed DenyHosts or iptables that limits your
>> connections:
>>
>> >># locate Deny |more
>>
>> >># sudo iptables-save |more
>>
>> >sudo locate Deny|more <--no respose
>>
>> >sudo locate iptables-save|more
>>
>> >/sbin/iptables-save
>>
>> >/usr/share/man/man8/iptables-save.8.gz
>>
>> >enter
>>
>> ># sudo iptables-save
>>
>> >You are looking to see if your iptables is up and configured to firewall
>> ssh.  Dump the response in here.
>>
>>  bmike1@Michaels-PC:~$ sudo locate iptables-save
>> /sbin/iptables-save
>> /usr/share/man/man8/iptables-save.8.gz
>> bmike1@Michaels-PC:~$
>>
>>
>> >Oops, sorry wrong link! ddclient is for opendns dynamic dns entries,
>> that logs into your provider and resets a public ip when needed.  Turn it
>> down for now:*
>> # sudo /etc/init.d/ddclient stop*
>>
>> ^-done
>>
>>
>> >Here's how to set it up (once you get ssh setup); it requires an opendns
>> account.
>> >http://ubuntuforums.org/showthread.php?t=1264710
>> 
>>  ^--if you can remember please remind me 
>> later
>>
>>  
>> >your system is updated, if it runs?  Correct?
>> ^ Correct
>>
>> >Check your /etc/nsswitch.conf file to be sure it has
>> >"hosts: files dns" Reference:
>> http://www.faqs.org/docs/securing/chap6sec71.html
>> I'm not sure what you want here. Here is the file:
>> # /etc/nsswitch.conf
>> passwd: compat
>> group: compat
>> shadow: compat
>> hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
>> networks: files
>> protocols: db files
>> services: db files
>> ethers: db files
>> rpc: db files
>> netgroup: nis
>>
>> >Then ping each server before trying to reconnect with ssh.<--- they ping
>> both ways.
>>
>> >I am pretty sure that this will work now that you have them both on the
>> same network. Be sure you don't
>> >have any iptables running denying your port 22 on both servers! iptables
>> -L doesn't have any deny rules in it
>>
>> I don't see any deny rules in my iptables.
>> --
>> :-)~MIKE~(-:
>>
>
>
>
> --
> :-)~MIKE~(-:
>
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



-- 
Dazed_75 a.k.a. Larry

Plea

Re: ssh in network

[Michael Havens]

server is installed on all of them.

On Mon, Apr 2, 2012 at 2:45 PM, Dazed_75  wrote:

> server needs to be installed on any and all machines you want to ssh TO.
> Server is the component/daemon that listens for a request to connect.
>
> On Mon, Apr 2, 2012 at 12:55 PM, Michael Havens  wrote:
>
>> guess what I just found out openssh-server wasn't installed  on the
>> laptop. So I installed it and now  netstat has the same line on it that
>> says port 22
>>
>>
>>   sudo netstat -antp | grep 22
>>   tcp0  0 0.0.0.0:22  0.0.0.0:*
>> LISTEN  433/sshd
>>
>> However, I still can't ssh to the ubuntu. But I scan ssh from  the ubuntu
>> to the mint. Yipee!
>>
>>
>>
>> On Mon, Apr 2, 2012 at 9:26 AM, Michael Havens  wrote:
>>
>>> On Sun, Apr 1, 2012 at 7:28 PM, Lisa Kachold 
>>> wrote:
>>> >Are you colorblind?
>>> ^-- only slightly
>>>
>>> >respond inline.
>>>
>>> ^---not sure what you mean.
>>>
>>> >Let's address each item until we resolve things:
>>>On Sun, Apr 1, 2012 at 5:49 PM, Michael Havens 
>>> wrote:
>>> >>>A route add command is not persistent past a reboot or network
>>> restart.
>>> >>It seems to have been. I rebooted and still can't ssh from the laptop
>>> to the ubuntu.
>>> >But you couldn't also ssh BEFORE you did the route add so these are two
>>> different things.
>>> Yes I could. I could ssh from the laptop to the ubuntu (printserver)
>>> until I issued the command ' sudo ip route add 
>>> 192.168.1.0/24dev eth0' on the ubuntu on the advice 
>>> of my google search. Then I tried to
>>> delete it and add the proper route (192.168.0.1) but that didn't help any.
>>>
>>> >Take down your wlan (are you using wicd?)
>>>
>>> ^---Wireless is now off. I don't know what Mint uses... it
>>> doesn't say.
>>> >>>Verify that both boxes have a listening ssh daemon:
>>>
>>> >># sudo netstat -antp | grep 22
>>>
>>> >>tcp0  0 0.0.0.0:22  0.0.0.0:*
>>> LISTEN  433/sshd
>>>
>>> >>
>>>
>>> >>tcp0  0 0.0.0.0:139 0.0.0.0:*
>>> LISTEN  12243/smbd
>>>
>>> >>tcp0  0 0.0.0.0:445 0.0.0.0:*
>>> LISTEN  12243/smbd
>>>
>>> >>
>>>
>>> >Good you have sshd listening on port 22 on ubuntu.
>>>
>>> >You do NOT have sshd (daemon) listening on your laptop.
>>>
>>> >Be sure you have started it if you want to ssh to the laptop from
>>> ubuntu:
>>>
>>> ># sudo /etc/init.d/ssh start
>>>
>>> >In order to make sure ssh starts at boot in Ubuntu:
>>>
>>> ># sudo update-rc.d ssh defaults <-done
>>>
>>> >Reference:  https://help.ubuntu.com/community/UbuntuBootupHowto
>>>
>>> >>Make sure you haven't installed DenyHosts or iptables that limits your
>>> connections:
>>>
>>> >># locate Deny |more
>>>
>>> >># sudo iptables-save |more
>>>
>>> >sudo locate Deny|more <--no respose
>>>
>>> >sudo locate iptables-save|more
>>>
>>> >/sbin/iptables-save
>>>
>>> >/usr/share/man/man8/iptables-save.8.gz
>>>
>>> >enter
>>>
>>> ># sudo iptables-save
>>>
>>> >You are looking to see if your iptables is up and configured to
>>> firewall ssh.  Dump the response in here.
>>>
>>>  bmike1@Michaels-PC:~$ sudo locate iptables-save
>>> /sbin/iptables-save
>>> /usr/share/man/man8/iptables-save.8.gz
>>> bmike1@Michaels-PC:~$
>>>
>>>
>>> >Oops, sorry wrong link! ddclient is for opendns dynamic dns entries,
>>> that logs into your provider and resets a public ip when needed.  Turn it
>>> down for now:*
>>> # sudo /etc/init.d/ddclient stop*
>>>
>>> ^-done
>>>
>>>
>>> >Here's how to set it up (once you get ssh setup); it requires an
>>> opendns account.
>>> >http://ubuntuforums.org/showthread.php?t=1264710
>>> 
>>>  ^--if you can remember please remind me 
>>> later
>>>
>>>  
>>> >your system is updated, if it runs?  Correct?
>>> ^ Correct
>>>
>>> >Check your /etc/nsswitch.conf file to be sure it has
>>> >"hosts: files dns" Reference:
>>> http://www.faqs.org/docs/securing/chap6sec71.html
>>> I'm not sure what you want here. Here is the file:
>>> # /etc/nsswitch.conf
>>> passwd: compat
>>> group: compat
>>> shadow: compat
>>> hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
>>> networks: files
>>> protocols: db files
>>> services: db files
>>> ethers: db files
>>> rpc: db files
>>> netgroup: nis
>>>
>>> >Then ping each server before trying to reconnect with ssh.<--- they
>>> ping both ways.
>>>
>>> >I am pretty sure that this will work now that you have them both on the
>>> same network. Be sure you don't
>>> >have any iptables running denying your port 22 on both servers!
>>> iptables -L doesn't have any deny rules in it
>>>
>>> I don't see any deny rules in my iptables.
>>> --
>>> :-)~MIKE~(-:
>>>
>>
>>
>>
>> --
>> :-)~MIKE~(-:
>>
>> ---

Re: ssh in network

[Dazed_75]

and yet your previous message was that you discovered it was not installed
on the laptop.  Hence my reminder that it needs to be on any box you want
to ssh TO.  [?]

On Mon, Apr 2, 2012 at 11:08 PM, Michael Havens  wrote:

> server is installed on all of them.
>
>
> On Mon, Apr 2, 2012 at 2:45 PM, Dazed_75  wrote:
>
>> server needs to be installed on any and all machines you want to ssh TO.
>> Server is the component/daemon that listens for a request to connect.
>>
>> On Mon, Apr 2, 2012 at 12:55 PM, Michael Havens  wrote:
>>
>>> guess what I just found out openssh-server wasn't installed  on the
>>> laptop. So I installed it and now  netstat has the same line on it that
>>> says port 22
>>>
>>>
>>>
>>
-- 
Dazed_75 a.k.a. Larry

Please protect my address like I protect yours. When sending messages to
multiple recipients, always use the BCC: (Blind carbon copy) and not To: or
CC:. Remove all addresses from the message body before sending a Forwarded
message. This can prevent spy programs capturing addresses from the
recipient list and message body.
<<330.gif>>---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: ssh in network

[Michael Havens]

yep. I even checked againafter I got /home working.

  openssh-server is already the newest version.
  openssh-server set to manually installed.
.

On Tue, Apr 3, 2012 at 8:31 AM, Dazed_75  wrote:

> and yet your previous message was that you discovered it was not installed
> on the laptop.  Hence my reminder that it needs to be on any box you want
> to ssh TO.  [?]
>
>
> On Mon, Apr 2, 2012 at 11:08 PM, Michael Havens  wrote:
>
>> server is installed on all of them.
>>
>>
>> On Mon, Apr 2, 2012 at 2:45 PM, Dazed_75  wrote:
>>
>>> server needs to be installed on any and all machines you want to ssh
>>> TO.  Server is the component/daemon that listens for a request to connect.
>>>
>>> On Mon, Apr 2, 2012 at 12:55 PM, Michael Havens wrote:
>>>
 guess what I just found out openssh-server wasn't installed  on the
 laptop. So I installed it and now  netstat has the same line on it that
 says port 22



>>>
> --
> Dazed_75 a.k.a. Larry
>
> Please protect my address like I protect yours. When sending messages to
> multiple recipients, always use the BCC: (Blind carbon copy) and not To: or
> CC:. Remove all addresses from the message body before sending a Forwarded
> message. This can prevent spy programs capturing addresses from the
> recipient list and message body.
>
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



-- 
:-)~MIKE~(-:
<<330.gif>>---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss