Topic: Port Forwarding Syntax

[chris g]

Could somone please post a working port forward command?  I have tried something resembling

ipmasqadm portfw -a -P tcp -L 1.1.1.1 5800 -R 2.2.2.2 5800

I am wishing to use VNC to remotely administer win98 machines.  
Thank you for any help,

Chris G

[TheRealWaldo]

/usr/sbin/ipmasqadm autofw -A -r tcp 5900 5900 -h xx.xx.xx.xx

VNC uses 5900+screen, default for windows is screen = 0.

replace xx.xx.xx.xx with the machines address running the VNC server.

W.

[Dan Brown]

...or just use ssh tunneling, which requires no server-side configuration at all (other than allowing public SSH access).

[TheRealWaldo]

He's using it to administer Windows 98 machines behind e-smith.

W.

[Dan Brown]

...and?

[Dan Brown]

OK, maybe I could have explained a bit.  The type of machine behind the e-smith is irrelevant; you can create a tunnel to it, though the e-smith box, with SSH.  I do it regularly.  With VNC, even.

[TheRealWaldo]

Sorry, missed the 'tunneling' part.  My bad.

Yep, a little more secure as well.

W.

[Chris G]

Thanks for all the great info.  Could you expand on the ssh tunneling through the e-smith box?  I searched around but could not seems to find anything that I can apply to this situation.

[Andrew]

Is there a reason why no-one is suggeting the port forwarding RPM.  I used that to access a W2K box behind the SME server - no probs.

  e-smith-ipportfw-0.1.1-1.noarch.rpm

Cheers,
A.

[Andrew]

Sorry all, I got that RPM wrong - that one didn't work for me and I went back to the tried and true:
 
  dmc-mitel-portforwarding-0.0.1-4.noarch.rpm

Cheers,
A.

[Dan Brown]

Chris, this is really a matter of the documentation of your SSH client.  I use putty 0.52, and I set it up under connection/SSH/Tunnels.  Set the local port to 5900, and the destination to [IP address on your lan]:5900.  Then just point your VNC viewer to localhost.