[Madlug] "win-2-linux - an easy way"

[Farhan Ahmad]

Brian, like Nate suggested, see if you can SSH locally from the linux
machine (try localhost or 127.0.0.1 instead of the actual IP address).  If
you can, which I am guessing is going to be the case, then you should check
your /etc/hosts.allow and /etc/hosts.deny files.  Depending on your
distribution these could be very restrictive.

I see Nate's confusion.  From the Windows machine, you are using ftp?  You
should be using the winscp GUI or the 'winscp' command.


- Farhan

-----Original Message-----
From: madlug-bounces at madisonlinux.org
[mailto:madlug-bounces at madisonlinux.org] On Behalf Of Nate C-K
Sent: Thursday, March 20, 2008 9:48 AM
To: Brian Hagen; madlug at madisonlinux.org
Subject: Re: [Madlug] "win-2-linux - an easy way"

So, you've established that the SSH server is indeed
running on your Linux box. However, it's still
unreachable from the Windows box. The SSH server looks
to be giving some kind of response, but it's not
actually opening the connection.

I'm not exactly sure where to go from here in
diagnosing the problem. With the new information that
you've provided, though, hopefully someone else on the
list will have some suggestions.

Have you tried opening an SSH connection from the
Linux box to itself (run "ssh localhost" in Linux)?
That wouldn't be useful in itself but it would confirm
that the SSH server is working as you would expect.

I'm a little confused about the text you've pasted for
[1]. Where did that come from? Did you type that at
the shell prompt yourself in Linux? Also, what's the
response from WinSCP when you try to connect?

I would not bother any more with trying to make
Windows FTP work, concentrate on getting this working
with WinSCP instead.

--- Brian Hagen <bdhagen at jvlnet.com> wrote:

> Nate,
> 
>     Thanks for the suggestions. From other's
> responses I have gotten an 
> app called
> "WINSCP" to run on the Windows boxes and it does
> very well.
> 
>     Even so, I tried out a couple of things you
> mentioned, and this is 
> some of the
> results:
>     [1]
> 
> [shell-prompt] sftp 192.168.1.100
> Connecting to 192.168.1.100...
> ssh: connect to host 192.168.1.100 port 22:
> Connection refused
> Couldn't read packet: Connection reset by peer
> 
> ===================================
> 
>     [2]
> 
> ps ax | grep sshd
>  1896 ?        Ss     0:00 /usr/sbin/sshd
>  2512 pts/1    R+     0:00 grep sshd
> 
>     ============================
> 
>     [3]
> 
>     Running ftp from a DOS prompt on the Windows box
> causes a rather lengthy delay followed by an ftp
> prompt
> reading "> ftp connect :10005". Entering "dir"
> causes the response
> "Not connected". I can exit normally using 'bye',
> but am a bit confused
> as to why Windows set up an ftp prompt when in fact
> there was no
> successful ftp connection.
> 
>     Anyway, thanks for the help again. If anyone
> else asks you for
> a similar solution, I can say that the "WINSCP" app
> is excellent for it.
> 
>     (maybe someday I'll get good enough at Linux to
> actually get samba 
> running ...)
> 
> Brian

_______________________________________________
Madlug mailing list  -  Madlug at madisonlinux.org
http://www.madisonlinux.org/mailman/listinfo/madlug