[clug-talk] CLUG Test

Gustin Johnson gustin at echostar.ca
Tue Sep 6 11:40:21 PDT 2005

Quoting D Bhardwaj <dbhardwaj at shaw.ca>:

> I wanted to get this to work with native windows 2ks first, maybe 
> play with linux version later.
> Right now I have IIS/FTP configured- I think, and also virtual server 
> ftp enabled on the router. However, when testing, it keeps coming up 
> with 'this document contains no data'...

FTP will only work in passive mode through a NAT firewall.  I am not sure how
well ftp works when the server is NAT'd though, I had problems with this so I
simply switched to sftp.  This was several years ago.  FTP has many 
issues with
NAT connections and I suspect this is where the problem is.  Check to 
make sure
that your ftp client supports passive mode and that it is enabled.  Other than
that all I can really suggest is to use a different protocal.  SSH is useful
regardless of the OS.

Any windows box that I manage has cygwin installed simply because of the
usefullness of bash, ssh, stunnel, rsync, and now unison, which is an awsome
app btw.


> any help is welcome.
> Dharam
> Content-Type: multipart/signed; boundary="nextPart3804862.iTMDejp3FC";
> 	protocol="application/pgp-signature"; micalg=pgp-sha1
> Content-Transfer-Encoding: 7bit
> --nextPart3804862.iTMDejp3FC
> Content-Type: text/plain;
>  charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
> The easiest option I have found is ssh.  With linux it is a no brainer.  Fo=
> r=20
> windows there is a package called cygwin (www.cygwin.com).  This package is=
> a=20
> collection of linux/unix software for windows, including a fully functional=
> =20
> ssh server.  There are lots of nice gui sftp (one form of file transfer ove=
> r=20
> ssh) clients for both *Nix and windows.  Behaves similar to ftp but nothing=
> =20
> is transmitted in the clear.  Other options abound, some of my favorites ar=
> e=20
> rdp (for windows to windows) and rsync.
> The following is a port forwarding for commonly used transfer protocalls
> port  service
> 80  web
> 20  ftp
> 21  ftp=20
> 22  ssh/scp/sftp
> 443  web-ssl
> 873  rsync
> 3389 rdp (remote desktop)
> Depending on the router, ftp may or may not work through a router.  This is=
> a=20
> really short answer to a moderately complicated issue.
> Hope this helps
No trees were harmed in the transmission of this message, however a 
large number
of electrons were seriously inconvenienced.

This message was sent using Echostar Secure Webmail

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: PGP Digital Signature
Url : /pipermail/clug-talk_clug.ca/attachments/20050906/fa89ab4f/attachment.bin

More information about the clug-talk mailing list