[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

SSH and SWAT open / listening?



After I re-lilo'ed the box with the help of this list I sent a printjob
successfully from a Windows box on the network. Also was and am able to see
the Debian laptop on the network in the Windows nethood. However now after a
reboot (cabling change etc.) I can't print to it. Can't open SWAT from the
browser on the Windows box. Can ping both ways. Was able to authenticate to
SAMBA, but can't SSH. I guess some of the hundreds of upgrades changed some
config files and moved stuff around. I recall a bunch of prompts asking
about keeping scripts or going with the package maintainer's new configs - I
choose to upgrade on all of these. I'm guessing something network/firewall-y
changed. Poked around in all the config and log files I could remember to
look at and that I found. Everything looks good...

What do I run/view to see if SSH and SWAT all open / listening?

netstat -a shows swat listening but I don't see ssh there.

/etc/shh/sshd_config looks okay

/etc/network/interfaces looks fine

can I re-run the swat and sshd setups?

After I get my ssh and swat and samba's hp1200 on lpt1 working my next
challenge is to get the USB working and share a Epson printer off that :-)

Below is a sort of extra background...

TIA,
- Zake


--> From: high_desert [mailto:hidesert@cox.net]
--> Sent: Monday, January 16, 2006 4:02 PM
--> To: Debian Laptop Listserv
--> Subject: RE: Debian repair reload drama howto?
-->
-->
--> My LILO RECOVERY
-->
--> http://www.toms.net/rb/
--> http://www.linuxdocs.org/HOWTOs/LILO-crash-rescue-HOWTO-1.html
-->
--> 1.	downloaded, uncompressed, installed to floppy, tomsrtbt
--> 2.	booted box off tomsrtbt floppy
--> 3.	fdisk -l (to see which device is boot and which is /)
--> 4.	mkdir rootpartition
--> 5.	mount /dev/hda1 /rootpartition
--> 6.	cat /rootpartition/etc/fstab (to see if /boot, /usr, /var,
--> etc. are on
--> other partitions)
--> 7.	mount /dev/hda3 /rootpartition/home/share
--> 8.	vi /etc/fstab
--> a.	added lines:
--> b.	/dev/hda1 /rootpartition ext2 1 1
--> c.	/dev/hda3 /rootpartition/home/share ext2 1 1
--> 9.	cat /etc/fstab (to check vi)
--> 10.	mount -a
--> 11.	chroot /rootpartition /sbin/lilo -q
--> 12.	man chroot
--> 13.	chroot /rootpartition /sbin/lilo
--> a.	Warning: '/proc/partitions' does not exist, disk scan bypassed
--> b.	Added Linux *
--> c.	Skipping vmlinuz.old
--> 14.	exit
--> 15.	hard reboot
-->
--> SUCCESS! Now I don't have to recreate my CUPS, SWAT, fileshare,
--> and SAMBA
--> WiNS and PDCE stuff!
--> Thanks for the pointers, great ideas, and bonus info
--> debian-laptop@lists.debian.org



--> -----Original Message-----
--> From: high_desert [mailto:hidesert@cox.net]
--> Sent: Sunday, January 15, 2006 1:13 PM
--> To: Debian Laptop Listserv
--> Subject: Debian repair reload drama howto?
-->
-->
--> Had a Debian file and print server running for like two years, serving a
--> handful of home Linux, MAC, and Windows clients. December I
--> upgraded the OS
--> and apps all to the latest stable version. The only thing I can
--> think I did
--> 'sub-optimally' was run the entire process via ssh (the server
--> is an older
--> laptop and was shoved in behind some printers on a shelf where
--> it was very
--> uncomfortable to open it and balance it and type.) and one
--> prompt for the
--> kernel or PCMCIA or NIC drivers asked if I wanted to skip restarting
--> something - I said not to restart it, as I wasn't clear if I could
--> reestablish the ssh session to finish the upgrade. There was
--> some message
--> about possibly corrupting something - but no back out options,
--> so. Anyway it
--> now boots to "LI". While I saw references here and there to
--> rescue disks I
--> didn't find any for the current Debian version, and the few
--> homemade ones I
--> found didn't work. Pulled the network card to see if that would
--> bypass the
--> blockage. Though I think I booted off CD before, it won't do it
--> now. Nothing
--> in the BIOS on that either. Physically it can house either a CD or a
--> floppy - not both at once. I tried booting for repair / reinstall via
--> network floppies, but it won't load the NIC floppy. Tried
--> different media
--> and download sites to no avail. Now it's been sitting for a new
--> weeks, dead.
--> Figured I'd revisit this three day weekend. I can recreate the CUPS/SWAT
--> config, user names, etc.. All the files on there are also
--> stored in at least
--> one other place.
-->
--> Now I was thinking of pulling the hard drive and copying
--> whatever onto it
--> and then returning it to the laptop and booting it, to then
--> load a new OS. I
--> have the hard drive out and in an external USB hard drive thing.
-->
--> Question: What do I copy onto it to do this?



Reply to: