Well, I just thought about it, and it occurred to me that since I had port 139 going to port 139 both directions, perhaps the packets were going full circle. Therefore, I changed the incoming tunnel to 138->138 instead, as a test. I didn't get an error about creating the incoming tunnel after that. Therefore, I have three questions:

1) Is SSH smart enough to keep the packets from going back and forth through the tunnels if you have bi-directional, like 139 <--> 139?
2) If no, then why did this make the error messages go away?
3) If yes, then how can I get SMB working? Will the server respond on a different port?

RolledOat thanks for your explanations, forgive my ignorance if it's posible. I just wanted to give it a try. Now I know.
I've been reading two or three times something on the ssh man page . I got it all in front of my eyes but I need some time to understand.
thanks.

No problem. The reason I know it was a lot of head banging, and now that I know enough to be dangerous (I expect SSH can do so much more), I want to share the knowledge.

RO

RolledOat is normal not to see the panel or icons on the vnc desktop?
If I do 'xterm -display :2 ' then I can start all the apps from the command line on the vnc desktop and I see them, but if not then I only see the blue background of my desktop and the pointer is busy.
I tried some options on the client side and always got the same.
Is it always that way?

You probaby don't have the corect X type defined in you ~/user directory. From the user's home directory,
cd .vnc and look at xstartup. Here s mine, unmodified as created
on startup in Redhat 8.0.

more xstartup
#!/bin/sh

# Red Hat Linux VNC session startup script
exec /etc/X11/xinit/xinitrc

If you see .twmrc, you will get a drab grey background and a single xterm. See what, on the server side, is the x session being started.

From http://www.uk.research.att.com/vnc/faq.html#q16

Q16 I connected to my Unix VNC server and I just see a grey desktop with a cursor.
After the vncserver script has started the Xvnc server, it then runs your ~/.vnc/xstartup script. By default this will try to start the twm window manager, but if twm isn't on your path, or if you prefer something else, you can edit xstartup. The log file may also give you clues about what is happening.

RO

RO, you said this a few replies ago... Could you detail how to carry this out a bit better? I don't know how to output sound to a particular socket in Linux. I think I could figure out how to play it from Windows, though.

It would take some development, or probably existing stuff (like make /dev/dsp an alias that pipes to a port, etc). In xmms output plugin, you create your own to send to port instead of the sound driver (I think there are plugins to do this available at xmms.org), then at the client end you grap the port and | /dev/dsp. I haven't done this, per se, however, I have helped people mount to play xmms over a network, tied into their stereo. The real point I was trying to make is that SSH can redirect any port remotely to any port locally, it doesn 't have to be 5901, 5902, etc.

RO

guage73, here is an icecast plugin for XMMS. Redirect the port you want through SSH to the listenting client.

RO

http://star.arm.ac.uk/~spm/software/liveice.html

hi RolledOat
I've been reading the vnc faqs and trying to load the session manager. I could not get the icons or panel.
I've posted that in a new thread called Gnome and VNC. I thought it'd be better to talk about VNC overyonder not here because of the title: SSH ...
Thanks for the info. I got no errors but think is the window manager the source of the problem.

I have installed VNC on my Linux 8.0 box, and I can access it from My Windows XP computer, but I am getting just a text mode screen. Also, how to I have vncserver load automatically on system startup?

I am not sure what you mean by text screen mode? If you look in your ~.vnc directory, what does your xstartup look like. Here is the one that I have on my machine. I installed VNC during the initial install, so it might be different than a post install. If you see twmrc, then I can see why it is less than stellar.

#!/bin/sh

# Red Hat Linux VNC session startup script
exec /etc/X11/xinit/xinitrc

If you want it to start at root on startup, then you can put a call to the vnc server start /etc/rc.d/rc.local . This is the last script run on boot. If you want it for individual users after logging in, then I would try putting it into .bashrc in the specific users home directory. Not really supposed to go in there, but I don't know any other way to start a process for an individual user. Anyone else have idea's?

RO

By text screen mode, I mean that when I successfully connect to the Linux machine, it look as if I am running a terminal, or when the Linux box boots I login in via text only, not the GUI.

By the way, I am trying to acconplish using VNC to connect to the Linux box, and use the KDE interface as if I was sitting there.