-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 06, 2005, at 5:40 PM, Cloyce D. Spradling wrote: > I think the IPv6 _is_ bugging you. Actually, I think that SSH is only > forwarding IPv4 ports for you. Thus the 127.0.0.1 suggestion. But > I've > been wrong before, and it'll probably happen again someday... Very interesting thought. I follow you now, and I'll try things the IPv4 way just to be sure. > Run tcpdump or some other network sniffer on your local connection and > verify that that's really what's happening. And you might also want to > verify that the system to which you're connected via SSH is allowed to > connect to your ISP's POP server. Rather than using the SSH Tunnel Manager GUI to initiate the tunnel, I did things the old fashioned way: ssh -N -p 22 -g -C -c 3des user_id at ssh_host -L 1100/pop-server/110 -L 2500/smtp-server/25 Then I initiated my telnet session to port 1100 in another window (using both localhost and 127.0.0.1 to test the IPv4 theory). Here's what I saw in the SSH command's output: channel 4: open failed: administratively prohibited: open failed It would appear that the SSH host I was using doesn't allow the connection to the remote host to be made. I would think with a different SSH host I'll be OK. Thanks for the ideas. - -- Jeff Winchester jeffw at tampabay.rr.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCK8n6rwFnct83o/4RAhliAKCUdx4IHnkuU79IBUiXpy32hd91KQCgpCBW olD8hgqIqoOZQ43lyoVDDjw= =EksB -----END PGP SIGNATURE-----